Think I found the issue from an strace, the rubygems-sqlit3 rpm was missing.. still curious on where the logs end up for it though. The fact that its using sqllite also doesn't help as I think I am running into locking issues if I try to run a cross environment update.
How to deal with sqllite locking as well as I see this quite a bit if I am using puppetqd/mysql combination or a local sqlite setup (without the queing). Got 1 failure(s) while initializing: change from 664 to 660 failed: failed to chmod /var/lib/puppet/state/clientconfigs.sqlite3: Operation not permitted - /var/lib/puppet/state/clientconfigs.sqlite3 On Mon, Jun 7, 2010 at 3:22 PM, Christopher Johnston <chjoh...@gmail.com>wrote: > Has anyone been using this in production to store facts remotely in a > distributed environment? I have been testing it in my lab where latency and > bandwith to a remote mysql server is very good so it works well. But if I > attempt to use it across a wan with ~150ms puppetqd seems to die. If I > don't have it running the stompserver/activemq looks to be in the path but > trying to debug why puppetqd would fail. > > Also where is it logging? I don't see anything for it in /var/log/messages > or with apache.. > > > > -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-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.
