Puppet stops responding on the client. We issue the following:
$ sudo service puppet restart
|
Stopping puppet agent: [ OK ]
|
Starting puppet agent: [ OK ]
|
$ sudo puppet agent --test
|
Notice: Run of Puppet configuration client already in progress; skipping (/var/lib/puppet/state/agent_catalog_run.lock exists)
|
$ date
|
Thu May 8 10:14:41 EST 2014
|
$ ps aux |grep pupp
|
root 12838 0.0 4.7 200780 96872 ? S May07 0:21 puppet agent: applying configuration
|
$ sudo strace -p 12838
|
Process 12838 attached - interrupt to quit
|
select(5, [4], NULL, NULL, NULL
|
Wed May 07 06:25:30 +1000 2014 Puppet (notice): Finished catalog run in 207.42 seconds
|
Wed May 07 06:55:12 +1000 2014 Puppet (notice): Finished catalog run in 204.99 seconds
|
Thu May 08 03:29:01 +1000 2014 Puppet (notice): Caught HUP; calling restart
|
This happens on for remote sites predominantly with 'flakey' but not troublesome connectivity. Happening enough to warrant an issue being raised. It may have been happening in prior releases but we have changed the way we monitor puppet agents now so it could be that we are just seeing it now - we updated from 2.6.16 to 3.4.3.
I will try to get more detail but generally I can't reproduce and have to wait for it to happen.
Bug
Normal
