Fwd: How to make juju aware of IP address changes?
darryl.weaver at canonical.com
Mon Dec 9 22:57:09 UTC 2013
>> We *could* consider disabling logging when the disk is tending
>> towards full, but I suspect that could make a bad problem worse
>> by losing any possibility of seeing what has actually been going
>I think that if we manage the first several items here (backing off and
>log rotate), we shouldn't get into this problem. I'm -1 on attempting
>to disable logging on low disk
IMHO it would be prudent to also handle the case when the disk is full as
this could happen due to other processes for whatever reason filling up the
If it does, then it should be handled gracefully and raise an error, rather
than making the problem worse or assuming it will never happen.
EMEA Cloud Sales Engineer,
Desk: +44 (0)207 630 2400 ext 507516
Mobile: +44 (0)7720088049
GPG FPR: EA3F 3805 9347 87EC 9CBB 8C1E DADC 82C9 B16B 0403
On 8 December 2013 21:47, Tim Penhey <tim.penhey at canonical.com> wrote:
> On 07/12/13 05:04, roger peppe wrote:
> > I think that there are a few things that could help here,
> > most important points first:
> > - We should limit agent restarting in some way (exponential backoff or
> > retry limits or both)
> I think this is a key one. If the agent is repeatedly failing, we
> should back-off and ask for help :-)
> > - We should rotate log files and compress old ones.
> Yes. We have a pending proposal from Nate that adds in log rotation.
> > - We should have kind of policy for expiring and deleting old log files.
> The standard log rotation kind of handles this. You say things like:
> * Max of 100 MB
> * gzip all but the first
> * keep 5 backups
> This is fairly normal.
> > - We should have some way of garbage collecting the transaction log.
> This is our internal issue, but yes, we should consider this as a fairly
> high priority item. As I understand it, our transaction log is
> primarily for notifications and transactional-ability. What else do we
> use it for? How long is the log useful for?
> I know that full logs are useful for diagnosis, but probably not
> worthwhile keeping forever.
> Is it feasible for us to be able to export the transaction log to an
> external file, and then truncate the internal log?
> > We *could* consider disabling logging when the disk is tending
> > towards full, but I suspect that could make a bad problem worse
> > by losing any possibility of seeing what has actually been going
> > on.
> I think that if we manage the first several items here (backing off and
> log rotate), we shouldn't get into this problem. I'm -1 on attempting
> to disable logging on low disk.
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Juju