The pids appear to be constant since I last reported them. Your theory about the machine being out of disk is correct.
Indeed the log files are 1.4 and 1.6 GB for all-machines and machine-0.log. I'll try xz'ing them and then sending them along to you. Is it okay if I e-mail them directly to you and anyone else who is interested (please mail me personally) assuming they compress down to ~megabytes? On 29 November 2013 11:26, roger peppe <[email protected]> wrote: > On 29 November 2013 10:26, Peter Waller <[email protected]> wrote: > > On 28 November 2013 17:44, Peter Waller <[email protected]> wrote: > >> > >> I'm still having the problem of it spinning, every few seconds all of > the > >> machines are still spewing into the logs, despite my attempt at asking > it to > >> "upgrade" to a different version. > > > > > > Last night I left it spinning absent any better ideas. It didn't seem to > be > > causing any obvious harm that I could find. > > > > This morning `juju status` doesn't work and nor does juju debug-log. > > > > On the bootstrap node the following is running for `ps aux | grep juju` > > > > root 23973 0.0 0.0 4440 624 ? Ss Aug29 0:00 /bin/sh > -e > > -c /var/lib/juju/tools/machine-0/jujud machine --log-file > > /var/log/juju/machine-0.log --data-dir '/var/lib/juju' --machine-id 0 > > --debug >> /var/log/juju/machine-0.log 2>&1 /bin/sh > > root 23974 0.2 1.4 309440 24340 ? Sl Aug29 346:48 > > /var/lib/juju/tools/machine-0/jujud machine --log-file > > /var/log/juju/machine-0.log --data-dir /var/lib/juju --machine-id 0 > --debug > > > > $ juju debug-log | grep --line-buffered -v jsoncodec > > ERROR no reachable servers > > > > $ juju status > > <hangs seemingly indefinitely> > > > > Any advice or documentation someone can point me at to get this system > back > > into a working state? > > If you do the above ps, then wait 5 seconds and try again, have the > process ids changed? > If so, that means it's probably continually bouncing for some reason. > > It would be useful to see the logs, in particular > /var/log/juju/machine-0.log. > Firstly how big are they? It is possible that the machine is out of disk > space > and that's caused the mongo database storage to stop working. > You could try deleting the log files (perhaps save them first for > later diagnosis). > > Secondly, perhaps you could paste somewhere the last few thousand lines > of the logs, that might give us more of an idea of what's happening > currently. > > Please feel free to ping us on IRC (#juju-dev or #juju on freenode.net; my > nickname is rogpeppe there) and we could help more directly. > > cheers, > rog. >
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
