I have created my first ''fact'', first attempt at Ruby too, and
configured the fileserver to server it but when a Fedora (5 or 6)
client sync''s puppetd appears to hang. CentOS clients sync and use the
new fact fine.
Find attached the fact file and the output from ''puppetd --debug
--factsync'' on a FC5 client is below. This is a 0.20.1 client and the
FC6 is a 0.22.0 and is having the same problem.
Without the --factsync the command completes fine. After pressing (ctrl
+ c) puppetd takes some time to exit, a minute or two, which is odd.
I have tested the fact on FC6 & 5 without any problems.
# cp /var/lib/puppet/facts/network.rb ~/rubylib/facter/
# RUBYLIB=~/rubylib/ facter
To test further I created home.rb (see attached) from Luke''s example
and
it works fine.
Any help appreciated and any comments/suggestions on my first fact are
welcome.
Ben
---------------------------------------------------
# puppetd --debug --factsync
debug: puppet: Setting vardir to ''/var/lib/puppet''
debug: puppet: Setting logdir to ''/var/log/puppet''
debug: puppet: Setting rundir to ''/var/run/puppet''
debug: puppet: Setting lockdir to ''/var/lock''
debug: puppet: Setting ssldir to ''$vardir/ssl''
debug: puppetd: Setting classfile to ''$vardir/classes.txt''
debug: puppetd: Setting localconfig to ''$vardir/localconfig''
debug: puppetconfig/puppet/file=/var/lib/puppet/state/state.yaml:
Autorequiring file /var/lib/puppet
debug: puppetconfig/puppet/file=/var/lib/puppet/state/state.yaml:
Autorequiring file /var/lib/puppet/state
debug: puppetconfig/puppet/file=/var/lib/puppet/state/state.yaml:
subscribes to /var/lib/puppet
debug: puppetconfig/puppet/file=/var/lib/puppet/state/state.yaml:
subscribes to /var/lib/puppet/state
debug: puppetconfig/puppet/file=/var/lib/puppet/ssl: Autorequiring file
/var/lib/puppet
debug: puppetconfig/puppet/file=/var/lib/puppet/ssl: subscribes to
/var/lib/puppet
debug: puppetconfig/puppet/file=/var/lib/puppet/state: Autorequiring
file /var/lib/puppet
debug: puppetconfig/puppet/file=/var/lib/puppet/state: subscribes to
/var/lib/puppet
debug: puppetconfig/puppet/file=/etc/puppet/namespaceauth.conf:
Autorequiring file /etc/puppet
debug: puppetconfig/puppet/file=/etc/puppet/namespaceauth.conf:
subscribes to /etc/puppet
debug: puppetconfig/puppet/file=/var/lib/puppet/templates: Autorequiring
file /var/lib/puppet
debug: puppetconfig/puppet/file=/var/lib/puppet/templates: subscribes to
/var/lib/puppet
debug: puppetconfig/puppet/file=/var/lib/puppet/plugins: Autorequiring
file /var/lib/puppet
debug: puppetconfig/puppet/file=/var/lib/puppet/plugins: subscribes to
/var/lib/puppet
debug: puppetconfig/puppet/file=/var/lib/puppet/facts: Autorequiring
file /var/lib/puppet
debug: puppetconfig/puppet/file=/var/lib/puppet/facts: subscribes to
/var/lib/puppet
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/certs/ca.pem:
Autorequiring file /var/lib/puppet
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/certs/ca.pem:
Autorequiring file /var/lib/puppet/ssl
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/certs/ca.pem:
Autorequiring file /var/lib/puppet/ssl/certs
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/certs/ca.pem:
subscribes to /var/lib/puppet
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/certs/ca.pem:
subscribes to /var/lib/puppet/ssl
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/certs/ca.pem:
subscribes to /var/lib/puppet/ssl/certs
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/certs:
Autorequiring file /var/lib/puppet
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/certs:
Autorequiring file /var/lib/puppet/ssl
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/certs:
subscribes to /var/lib/puppet
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/certs:
subscribes to /var/lib/puppet/ssl
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/public_keys:
Autorequiring file /var/lib/puppet
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/public_keys:
Autorequiring file /var/lib/puppet/ssl
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/public_keys:
subscribes to /var/lib/puppet
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/public_keys:
subscribes to /var/lib/puppet/ssl
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/private_keys/fedora5.example.com.pem:
Autorequiring file /var/lib/puppet
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/private_keys/fedora5.example.com.pem:
Autorequiring file /var/lib/puppet/ssl
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/private_keys/fedora5.example.com.pem:
Autorequiring file /var/lib/puppet/ssl/private_keys
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/private_keys/fedora5.example.com.pem:
subscribes to /var/lib/puppet
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/private_keys/fedora5.example.com.pem:
subscribes to /var/lib/puppet/ssl
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/private_keys/fedora5.example.com.pem:
subscribes to /var/lib/puppet/ssl/private_keys
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/private_keys:
Autorequiring file /var/lib/puppet
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/private_keys:
Autorequiring file /var/lib/puppet/ssl
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/private_keys:
subscribes to /var/lib/puppet
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/private_keys:
subscribes to /var/lib/puppet/ssl
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/private:
Autorequiring file /var/lib/puppet
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/private:
Autorequiring file /var/lib/puppet/ssl
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/private:
subscribes to /var/lib/puppet
debug: puppetconfig/certificates/file=/var/lib/puppet/ssl/private:
subscribes to /var/lib/puppet/ssl
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/public_keys/fedora5.example.com.pem:
Autorequiring file /var/lib/puppet
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/public_keys/fedora5.example.com.pem:
Autorequiring file /var/lib/puppet/ssl
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/public_keys/fedora5.example.com.pem:
Autorequiring file /var/lib/puppet/ssl/public_keys
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/public_keys/fedora5.example.com.pem:
subscribes to /var/lib/puppet
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/public_keys/fedora5.example.com.pem:
subscribes to /var/lib/puppet/ssl
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/public_keys/fedora5.example.com.pem:
subscribes to /var/lib/puppet/ssl/public_keys
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/certs/fedora5.example.com.pem:
Autorequiring file /var/lib/puppet
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/certs/fedora5.example.com.pem:
Autorequiring file /var/lib/puppet/ssl
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/certs/fedora5.example.com.pem:
Autorequiring file /var/lib/puppet/ssl/certs
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/certs/fedora5.example.com.pem:
subscribes to /var/lib/puppet
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/certs/fedora5.example.com.pem:
subscribes to /var/lib/puppet/ssl
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/certs/fedora5.example.com.pem:
subscribes to /var/lib/puppet/ssl/certs
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/private/password:
Autorequiring file /var/lib/puppet
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/private/password:
Autorequiring file /var/lib/puppet/ssl
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/private/password:
Autorequiring file /var/lib/puppet/ssl/private
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/private/password:
subscribes to /var/lib/puppet
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/private/password:
subscribes to /var/lib/puppet/ssl
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/private/password:
subscribes to /var/lib/puppet/ssl/private
debug: puppetconfig/puppet/file=/var/lib/puppet/state/state.yaml:
Changing mode
debug: puppetconfig/puppet/file=/var/lib/puppet/state/state.yaml: 1
change(s)
debug: puppetconfig/puppet/file=/var/lib/puppet/state/state.yaml/mode:
mode changed ''640'' to ''660''
debug: puppetconfig/puppet/file=/etc/puppet/namespaceauth.conf: File
does not exist
debug: puppetconfig/puppet/file=/var/lib/puppet/plugins: File does not exist
debug: puppetconfig/puppet/file=/var/lib/puppet/facts: File does not exist
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/private/password:
File does not exist
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/private/password:
Changing mode
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/private/password: 1
change(s)
debug:
puppetconfig/certificates/file=/var/lib/puppet/ssl/private/password/mode:
File does not exist; cannot set mode
debug: Finishing transaction -606727528 with 2 changes
notice: Starting Puppet client version 0.20.1
info: Creating PID file to /var/run/puppet/puppetd.pid
debug: getting config
debug: Loaded state in 0.00 seconds
info: Retrieving facts
debug: Calling fileserver.describe
debug: Calling fileserver.list
debug: fact_collector/file=/var/lib/puppet/facts: Creating checksum
{time}Wed Jan 10 17:35:21 +1100 2007
debug: Calling fileserver.describe
debug: Calling fileserver.list
debug: fact_collector/file=/var/lib/puppet/facts/home.rb/checksum:
Initializing checksum hash
debug: fact_collector/file=/var/lib/puppet/facts/home.rb: Creating
checksum {md5}153cd374d92c50a790b5dc682f9d9e36
debug: fact_collector/file=/var/lib/puppet/facts/home.rb: Changing source
debug: fact_collector/file=/var/lib/puppet/facts/home.rb: 1 change(s)
debug: Calling fileserver.describe
debug: Calling fileserver.list
debug: fact_collector/file=/var/lib/puppet/facts/network.rb: File does
not exist
debug: fact_collector/file=/var/lib/puppet/facts/network.rb: Changing
checksum,source,owner,group,mode
debug: fact_collector/file=/var/lib/puppet/facts/network.rb: 5 change(s)
debug: fact_collector/file=/var/lib/puppet/facts: 6 change(s)
debug: Calling fileserver.retrieve
debug: fact_collector/file=/var/lib/puppet/facts/home.rb/checksum:
Replacing /var/lib/puppet/facts/home.rb checksum
{md5}153cd374d92c50a790b5dc682f9d9e36 with
{md5}96a1ab137e956f13039a63d3f3cdaa4f
notice: fact_collector/file=/var/lib/puppet/facts/home.rb/source: source
changed ''{md5}153cd374d92c50a790b5dc682f9d9e36'' to
''{md5}96a1ab137e956f13039a63d3f3cdaa4f''
debug: fact_collector/file=/var/lib/puppet/facts/network.rb/checksum:
setting md5 (currently absent)
notice: fact_collector/file=/var/lib/puppet/facts/network.rb/checksum:
defined ''checksum'' as
''{md5}8f7d09c0c1c484ba32924e5057118929''
debug: Calling fileserver.retrieve
debug: fact_collector/file=/var/lib/puppet/facts/network.rb/checksum:
Replacing /var/lib/puppet/facts/network.rb checksum
{md5}8f7d09c0c1c484ba32924e5057118929 with
{md5}df68dd3b48f142e90829ba82d24c8eec
notice: fact_collector/file=/var/lib/puppet/facts/network.rb/source:
defined ''source'' as
''{md5}df68dd3b48f142e90829ba82d24c8eec''
debug: Finishing transaction -606701108 with 6 changes
info: Loading fact home
info: Loading fact network
Hang!!
---------------------------------------------------------
_______________________________________________
Puppet-users mailing list
Puppet-users@madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users
On Jan 10, 2007, at 1:02 AM, Abnormaliti wrote:> I have tested the fact on FC6 & 5 without any problems. > > # cp /var/lib/puppet/facts/network.rb ~/rubylib/facter/ > # RUBYLIB=~/rubylib/ facter > > To test further I created home.rb (see attached) from Luke''s > example and it works fine.So you can successfully sync the home fact but not the network fact? There''s definitely a bit of a bug here -- Puppet should timeout when loading facts (filed as #427) -- but it seems to be a bug in your network fact, somehow. Can you run the following script on the machine that''s failing: require ''facter'' puts Facter.value(:interfacecount) Facter.clear Facter.loadfacts puts Facter.value(:interfacecount) That''s basically what Puppet does internally -- copy the facts into place, clear the existing facts, and load the new ones. If that fails, then we can track it down more closely. If it doesn''t hang, then there''s something weirder going on. -- The conception of two people living together for twenty-five years without having a cross word suggests a lack of spirit only to be admired in sheep. --Alan Patrick Herbert --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
Luke Kanies wrote:> On Jan 10, 2007, at 1:02 AM, Abnormaliti wrote: > >> I have tested the fact on FC6 & 5 without any problems. >> >> # cp /var/lib/puppet/facts/network.rb ~/rubylib/facter/ >> # RUBYLIB=~/rubylib/ facter >> >> To test further I created home.rb (see attached) from Luke''s >> example and it works fine. >> > > So you can successfully sync the home fact but not the network fact? > > There''s definitely a bit of a bug here -- Puppet should timeout when > loading facts (filed as #427) -- but it seems to be a bug in your > network fact, somehow. > > Can you run the following script on the machine that''s failing: > > require ''facter'' > > puts Facter.value(:interfacecount) > > Facter.clear > Facter.loadfacts > > puts Facter.value(:interfacecount) > > That''s basically what Puppet does internally -- copy the facts into > place, clear the existing facts, and load the new ones. If that > fails, then we can track it down more closely. If it doesn''t hang, > then there''s something weirder going on. > > -- > The conception of two people living together for twenty-five years > without having a cross word suggests a lack of spirit only to be > admired in sheep. --Alan Patrick Herbert > --------------------------------------------------------------------- > Luke Kanies | http://reductivelabs.com | http://madstop.com > > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users > > >luke, Thanks for your response and this project. i took your script and the results were correct. i expanded it to include all expected results and that was all good too. require ''facter'' puts Facter.value(:interfacecount) puts Facter.value(:eth0ipaddress) puts Facter.value(:eth0macaddress) puts Facter.value(:eth0netmask) puts Facter.value(:eth0network) Facter.clear Facter.loadfacts puts Facter.value(:interfacecount) puts Facter.value(:eth0ipaddress) puts Facter.value(:eth0macaddress) puts Facter.value(:eth0netmask) puts Facter.value(:eth0network) Results # RUBYLIB=~/rubylib/ ruby bin/test.rb 1 10.3.1.93 00:0c:29:9d:13:0c 255.255.255.0 10.3.1.0 1 10.3.1.93 00:0c:29:9d:13:0c 255.255.255.0 10.3.1.0 I left ''puppetd --debug --factsync'' running overnight and found this output this morning. .. info: Loading fact network notice: Locked by process 3699 notice: Lock file /var/lib/puppet/state/puppetdlock exists; skipping configuration run notice: Locked by process 3699 notice: Lock file /var/lib/puppet/state/puppetdlock exists; skipping configuration run notice: Locked by process 3699 notice: Lock file /var/lib/puppet/state/puppetdlock exists; skipping configuration run notice: Locked by process 3699 notice: Lock file /var/lib/puppet/state/puppetdlock exists; skipping configuration run notice: Locked by process 3699 notice: Lock file /var/lib/puppet/state/puppetdlock exists; skipping configuration run notice: Locked by process 3699 notice: Lock file /var/lib/puppet/state/puppetdlock exists; skipping configuration run notice: Locked by process 3699 notice: Lock file /var/lib/puppet/state/puppetdlock exists; skipping configuration run notice: Locked by process 3699 notice: Lock file /var/lib/puppet/state/puppetdlock exists; skipping configuration run notice: Locked by process 3699 notice: Lock file /var/lib/puppet/state/puppetdlock exists; skipping configuration run notice: Locked by process 3699 notice: Lock file /var/lib/puppet/state/puppetdlock exists; skipping configuration run notice: Locked by process 3699 notice: Lock file /var/lib/puppet/state/puppetdlock exists; skipping configuration run notice: Locked by process 3699 notice: Lock file /var/lib/puppet/state/puppetdlock exists; skipping configuration run notice: Locked by process 3699 notice: Lock file /var/lib/puppet/state/puppetdlock exists; skipping configuration run notice: Locked by process 3699 notice: Lock file /var/lib/puppet/state/puppetdlock exists; skipping configuration run notice: Locked by process 3699 notice: Lock file /var/lib/puppet/state/puppetdlock exists; skipping configuration run notice: Locked by process 3699 notice: Lock file /var/lib/puppet/state/puppetdlock exists; skipping configuration run notice: Locked by process 3699 notice: Lock file /var/lib/puppet/state/puppetdlock exists; skipping configuration run
On Jan 10, 2007, at 4:58 PM, Abnormaliti wrote:> luke, > > Thanks for your response and this project. > > i took your script and the results were correct. i expanded it to > include all expected results and that was all good too. > > require ''facter'' > > puts Facter.value(:interfacecount) > puts Facter.value(:eth0ipaddress) > puts Facter.value(:eth0macaddress) > puts Facter.value(:eth0netmask) > puts Facter.value(:eth0network) > > > Facter.clear > Facter.loadfacts > > puts Facter.value(:interfacecount) > puts Facter.value(:eth0ipaddress) > puts Facter.value(:eth0macaddress) > puts Facter.value(:eth0netmask) > puts Facter.value(:eth0network) > > Results > > # RUBYLIB=~/rubylib/ ruby bin/test.rb > 1 > 10.3.1.93 > 00:0c:29:9d:13:0c > 255.255.255.0 > 10.3.1.0 > 1 > 10.3.1.93 > 00:0c:29:9d:13:0c > 255.255.255.0 > 10.3.1.0Okay, so the facts appear to be working in Facter.> I left ''puppetd --debug --factsync'' running overnight and found this > output this morning. > > .. > info: Loading fact network > notice: Locked by process 3699 > notice: Lock file /var/lib/puppet/state/puppetdlock exists; skipping > configuration runIs there another puppetd process running with pid 3699? That''s what it seems like; either that, or there''s somehow a stray lock around. -- Now and then an innocent man is sent to the legislature. --Kin Hubbard --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
On Thu, Jan 11, 2007 at 11:34:53AM -0600, Luke Kanies wrote:> On Jan 10, 2007, at 4:58 PM, Abnormaliti wrote: > > I left ''puppetd --debug --factsync'' running overnight and found this > > output this morning. > > > > .. > > info: Loading fact network > > notice: Locked by process 3699 > > notice: Lock file /var/lib/puppet/state/puppetdlock exists; skipping > > configuration run > > Is there another puppetd process running with pid 3699? That''s what > it seems like; either that, or there''s somehow a stray lock around.If we''re talking about a reasonably recent version of Puppet, then there''s *definitely* something running with PID 3699, because otherwise Puppet would clear the lockfile as being stale. Abnormaliti, are you sure there isn''t another instance of puppetd running on the machine? - Matt -- I still can''t see a wasp without thinking "400K 1W" -- Derek Potter, uk.misc
Luke Kanies wrote:> On Jan 10, 2007, at 4:58 PM, Abnormaliti wrote: > > >> luke, >> >> Thanks for your response and this project. >> >> i took your script and the results were correct. i expanded it to >> include all expected results and that was all good too. >> >> require ''facter'' >> >> puts Facter.value(:interfacecount) >> puts Facter.value(:eth0ipaddress) >> puts Facter.value(:eth0macaddress) >> puts Facter.value(:eth0netmask) >> puts Facter.value(:eth0network) >> >> >> Facter.clear >> Facter.loadfacts >> >> puts Facter.value(:interfacecount) >> puts Facter.value(:eth0ipaddress) >> puts Facter.value(:eth0macaddress) >> puts Facter.value(:eth0netmask) >> puts Facter.value(:eth0network) >> >> Results >> >> # RUBYLIB=~/rubylib/ ruby bin/test.rb >> 1 >> 10.3.1.93 >> 00:0c:29:9d:13:0c >> 255.255.255.0 >> 10.3.1.0 >> 1 >> 10.3.1.93 >> 00:0c:29:9d:13:0c >> 255.255.255.0 >> 10.3.1.0 >> > > Okay, so the facts appear to be working in Facter. > > >> I left ''puppetd --debug --factsync'' running overnight and found this >> output this morning. >> >> .. >> info: Loading fact network >> notice: Locked by process 3699 >> notice: Lock file /var/lib/puppet/state/puppetdlock exists; skipping >> configuration run >> > > Is there another puppetd process running with pid 3699? That''s what > it seems like; either that, or there''s somehow a stray lock around. > > -- > Now and then an innocent man is sent to the legislature. > --Kin Hubbard > --------------------------------------------------------------------- > Luke Kanies | http://reductivelabs.com | http://madstop.com > > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users > > >There was no other puppet''s running. However I reboot to start a clean try. Tried each of the following, between each i checked for running puppet''s and if /var/lib/puppet/state/puppetdlock exists. Fedora 5 (puppetd --version == 0.22.0): puppetd -o (works) puppetd -o -v (works) puppetd -o -v --factsync (works) puppetd -o --debug --factsync (works) puppetd --debug --factsync (**hangs**) puppetd -v --factsync (**hangs**) puppetd -o -v --factsync (still works) puppetd --logdest=/var/log/puppet/puppetd.log --autoflush --factsync (**hangs**) Fedora 6 (puppetd --version == 0.22.0): puppetd -o (works) puppetd -o -v (works) puppetd -o -v --factsync (works) puppetd -o --debug --factsync (works) puppetd --debug --factsync (**hangs**) puppetd -v --factsync (**hangs**) puppetd -o -v --factsync (still works) puppetd --logdest=/var/log/puppet/puppetd.log --autoflush --factsync (**hangs**) Note: After a ''hang'' is canceled the lock file is left behind. i rm''d it as required between these tests. CentOS 4.4 (puppetd --version == 0.22.0): puppetd -o (works) puppetd -o -v (works) puppetd -o -v --factsync (works) puppetd -o --debug --factsync (works) puppetd --debug --factsync (works) puppetd -v --factsync (works) puppetd -o -v --factsync (still works) puppetd --logdest=/var/log/puppet/puppetd.log --autoflush --factsync (works) On the fedora''s it is interesting that "puppetd -o -v --factsync" works. Does this help at all in finding the cause? Yours truly, Ben
Abnormaliti wrote:> There was no other puppet''s running. However I reboot to start a clean try. > > Tried each of the following, between each i checked for running puppet''s > and if /var/lib/puppet/state/puppetdlock exists. > > Fedora 5 (puppetd --version == 0.22.0): > > puppetd -o (works) > puppetd -o -v (works) > puppetd -o -v --factsync (works) > puppetd -o --debug --factsync (works) > puppetd --debug --factsync (**hangs**) > puppetd -v --factsync (**hangs**) > puppetd -o -v --factsync (still works) > puppetd --logdest=/var/log/puppet/puppetd.log --autoflush --factsync > (**hangs**) > > Fedora 6 (puppetd --version == 0.22.0): > > puppetd -o (works) > puppetd -o -v (works) > puppetd -o -v --factsync (works) > puppetd -o --debug --factsync (works) > puppetd --debug --factsync (**hangs**) > puppetd -v --factsync (**hangs**) > puppetd -o -v --factsync (still works) > puppetd --logdest=/var/log/puppet/puppetd.log --autoflush --factsync > (**hangs**) > > Note: After a ''hang'' is canceled the lock file is left behind. i rm''d > it as required between these tests. > > CentOS 4.4 (puppetd --version == 0.22.0): > > puppetd -o (works) > puppetd -o -v (works) > puppetd -o -v --factsync (works) > puppetd -o --debug --factsync (works) > puppetd --debug --factsync (works) > puppetd -v --factsync (works) > puppetd -o -v --factsync (still works) > puppetd --logdest=/var/log/puppet/puppetd.log --autoflush --factsync > (works) > > On the fedora''s it is interesting that "puppetd -o -v --factsync" works. > > Does this help at all in finding the cause? > > Yours truly, > > Ben > > > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users > > >Can you give me anything more help with this? Where else can i look? Ben
On Jan 12, 2007, at 3:42 PM, Abnormaliti wrote:> There was no other puppet''s running. However I reboot > > On the fedora''s it is interesting that "puppetd -o -v --factsync" > works. > > Does this help at all in finding the cause?This makes it likely that the problem only occurs when stdin is opened as /dev/null or something similar. Can you try daemonizing your earlier test code? That should test whether that''s the problem. You should be able to add the following code to your test code: require ''puppet'' include Puppet::Daemon daemonize() This should put the test code in the same position as puppetd when running in the background. Then just see if the process exits when done. You may also want to open a file and print the output of the facts into that file, since stdout will be /dev/null. -- Be wary of the man who urges an action in which he himself incurs no risk. -- Joaquin Setanti --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com