Puppet users - Sep 2009 - puppetd daemon dies for no apparent reason

I spent some time getting a test site manifest to work with puppetd -
tvd.  Now I want to leave puppetd running on the host so that I can
trigger puppet runs remotely with puppetrun.

However, puppetd won''t stay alive.

This is on Fedora 10.  I issue

# service puppet start

and everything looks good.  But after a minute or two, "service puppet
status" reports that the process is dead even though a pid file
exists.  This is the only trace that remains in /var/log/messages:

... information about the previously successful puppetd -tvd run ...
Sep 25 18:28:57 LG-SIX-CWESTIN puppetd[2706]: Finished catalog run in
1.20 seconds
Sep 25 18:30:43 LG-SIX-CWESTIN puppetd[3098]: Reopening log files
Sep 25 18:30:43 LG-SIX-CWESTIN puppetd[3098]: Setting the :cacrl to
''false'' is deprecated; Puppet will just ignore the crl if
yours is
missing
Sep 25 18:30:43 LG-SIX-CWESTIN puppetd[3098]: Starting Puppet client
version 0.25.0
Sep 25 18:30:44 LG-SIX-CWESTIN puppetd[3098]: Cached
certificate_revocation_list for ca failed: Cannot manage the CRL
when :cacrl is set to false
Sep 25 18:30:44 LG-SIX-CWESTIN puppetd[3098]: Could not retrieve
catalog from remote server: Could not intern from s: Cannot manage the
CRL when :cacrl is set to false
Sep 25 18:30:44 LG-SIX-CWESTIN puppetd[3098]: Using cached catalog
Sep 25 18:30:45 LG-SIX-CWESTIN puppetd[3098]: Finished catalog run in
0.79 seconds
Sep 25 18:30:45 LG-SIX-CWESTIN puppetd[3098]: Cached
certificate_revocation_list for ca failed: Cannot manage the CRL
when :cacrl is set to false

Puzzled by the "Could not retrieve catalog...." when it clearly did,
because I checked, and the host is correctly configured as per the
site manifest.

I''m not setting cacrl in my /etc/puppet/puppet.conf.

Any ideas on why its dying, and what I should do to fix that?

TIA,
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
-~----------~----~----~----~------~----~------~--~---

More information:

In my efforts to get past some other messages regarding "could not
intern from JSON," I had installed (yum install) the ruby-json
package.  With that installed, puppetd refused to run at all.  I dug
around and found some blags that said this message was ignorable.  So
I (yum) uninstalled that package.  Uninstalled, puppetd would run -
tvd, but wouldn''t stay alive as a daemon.  I began to suspect there
may have been other dependent packages that were gumming things up.

So I''ve recreated my host (this was all in an experimental VM) without
installing the ruby-json package, and now puppet stays alive.
However, it refuses to pull the local host''s manifest on demand.
puppetd will pull the manifest when it wakes up periodically, but if I
try to trigger it from another host using puppetrun, it still gives me
the message above, complaining that it can''t retrieve the catalog.  If
I make changes, it will get them on the next scheduled wakeup, but I
can''t trigger it remotely.

Does that ring any bells?

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