Puppet automatic operation and maintenance troubleshooting cases

In recent days, , A group maintained by oneself Puppet Agent machine , The following error has been reported ：

[[email protected] src]# puppetd --test --server server.linuxidc.com

notice: Run of Puppet configuration client already in progress; skipping

resolvent ：

Before using the online method , Delete puppet.lock file , The order is as follows ：

rm /var/lib/puppet/state/puppet.lock

The fault is still found ; Later, it was found that this phenomenon was due to /etc/puppet/manifests/site.pp The configuration file is not written correctly , We can just correct it , In fact, it will be like puppet server Inside site.pp and init.pp When there are relatively large changes , It's better to use puppet parser validate Command check first , Examples are as follows ：

[[email protected] manifests]# puppet parser validate site.pp

err: Could not parse for environment production: Syntax error at 'source'; expected '}' at

/etc/puppet/manifests/site.pp:8

err: Try 'puppet help parser validate' for usage

As shown above , It's obvious to mention signs site.pp The first 8 There's a mistake in the line , Prompt us to correct , After correction, troubleshoot , in fact puppet parser validate The command is used for puppet server Grammar is very useful , Examples are as follows ：

puppet parser validate node.pp

node.pp There are grammatical errors in itself , The first 10 Row missing } Number , The error information is as follows ：

err: Could not parse for environment production: Syntax error at end of file; expected '}' at /etc/puppet/manifests/node.pp:10

err: Try 'puppet help parser validate' for usage

Puppet Learning Series ：

Puppet Learning one ： Installation and simple example application http://www.linuxidc.com/Linux/2013-08/88710.htm

Puppet Study two : Simple module configuration and Application http://www.linuxidc.com/Linux/2013-08/88711.htm