I am having the same problem now with puppet-2.7.6 on FreeBSD. That original post by Chris has no response since may. Developers, do you have any idea why that happenes? Thanks! ---------- Forwarded message ---------- From: Chris Phillips <ch...@untrepid.com> Date: May 10, 1:35 am Subject: Could not retrieve metadata - 2.6.7 / RHEL4 / remote site To: Puppet Users Hi, I''ve got a 2.6.7 server and client setup running pretty nicely in a single site on a few rhel5 and 6 boxes, and today branched out with a RHEL4 node on a remote site. This was installing 2.6.7 (and facter 1.5.8) from source due to the lack of el4 rpms (el5''s from yum.puppetlabs.com on all other RHEL boxes so far), with oldish official ruby 1.8.1 el4 rpms. On this new node I''m getting about a 30-40% failure rate in terms of runs, with errors in retrieving metadata: Mon May 09 22:16:12 +0100 2011 /Stage[main]/Nss-ldap/File[/etc/nsswitch.conf] (err): Could not evaluate: Could not retrieve file metadata for puppet:///modules/nss-ldap/nsswitch.conf: at /etc/puppet/modules/nss-ldap/manifests/init.pp:37 This happens on various different modules, but always the same error, trying to get a file for a source reference. I''m aware there are a few new variables I''ve thrown in, but the WAN connectivity seems to be fine, no packet loss or anything, and also as these errors are reported on the server and client, it''s not like it''s actually losing connection with the puppet server. Does this intermittent error ring any bells? With tagmail reports telling us about this, it''s not really ignorable for us. Thanks Chris -- 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.
Example: Nov 21 22:56:35 comp01 puppet-agent[46828]: (/Stage[main]/Bsd/File[/ etc/inetd.conf]) Could not evaluate: end of file reached Could not retrieve file metadata for puppet:///modules/bsd/etc/inetd.conf: end of file reached at /usr/local/etc/puppet/modules/bsd/manifests/init.pp: 80 This messages appear for random clients for random lines in init.pp. On Nov 21, 11:35 pm, Dmitry <trtrmi...@gmail.com> wrote:> I am having the same problem now with puppet-2.7.6 on FreeBSD. > That original post by Chris has no response since may. > > Developers, do you have any idea why that happenes? > > Thanks! > > > > > > > > ---------- Forwarded message ---------- > From: Chris Phillips <ch...@untrepid.com> > Date: May 10, 1:35 am > Subject: Could not retrieve metadata - 2.6.7 / RHEL4 / remote site > To: Puppet Users > > Hi, > > I''ve got a 2.6.7 server and client setup running pretty nicely in a > single > site on a few rhel5 and 6 boxes, and today branched out with a RHEL4 > node on > a remote site. This was installing 2.6.7 (and facter 1.5.8) from > source due > to the lack of el4 rpms (el5''s from yum.puppetlabs.com on all other > RHEL > boxes so far), with oldish official ruby 1.8.1 el4 rpms. On this new > node > I''m getting about a 30-40% failure rate in terms of runs, with errors > in retrieving metadata: > > Mon May 09 22:16:12 +0100 2011 > /Stage[main]/Nss-ldap/File[/etc/nsswitch.conf] (err): Could not > evaluate: > Could not retrieve file metadata for > puppet:///modules/nss-ldap/nsswitch.conf: at > /etc/puppet/modules/nss-ldap/manifests/init.pp:37 > > This happens on various different modules, but always the same error, > trying > to get a file for a source reference. I''m aware there are a few new > variables I''ve thrown in, but the WAN connectivity seems to be fine, > no > packet loss or anything, and also as these errors are reported on the > server > and client, it''s not like it''s actually losing connection with the > puppet > server. Does this intermittent error ring any bells? With tagmail > reports > telling us about this, it''s not really ignorable for us. > > Thanks > > Chris-- 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.
Hi, On 11/21/2011 08:38 PM, Dmitry wrote:> Example: > > Nov 21 22:56:35 comp01 puppet-agent[46828]: (/Stage[main]/Bsd/File[/ > etc/inetd.conf]) Could not evaluate: end of file reached Could not > retrieve file metadata for puppet:///modules/bsd/etc/inetd.conf: end > of file reached at /usr/local/etc/puppet/modules/bsd/manifests/init.pp: > 80 > > This messages appear for random clients for random lines in init.pp.any other funny effects visible on your master at those times? I/O errors or somesuch? It would appear that your init.pp cannot be read properly or somesuch. Are there any background processes (e.g. automatic svn updates or similar) that could be responsible for disrupting the master''s file operations on the manifest? -- 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.