Can anyone help me with this error I am having. I am using puppet on
Debian Etch, version 0.20.1-1 from apt works OK, but due to one or two
problems we want to use the version from testing, 0.23.2-10, but the
puppetd just fails upon startup spitting this out:
Starting puppet configuration management
tool/usr/lib/ruby/1.8/timeout.rb:54:in `open'': execution expired
(Timeout::Error)
from /usr/lib/ruby/1.8/net/http.rb:560:in `connect''
from /usr/lib/ruby/1.8/timeout.rb:56:in `timeout''
from /usr/lib/ruby/1.8/timeout.rb:76:in `timeout''
from /usr/lib/ruby/1.8/net/http.rb:560:in `connect''
from /usr/lib/ruby/1.8/net/http.rb:553:in `do_start''
from /usr/lib/ruby/1.8/net/http.rb:548:in `start''
from /usr/lib/ruby/1.8/puppet/network/xmlrpc/client.rb:173:in
`start''
from /usr/lib/ruby/1.8/puppet/network/client.rb:93:in
`initialize''
from /usr/lib/ruby/1.8/puppet/network/client/master.rb:250:in
`initialize''
from /usr/sbin/puppetd:312:in `new''
from /usr/sbin/puppetd:312
I have searched for a solution, but cannot find one...
Joe
On Oct 12, 2007, at 8:21 AM, Joseph Holland wrote:> Can anyone help me with this error I am having. I am using puppet on > Debian Etch, version 0.20.1-1 from apt works OK, but due to one or two > problems we want to use the version from testing, 0.23.2-10, but the > puppetd just fails upon startup spitting this out: > > Starting puppet configuration management > tool/usr/lib/ruby/1.8/timeout.rb:54:in `open'': execution expiredIs the server running? If so, what does it say? We need the output from both client and server to be of any help. -- I hate to advocate drugs, alcohol, violence, or insanity to anyone, but they''ve always worked for me. -- Hunter S. Thompson --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
OK, I figured it out... With 0.20.x the puppetd process would startup whether configured or not, whereas with the latest versions it will not. Once I saw that the puppetd was not starting I never bothered to configure the server side of things because I had assumed that it was a ruby problem or something... Thanks for the help, Joe. Luke Kanies wrote:> On Oct 12, 2007, at 8:21 AM, Joseph Holland wrote: > > >> Can anyone help me with this error I am having. I am using puppet on >> Debian Etch, version 0.20.1-1 from apt works OK, but due to one or two >> problems we want to use the version from testing, 0.23.2-10, but the >> puppetd just fails upon startup spitting this out: >> >> Starting puppet configuration management >> tool/usr/lib/ruby/1.8/timeout.rb:54:in `open'': execution expired >> > > Is the server running? If so, what does it say? > > We need the output from both client and server to be of any help. > > -- > I hate to advocate drugs, alcohol, violence, or insanity to anyone, > but > they''ve always worked for me. -- Hunter S. > Thompson > --------------------------------------------------------------------- > Luke Kanies | http://reductivelabs.com | http://madstop.com > > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users >
Joseph Holland
2007-Oct-30 12:00 UTC
err: Could not retrieve configuration: Cannot connect to server and there is no cached configuration
err: Could not retrieve configuration: Cannot connect to server and there is no cached configuration Can anyone help me with this, I have set puppetmaster up on a debian etch machine, set up puppet on another and signed the certificate and now when I run puppetd -v -o all I get is this error... Joe
Rajeshwaran G
2007-Oct-30 18:03 UTC
Re: err: Could not retrieve configuration: Cannot connect to server and there is no cached configuration
Joe, I too have come across this problem.. make sure your have the manifest file with no syntax error. If you are to add a class or file .. sometimes multiples files in a class ..check for examples and you might have missed semi colon or comma ..etc some where. Rajeshwaran On 10/30/07, Joseph Holland <joseph.holland@kepak.com> wrote:> > err: Could not retrieve configuration: Cannot connect to server and > there is no cached configuration > > Can anyone help me with this, I have set puppetmaster up on a debian > etch machine, set up puppet on another and signed the certificate and > now when I run puppetd -v -o all I get is this error... > > > Joe > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users >-- He also serves Who only stands and waits.... _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
Luke Kanies
2007-Oct-30 18:24 UTC
Re: err: Could not retrieve configuration: Cannot connect to server and there is no cached configuration
On Oct 30, 2007, at 1:03 PM, Rajeshwaran G wrote:> too have come across this problem.. > make sure your have the manifest file with no syntax error. If you > are to add a class or file .. sometimes multiples files in a > class ..check for examples and you might have missed semi colon or > comma ..etc some where.And check your server-side logs. I do my best to make it so the client sees any failures on the server, but it isn''t always possible. The server should log the failure, though. -- A child can go only so far in life without potty training. It is not mere coincidence that six of the last seven presidents were potty trained, not to mention nearly half of the nation''s state legislators. -- Dave Barry --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
Matthew Palmer
2007-Oct-30 19:14 UTC
Re: err: Could not retrieve configuration: Cannot connect to server and there is no cached configuration
On Tue, Oct 30, 2007 at 12:00:08PM +0000, Joseph Holland wrote:> err: Could not retrieve configuration: Cannot connect to server and > there is no cached configuration > > Can anyone help me with this, I have set puppetmaster up on a debian > etch machine, set up puppet on another and signed the certificate and > now when I run puppetd -v -o all I get is this error...Your syslogs (on client, server, or both) will have information on why this happened. On Debian systems, the messages should be in /var/log/daemon.log. - Matt
micah
2007-Nov-07 17:41 UTC
Re: err: Could not retrieve configuration: Cannot connect to server and there is no cached configuration
On Wed, 31 Oct 2007 06:14:46 +1100, Matthew Palmer wrote:> On Tue, Oct 30, 2007 at 12:00:08PM +0000, Joseph Holland wrote: >> err: Could not retrieve configuration: Cannot connect to server and >> there is no cached configuration >> >> Can anyone help me with this, I have set puppetmaster up on a debian >> etch machine, set up puppet on another and signed the certificate and >> now when I run puppetd -v -o all I get is this error... >You may be reaching a node limit that is causing your puppetmaster to choke on too many incoming connections at once. If you haven''t done so, the path to ramping up more nodes seems to be: switch to using mysql or postgresql backend if you are using storedconfigs, then once you get somewhere around 30 nodes or so, you will need to switch to and apache +mongrel setup. I''m running 31 nodes at the moment, without mongrel, I get this problem occasionally when the client skew times aren''t spread enough so too many clients are connecting at once. I start to get these client errors and the only way to get things back is to kill the puppetmaster and start it again. I will likely need to switch to mongrel soon. micah