I have managed to solve this problem / find a work around, by playing
with the passenger settings in my apache config file.
By adding more PassengerMaxPoolSize and increasing the
PassengerPoolIdleTime i have made it so passenger can spawn up to 30
puppetmasterd processes and keeps the processes ru
On Mon, May 17, 2010 at 6:05 AM, Abhishek wrote:
>
>
> On Apr 11, 4:57 pm, Mark Nelson wrote:
> > Hello
> >
> > I am using the following software -
> >
> > *Operating System:
> >
> > *Scientific Linux SL release 5.3 (Boron), Scientific Linux is a rebuild
> > of Redhat Enterprise
> >
> > *Ruby ve
On Apr 11, 4:57 pm, Mark Nelson wrote:
> Hello
>
> I am using the following software -
>
> *Operating System:
>
> *Scientific Linux SL release 5.3 (Boron), Scientific Linux is a rebuild
> of Redhat Enterprise
>
> *Ruby version:*
>
> ruby-shadow-1.4.1-7.el5.x86_64
> ruby-irb-1.8.5-5.el5_3.7.x86_6
I have added environment = production to all hosts puppet.conf file,
but still get the same intermittent errors.
I seem to be able to trigger this issue by.
1) Restarting Apache, so passenger and puppetmasterd are refreshed
2) Confirming there are no rack processes by running passenger-status
3) E
On Fri, May 14, 2010 at 5:11 PM, josbal wrote:
> Hi Nigel,
>
> Yes i am using environments. I have a production (default)
> environement and a testing environment.
>
> All my hosts us the production environment currently.
>
> Here is what my puppetmasterd puppet.conf file looks like:
>
> [main]
>
Hi Nigel,
Yes i am using environments. I have a production (default)
environement and a testing environment.
All my hosts us the production environment currently.
Here is what my puppetmasterd puppet.conf file looks like:
[main]
# Where Puppet stores dynamic and growing data.
# The defa
On Thu, May 13, 2010 at 7:55 PM, josbal wrote:
> Have you found a solution to this problem? I am having the same issue
> after upgrading to puppet 0.25.4 and passenger.
>
> The error message im getting is: Error 400 on SERVER: Not authorized
> to call find on /file_metadata/hp_psp/opsywnsr0099.au
Have you found a solution to this problem? I am having the same issue
after upgrading to puppet 0.25.4 and passenger.
The error message im getting is: Error 400 on SERVER: Not authorized
to call find on /file_metadata/hp_psp/opsywnsr0099.aus.optiver.com.pem
Could not retrieve file metadata for
pu
