agent suddenly disabled

[Thomas]

Disclaimer: I'm a newbie... I've only been using Puppet for a few
days.

My agent has been running fine for a few days but now when I perform:
puppet agent --no-daemonize --verbose --onetime

I get the following message:
notice: Skipping run of Puppet configuration client; administratively
disabled; use 'puppet Puppet configuration client --enabled' to re-
enable.

I've tried running that command both on the agent and the node and it
complains:
Error: Unknown Puppet subcommand 'Puppet'

Sorry for the dumb question and please let me know if there is a more
appropriate forum for this type of question.

Thanks! Thomas Kenny

[Patrick Carlisle]

This is a bug in the error message (http://projects.puppetlabs.com/issues/13299). The correct command is 'puppet agent --enable'.

[Thomas]

That worked, thanks!

[Eric Lake]

I am wondering what would cause a puppet client to get into a state like this. I had a test vm do the same thing to me today.

[Tony Maro]

On Tuesday, May 1, 2012 12:00:19 PM UTC-4, Eric Lake wrote:

I am wondering what would cause a puppet client to get into a state like this. I had a test vm do the same thing to me today.

Since nobody else responded first let me say thanks for posting the correct syntax - I googled the error and ended up here.  Second, mine was triggered by an application filling my available hard drive space with a log file.  I removed the 960 GB log file (from 3 weeks of running, lol) and rebooted and puppet refused to run anymore until doing this.

So I'm assuming this is some sort of safety net to keep it from screwing up your system entirely if something goes horribly wrong, like being unable to write temp files, etc.