Re: [Puppet Users] puppet clients
You've got a full stop '.' at the include ntp line.
Cheers,
Den
On 15/06/2011, at 2:30, Craig White wrote:
>
> On Jun 14, 2011, at 8:33 AM, Peter Bukowinski wrote:
>
>> Try quoting your node names, e.g.
>>
>> node 'ubuntu2.ttinet' {
>
> trying to keep this as simple as possible just to get one client to work.
>
> # cat site.pp
> import "templates"
> import "nodes"
>
> # cat nodes.pp
> node 'ubuntu.ttinet' {
>include ntp.
> }
>
> node 'ubuntu2.ttinet' {
>include ntp,
> }
>
> # cat templates.pp
> class baseclass {
> }
>
> node default {
>include baseclass
> }
>
> info: Not using expired node for ubuntu2.ttinet from cache; expired at Tue
> Jun 14 09:23:28 -0700 2011
> info: Caching node for ubuntu2.ttinet
> debug: importing '/etc/puppet/manifests/templates.pp' in environment
> production
> debug: importing '/etc/puppet/manifests/nodes.pp' in environment production
> err: Could not parse for environment production: Syntax error at '.';
> expected '}' at /etc/puppet/manifests/nodes.pp:2 on node ubuntu2.ttinet
> err: Could not parse for environment production: Syntax error at '.';
> expected '}' at /etc/puppet/manifests/nodes.pp:2 on node ubuntu2.ttinet
> ^Cnotice: Caught INT; calling stop
>
> quoting the node names changed nothing
>
> If there is actually some tutorial somewhere that actually shows me what it
> is I need to do to connect in a second computer beyond just getting the
> certificate, please let me know but I have been working on this since last
> Friday. I am not that stupid. I got Chef working in just 2 or 3 hours.
>
> Thanks
>
> Craig
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet clients
Thanks - asked my company to buy it but I might just buy it myself if they
aren't interested.
Sounds like just the ticket for me... progress has been really slow.
Craig
On Jun 14, 2011, at 10:32 AM, Nathan Clemons wrote:
> I will also mention that there are now a few books on Puppet. I'm currently
> reading through Pro Puppet by James Turnbull (who wrote the original Pulling
> Strings with Puppet book), and it's quite good. The original book was a bit
> light on some details, Pro Puppet really dives in and shows how all the
> pieces fit together.
>
> http://www.apress.com/catalogsearch/result/?q=puppet&submit=Go
>
> --
> Nathan Clemons
> http://www.livemocha.com
> The worlds largest online language learning community
>
>
>
> On Tue, Jun 14, 2011 at 10:02 AM, Craig White wrote:
>
> On Jun 14, 2011, at 9:35 AM, R.I.Pienaar wrote:
>
> > The error message says:
> >
> > err: Could not parse for environment production: Syntax error at '.';
> > expected '}' at /etc/puppet/manifests/nodes.pp:2 on node ubuntu2.ttinet
> >
> > and your file in question:
> >
> >> # cat nodes.pp
> >> node 'ubuntu.ttinet' {
> >>include ntp.
> >> }
> >
> >
> > So what's on line 2? a "." at the end, and the error tells you it did not
> > expect the ".".
> >
> > Did you remove the "."?
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> > puppet-users+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> > http://groups.google.com/group/puppet-users?hl=en.
> >
>
>
> the period was indeed a typo but I had to remove the ',' (comma) as well to
> make it work. It finally worked! I guess you always need the commas except
> when they toss you errors.
>
> I'm sure I will have more questions but I will exhaust Google and the
> documentation first. I've been able to install packages now and see somewhat
> where this is leading.
>
> Thanks all
>
> Craig
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
--
Craig White ~~ craig.wh...@ttiltd.com
1.800.869.6908 ~~~ www.ttiassessments.com
Need help communicating between generations at work to achieve your desired
success? Let us help!
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet clients
I will also mention that there are now a few books on Puppet. I'm currently
reading through Pro Puppet by James Turnbull (who wrote the original Pulling
Strings with Puppet book), and it's quite good. The original book was a bit
light on some details, Pro Puppet really dives in and shows how all the
pieces fit together.
http://www.apress.com/catalogsearch/result/?q=puppet&submit=Go
--
Nathan Clemons
http://www.livemocha.com
The worlds largest online language learning community
On Tue, Jun 14, 2011 at 10:02 AM, Craig White wrote:
>
> On Jun 14, 2011, at 9:35 AM, R.I.Pienaar wrote:
>
> > The error message says:
> >
> > err: Could not parse for environment production: Syntax error at '.';
> expected '}' at /etc/puppet/manifests/nodes.pp:2 on node ubuntu2.ttinet
> >
> > and your file in question:
> >
> >> # cat nodes.pp
> >> node 'ubuntu.ttinet' {
> >>include ntp.
> >> }
> >
> >
> > So what's on line 2? a "." at the end, and the error tells you it did not
> expect the ".".
> >
> > Did you remove the "."?
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
> >
>
>
> the period was indeed a typo but I had to remove the ',' (comma) as well to
> make it work. It finally worked! I guess you always need the commas except
> when they toss you errors.
>
> I'm sure I will have more questions but I will exhaust Google and the
> documentation first. I've been able to install packages now and see somewhat
> where this is leading.
>
> Thanks all
>
> Craig
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet clients
On Jun 14, 2011, at 9:35 AM, R.I.Pienaar wrote:
> The error message says:
>
> err: Could not parse for environment production: Syntax error at '.';
> expected '}' at /etc/puppet/manifests/nodes.pp:2 on node ubuntu2.ttinet
>
> and your file in question:
>
>> # cat nodes.pp
>> node 'ubuntu.ttinet' {
>>include ntp.
>> }
>
>
> So what's on line 2? a "." at the end, and the error tells you it did not
> expect the ".".
>
> Did you remove the "."?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
the period was indeed a typo but I had to remove the ',' (comma) as well to
make it work. It finally worked! I guess you always need the commas except when
they toss you errors.
I'm sure I will have more questions but I will exhaust Google and the
documentation first. I've been able to install packages now and see somewhat
where this is leading.
Thanks all
Craig
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet clients
The error message says:
err: Could not parse for environment production: Syntax error at '.'; expected
'}' at /etc/puppet/manifests/nodes.pp:2 on node ubuntu2.ttinet
and your file in question:
> # cat nodes.pp
> node 'ubuntu.ttinet' {
> include ntp.
> }
So what's on line 2? a "." at the end, and the error tells you it did not
expect the ".".
Did you remove the "."?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet clients
Is it just my imagination, or are you putting a full stop/period/comma
after the 'include ntp' lines in nodes.pp?
On Tue, Jun 14, 2011 at 5:30 PM, Craig White wrote:
>
> On Jun 14, 2011, at 8:33 AM, Peter Bukowinski wrote:
>
>> Try quoting your node names, e.g.
>>
>> node 'ubuntu2.ttinet' {
>
> trying to keep this as simple as possible just to get one client to work.
>
> # cat site.pp
> import "templates"
> import "nodes"
>
> # cat nodes.pp
> node 'ubuntu.ttinet' {
> include ntp.
> }
>
> node 'ubuntu2.ttinet' {
> include ntp,
> }
>
> # cat templates.pp
> class baseclass {
> }
>
> node default {
> include baseclass
> }
>
> info: Not using expired node for ubuntu2.ttinet from cache; expired at Tue
> Jun 14 09:23:28 -0700 2011
> info: Caching node for ubuntu2.ttinet
> debug: importing '/etc/puppet/manifests/templates.pp' in environment
> production
> debug: importing '/etc/puppet/manifests/nodes.pp' in environment production
> err: Could not parse for environment production: Syntax error at '.';
> expected '}' at /etc/puppet/manifests/nodes.pp:2 on node ubuntu2.ttinet
> err: Could not parse for environment production: Syntax error at '.';
> expected '}' at /etc/puppet/manifests/nodes.pp:2 on node ubuntu2.ttinet
> ^Cnotice: Caught INT; calling stop
>
> quoting the node names changed nothing
>
> If there is actually some tutorial somewhere that actually shows me what it
> is I need to do to connect in a second computer beyond just getting the
> certificate, please let me know but I have been working on this since last
> Friday. I am not that stupid. I got Chef working in just 2 or 3 hours.
>
> Thanks
>
> Craig
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet clients
On Jun 14, 2011, at 8:33 AM, Peter Bukowinski wrote:
> Try quoting your node names, e.g.
>
> node 'ubuntu2.ttinet' {
trying to keep this as simple as possible just to get one client to work.
# cat site.pp
import "templates"
import "nodes"
# cat nodes.pp
node 'ubuntu.ttinet' {
include ntp.
}
node 'ubuntu2.ttinet' {
include ntp,
}
# cat templates.pp
class baseclass {
}
node default {
include baseclass
}
info: Not using expired node for ubuntu2.ttinet from cache; expired at Tue Jun
14 09:23:28 -0700 2011
info: Caching node for ubuntu2.ttinet
debug: importing '/etc/puppet/manifests/templates.pp' in environment production
debug: importing '/etc/puppet/manifests/nodes.pp' in environment production
err: Could not parse for environment production: Syntax error at '.'; expected
'}' at /etc/puppet/manifests/nodes.pp:2 on node ubuntu2.ttinet
err: Could not parse for environment production: Syntax error at '.'; expected
'}' at /etc/puppet/manifests/nodes.pp:2 on node ubuntu2.ttinet
^Cnotice: Caught INT; calling stop
quoting the node names changed nothing
If there is actually some tutorial somewhere that actually shows me what it is
I need to do to connect in a second computer beyond just getting the
certificate, please let me know but I have been working on this since last
Friday. I am not that stupid. I got Chef working in just 2 or 3 hours.
Thanks
Craig
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet clients
Try quoting your node names, e.g.
node 'ubuntu2.ttinet' {
--
Peter M. Bukowinski
Systems Engineer
Janelia Farm Research Campus, HHMI
On Tuesday, June 14, 2011 at 11:26 AM, Craig White wrote:
>
> On Jun 13, 2011, at 5:02 PM, Nan Liu wrote:
>
> > On Mon, Jun 13, 2011 at 4:19 PM, Craig White > (mailto:craig.wh...@ttiltd.com)> wrote:
> > >
> > > On Jun 13, 2011, at 3:10 PM, Nan Liu wrote:
> > >
> > > > On Mon, Jun 13, 2011 at 1:57 PM, Craig White > > > (mailto:craig.wh...@ttiltd.com)> wrote:
> > > > > I've gone over the documentation several times now and I can't figure
> > > > > out how to 'apply' a manifest to a client.
> > > > >
> > > > > The client does have a signed certificate but the only thing in the
> > > > > /etc/puppet folder on the client is an ssl directory.\
> > > >
> > > > If you are running puppet against a remote puppet master, you should
> > > > run puppet agent rather than puppet apply. puppet apply is only when
> > > > you have a copy of the manifest locally.
> > > >
> > > > > I have a manifest that works fine on the puppet 'master'
> > > > >
> > > > > I have added the client into /etc/puppet/manifests/nodes.pp
> >
> > Didn't notice this earlier, the default manifests file puppet master
> > compiles is /etc/puppet/manifests/site.pp, you need to import nodes.pp
> > in site.pp, or simply write the node information in site.pp manifest.
> >
> > > if the puppet agent command would have worked for me, I wouldn't have
> > > asked. My puppet master has manifests/nodes.pp which lists the client
> > > fqdn (matches the cert too) and it includes 'ntp' which is found in
> > > modules/ntp/manifests/ntp.pp (see my original e-mail) but it doesn't seem
> > > to happen no matter how many times I invoke the 'puppet agent command
> > > from the client system). The client system did however get a certificate
> > > from the server.
> >
> > If the suggestion above doesn't work, try to include a default node in
> > site.pp:
> > node default {
> > include ntp
> > }
> >
> > Beyond that, start running puppet master with the option
> > --no-daemonize --verbose (add --debug as necessary) and send any
> > applicable output. It should autoload classes in modules and compile
> > catalog for the taget node successfully (see sample below):
>
> still no joy ;-(
>
> # cat site.pp
> import "templates"
> import "nodes"
>
> # cat nodes.pp
> node ubuntu.ttinet {
> include ntp
> }
>
> node ubuntu2.ttinet {
> include ntp
> package { "apt":
> ensure => installed,
> }
> file{"/etc/apt/sources.list":
> ensure => present,
> owner => root,
> require => Package["apt"]
> }
> }
>
> # cat templates.pp
> class baseclass {
> }
>
> node default {
> include baseclass
> }
>
> root@ubuntu:/etc/puppet/manifests# puppet master --no-daemonize --verbose
> --debug
> debug: Failed to load library 'shadow' for feature 'libshadow'
> debug: Puppet::Type::User::ProviderUser_role_add: file roledel does not exist
> debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does
> not exist
> debug: Puppet::Type::User::ProviderLdap: true value when expecting false
> debug: Puppet::Type::User::ProviderPw: file pw does not exist
> debug: Failed to load library 'selinux' for feature 'selinux'
> debug: Puppet::Type::File::ProviderMicrosoft_windows: feature
> microsoft_windows is missing
> debug: Failed to load library 'ldap' for feature 'ldap'
> debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
> debug: /File[/var/lib/puppet/server_data]: Autorequiring File[/var/lib/puppet]
> debug: /File[/var/lib/puppet/log]: Autorequiring File[/var/lib/puppet]
> debug: /File[/etc/puppet/ssl/public_keys/ubuntu.ttinet.pem]: Autorequiring
> File[/etc/puppet/ssl/public_keys]
> debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
> debug: /File[/etc/puppet/auth.conf]: Autorequiring File[/etc/puppet]
> debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
> debug: /File[/var/lib/puppet/yaml]: Autorequiring File[/var/lib/puppet]
> debug: /File[/etc/puppet/manifests]: Autorequiring File[/etc/puppet]
> debug: /File[/etc/puppet/ssl/private_keys/ubuntu.ttinet.pem]: Autorequiring
> File[/etc/puppet/ssl/private_keys]
> debug: /File[/etc/puppet/ssl/certs/ubuntu.ttinet.pem]: Autorequiring
> File[/etc/puppet/ssl/certs]
> debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet]
> debug: /File[/var/lib/puppet/reports]: Autorequiring File[/var/lib/puppet]
> debug: /File[/var/lib/puppet/bucket]: Autorequiring File[/var/lib/puppet]
> debug: /File[/etc/puppet/manifests/site.pp]: Autorequiring
> File[/etc/puppet/manifests]
> debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/puppet/ssl]
> debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
> debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
> debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
> debug: /File[/var/lib/puppe
Re: [Puppet Users] puppet clients
On Jun 13, 2011, at 5:02 PM, Nan Liu wrote:
> On Mon, Jun 13, 2011 at 4:19 PM, Craig White wrote:
>>
>> On Jun 13, 2011, at 3:10 PM, Nan Liu wrote:
>>
>>> On Mon, Jun 13, 2011 at 1:57 PM, Craig White wrote:
I've gone over the documentation several times now and I can't figure out
how to 'apply' a manifest to a client.
The client does have a signed certificate but the only thing in the
/etc/puppet folder on the client is an ssl directory.\
>>>
>>> If you are running puppet against a remote puppet master, you should
>>> run puppet agent rather than puppet apply. puppet apply is only when
>>> you have a copy of the manifest locally.
>>>
I have a manifest that works fine on the puppet 'master'
I have added the client into /etc/puppet/manifests/nodes.pp
>
> Didn't notice this earlier, the default manifests file puppet master
> compiles is /etc/puppet/manifests/site.pp, you need to import nodes.pp
> in site.pp, or simply write the node information in site.pp manifest.
>
>> if the puppet agent command would have worked for me, I wouldn't have asked.
>> My puppet master has manifests/nodes.pp which lists the client fqdn (matches
>> the cert too) and it includes 'ntp' which is found in
>> modules/ntp/manifests/ntp.pp (see my original e-mail) but it doesn't seem to
>> happen no matter how many times I invoke the 'puppet agent command from the
>> client system). The client system did however get a certificate from the
>> server.
>
> If the suggestion above doesn't work, try to include a default node in
> site.pp:
> node default {
> include ntp
> }
>
> Beyond that, start running puppet master with the option
> --no-daemonize --verbose (add --debug as necessary) and send any
> applicable output. It should autoload classes in modules and compile
> catalog for the taget node successfully (see sample below):
still no joy ;-(
# cat site.pp
import "templates"
import "nodes"
# cat nodes.pp
node ubuntu.ttinet {
include ntp
}
node ubuntu2.ttinet {
include ntp
package { "apt":
ensure => installed,
}
file{"/etc/apt/sources.list":
ensure => present,
owner => root,
require => Package["apt"]
}
}
# cat templates.pp
class baseclass {
}
node default {
include baseclass
}
root@ubuntu:/etc/puppet/manifests# puppet master --no-daemonize --verbose
--debug
debug: Failed to load library 'shadow' for feature 'libshadow'
debug: Puppet::Type::User::ProviderUser_role_add: file roledel does not exist
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does
not exist
debug: Puppet::Type::User::ProviderLdap: true value when expecting false
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Puppet::Type::File::ProviderMicrosoft_windows: feature microsoft_windows
is missing
debug: Failed to load library 'ldap' for feature 'ldap'
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/server_data]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/log]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/public_keys/ubuntu.ttinet.pem]: Autorequiring
File[/etc/puppet/ssl/public_keys]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/auth.conf]: Autorequiring File[/etc/puppet]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/yaml]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/manifests]: Autorequiring File[/etc/puppet]
debug: /File[/etc/puppet/ssl/private_keys/ubuntu.ttinet.pem]: Autorequiring
File[/etc/puppet/ssl/private_keys]
debug: /File[/etc/puppet/ssl/certs/ubuntu.ttinet.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/reports]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/bucket]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/manifests/site.pp]: Autorequiring
File[/etc/puppet/manifests]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/log/masterhttp.log]: Autorequiring
File[/var/lib/puppet/log]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/var/lib/puppet/rrd]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/p
Re: [Puppet Users] puppet clients
On Mon, Jun 13, 2011 at 4:19 PM, Craig White wrote:
>
> On Jun 13, 2011, at 3:10 PM, Nan Liu wrote:
>
>> On Mon, Jun 13, 2011 at 1:57 PM, Craig White wrote:
>>> I've gone over the documentation several times now and I can't figure out
>>> how to 'apply' a manifest to a client.
>>>
>>> The client does have a signed certificate but the only thing in the
>>> /etc/puppet folder on the client is an ssl directory.\
>>
>> If you are running puppet against a remote puppet master, you should
>> run puppet agent rather than puppet apply. puppet apply is only when
>> you have a copy of the manifest locally.
>>
>>> I have a manifest that works fine on the puppet 'master'
>>>
>>> I have added the client into /etc/puppet/manifests/nodes.pp
Didn't notice this earlier, the default manifests file puppet master
compiles is /etc/puppet/manifests/site.pp, you need to import nodes.pp
in site.pp, or simply write the node information in site.pp manifest.
> if the puppet agent command would have worked for me, I wouldn't have asked.
> My puppet master has manifests/nodes.pp which lists the client fqdn (matches
> the cert too) and it includes 'ntp' which is found in
> modules/ntp/manifests/ntp.pp (see my original e-mail) but it doesn't seem to
> happen no matter how many times I invoke the 'puppet agent command from the
> client system). The client system did however get a certificate from the
> server.
If the suggestion above doesn't work, try to include a default node in site.pp:
node default {
include ntp
}
Beyond that, start running puppet master with the option
--no-daemonize --verbose (add --debug as necessary) and send any
applicable output. It should autoload classes in modules and compile
catalog for the taget node successfully (see sample below):
debug: importing
'/etc/puppetlabs/puppet/modules/motd/manifests/init.pp' in environment
production
debug: Automatically imported motd from motd into production
debug: Scope(Class[Motd]): Retrieving template motd/motd.erb
debug: template[/etc/puppetlabs/puppet/modules/motd/templates/motd.erb]:
Bound template variables for
/etc/puppetlabs/puppet/modules/motd/templates/motd.erb in 0.00 seconds
debug: template[/etc/puppetlabs/puppet/modules/motd/templates/motd.erb]:
Interpolated template
/etc/puppetlabs/puppet/modules/motd/templates/motd.erb in 0.00 seconds
notice: Compiled catalog for node in environment production in 0.03 seconds
Thanks,
Nan
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet clients
On Jun 13, 2011, at 3:10 PM, Nan Liu wrote: > On Mon, Jun 13, 2011 at 1:57 PM, Craig White wrote: >> I've gone over the documentation several times now and I can't figure out >> how to 'apply' a manifest to a client. >> >> The client does have a signed certificate but the only thing in the >> /etc/puppet folder on the client is an ssl directory.\ > > If you are running puppet against a remote puppet master, you should > run puppet agent rather than puppet apply. puppet apply is only when > you have a copy of the manifest locally. > >> I have a manifest that works fine on the puppet 'master' >> >> I have added the client into /etc/puppet/manifests/nodes.pp >> >> I see a page on the website that talks about 'puppet device' but i don't >> seem to have that option: > > You are looking at 2.7 documentation and using an older client, run > puppet --version and review the documentation from the appropriate > version. > > Thanks, > > Nan > > - if the puppet agent command would have worked for me, I wouldn't have asked. My puppet master has manifests/nodes.pp which lists the client fqdn (matches the cert too) and it includes 'ntp' which is found in modules/ntp/manifests/ntp.pp (see my original e-mail) but it doesn't seem to happen no matter how many times I invoke the 'puppet agent command from the client system). The client system did however get a certificate from the server. I guess no one will accuse you of not having up-to-date documentation and yes, I am using the 2.6.8 puppet gem on both systems (ubuntu dist was much older). Thanks Craig -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet clients
I can run that command no problem but it never does 'apply' the manifest that
is stated in $PUPPET_ROOT/manifests/nodes.pp which is a fairly simple ntp
install. (see below for nodes.pp & modules/manifests/ntp.pp)
# puppet agent --test --verbose --noop --server ubuntu.ttinet
info: Caching catalog for ubuntu2.ttinet
info: Applying configuration version '1308006207'
notice: Finished catalog run in 0.01 seconds
root@ubuntu2:/etc/puppet# puppet agent --test --verbose --server ubuntu.ttinet
info: Caching catalog for ubuntu2.ttinet
info: Applying configuration version '1308006283'
notice: Finished catalog run in 0.01 seconds
I am quite certain that the problem is me but the documentation never quite
gets to the point where a manifest is actually applied to a remote client and I
have struggled with this for more than 4 hours now.
Thanks
Craig
On Jun 13, 2011, at 3:12 PM, Denmat wrote:
> From a cursory glance at the new doco, I couldn't find it either (forgive me
> if it is there though). I could find a 'puppet apply' but not 'agent' in the
> 'getting started' sections. There is of course the puppet commands page but
> that does provide examples. Anyhoo..
>
> puppet agent --test --verbose --noop --server
>
> That will do a 'dry-run' on the client. To update the client remove the
> --noop. See the man pages for the --test switch, it bundles a few other
> options (but doesn't really 'test' anything -- it will apply your manifest on
> your client).
>
> Cheers,
> Den
>
> On 14/06/2011, at 6:57, Craig White wrote:
>
>> I've gone over the documentation several times now and I can't figure out
>> how to 'apply' a manifest to a client.
>>
>> The client does have a signed certificate but the only thing in the
>> /etc/puppet folder on the client is an ssl directory.
>>
>> I have a manifest that works fine on the puppet 'master'
>>
>> I have added the client into /etc/puppet/manifests/nodes.pp
>>
>> I see a page on the website that talks about 'puppet device' but i don't
>> seem to have that option:
>>
>> # puppet
>> Usage: puppet command
>> Available commands are: agent, apply, cert, describe, doc, filebucket,
>> inspect, kick, master, queue, resource
>>
>> How do I get the puppet client to run the manifest?
>>
>> # cat /etc/puppet/manifests/nodes.pp
>> node ubuntu.ttinet {
>> include ntp
>> }
>>
>> node ubuntu2.ttinet {
>> include ntp
>> }
>>
>> # cat /etc/puppet/modules/ntp/manifests/ntp.pp
>> # ntp.pp
>>
>> class ntp {
>> case $operatingsystem {
>> centos, redhat: {
>> $service_name = 'ntpd'
>> $conf_file = 'ntp.conf.el'
>> }
>> debian, ubuntu: {
>> $service_name = 'ntp'
>> $conf_file = 'ntp.conf.debian'
>> }
>> }
>>
>> package { 'ntp':
>> ensure => installed,
>> }
>>
>> service { 'ntp':
>> name => $service_name,
>> ensure => running,
>> enable => true,
>> subscribe => File['ntp.conf'],
>> }
>>
>> file { 'ntp.conf':
>> path => '/etc/ntp.conf',
>> ensure => file,
>> require => Package['ntp'],
>> source => "puppet:///files/ntp/${conf_file}",
>> }
>> }
>>
>> # class {'ntp': }
>>
>> --
>> Craig White ~~ craig.wh...@ttiltd.com
>> 1.800.869.6908 ~~~ www.ttiassessments.com
>>
>> Need help communicating between generations at work to achieve your desired
>> success? Let us help!
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To post to this group, send email to puppet-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> puppet-users+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
--
Craig White ~~ craig.wh...@ttiltd.com
1.800.869.6908 ~~~ www.ttiassessments.com
Need help communicating between generations at work to achieve your desired
success? Let us help!
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet clients
>From a cursory glance at the new doco, I couldn't find it either (forgive me
>if it is there though). I could find a 'puppet apply' but not 'agent' in the
>'getting started' sections. There is of course the puppet commands page but
>that does provide examples. Anyhoo..
puppet agent --test --verbose --noop --server
That will do a 'dry-run' on the client. To update the client remove the --noop.
See the man pages for the --test switch, it bundles a few other options (but
doesn't really 'test' anything -- it will apply your manifest on your client).
Cheers,
Den
On 14/06/2011, at 6:57, Craig White wrote:
> I've gone over the documentation several times now and I can't figure out how
> to 'apply' a manifest to a client.
>
> The client does have a signed certificate but the only thing in the
> /etc/puppet folder on the client is an ssl directory.
>
> I have a manifest that works fine on the puppet 'master'
>
> I have added the client into /etc/puppet/manifests/nodes.pp
>
> I see a page on the website that talks about 'puppet device' but i don't seem
> to have that option:
>
> # puppet
> Usage: puppet command
> Available commands are: agent, apply, cert, describe, doc, filebucket,
> inspect, kick, master, queue, resource
>
> How do I get the puppet client to run the manifest?
>
> # cat /etc/puppet/manifests/nodes.pp
> node ubuntu.ttinet {
> include ntp
> }
>
> node ubuntu2.ttinet {
> include ntp
> }
>
> # cat /etc/puppet/modules/ntp/manifests/ntp.pp
> # ntp.pp
>
> class ntp {
> case $operatingsystem {
>centos, redhat: {
> $service_name = 'ntpd'
> $conf_file = 'ntp.conf.el'
>}
>debian, ubuntu: {
> $service_name = 'ntp'
> $conf_file = 'ntp.conf.debian'
>}
> }
>
> package { 'ntp':
>ensure => installed,
> }
>
> service { 'ntp':
>name => $service_name,
>ensure => running,
>enable => true,
>subscribe => File['ntp.conf'],
> }
>
> file { 'ntp.conf':
>path => '/etc/ntp.conf',
>ensure => file,
>require => Package['ntp'],
>source => "puppet:///files/ntp/${conf_file}",
> }
> }
>
> # class {'ntp': }
>
> --
> Craig White ~~ craig.wh...@ttiltd.com
> 1.800.869.6908 ~~~ www.ttiassessments.com
>
> Need help communicating between generations at work to achieve your desired
> success? Let us help!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet clients
On Mon, Jun 13, 2011 at 1:57 PM, Craig White wrote: > I've gone over the documentation several times now and I can't figure out how > to 'apply' a manifest to a client. > > The client does have a signed certificate but the only thing in the > /etc/puppet folder on the client is an ssl directory.\ If you are running puppet against a remote puppet master, you should run puppet agent rather than puppet apply. puppet apply is only when you have a copy of the manifest locally. > I have a manifest that works fine on the puppet 'master' > > I have added the client into /etc/puppet/manifests/nodes.pp > > I see a page on the website that talks about 'puppet device' but i don't seem > to have that option: You are looking at 2.7 documentation and using an older client, run puppet --version and review the documentation from the appropriate version. Thanks, Nan -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] puppet clients
I've gone over the documentation several times now and I can't figure out how
to 'apply' a manifest to a client.
The client does have a signed certificate but the only thing in the /etc/puppet
folder on the client is an ssl directory.
I have a manifest that works fine on the puppet 'master'
I have added the client into /etc/puppet/manifests/nodes.pp
I see a page on the website that talks about 'puppet device' but i don't seem
to have that option:
# puppet
Usage: puppet command
Available commands are: agent, apply, cert, describe, doc, filebucket, inspect,
kick, master, queue, resource
How do I get the puppet client to run the manifest?
# cat /etc/puppet/manifests/nodes.pp
node ubuntu.ttinet {
include ntp
}
node ubuntu2.ttinet {
include ntp
}
# cat /etc/puppet/modules/ntp/manifests/ntp.pp
# ntp.pp
class ntp {
case $operatingsystem {
centos, redhat: {
$service_name = 'ntpd'
$conf_file = 'ntp.conf.el'
}
debian, ubuntu: {
$service_name = 'ntp'
$conf_file = 'ntp.conf.debian'
}
}
package { 'ntp':
ensure => installed,
}
service { 'ntp':
name => $service_name,
ensure => running,
enable => true,
subscribe => File['ntp.conf'],
}
file { 'ntp.conf':
path => '/etc/ntp.conf',
ensure => file,
require => Package['ntp'],
source => "puppet:///files/ntp/${conf_file}",
}
}
# class {'ntp': }
--
Craig White ~~ craig.wh...@ttiltd.com
1.800.869.6908 ~~~ www.ttiassessments.com
Need help communicating between generations at work to achieve your desired
success? Let us help!
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Clients requesting classes
Stig Sandbeck Mathisen writes:
> ,
> | node *.desktops.example.org {
> | case $server_role {
> | /:desktop:/ { include my::desktop::class }
> | /:mission_critical:/ { include corp::absolutely::vital:class }
> | /:whohooo:/ { include rubber::ducky }
> | }
> | }
> `
This should perhaps use a series of if tests instead, or you'll only get
the classes from the first match.
--
Stig Sandbeck Mathisen
Oooo, shiny!
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Clients requesting classes
On Tue, Jan 11, 2011 at 09:05:43AM -0800, Nigel Kersten wrote: > > I disagree that this approach is fundamentally wrong, but it's not > always appropriate. I'll concede I'm being a little over-emphatic, but the OP's situation didn't read to me as if it had anything to justify that approach. And I did tell him how to do it, anyway. Can't say fairer than that. -- Bruce I must admit that the existence of Disneyland (which I know is real) proves that we are not living in Judea in AD 50. -- Philip K. Dick -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Clients requesting classes
Exinferis writes:
> Is that somehow possible with puppet?
Role-based configuration is possible with puppet. The selection of
available roles will have to be preconfigured, but it is possible.
Instead of selecting on the registered host name you select on the role
it reports to have.
You will need to make a "role" fact, and you need to use a selector
within the default node definition, or with a matching wildcard node
definition:
,[ server_role ]
| # role.rb
| Facter.add("role") do
| setcode do
| begin
| file = File.new("/etc/role", "r")
| line = file.gets
| line.chomp
| rescue => err
| "undefined"
| end
| end
| end
`
This allows for config like:
,
| node default {
| case $server_role {
| 'desktop': {
| include my::desktop::class
| include my::other::things
| }
| }
| }
`
You should also be able to list multiple roles. If you specify roles in
your file like this:
:one:two:three:desktop:whohooo:mission_critical:
you can match on:
,
| node *.desktops.example.org {
| case $server_role {
| /:desktop:/ { include my::desktop::class }
| /:mission_critical:/ { include corp::absolutely::vital:class }
| /:whohooo:/ { include rubber::ducky }
| }
| }
`
...of course, I don't see that anyone would have absolutely vital stuff
on a desktop, but you get the picture. :)
Note: This will not remove things installed by other roles, if you
switch roles. Your classes will have to fix that. If one role installs
"apache HTTPD", your other roles would have to know about this, and
remove it. This is not specific to role-based configuration.
--
Stig Sandbeck Mathisen
(fnord)
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Clients requesting classes
On Tue, Jan 11, 2011 at 8:57 AM, Bruce Richardson wrote: > On Tue, Jan 11, 2011 at 02:09:27AM -0800, Exinferis wrote: >> But what we really want to achieve is not to register every node in >> our master configuration (hostnames can totally vary so no wildcard >> matching), but to give the nodes the possibility to request a specific >> class or to report themselves as a specific type of server. > > I think that approach is fundamentally wrong. I do not believe that a > puppetmaster should allow clients to decide which host they are, or > which configuration they receive. The whole point about central > configuration is that you manage it centrally; if your clients can > decide, how do you determine what is going on without inspecting every > host directly? I disagree that this approach is fundamentally wrong, but it's not always appropriate. Imagine you're managing thousands of desktops. Rather than giving them administrative rights, why not allow them to tweak the configuration that they receive and allow them to tune certain parameters that specify the kind of configuration that will be applied? You can use reports to see what the actual state of your fleet is, you don't need to manage a central database for minor differences. > If most of your hosts are going to have the same configuration, but some > will differ, why not use the default node for the common configuration > and make different entries for other hosts when you need to? What do > you gain by having to go and make configuration changes on each host, > rather than just changing configurations in one place? I can tell you > one thing you lose; you lose the ability to rebuild from scratch a node > that died (with, say, an unrecoverable hard disk). > > If you really want to do this thing, you could achieve it by modifying > your default node configuration so that the extra configuration options > are contained in classes which are only included if certain facts are > true. You then only create those facts on the hosts you want to have > those configurations. I urge you not to do this. And on the flip side, I say that this is a perfectly valid way of managing certain deployments. > > -- > Bruce > > Hierophant: someone who remembers, when you are on the way down, > everything you did to them on the way up. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Clients requesting classes
On Tue, Jan 11, 2011 at 02:09:27AM -0800, Exinferis wrote: > But what we really want to achieve is not to register every node in > our master configuration (hostnames can totally vary so no wildcard > matching), but to give the nodes the possibility to request a specific > class or to report themselves as a specific type of server. I think that approach is fundamentally wrong. I do not believe that a puppetmaster should allow clients to decide which host they are, or which configuration they receive. The whole point about central configuration is that you manage it centrally; if your clients can decide, how do you determine what is going on without inspecting every host directly? If most of your hosts are going to have the same configuration, but some will differ, why not use the default node for the common configuration and make different entries for other hosts when you need to? What do you gain by having to go and make configuration changes on each host, rather than just changing configurations in one place? I can tell you one thing you lose; you lose the ability to rebuild from scratch a node that died (with, say, an unrecoverable hard disk). If you really want to do this thing, you could achieve it by modifying your default node configuration so that the extra configuration options are contained in classes which are only included if certain facts are true. You then only create those facts on the hosts you want to have those configurations. I urge you not to do this. -- Bruce Hierophant: someone who remembers, when you are on the way down, everything you did to them on the way up. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet Clients requesting classes
We are currently using puppet with a node based configuration on the
master, so we have a structure similar to that:
node xyz {
/* do something here */
}
node default {
/* do something here */
}
in the included files and classes we have our setup procedures ongoing
and everything is working as intended.
But what we really want to achieve is not to register every node in
our master configuration (hostnames can totally vary so no wildcard
matching), but to give the nodes the possibility to request a specific
class or to report themselves as a specific type of server.
So when I start my new server for the first time I put the information
about the server type into the puppet config file or anywhere else
where suitable. The I start my puppet client, sign its certificate on
the master and the puppet client reports to the server being a server
of type "xyz" (or whatever type I configured it to be) and it pulls
the configuration of the master.
Is that somehow possible with puppet?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet clients dieing
Nat wrote: has anyone else experienced puppet clients that die when the network goes down for an extended period of time ? That happens here as well. We even have a script to monitor last_run times of all puppet clients to detect this. It seems that a puppet master not answering for some time can cause that, but this doesn't seem to be the only cause. k -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] puppet clients dieing
Hi list, has anyone else experienced puppet clients that die when the network goes down for an extended period of time ? OS rhel 5 puppet clients / master 0.25.1 clients are left in a state where ~# service puppet status puppetd dead but pid file exists ~# service puppet restart Stopping puppet: [FAILED] Starting puppet: [ OK ] Obviously the stopping part fails because the puppet process has dies previously. Regards, Nathan -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet clients stop talking to the puppetmaster server
Here's the scenario, We have roughly 700 OpenSolaris hosts running puppet-0.24.4, facter-1.3.8, and ruby 1.8.6. Puppetmaster server is running OpenSolaris, puppet-0.24.5, facter-1.5.2, and ruby 1.8.6. I'm running 4 puppetmasterd instances with mongrel fronted by apache in load balancer mode. It seems that quite a few (roughly a third) of the boxes stop checking in to the puppetmaster server, or just stop downloading/creating the new classes file from the puppetmaster server. If I ssh into each box, stop puppetd and restart it, it downloads the new /var/puppet/ state/classes.txt and everything is good again. All of the clients are identical, same OS versions, same patch levels, same puppet.conf, etc. I am not seeing anything in the logs on the puppetmaster server (either in the apache logs or puppetmasterd logs) that is indicative of an issue. Any thoughts? Thanks, Josh --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com 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 -~--~~~~--~~--~--~---
