Hi puppeteers,
I have a problem with one of my puppets. When I run puppetd and a file
needs to be updated I get the following error message:
debug: //jupiter/freebsd_base/File[/etc/rc.conf]: Changing source
debug: //jupiter/freebsd_base/File[/etc/rc.conf]: 1 change(s)
debug: Calling fileserver.retrieve
debug: Calling puppetbucket.addfile
err: Could not call puppetbucket.addfile: #<Errno::EINVAL: Invalid
argument - connect(2)>
err: //jupiter/freebsd_base/File[/etc/rc.conf]/source: change from
{md5}7a0407239c13f0355c0ece466ec613cd to
puppet://puppet.domain.net/files/sys/jupiter/rc.conf failed: Invalid
argument - connect(2)
debug: Calling fileserver.describe
Looks like I might have a problem with the filebucket. When I manually
remove /etc/rc.conf from the client puppet will apply the new file
without problems. Here is my filebucket configuration:
filebucket { main: server => puppet }
File { backup => main }
It''s weird because this is the only machine that has problems and
it''s
running my standard config that works fine for others. I''m running
FreeBSD 6.2, ruby 1.8.6, puppet 0.23.2 and facter 1.3.8. Puppetmaster
is using mongrel.
I run puppetd --debug on the client and I also tried debug on
puppetmaster end but haven''t found any clues. tcpdump did not show
anything unusual either. Do you have any ideas where I could look next
or what could have caused it? I''d appreciate any pointers.
Many Thanks,
Rek.
_______________________________________________
Puppet-users mailing list
Puppet-users@madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users
On Dec 19, 2007, at 10:35 AM, Rek Jed wrote:> Hi puppeteers, > > I have a problem with one of my puppets. When I run puppetd and a > file needs to be updated I get the following error message: > > debug: //jupiter/freebsd_base/File[/etc/rc.conf]: Changing source > debug: //jupiter/freebsd_base/File[/etc/rc.conf]: 1 change(s) > debug: Calling fileserver.retrieve > debug: Calling puppetbucket.addfile > err: Could not call puppetbucket.addfile: #<Errno::EINVAL: Invalid > argument - connect(2)> > err: //jupiter/freebsd_base/File[/etc/rc.conf]/source: change from > {md5}7a0407239c13f0355c0ece466ec613cd to puppet://puppet.domain.net/ > files/sys/jupiter/rc.conf failed: Invalid argument - connect(2) > debug: Calling fileserver.describe > > Looks like I might have a problem with the filebucket. When I > manually remove /etc/rc.conf from the client puppet will apply the > new file without problems. Here is my filebucket configuration: > > filebucket { main: server => puppet } > File { backup => main } > > It''s weird because this is the only machine that has problems and > it''s running my standard config that works fine for others. I''m > running FreeBSD 6.2, ruby 1.8.6, puppet 0.23.2 and facter 1.3.8. > Puppetmaster is using mongrel. > > I run puppetd --debug on the client and I also tried debug on > puppetmaster end but haven''t found any clues. tcpdump did not show > anything unusual either. Do you have any ideas where I could look > next or what could have caused it? I''d appreciate any pointers.Are you running against a newer server version? Are the other, functional machines running the same client and ruby versions as the broken client? -- The most overlooked advantage to owning a computer is that if they foul up there''s no law against wacking them around a little. -- Joe Martin --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
Hi,> > Are you running against a newer server version? Are the other, > functional machines running the same client and ruby versions as the > broken client? >The server is running the same version of puppet so do the other functional clients. As for Ruby, the server is running 1.8.6 (2007-03-13 patchlevel 0) on FreeBSD 6.1. Most of the other clients run the same version of ruby as the server, I also have a few running 1.8.6 (2007-09-24 patchlevel 111) without problems. The troubled client was running ruby 1.8.5 when I first installed puppet on it, I later upgraded to 1.8.6 (2007-09-24 patchlevel 111) thinking that it might fix it, but it didn''t help. Is there a way to disable the filebucket for a single client? _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
On Dec 20, 2007, at 12:11 PM, Rek Jed wrote:> The server is running the same version of puppet so do the other > functional clients. As for Ruby, the server is running 1.8.6 > (2007-03-13 patchlevel 0) on FreeBSD 6.1. Most of the other > clients run the same version of ruby as the server, I also have a > few running 1.8.6 (2007-09-24 patchlevel 111) without problems. > The troubled client was running ruby 1.8.5 when I first installed > puppet on it, I later upgraded to 1.8.6 (2007-09-24 patchlevel 111) > thinking that it might fix it, but it didn''t help.Hrm. So all clients except this one work? That''s always bad, because it''s nearly impossible to track down.> Is there a way to disable the filebucket for a single client?Sure; just selectively change the default file bucket for that single host, using a case statement or whatever. -- Wear the old coat and buy the new book. -- Austin Phelps --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com