Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Message from discussion using inetd/xinetd with puppetrun?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Peter Meier  
View profile  
 More options Jun 25 2008, 4:22 pm
From: Peter Meier <peter.me...@immerda.ch>
Date: Wed, 25 Jun 2008 22:22:20 +0200
Local: Wed, Jun 25 2008 4:22 pm
Subject: Re: [Puppet Users] Re: using inetd/xinetd with puppetrun?
Hi

>> We're not running it on any virtual hosts and are seeing large memory
>> footprints as well.  Also seeing really large footprints for the
>> puppetmaster (though I don't care as much about that).

> puppetmaster still leaks like a sieve for us.  :/  We have to restart it
> nightly to keep the system from running out of memory, and even that
> doesn't always work.  It's a problem that's been going on for a long time,
> unfortunately, and it's not at all clear what's causing it.

> We're currently running a slightly patched version of 0.24.4.

I have the same problem on centos 5 boxes, x86_64 as well i386, all
running in xenguests and 0.24.4 (as well the guests). I deploy a cron on
puppetmasters to restart puppetmaster every 4 hours. Just to be on the
safe side. As well I'm having some big problems with certain modules and
use cases [1]. However currently I simply get problems like these
working with workarounds. :-/

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND

 6562 root      15   0  183m  96m 2260 S    0 32.2   6:35.53 puppetd

on a host with 300mb ram.

I couldn't yet figure out what is causing this problem, but it certainly
exists. Unfortunately I don't know yet a lot how to debug problems like
these and I'm hoping that problems like these might go away with the
switch away from xmlrpc, as I could see a lot of memory problems there.
but now i'm just guessing.

however I certainly don't have anymore any corrupted file due to memory
leaks! :)

if anybody would like to dig into this problem and would like to have
data from hosts i'm having access to it, please ping me on irc
(duritong). I'd really like to help on this problem.

greets pete

[1]
http://groups.google.com/group/puppet-users/browse_thread/thread/26aa...


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google