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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
