On Mar 9, 2010, at 5:50 PM, Patrick wrote:

> 
> On Mar 9, 2010, at 1:59 PM, Brian Keifer wrote:
> 
>> 
>> On Mar 9, 2010, at 4:57 PM, Patrick wrote:
>> 
>>> 
>>> On Mar 9, 2010, at 6:36 AM, Brian Keifer wrote:
>>> 
>>>> 
>>>> On Mar 9, 2010, at 12:17 AM, Dan Bode wrote:
>>>> 
>>>>> 
>>>>> 1. Check the source attribute assignment.
>>>>> 
>>>>> source => puppet:///modules/stats/denora.conf
>>>>> 
>>>>> the third slash means use same server address as the server we connected 
>>>>> to.
>>>>> 
>>>>> maybe its hardcoded to be the server name?
>>>>> 
>>>>> 2. you could also try:
>>>>> 
>>>>> [puppetmasterd]
>>>>> certdnsnames=badger.valinor.net
>>>>> 
>>>>> on the server if you need this name to be accepted by the cert.
>>>>> 
>>>> 
>>>> Thanks!  I had been using source => 
>>>> "puppet://$servername/module/path/filename.ext".  I switched to puppet:/// 
>>>> and added the certdnsnames line to my puppetmaster's config file.  My 
>>>> config looks a bit cleaner, but I'm still getting the random errors on my 
>>>> file definitions:
>>>> 
>>>> err: //inspircd/File[/home/procrast/inspircd/conf/modules.conf]: Failed to 
>>>> retrieve current state of resource: undefined method `closed?' for 
>>>> nil:NilClass Could not retrieve file metadata for 
>>>> puppet:///inspircd/modules.conf: undefined method `closed?' for 
>>>> nil:NilClass at /etc/puppet/modules/inspircd/manifests/init.pp:15
>>>> 
>>>> From several test runs with:
>>>> 
>>>>    puppetd --server puppet.procrast.net --fqdn badger.procrast.net 
>>>> --no-daemonize --onetime --verbose
>>>> 
>>>> I get between 3 and 9 of these errors each time, always a different subset 
>>>> of my files.  These same files serve properly to my other two clients.
>>>> 
>>>> I don't get it.
>>> 
>>> This might be related to http://projects.reductivelabs.com/issues/3083.  
>>> Try using "puppetca --list --all" on the server and check if those clients 
>>> are in the list.  If they are not in the list, it's probably that bug.
>>> -Patrick
>>> 
>> 
>> The problem client does appear to be listed.
>> 
>> [r...@badger /etc/puppet]# puppetca --list --all
>> + badger.procrast.net
>> + puppet.procrast.net
> 
> Does puppetca show the other clients (that work) as being in the same domain? 
>  Also, take a look at /etc/puppet/fileserver.conf.
> 

Yep.  They all show .procrast.net addresses.  My fileserver.conf is quite basic 
at the moment.  It's got the path to the files for each module and an "allow *" 
for each.

I believe the fileserver.conf is set up correctly, as the problems are 
sporadic.  On one run a file may fail, but on the other runs it copies 
properly.  Additionally, the other two clients that are not on the same machine 
as the fileserver have no issues at all.

Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to