[Systems] 18 Systems-logs moderator request(s) waiting
cjlhomeaddress at gmail.com
Mon Oct 10 10:57:51 EDT 2011
I'm subbed on systems, no need to cc.
I'm not really the backend guy to do this, I'd be more comfortable with
Gonzalo Rafael or Aleksey (or really any systems people) doing the VM
reboot. I'd say pick a time, drop a quick note to the L10n list warning of
downtime and do it. AFAIK we've got a cron job that kicks off between
midnight and 1:00 a.m. (Boston time), so other than not mangling that, any
On Mon, Oct 10, 2011 at 5:53 AM, Sascha Silbe <silbe at sugarlabs.org> wrote:
> 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 --------------
An HTML attachment was scrubbed...
More information about the Systems