Puppet users - Mar 2010 - "Failed to retrieve current state of resource" messages

I''ve sent one in for this... we''re running the client every 30
minutes
via cron, and we probably get ten reports a day (per node) just like
this one.  It started once we went from EPEL''s v0.24 to v0.25. 
I''ve
sent one message like this to the group, but didn''t get a response.

Tue Mar 23 12:06:43 -0400 2010 //XXXX/File[/etc/init.d/XXXX] (err):
Failed to retrieve current state of resource: end of file reached
Could not retrieve file metadata for puppet:///modules/XXXX/XXXX: end
of file reached at /etc/puppet/modules/XXXX/manifests/init.pp:45

The stanza that it''s referencing is:

  file { "/etc/init.d/XXXX":
        owner   => root,
        group   => root,
        mode    => 700,
        source  => "puppet:///modules/XXXX/XXXX",
  }

Any ideas?

Thanks for the help.

-- 
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.

Are you using webrick, mongrel, or passenger?

Sent from my iPhone

On Mar 23, 2010, at 5:32 PM, Kent Rankin <rankin.kent@gmail.com> wrote:
> I''ve sent one in for this... we''re running the client
every 30 minutes
> via cron, and we probably get ten reports a day (per node) just like
> this one.  It started once we went from EPEL''s v0.24 to v0.25. 
I''ve
> sent one message like this to the group, but didn''t get a
response.
>
> Tue Mar 23 12:06:43 -0400 2010 //XXXX/File[/etc/init.d/XXXX] (err):
> Failed to retrieve current state of resource: end of file reached
> Could not retrieve file metadata for puppet:///modules/XXXX/XXXX: end
> of file reached at /etc/puppet/modules/XXXX/manifests/init.pp:45
>
> The stanza that it''s referencing is:
>
>  file { "/etc/init.d/XXXX":
>        owner   => root,
>        group   => root,
>        mode    => 700,
>        source  => "puppet:///modules/XXXX/XXXX",
>  }
>
> Any ideas?
>
> Thanks for the help.
>
> --  
> 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.

I''ve made no changes, so I''m assuming that it''s
webrick.  Would this
impact that?


On Tue, Mar 23, 2010 at 8:22 PM, Christopher Johnston
<chjohnst@gmail.com> wrote:
> Are you using webrick, mongrel, or passenger?
>
> Sent from my iPhone
>
> On Mar 23, 2010, at 5:32 PM, Kent Rankin <rankin.kent@gmail.com>
wrote:
>
>> I''ve sent one in for this... we''re running the client
every 30 minutes
>> via cron, and we probably get ten reports a day (per node) just like
>> this one.  It started once we went from EPEL''s v0.24 to v0.25.
 I''ve
>> sent one message like this to the group, but didn''t get a
response.
>>
>> Tue Mar 23 12:06:43 -0400 2010 //XXXX/File[/etc/init.d/XXXX] (err):
>> Failed to retrieve current state of resource: end of file reached
>> Could not retrieve file metadata for puppet:///modules/XXXX/XXXX: end
>> of file reached at /etc/puppet/modules/XXXX/manifests/init.pp:45
>>
>> The stanza that it''s referencing is:
>>
>>  file { "/etc/init.d/XXXX":
>>       owner   => root,
>>       group   => root,
>>       mode    => 700,
>>       source  => "puppet:///modules/XXXX/XXXX",
>>  }
>>
>> Any ideas?
>>
>> Thanks for the help.
>>
>> -- 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.

Am Tue, 23 Mar 2010 22:42:57 -0400 schrieb Kent Rankin:
> I''ve made no changes, so I''m assuming that it''s
webrick.  Would this
> impact that?
had this error too. try to go on with mongrel or passenger. webrick''s 
intended use is for development and is not optimized for real production. 

- Thomas
>>>
>>> Tue Mar 23 12:06:43 -0400 2010 //XXXX/File[/etc/init.d/XXXX] (err):
>>> Failed to retrieve current state of resource: end of file reached
>>> Could not retrieve file metadata for puppet:///modules/XXXX/XXXX:
end
>>> of file reached at /etc/puppet/modules/XXXX/manifests/init.pp:45
>>>
-- 
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.