Jnimo
2011-Sep-30 10:47 UTC
[Puppet Users] Unable to run puppetrun properly, puppet --test works fine
Hello. I have been using puppet for the last 10 months and everything is working fine, however, at the moment we have a cron job running in the clients that pull the configuration from the servers, we want to change this and be able to do a puppetrun from the server to the clients (just in case we need to rollback something) puppetd in the client side is working fine (I think), I have configure the pupet.conf, auth.conf namespaceauth.conf (with only the ip of the puppet server), and the service start and run fine. [root@ns6 cron.d]# netstat -pna | grep -i ruby tcp 0 0 0.0.0.0:8139 0.0.0.0:* LISTEN 3223/ruby port is open and in LISTEN mode, however, when I try to deploy from the master: [root@puppet classes]# puppetrun --host ns6.xxx.xxx Triggering ns6.xxxx.xxx ns6.xxx.xxx finished with exit code 0 Finished it comes with a exit code 0, nothing in the logs on master or client, tcpdump shows that there is some traffic between them, but the changes are not commited to the client, if I run with --test on the client, I see that the changes are made without a problem. iptables are disable, both servers are connected in the 10.10.131.0/24 network, same switch, no vlan, no fw, I''m running out of Ideas, anyone can give me a hand? thanks -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Christopher Wood
2011-Sep-30 17:54 UTC
Re: [Puppet Users] Unable to run puppetrun properly, puppet --test works fine
On Fri, Sep 30, 2011 at 03:47:56AM -0700, Jnimo wrote:> Hello. > > I have been using puppet for the last 10 months and everything is > working fine, however, at the moment we have a cron job running in the > clients that pull the configuration from the servers, we want to > change this and be able to do a puppetrun from the server to the > clients (just in case we need to rollback something) > > puppetd in the client side is working fine (I think), I have configure > the pupet.conf, auth.conf namespaceauth.conf (with only the ip of the > puppet server), and the service start and run fine. > > [root@ns6 cron.d]# netstat -pna | grep -i ruby > tcp 0 0 0.0.0.0:8139 > 0.0.0.0:* LISTEN 3223/ruby > > port is open and in LISTEN mode, however, when I try to deploy from > the master: > > [root@puppet classes]# puppetrun --host ns6.xxx.xxx > Triggering ns6.xxxx.xxx > ns6.xxx.xxx finished with exit code 0 > Finished > > it comes with a exit code 0, nothing in the logs on master or client, > tcpdump shows that there is some traffic between them, but the changes > are not commited to the client, if I run with --test on the client, I > see that the changes are made without a problem. > > iptables are disable, both servers are connected in the 10.10.131.0/24 > network, same switch, no vlan, no fw, I''m running out of Ideas, anyone > can give me a hand?If you see "puppet-agent[21734]: triggered run" or something similar on the agent, then your agent might be waiting for the "splay" period to elapse before it actually does the run. I got around needing splay by puppetizing/templating puppet.conf on the agents, and setting the runinterval to a semi-random number (every 3600 seconds + rand(3600) seconds). You might otherwise want to run the agent from the console in the foreground with debug on. There might be some issue that doesn''t come up with the normal level of log messages.> thanks > > -- > 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+unsubscribe@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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Jimmy Nimo
2011-Sep-30 18:21 UTC
Re: [Puppet Users] Unable to run puppetrun properly, puppet --test works fine
Thank I will try that on monday. Good weekend everybody On Fri, Sep 30, 2011 at 6:54 PM, Christopher Wood <christopher_wood@pobox.com> wrote:> On Fri, Sep 30, 2011 at 03:47:56AM -0700, Jnimo wrote: >> Hello. >> >> I have been using puppet for the last 10 months and everything is >> working fine, however, at the moment we have a cron job running in the >> clients that pull the configuration from the servers, we want to >> change this and be able to do a puppetrun from the server to the >> clients (just in case we need to rollback something) >> >> puppetd in the client side is working fine (I think), I have configure >> the pupet.conf, auth.conf namespaceauth.conf (with only the ip of the >> puppet server), and the service start and run fine. >> >> [root@ns6 cron.d]# netstat -pna | grep -i ruby >> tcp 0 0 0.0.0.0:8139 >> 0.0.0.0:* LISTEN 3223/ruby >> >> port is open and in LISTEN mode, however, when I try to deploy from >> the master: >> >> [root@puppet classes]# puppetrun --host ns6.xxx.xxx >> Triggering ns6.xxxx.xxx >> ns6.xxx.xxx finished with exit code 0 >> Finished >> >> it comes with a exit code 0, nothing in the logs on master or client, >> tcpdump shows that there is some traffic between them, but the changes >> are not commited to the client, if I run with --test on the client, I >> see that the changes are made without a problem. >> >> iptables are disable, both servers are connected in the 10.10.131.0/24 >> network, same switch, no vlan, no fw, I''m running out of Ideas, anyone >> can give me a hand? > > If you see "puppet-agent[21734]: triggered run" or something similar on the agent, then your agent might be waiting for the "splay" period to elapse before it actually does the run. > > I got around needing splay by puppetizing/templating puppet.conf on the agents, and setting the runinterval to a semi-random number (every 3600 seconds + rand(3600) seconds). > > You might otherwise want to run the agent from the console in the foreground with debug on. There might be some issue that doesn''t come up with the normal level of log messages. > >> thanks >> >> -- >> 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+unsubscribe@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+unsubscribe@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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.