[Systems] 18 Systems-logs moderator request(s) waiting
sascha-ml-reply-to-2011-4 at silbe.org
Mon Oct 10 05:53:14 EDT 2011
Excerpts from systems-logs-bounces's message of 2011-10-09 14:00:19 +0200:
> From: root at treehouse.sugarlabs.org on Sat Sep 24 05:35:22 2011
> Subject: Cron <root at treehouse> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
> Cause: Message body is too big: 4237310 bytes with a limit of 1024 KB
The reason for the backup process on treehouse failing was that the same
file system (root file system of the pootle VM) was mounted on both the
pootle VM _and_ treehouse. This caused file system corruption, leading
to a directory loop (hard linked).
I've now unmounted /mnt/pootle-root on treehouse (the host machine),
created /forcefsck on pootle (the VM) and discarded the pending
treehouse log messages in the systems-logs queue (we really don't want
to deliver > 75MB of logs to all subscribers).
We should reboot the Pootle VM ASAP to get the file system checked. This
might take a while, so we need to coordinate with the localization folks
(-> CC'ed Chris, Gonzalo & Rafael).
Please tell me when a good time for a reboot would be (on any day other
than Wednesday or Thursday). I'd like to attend the reboot in case the
file system corruption causes it not to come up again. Alternatively
Bernie could do it.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 665 bytes
Desc: not available
More information about the Systems