On May 20, 2010, at 5:56 AM, Patrick wrote:
> We would like to roll out several clients with puppet. I want to make sure
> that the clients can run a long time (~years) without requiring me to login.
> Reason: It would be hard to get access to this machines as they are far away
> from my site. The clients would also not always be connected to the network.
There are a options that decide if puppet will run using cached information if
it can't see the server. You should probably explicitly decide if you want
this or not. I think it's on by default.
> How would a default puppet.conf look like?
> I would like to use this config:
>
> ### /etc/puppet/puppet.conf
> [main]
> logdir=/var/log/puppet
> vardir=/var/lib/puppet
> ssldir=/var/lib/puppet/ssl
> rundir=/var/run/puppet
>
> [puppetd]
> server=myserver.example.com
> report = true
> # Make sure future facts/providers/types are synced
> pluginsync = true
> ###################
>
> For example the "pluginsync" switch should be switched on before rolling out
> the clients to make sure future types are synced to my clients. Are there
> other options which are important for my intention?
Actually, if you don't use plugins now, making sure it's turned on isn't really
important because you can use puppet itself to turn it on. Still better to do
it now though because it's easier to troubleshoot when you can sit at the
computer. Also, if you do turn it on using puppet, it'll take an extra run to
finish since the plugins won't be synced till the next run. Here's an example
of how to turn it off, and turn reporting on.
augeas {"puppet_conf":
context => "/files/etc/puppet/puppet.conf/",
changes => [ "set main/pluginsync false", "set puppetd/report true" ],
require => Package["libaugeas-ruby"],
}
If you want to see a list of options, try running puppet --genconfig and/or
puppetd --genconfig.
> 2nd question:
> I also noticed that error messages on the client are not appearing in my
> server log e.g
>
> "err: Could not load downloaded file
> /var/lib/puppet/lib/puppet/provider/shells/parsed.rb: undefined method
> `provide' for nil:NilClass"
>
> Is there a way to force the client to send error messages back to the server?
I think you can do this by telling puppet to use a remote syslog if all else
fails.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
