[MAAS] Deploy a charm into machine 0 = log loop

[David Fischer]

Dear JuJu Team,

The last two days I deployed some charms into a small cluster of 4 servers.

In order to avoid using a 24 threads for only managing instances with JuJu I decided to deploy some services (my own GlusterFS charm) into machine 0.

I checked the debug-log and what I've seen is that the log is appended with old messages again and again.

I opened a terminal into machine 0 to check the logs and what I've seen confirmed my first idea : The file -> /var/log/juju/all-machines.log is growing fast (as fast as my HDD can manage).

I decided to remove this file and create a nice trip, destination unknown, for the log messages : ln -s /dev/null all-machines.log.

I am using the latest juju-core from a raring desktop to deploy charms into precise servers with MAAS. I also upgraded MAAS with proposed repository in order to avoid bug #1204507.

Hope this helps to make this project even better for the good of the community !

Kind Regards,

David

[John A Meinel (jameinel)]

this sounds like a duplicate of bug #1211147. You mention "using the latest" can you run "juju version" to check what version you are actually running?

You can get the newest stable series from "ppa:juju/stable" though that doesn't have this fix (I believe). You would want "ppa:juju/devel" to test if this bug is fixed for you (it *should* be fixed in 1.13.2 but we've had some trouble reproducing and isolating the bug).

[John A Meinel (jameinel)]

If you have this happening right now, getting a copy of all your files in /etc/rsyslog* (.d etc) would probably be helpful.
I also wonder if logrotate might be triggering something. (We say to sync all files except X, but the logrotate causes X to no longer match the ignored list, or something odd like that.)

[David Fischer (david-fischer-ch)]

Ok, thank you for your quick answer.

I will not upgrade juju-core as my demo must work for the IBC 2013 ... And it is no more room for "new" bugs.
However I am happy that this bug is already fixed.

You are free to change the status of the ticket to duplicate.

Thank you.