Sorry folks, I'm replying to myself but here is what I found out. For some reason running with shorter --runinterval gives me a warning on the second and further update sessions with puppetmasterd:
"Other end went away; restarting connection and retrying." But puppetmasterd is running for sure.... Here is a sample verbose session: ========================================================================== pacha...@stage ~ $ sudo puppetd --no-daemonize --server master --verbose --runinterval 30 Password: notice: Starting Puppet client version 0.24.4 info: Retrieving plugins info: Caching catalog at /var/lib/puppet/localconfig.yaml notice: Starting catalog run ... * Some changes are applied here* ... notice: Finished catalog run in 2.15 seconds * Next interval * info: Retrieving plugins info: Configuration is up to date notice: Starting catalog run notice: Finished catalog run in 5.88 seconds info: Retrieving plugins warning: Other end went away; restarting connection and retrying info: Configuration is up to date notice: Starting catalog run notice: Finished catalog run in 1.08 seconds ========================================================================== If I cancel this command witch Ctrl-C and start it again puppetd retrieves the new changes from the master. I definitely don't understand something very obvious related to the proper invocation of the puppetd daemon, please guide into the right direction. -- Best regards, Pavel --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
