I upgraded ruby, installed mongrel again. Everything is now working
successfully.
Tom
On Mon, Jan 26, 2009 at 10:11 PM, Bunkzillla wrote:
>
> I started from scratch scratch...
>
> I'm getting further. I'll post more tomorrow.
>
>
>
> On Jan 26, 8:57 pm, bunkytom wrote:
> > No I mean when I
I started from scratch scratch...
I'm getting further. I'll post more tomorrow.
On Jan 26, 8:57 pm, bunkytom 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 puppetmaster
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 us
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
r
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[p
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
