On Fri, Nov 30, 2012 at 4:34 PM, GordonJB wrote:
> Also, 'lsof -i :8140' returned nothing.
OK, let's start there then. You should have an
/etc/httpd/conf.d/puppetmaster.conf that looks somewhat like the one
at
http://docs.puppetlabs.com/guides/passenger.html#apache-configuration-for-puppet-024
Killing apache seemed to get rid of that master process. Restarting the
apache server however brought back another master process after a couple of
minutes:
puppet8549 1 22 16:25 ?00:00:03 master
I think this was due to clients checking in, however they did not
disappear. I cur
On Fri, Nov 30, 2012 at 3:03 PM, GordonJB wrote:
> I am, but there were standalone processes I'm not sure how to kill and
> disable.
>
> I've currently got (from ps -ef | grep puppet):
> root 1296 1 0 11:34 ?00:00:13 /usr/bin/ruby
> /usr/bin/puppet agent
> puppet2246 1 0
t; To: puppet...@googlegroups.com
> Sent: Friday, November 30, 2012 9:24:54 AM
> Subject: Re: [Puppet Users] Simultaneous Client updates
>
> On Fri, Nov 30, 2012 at 2:08 PM, GordonJB >
> wrote:
> > I don't suppose you know how to stop the service on 3.0? There is
bbes)
- Original Message -
From: "Matthew Burgess"
To: puppet-users@googlegroups.com
Sent: Friday, November 30, 2012 9:24:54 AM
Subject: Re: [Puppet Users] Simultaneous Client updates
On Fri, Nov 30, 2012 at 2:08 PM, GordonJB wrote:
> I don't suppose you know how to s
On Fri, Nov 30, 2012 at 2:08 PM, GordonJB wrote:
> I don't suppose you know how to stop the service on 3.0? There is no
> puppetmaster process left, just puppet, and I'd like to keep the puppet
> client running!
If there's no master process left, then it is stopped, surely?
Here's an output of '
I don't suppose you know how to stop the service on 3.0? There is no
puppetmaster process left, just puppet, and I'd like to keep the puppet
client running!
Thanks, Gordon
On Friday, 30 November 2012 12:02:06 UTC, Matthew Burgess wrote:
>
> On Fri, Nov 30, 2012 at 11:29 AM, GordonJB >
> wrote:
On Fri, Nov 30, 2012 at 11:29 AM, GordonJB wrote:
> 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
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
futur
On Thu, Nov 29, 2012 at 4:44 PM, GordonJB 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 con
On 11/29/2012 8:44 AM, GordonJB 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.
I'm betting that most of your servers are checking in at the same time.
Half of the clients make it
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.
On Thursday, 29 November 2012 16:37:56 UTC, Matthew Burgess wrote:
>
> On Thu, Nov 29, 2012 at 4:15 PM, GordonJB >
> wrote:
> > I believe I'v
On Thu, Nov 29, 2012 at 4:15 PM, GordonJB wrote:
> I believe I've set up Apache/Passenger correctly, yes. Running
> passenger-status shows 12 processes running under the
> /usr/share/puppet/rack/puppetmasterd domain. Would setting up cron jobs be
> on top of this passenger configuration, or should
I believe I've set up Apache/Passenger correctly, yes. Running
passenger-status shows 12 processes running under the
/usr/share/puppet/rack/puppetmasterd domain. Would setting up cron jobs be
on top of this passenger configuration, or should Apache/Passenger be
enough?
Thanks,
Gordon
On Thur
On Thu, Nov 29, 2012 at 3:35 PM, GordonJB wrote:
> Hi all,
>
> I'm currently getting a lot of update failures showing up with no logs in
> the dashboard. This happens for about half of our 28 nodes, about once an
> hour. When re-run half an hour later, everything seems fine.
>
> Through a combinat
Hi all,
I'm currently getting a lot of update failures showing up with no logs in
the dashboard. This happens for about half of our 28 nodes, about once an
hour. When re-run half an hour later, everything seems fine.
Through a combination of server restarts and our Puppet master locking up
ent
16 matches
Mail list logo
