Ramin: Yes, they were all checking in within a span of about two minutes.

Passenger tuning is something that needs doing I think, the failures seem 
to have calmed down a lot over night, and the runs are a tiny bit more 
spread out, but obviously I'd like to avoid having this problem in the 
future. Cleaning up the dashboard DB is also something that needs to be 
done.

Matt:
1) I didn't think so, but looking in my ps, I have the following:

puppet   17826     1  1 03:27 ?        00:04:37 master
www-data 18614  1350  0 Nov29 ?        00:00:00 /usr/sbin/apache2 -k start
root     18626  1350  0 Nov29 ?        00:00:06 
/usr/lib/phusion_passenger/ApplicationPoolServerExecutable 0 
/usr/lib/phusion_passenger/passenger-spawn-server  /usr/bin/ruby 
 /tmp/passenger.1350
root     18628 18626  0 Nov29 ?        00:02:19 Passenger spawn server
www-data 18638  1350  0 Nov29 ?        00:04:41 /usr/sbin/apache2 -k start
www-data 18639  1350  0 Nov29 ?        00:04:39 /usr/sbin/apache2 -k start

I thought the puppet master service was puppet-master, is that it up the 
top?

2) Apache is running and listening on 8140.

3) The server parameter hasn't been set, as puppet resolves to the puppet 
master on our DNS.

I'm not using Puppet DB for anything currently.

Thanks,
Gordon
On Thursday, 29 November 2012 19:09:41 UTC, Matthew Burgess wrote:
>
> On Thu, Nov 29, 2012 at 4:44 PM, GordonJB <[email protected]<javascript:>> 
> wrote: 
> > storeconfigs is not enabled on the master. 
> > 
> > Just realised I probably should have mentioned versions, I'm on master & 
> > nodes 3.0.1 and dashboard is 1.2.12. 
>
> Hmm, OK then.  Just so as the "let's not assume anything" base is covered; 
>
> Can you confirm that: 
>
> 1) You do not have any puppetmaster daemon's running? 
> 2) You have Apache running with a VirtualHost listening on port 8140? 
> 3) Your agent's puppet.conf file points to the correct server (via the 
> 'server' parameter)? 
>
> All of that can probably be confirmed easily enough by looking in 
> Apache's access logs to see the incoming connections from your 
> clients. 
>
> After that, it sounds like it might be Passenger tuning, which Ramin's 
> post covers. 
>
> One more thought; are you using PuppetDB for anything, just in case it 
> isn't Apache/Passenger contention? 
>
> Regards, 
>
> Matt. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/ofbc41s74OoJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to