I upgraded ruby, installed mongrel again. Everything is now working successfully.
Tom On Mon, Jan 26, 2009 at 10:11 PM, Bunkzillla <bunky...@gmail.com> wrote: > > I started from scratch scratch... > > I'm getting further. I'll post more tomorrow. > > > > On Jan 26, 8:57 pm, bunkytom <bunky...@gmail.com> wrote: > > No I mean when I try to do the puppetd -vdt --server localhost > --masterport > > 18140 > > > > it just hangs. > > > > I've tried doing the gems install mongrel again. The puppetmasterd is > > starting, is there anyway of getting more debug information other than > the > > puppetmasterd -vd ? That's not showing anything useful as far as I can > > tell. > > > > On Mon, Jan 26, 2009 at 1:43 PM, Andrew Shafer <and...@reductivelabs.com > >wrote: > > > > > I get that it just hangs, that is the puppetd making the request to the > > > puppemasterd. > > > > > Then you also had a Pound log that looks like the request was received > > > there and but Pound was stuck waiting for mongrel on 127.0.0.1:18140. > > > > > Without more data, I think you are right that the problem is mongrel > > > related. Have you tried setting it up again from scratch? > > > > > On Mon, Jan 26, 2009 at 9:32 AM, Bunkzillla <bunky...@gmail.com> > wrote: > > > > >> It just hangs... > > > > >> debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/ > > >> lib/puppet/state/state.yaml]: Changing mode > > >> debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/ > > >> lib/puppet/state/state.yaml]: 1 change(s) > > >> debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/ > > >> lib/puppet/state/state.yaml]/mode: mode changed '640' to '660' > > >> debug: Finishing transaction -606634738 with 1 changes > > >> debug: Loaded state in 0.01 seconds > > >> debug: Retrieved facts in 0.30 seconds > > >> debug: Retrieving catalog > > >> debug: Calling puppetmaster.getconfig > > > > >> On Jan 25, 11:42 pm, Andrew Shafer <and...@reductivelabs.com> wrote: > > >> > Based on what you have so far, I think you are correct. > > > > >> > Mongrel is probably not working. > > > > >> > If I'm reading things correctly, you are getting a request on pound > > >> which > > >> > evokes no response from the mongrels. > > > > >> > I've never seen this problem or troubleshot it, but what do you get > from > > >> > 127.0.0.1:18140? Is it possible mongrel is running, but the mongrel > > >> +pound > > >> > isn't configured? > > > > >> > On Sun, Jan 25, 2009 at 9:15 PM, Bunkzillla <bunky...@gmail.com> > wrote: > > > > >> > > I've had puppet 0.24.6 running successfully using webrick, but > it's > > >> > > time to move to multiple puppetmasterd processes. > > > > >> > > mongrel (0.3.3) > > >> > > A small fast HTTP library and server that runs Rails, Camping, > and > > >> > > Nitro apps. > > > > >> > > Running on CentOS 4.2 > > > > >> > > I'm thinking it's something with mongrel, cause things just hang, > I > > >> > > don't get cert errors. > > > > >> > > I've followed the using mongrel with pound twiki page. > > > > >> > > Here is a listing of my pem files > > > > >> > > ./puppet/ssl/csr_devpet.admin.sf.example.com.pem > > >> > > ./puppet/ssl/private_keys/devpet.admin.sf.example.com.pem > > >> > > ./puppet/ssl/certs/devpet.admin.sf.example.com.pem > > >> > > ./puppet/ssl/certs/ca.pem > > >> > > ./puppet/ssl/ca/signed/devpet.admin.sf.example.com.pem > > >> > > ./puppet/ssl/ca/ca_crl.pem > > >> > > ./puppet/ssl/ca/ca_key.pem > > >> > > ./puppet/ssl/ca/ca_pub.pem > > >> > > ./puppet/ssl/ca/ca_crt.pem > > >> > > ./puppet/ssl/public_keys/devpet.admin.sf.example.com.pem > > > > >> > > I created the pound key file doing the following: > > > > >> > > cat /var/lib/puppet/ssl/private_keys/devpet.admin.sf.yav4.com.pem > >> \ > > >> > > /var/lib/puppet/ssl/pound/host_key_and_cert_chain.pem > > > > >> > > cat /var/lib/puppet/ssl/certs/devpet.admin.sf.yav4.com.pem >> \ > > >> > > /var/lib/puppet/ssl/pound/host_key_and_cert_chain.pem > > > > >> > > cat /var/lib/puppet/ssl/ca/ca_crt.pem >> \ > > >> > > /var/lib/puppet/ssl/pound/host_key_and_cert_chain.pem > > > > >> > > debug: > /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/ > > >> > > lib/puppet/state/state.yaml]: 1 change(s) > > >> > > debug: > /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/ > > >> > > lib/puppet/state/state.yaml]/mode: mode changed '640' to '660' > > >> > > debug: Finishing transaction -606617684 with 1 changes > > >> > > debug: Loaded state in 0.01 seconds > > >> > > debug: Retrieved facts in 0.31 seconds > > >> > > debug: Retrieving catalog > > >> > > debug: Calling puppetmaster.getconfig > > >> > > err: Connection timeout calling puppetmaster.getconfig: execution > > >> > > expired > > >> > > err: Could not retrieve catalog: exception class/object expected > > >> > > warning: Not using cache on failed catalog > > > > >> > > I see this from pound: > > > > >> > > Jan 25 20:03:32 devpet pound: response error read from > > >> > > 127.0.0.1:18140: Connection timed out > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
