Hi, I thing this issue has been mentioned several times in this list but I can''t see any conclusion. In about 10% of all runs Puppet randomly fails on some (random) File resource either with this error: Thu Jun 24 02:40:03 +0000 2010 //<random module>/File[<random file>] (err): Failed to generate additional resources using ''eval_generate'': or this error: Wed Jun 23 18:56:33 +0000 2010 //<random module>/File[<random file>] (err): Failed to retrieve current state of resource: Could not retrieve file metadata for puppet:///modules/<random module>/<random file>: at /etc/puppet/manifests/<random manifest>.pp:<line> the only common source of these failures is the File resource which in my case has always multiple sources like this: file { "/path/to/my/file": source => [ "/modules/files/file.$host", "/modules/files/file.$operatingsystem", "/modules/files/file" ] } it is sure, that at least the file /modules/files/file always exists, so this shouldn''t fail. running puppet 0.25.5, had this issue already in 0.25.4 does have anyone any clue? this is very annoying as the mail reports can''t be taken seriously. thanks, Antony -- 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 24/06/10 14:51, Antony Mayi wrote:> [snip] > In about 10% of all runs Puppet randomly fails on some (random) File > resource either with this error: > > Thu Jun 24 02:40:03 +0000 2010 //<random module>/File[<random file>] > (err): Failed to generate additional resources using ''eval_generate'': > > or this error: > > Wed Jun 23 18:56:33 +0000 2010 //<random module>/File[<random file>] > (err): Failed to retrieve current state of resource: Could not > retrieve file metadata for puppet:///modules/<random module>/<random > file>: at /etc/puppet/manifests/<random manifest>.pp:<line> > > [snip[ > > does have anyone any clue? this is very annoying as the mail reports > can''t be taken seriously.How is your puppetmaster running? How many clients do you have? I think these errors come from the fact that the master is overloaded and doesn''t answer to the file resource request in a timely way, so a timeout triggers. Usual advice: if you run with webrick, use something that is more scalable (including passenger or nginx+mongrel). -- Brice Figureau My Blog: http://www.masterzen.fr/ -- 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.
thanks Brice, that''s a very good point and I am going to investigate it. the master is running as a virtual machine with limited resources so this can be really the issue. thanks, Antony. ________________________________ From: Brice Figureau <brice-puppet@daysofwonder.com> To: puppet-users@googlegroups.com Sent: Thu, 24 June, 2010 18:58:05 Subject: Re: [Puppet Users] puppet random errors On 24/06/10 14:51, Antony Mayi wrote:> [snip] > In about 10% of all runs Puppet randomly fails on some (random) File > resource either with this error: > > Thu Jun 24 02:40:03 +0000 2010 //<random module>/File[<random file>] > (err): Failed to generate additional resources using ''eval_generate'': > > or this error: > > Wed Jun 23 18:56:33 +0000 2010 //<random module>/File[<random file>] > (err): Failed to retrieve current state of resource: Could not > retrieve file metadata for puppet:///modules/<random module>/<random > file>: at /etc/puppet/manifests/<random manifest>.pp:<line> > > [snip[ > > does have anyone any clue? this is very annoying as the mail reports > can''t be taken seriously.How is your puppetmaster running? How many clients do you have? I think these errors come from the fact that the master is overloaded and doesn''t answer to the file resource request in a timely way, so a timeout triggers. Usual advice: if you run with webrick, use something that is more scalable (including passenger or nginx+mongrel). -- Brice Figureau My Blog: http://www.masterzen.fr/ -- 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.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1> that''s a very good point and I am going to investigate it. the master > is running as a virtual machine with limited resources so this can be > really the issue.not only that: webrick is a single thread serving only one client at one point. this is the main reason why you need to scale things out with passenger or nginx+mongrel if you are getting more clients. cheers pete -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwlZ5cACgkQbwltcAfKi3/3QgCffZwfkkRNlBczhNmYNfnsFRt5 8IsAoKKdeWEYMIFYaGThsZRY8jic5PkT =SZK8 -----END PGP SIGNATURE----- -- 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.
Reasonably Related Threads
- Seperate CA's/Master behind load balancer
- Any ideas about this error with upgrading to 0.25.1?
- PC EU feedback: exported resource syntax is too magical, hard to read
- Toward a simple Nginx configuration for Puppet Mongrel
- Separating puppetmaster file serving and catalogs