Comment 4 for bug 1519473

Hi,

I think I'm running into the same bug with juju version 1.24.0 on a GCE environment, probably as a fallout from a charm upgrade.

The machine 0 jujud, when started, quickly (ballpark figure : 15 min) uses all the memory of the server, and then does nothing. All the clients command then start failing (eg "juju status").

machine-0.log is at https://pastebin.canonical.com/148046/ (cut from the start of the agent)
juju status (which works if you run it briefly after restarting machine-0 jujud) is at https://pastebin.canonical.com/148047/ - as you can see, each unit is in a "hook failed" status.

And finally a pmap of the machine-0 jujud process : https://pastebin.canonical.com/148033/

If you need more data, we should be able to keep the environment for a few days, but we'll need to redeploy after that.

Thanks !