Comment 5 for bug 2051179

We have done some debugging on this today with Harry. Looking at the SOS report from one of the affected nodes we can see the Grafana charm is banging around with SIGKILL on the juju debug-log command. Running the command manually with strace we can also see that the program doesn't even hit its main function before being killed.

The kernel logs look very empty and we currently suspect that if we can get the full version of these logs it will contain the reason why this is happening.

There does not appear to be any juju code paths that could be causing this at the moment.

The problem also goes away when scheduling the pod to another node. At the moment our thinking this is node specific.