On Monday, October 20, 2014 8:46:42 AM UTC-5, [email protected] wrote:
>
> The issue that i don't fully understand is why the puppet run seems to
> finish:
>
> Oct 8 19:58:07 node2 puppet-agent[18912]:
> (/Stage[main]/Task_node2__package___45_58_54_52_2dlsbwrapper4/Package[EXTR-lsbwrapper4]/ensure)
>
> ensure changed '1.0.0-1' to '2.0.0-1'
> Oct 8 19:58:12 node2 puppet-agent[18912]:
> (/Stage[main]/Task_node2__package___45_58_54_52_2dlsbwrapper8/Package[EXTR-lsbwrapper8]/ensure)
>
> ensure changed '1.0.0-1' to '0:3.0.0-1'
> Oct 8 19:58:15 node2 puppet-agent[18912]:
> (/File[/etc/mcollective/facts.yaml]/content) content changed
> '{md5}cf91bdba62cbaa5149af42b81febbbf4' to
> '{md5}994da216388be7020bade56907c701ed'
> Oct 8 19:58:19 node2 puppet-agent[18912]: (/File[maincf]/seltype) seltype
> changed 'etc_runtime_t' to 'etc_t'
> Oct 8 19:58:22 node2 puppet-agent[18912]: Finished catalog run in 47.16
> seconds
>
> Yet after that the puppet seems to continue where it left off:
>
> Oct 8 19:58:57 node2 puppet-agent[20580]:
> (/Stage[main]/Task_node2__package___45_58_54_52_2dlsbwrapper28/Package[EXTR-lsbwrapper28]/ensure)
>
> ensure changed '1.0.0-1' to '0:2.0.0-1'
>
[...]
Note that the PID of the puppet-agent process changes, and that there is a
35-second gap in the log. I conclude that the agent was restarted in the
gap, but the relevant log output was edited out, up to and including that
describing a new catalog request being issued. This is what I was
referring to earlier when I complained about preferring "log output that
has not had relevant information edited out." Likely the restart was
mediated by Puppet itself, as I described above.
> Oct 8 19:58:58 node2 puppet-agent[20580]:
> (/File[/etc/mcollective/facts.yaml]/content) content changed
> '{md5}994da216388be7020bade56907c701ed' to
> '{md5}d8c1cb23e367c830bc34a564d49e8353'
> Oct 8 19:59:03 node2 puppet-agent[20580]: (/File[maincf]/seltype) seltype
> changed 'etc_runtime_t' to 'etc_t'
> Oct 8 19:59:05 node2 puppet-agent[20580]: Finished catalog run in 16.30
> seconds
>
> Not sure about this but my understanding is that a catalog run should be
> sequential if there is a global lock in place?
>
>
What about that makes you think there were concurrent catalog runs? I see
a bunch of log entries from one process, followed by a bunch of log entries
from a different process. How is that anything but sequential?
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/568634e4-5086-4c4d-8659-a8fbe46409b4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
