Ask Your Question

puppet agent run starts but doesn't stop

asked 2014-07-14 09:02:57 -0500

mmlumba gravatar image

updated 2014-07-14 09:15:04 -0500


I have a Windows 2008 R2 node running Puppet Enterprise (3.2.3). It has been in the unresponsive category on my Puppet dashboard for almost a month. When I look at the event viewer on Windows I notice that Puppet starts agent runs but does not give a notice saying the runs have been finished (i.e. "finished catalog in x seconds"). When I run puppet agent -t, the node always responds that a Puppet run is still in progress.

Any thoughts?

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2014-07-14 19:48:41 -0500

Stefan gravatar image

well there are two options: The agent was killed and left a lockfile behind or the agent is still running. So please check the process list for a running process and the existance/contents of the lockfile (run puppet agent --configprint agent_catalog_run_lockfile to find out where this is)

I don't know about windows but on linux there are different resources that can possibly hang when applying a catalog like an exec resource that triggers a script that is waiting for input or a mount resource when the underlying mount command hangs because of an unresponsive nfs server.

edit flag offensive delete link more


Thanks for your answer! It was very helpful. I deleted the lockfile, killed the rubyw.exe process, and ran puppet agent -t again to start another puppet run (which ended successfully).

mmlumba gravatar imagemmlumba ( 2014-07-15 08:23:32 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools


Asked: 2014-07-14 09:02:57 -0500

Seen: 1,046 times

Last updated: Jul 14 '14