Even if the config-changed hook was run when it was not supposed to, it shouldn't have caused any changed if values were not moved to anything different. If it did, then I believe we're having an idempotency problem there.
Still, hooks running when they shouldn't is not what expected. On 09/03/2014 08:03 AM, Andreas Hasenack wrote: > On Wed, Sep 3, 2014 at 10:00 AM, Simon Davy <[email protected] > <mailto:[email protected]>> wrote: > > On 3 September 2014 13:42, Darryl Weaver > <[email protected] <mailto:[email protected]>> > wrote: > > Thanks the IRC logs are pretty helpful. > > We are seeing the same issue here at Sky, > > config-changed hook runs "At random times". > > This is when there are no user changes to the Juju config and no > reboots > > happening. > > It is possible the juju agent restarted, but I don't think so, but > will have > > to collect some evidence first. > > Right, this is what I expect is happening to us, but tracking it is > tricky. We only noticed because our charm has an implementation issue > in that it tries to reuse an authtoken that has a 24hr expiry. > > It might be helpful if some one on juju-core could details if there > are specific circumstances where the juju agent may restart? > > > > Look in /var/log/syslog and /var/log/upstart for evidence of this > restart. Maybe it died, and then upstart will start it again to keep it > running. > > > -- José Antonio Rey -- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
