On Fri, Apr 24, 2009 at 9:45 PM, Nigel Kersten nig...@google.com wrote:
...
manifest (planning to release this btw), and I've been amazed at just
how much better Passenger/Rack performs compared to
Pound/Nginx/Mongrel.
How much did you tweak the passenger options? (e.g.
On Wed, Apr 29, 2009 at 11:29 PM, Ohad Levy ohadl...@gmail.com wrote:
On Fri, Apr 24, 2009 at 9:45 PM, Nigel Kersten nig...@google.com wrote:
...
manifest (planning to release this btw), and I've been amazed at just
how much better Passenger/Rack performs compared to
Pound/Nginx/Mongrel.
On Fri, Apr 24, 2009 at 6:25 AM, threetee three...@gmail.com wrote:
On Apr 21, 12:19 am, Jean-Baptiste Quenot cara...@gmail.com wrote:
2009/4/6 Mike Renfro ren...@tntech.edu:
I'd normally expect that to work, but I just have puppet keep cron
running, and have a periodic cron job that
On Apr 21, 12:19 am, Jean-Baptiste Quenot cara...@gmail.com wrote:
2009/4/6 Mike Renfro ren...@tntech.edu:
I'd normally expect that to work, but I just have puppet keep cron
running, and have a periodic cron job that checks if puppet has died,
and if so, restarts it:
Interesting, but
Luke,
I was the guy who brought up puppet client fails last June at the SF meetup.
The memory footprint of the puppetd client in idle mode (between
triggers) was enough
of a reason to dump the always-on client, but I also found that they
crashed regularly whenever
there was any difficulty
We are using puppetd though cron, and it seems to me much more reliable and
much less resource hungry..
if you have more than a few clients, switch to mongrel/passenger.
WAN is not a real issue if its stable, of course it takes longer runs but...
cheers,
Ohad
On Tue, Apr 21, 2009 at 3:19 PM,
We had this problem when we hit the scaling wall running webrick. We then
moved our puppetmaster to a beefy server (dual quadcore with 16 GB ram).
Here we run six puppetmasterds with mongrel and stored config. On the same
server we run nginx. With this setup we can loop over a lot of servers
Ohad, I remember you were saiyng something about running puppet from
inetd - can you share some info? I really think that cron+inetd
combination would suit my company better than puppetd (which is
restarted every hour via cron)
/br
Stanislaw
On Apr 21, 10:03 am, Ohad Levy ohadl...@gmail.com
Jean-Baptiste Quenot wrote:
2009/4/6 Mike Renfro ren...@tntech.edu:
I'd normally expect that to work, but I just have puppet keep cron
running, and have a periodic cron job that checks if puppet has died,
and if so, restarts it:
Interesting, but why would you expect Puppet to die? Would
On Tue, Apr 21, 2009 at 6:56 AM, Mike Renfro ren...@tntech.edu wrote:
Jean-Baptiste Quenot wrote:
2009/4/6 Mike Renfro ren...@tntech.edu:
I'd normally expect that to work, but I just have puppet keep cron
running, and have a periodic cron job that checks if puppet has died,
and if so,
2009/4/21 Trevor Vaughan peiriann...@gmail.com:
I haven't had any problems with the client stability.
But, I'm also not using the 'file' type to copy files over the
'puppet://' protocol.
I'm using the puppet:// protocol extensively yes. As I noticed it was
very slow especially with
2009/4/21 Bjørn Dyre Dyresen bj...@dyresen.net:
We had this problem when we hit the scaling wall running webrick. We then
moved our puppetmaster to a beefy server (dual quadcore with 16 GB ram).
Here we run six puppetmasterds with mongrel and stored config. On the same
server we run nginx.
On Tue, Apr 21, 2009 at 05:30:54PM +0200, Jean-Baptiste Quenot wrote:
Are you hitting the OOM killer? It sounds like you might be.
I don't think so because there is nothing in syslog. The last
message from puppetd is Starting catalog run. And then it dies.
The OOM killer isn't a
On Apr 21, 2009, at 2:19 AM, Jean-Baptiste Quenot wrote:
2009/4/6 Mike Renfro ren...@tntech.edu:
I'd normally expect that to work, but I just have puppet keep cron
running, and have a periodic cron job that checks if puppet has died,
and if so, restarts it:
Interesting, but why would you
Hi,
You can find a working daemon here:
http://github.com/ohadlevy/puppet/tree/puppetlisten under the
ext/puppetlisten subdir.
It doesn't use inetd as ruby socket implementation does not work inet, I'm
considering rewriting it in c but no real reason / time for now...
search the mailing list
15 matches
Mail list logo
