Hi, One of my machines has started to refuse reading the catalog from the server. The log shows the following: Mar 16 15:36:42 wmembf10 puppetd[7411]: Starting Puppet client version 0.25.5 Mar 16 15:36:46 wmembf10 puppetd[7411]: Could not retrieve catalog from remote server: Mar 16 15:36:46 wmembf10 puppetd[7411]: Using cached catalog Mar 16 15:36:46 wmembf10 puppetd[7411]: Could not retrieve catalog; skipping run Server and Client are both version 0.25.5. An identical System (wmembf09) has no such problems and updates the configuration just fine. Since I don''t get any indication what the problem could be I''m at a loss what to do about this. Any ideas? Regards, Dennis -- 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.
Dennis Jacobfeuerborn
2011-Mar-16 15:27 UTC
[Puppet Users] Re: Client no longer reads catalog
Wow, apparently running a "tcpdump -nn port 8140" un-wedges puppet and brings things back to normal. Problem is that I have no clue how or why running a tcpdump could possibly matter here even though it apparently does. Does anyone have an idea what might be going on here? Regards, Dennis -- 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.
On Mar 16, 10:27 am, Dennis Jacobfeuerborn <djacobfeuerb...@gmail.com> wrote:> Wow, apparently running a "tcpdump -nn port 8140" un-wedges puppet and > brings things back to normal. Problem is that I have no clue how or why > running a tcpdump could possibly matter here even though it apparently does. > Does anyone have an idea what might be going on here?Hmm. Port 8140 is the one that puppetd will listen on when you set listen=true in puppet.conf. <speculation type="wild">It is conceivable, though I would certainly account it a bug, that unexpected packets queued up on port 8140 might confuse puppetd. In that case, it might make sense that draining the queue via tcpdump restores service.</speculation> If you''re just using puppet in ordinary client/server mode then you shouldn''t need any of that; in that case make sure it''s switched off (the default), and that your local firewall is blocking the port (both TCP and UDP). -- 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.
Cody Robertson
2011-Mar-21 20:16 UTC
Re: [Puppet Users] Re: Client no longer reads catalog
On 03/21/2011 03:10 PM, jcbollinger wrote:> > On Mar 16, 10:27 am, Dennis Jacobfeuerborn<djacobfeuerb...@gmail.com> > wrote: >> Wow, apparently running a "tcpdump -nn port 8140" un-wedges puppet and >> brings things back to normal. Problem is that I have no clue how or why >> running a tcpdump could possibly matter here even though it apparently does. >> Does anyone have an idea what might be going on here? > Hmm. Port 8140 is the one that puppetd will listen on when you set > listen=true in puppet.conf.<speculation type="wild">It is > conceivable, though I would certainly account it a bug, that > unexpected packets queued up on port 8140 might confuse puppetd. In > that case, it might make sense that draining the queue via tcpdump > restores service.</speculation> > > If you''re just using puppet in ordinary client/server mode then you > shouldn''t need any of that; in that case make sure it''s switched off > (the default), and that your local firewall is blocking the port (both > TCP and UDP). >Doesn''t puppetd listen on 8139? -Cody Robertson -- 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.
On Mar 16, 11:27 am, Dennis Jacobfeuerborn <djacobfeuerb...@gmail.com> wrote:> Wow, apparently running a "tcpdump -nn port 8140" un-wedges puppet and > brings things back to normal. Problem is that I have no clue how or why > running a tcpdump could possibly matter here even though it apparently does. > Does anyone have an idea what might be going on here? > > Regards, > DennisIs puppet connecting to the master directly via IP or did you specify a hostname? If the latter what if you explicitly use the IP? puppetd --verbose --onetime --no-daemonize --server 1.2.3.4 -- 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.
On 03/16/2011 03:48 PM, Dennis Jacobfeuerborn wrote:> Hi, > One of my machines has started to refuse reading the catalog from the > server. The log shows the following: > > Mar 16 15:36:42 wmembf10 puppetd[7411]: Starting Puppet client version > 0.25.5 > Mar 16 15:36:46 wmembf10 puppetd[7411]: Could not retrieve catalog from > remote server: > Mar 16 15:36:46 wmembf10 puppetd[7411]: Using cached catalog > Mar 16 15:36:46 wmembf10 puppetd[7411]: Could not retrieve catalog; > skipping run > > Server and Client are both version 0.25.5. An identical System > (wmembf09) has no such problems and updates the configuration just fine. > Since I don''t get any indication what the problem could be I''m at a loss > what to do about this. Any ideas?Does puppetd --test -dv shed any more light? -- 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.