thr3ads.net - Puppet users - [Puppet Users] puppetmasterd stops listening on port 8140 [Sep 2008]

If this information is useful, please help other people find it:
Share via:

josh

2008-Sep-12 13:58 UTC

[Puppet Users] puppetmasterd stops listening on port 8140

Hello,
I am running puppet-0.24.5 with facter-1.5.2 and ruby 1.8.6
(2007-09-23 patchlevel 110) on OpenSolaris snv_91 on a Sun X2200.

Right now I have roughly 250 client or so talking to the puppetmaster
server, but after anywhere from a few minutes to a few hours, the
puppetmaster server stops listening on port 8140, even though the
puppetmasterd service is still running.

root@redmanager2:~> facter --version
1.5.2
root@redmanager2:~> puppetmasterd --version
0.24.5
root@redmanager2:~> ruby --version
ruby 1.8.6 (2007-09-23 patchlevel 110) [i386-solaris2.11]

I''ve enabled logging for puppetmasterd via the "logdest =
/var/puppet/
log/puppet.log" but I don''t see anything after "Listening on
port
8140"

Is there any way to either get more logging from puppetmasterd or try
and figure out why this is happening?  I''m in the middle of a puppet
rollout to roughly 800 hosts and the server needs to be stable.

Here is the puppet.conf:

[puppetmasterd]
    genconfig = false
    factdest = /var/puppet/facts
    statedir = /var/puppet/state
    libdir = /var/puppet/lib
    plugindest = /var/puppet/lib
    logdir = /var/puppet/log
    ssldir = /etc/puppet/ssl
    name = puppetmasterd
    factpath = /var/puppet/facts
    color = false
    rundir = /var/puppet/run
    pluginpath = /var/puppet/plugins
    mkusers = true
    bucketdir = /var/puppet/bucket
    yamldir = /var/puppet/yaml
    group = puppet
    masterhttplog = /var/puppet/log/masterhttp.log
    manifestdir = /etc/puppet/manifests
    ca = true
    config = /etc/puppet/puppet.conf
    manifest = /etc/puppet/manifests/site.pp
    user = puppet
    modulepath = /etc/puppet/modules:/usr/share/puppet/modules
    masterlog = /var/puppet/log/puppetmaster.log
    railslog = /var/puppet/log/rails.log
    caprivatedir = /etc/puppet/ssl/ca/private
    capass = /etc/puppet/ssl/ca/private/ca.pass
    serial = /etc/puppet/ssl/ca/serial
    cadir = /etc/puppet/ssl/ca
    capub = /etc/puppet/ssl/ca/ca_pub.pem
    csrdir = /etc/puppet/ssl/ca/requests
    autosign = /etc/puppet/autosign.conf
    cert_inventory = /etc/puppet/ssl/ca/inventory.txt
    cacert = /etc/puppet/ssl/ca/ca_crt.pem
    cacrl = /etc/puppet/ssl/ca/ca_crl.pem
    signeddir = /etc/puppet/ssl/ca/signed
    cakey = /etc/puppet/ssl/ca/ca_key.pem
    publickeydir = /etc/puppet/ssl/public_keys
    passfile = /etc/puppet/ssl/private/password
    hostprivkey = /etc/puppet/ssl/private_keys/xxxt.pem
    privatekeydir = /etc/puppet/ssl/private_keys
    hostcsr = /etc/puppet/ssl/csr_xxxx.pem
    hostpubkey = /etc/puppet/ssl/public_keys/xxxx.pem
    certdir = /etc/puppet/ssl/certs
    privatedir = /etc/puppet/ssl/private
    hostcert = /etc/puppet/ssl/certs/xxxx.pem
    localcacert = /etc/puppet/ssl/certs/ca.pem
    reportdir = /var/puppet/reports
    statefile = /var/puppet/state/state.yaml
    httplog = /var/puppet/log/http.log
    report = true
    classfile = /var/puppet/state/classes.txt
    splaylimit = 1800
    reportserver = 10.1.2.208
    ca_server = 10.1.2.208
    localconfig = /var/puppet/state/localconfig
    puppetdlockfile = /var/puppet/state/puppetdlock
    puppetdlog = /var/puppet/log/puppetd.log
    ca_port = 8140
    reportfrom = jrivel@reliantsec.net
    tagmap = /etc/puppet/tagmail.conf
    templatedir = /var/puppet/templates
    rrdinterval = 1800
    rrddir = /var/puppet/rrd
    rrdgraph = true
    fileserverconfig = /etc/puppet/fileserver.conf
    graph = true
    graphdir = /var/puppet/state/graphs
    clientbucketdir = /var/puppet/clientbucket
    logdest = /var/puppet/log/puppet.log

Thanks as always,
Josh


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Andrew Shafer

2008-Sep-12 16:59 UTC

head link

[Puppet Users] Re: puppetmasterd stops listening on port 8140

Josh,

You should get more logs if you start puppetmasterd with --debug.

Are you using Webrick or Mongrel with puppetmasterd?  (if you are using
Webrick, it might be time for Mongrel)

What is your average catalog compilation time for client requests?

I''m not certain what you mean by ''stops listening'',
but I believe the
process is becoming unresponsive.

Andrew


On Fri, Sep 12, 2008 at 7:58 AM, josh <dorqus@gmail.com> wrote:
>
> Hello,
> I am running puppet-0.24.5 with facter-1.5.2 and ruby 1.8.6
> (2007-09-23 patchlevel 110) on OpenSolaris snv_91 on a Sun X2200.
>
> Right now I have roughly 250 client or so talking to the puppetmaster
> server, but after anywhere from a few minutes to a few hours, the
> puppetmaster server stops listening on port 8140, even though the
> puppetmasterd service is still running.
>
> root@redmanager2:~> facter --version
> 1.5.2
> root@redmanager2:~> puppetmasterd --version
> 0.24.5
> root@redmanager2:~> ruby --version
> ruby 1.8.6 (2007-09-23 patchlevel 110) [i386-solaris2.11]
>
> I''ve enabled logging for puppetmasterd via the "logdest =
/var/puppet/
> log/puppet.log" but I don''t see anything after
"Listening on port
> 8140"
>
> Is there any way to either get more logging from puppetmasterd or try
> and figure out why this is happening?  I''m in the middle of a
puppet
> rollout to roughly 800 hosts and the server needs to be stable.
>
> Here is the puppet.conf:
>
> [puppetmasterd]
>    genconfig = false
>    factdest = /var/puppet/facts
>    statedir = /var/puppet/state
>    libdir = /var/puppet/lib
>    plugindest = /var/puppet/lib
>    logdir = /var/puppet/log
>    ssldir = /etc/puppet/ssl
>    name = puppetmasterd
>    factpath = /var/puppet/facts
>    color = false
>    rundir = /var/puppet/run
>    pluginpath = /var/puppet/plugins
>    mkusers = true
>    bucketdir = /var/puppet/bucket
>    yamldir = /var/puppet/yaml
>    group = puppet
>    masterhttplog = /var/puppet/log/masterhttp.log
>    manifestdir = /etc/puppet/manifests
>    ca = true
>    config = /etc/puppet/puppet.conf
>    manifest = /etc/puppet/manifests/site.pp
>    user = puppet
>    modulepath = /etc/puppet/modules:/usr/share/puppet/modules
>    masterlog = /var/puppet/log/puppetmaster.log
>    railslog = /var/puppet/log/rails.log
>    caprivatedir = /etc/puppet/ssl/ca/private
>    capass = /etc/puppet/ssl/ca/private/ca.pass
>    serial = /etc/puppet/ssl/ca/serial
>    cadir = /etc/puppet/ssl/ca
>    capub = /etc/puppet/ssl/ca/ca_pub.pem
>    csrdir = /etc/puppet/ssl/ca/requests
>    autosign = /etc/puppet/autosign.conf
>    cert_inventory = /etc/puppet/ssl/ca/inventory.txt
>    cacert = /etc/puppet/ssl/ca/ca_crt.pem
>    cacrl = /etc/puppet/ssl/ca/ca_crl.pem
>    signeddir = /etc/puppet/ssl/ca/signed
>    cakey = /etc/puppet/ssl/ca/ca_key.pem
>    publickeydir = /etc/puppet/ssl/public_keys
>    passfile = /etc/puppet/ssl/private/password
>    hostprivkey = /etc/puppet/ssl/private_keys/xxxt.pem
>    privatekeydir = /etc/puppet/ssl/private_keys
>    hostcsr = /etc/puppet/ssl/csr_xxxx.pem
>    hostpubkey = /etc/puppet/ssl/public_keys/xxxx.pem
>    certdir = /etc/puppet/ssl/certs
>    privatedir = /etc/puppet/ssl/private
>    hostcert = /etc/puppet/ssl/certs/xxxx.pem
>    localcacert = /etc/puppet/ssl/certs/ca.pem
>    reportdir = /var/puppet/reports
>    statefile = /var/puppet/state/state.yaml
>    httplog = /var/puppet/log/http.log
>    report = true
>    classfile = /var/puppet/state/classes.txt
>    splaylimit = 1800
>    reportserver = 10.1.2.208
>    ca_server = 10.1.2.208
>    localconfig = /var/puppet/state/localconfig
>    puppetdlockfile = /var/puppet/state/puppetdlock
>    puppetdlog = /var/puppet/log/puppetd.log
>    ca_port = 8140
>    reportfrom = jrivel@reliantsec.net
>    tagmap = /etc/puppet/tagmail.conf
>    templatedir = /var/puppet/templates
>    rrdinterval = 1800
>    rrddir = /var/puppet/rrd
>    rrdgraph = true
>    fileserverconfig = /etc/puppet/fileserver.conf
>    graph = true
>    graphdir = /var/puppet/state/graphs
>    clientbucketdir = /var/puppet/clientbucket
>    logdest = /var/puppet/log/puppet.log
>
> Thanks as always,
> Josh
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

josh

2008-Sep-12 17:09 UTC

head link

[Puppet Users] Re: puppetmasterd stops listening on port 8140

Andrew,
I am using Webrick ,and yes, the process becomes unresponsive.
I ran puppetmasterd in --no-daemonize mode, and nothing useful, after
a certain amount of time just no more log data was being generated.
It''s almost like it''s not reading my puppet.conf (Do I need to
call it
puppetmasterd.conf?  From what I understand it shouldn''t matter)

And yes, I''m reading on page 142 of the "Advanced Puppet"
book that
WEBrick can''t scale well. (Thanks James for the book - I just got it
yesterday and it''s quite helpful).  Time to crank open mongrel and see
if that helps.

Josh

On Sep 12, 12:59 pm, "Andrew Shafer" <and...@reductivelabs.com>
wrote:> Josh,
>
> You should get more logs if you start puppetmasterd with --debug.
>
> Are you using Webrick or Mongrel with puppetmasterd?  (if you are using
> Webrick, it might be time for Mongrel)
>
> What is your average catalog compilation time for client requests?
>
> I''m not certain what you mean by ''stops
listening'', but I believe the
> process is becoming unresponsive.
>
> Andrew
>
> On Fri, Sep 12, 2008 at 7:58 AM, josh <dor...@gmail.com> wrote:
>
> > Hello,
> > I am running puppet-0.24.5 with facter-1.5.2 and ruby 1.8.6
> > (2007-09-23 patchlevel 110) on OpenSolaris snv_91 on a Sun X2200.
>
> > Right now I have roughly 250 client or so talking to the puppetmaster
> > server, but after anywhere from a few minutes to a few hours, the
> > puppetmaster server stops listening on port 8140, even though the
> > puppetmasterd service is still running.
>
> > root@redmanager2:~> facter --version
> > 1.5.2
> > root@redmanager2:~> puppetmasterd --version
> > 0.24.5
> > root@redmanager2:~> ruby --version
> > ruby 1.8.6 (2007-09-23 patchlevel 110) [i386-solaris2.11]
>
> > I''ve enabled logging for puppetmasterd via the "logdest
= /var/puppet/
> > log/puppet.log" but I don''t see anything after
"Listening on port
> > 8140"
>
> > Is there any way to either get more logging from puppetmasterd or try
> > and figure out why this is happening?  I''m in the middle of a
puppet
> > rollout to roughly 800 hosts and the server needs to be stable.
>
> > Here is the puppet.conf:
>
> > [puppetmasterd]
> >    genconfig = false
> >    factdest = /var/puppet/facts
> >    statedir = /var/puppet/state
> >    libdir = /var/puppet/lib
> >    plugindest = /var/puppet/lib
> >    logdir = /var/puppet/log
> >    ssldir = /etc/puppet/ssl
> >    name = puppetmasterd
> >    factpath = /var/puppet/facts
> >    color = false
> >    rundir = /var/puppet/run
> >    pluginpath = /var/puppet/plugins
> >    mkusers = true
> >    bucketdir = /var/puppet/bucket
> >    yamldir = /var/puppet/yaml
> >    group = puppet
> >    masterhttplog = /var/puppet/log/masterhttp.log
> >    manifestdir = /etc/puppet/manifests
> >    ca = true
> >    config = /etc/puppet/puppet.conf
> >    manifest = /etc/puppet/manifests/site.pp
> >    user = puppet
> >    modulepath = /etc/puppet/modules:/usr/share/puppet/modules
> >    masterlog = /var/puppet/log/puppetmaster.log
> >    railslog = /var/puppet/log/rails.log
> >    caprivatedir = /etc/puppet/ssl/ca/private
> >    capass = /etc/puppet/ssl/ca/private/ca.pass
> >    serial = /etc/puppet/ssl/ca/serial
> >    cadir = /etc/puppet/ssl/ca
> >    capub = /etc/puppet/ssl/ca/ca_pub.pem
> >    csrdir = /etc/puppet/ssl/ca/requests
> >    autosign = /etc/puppet/autosign.conf
> >    cert_inventory = /etc/puppet/ssl/ca/inventory.txt
> >    cacert = /etc/puppet/ssl/ca/ca_crt.pem
> >    cacrl = /etc/puppet/ssl/ca/ca_crl.pem
> >    signeddir = /etc/puppet/ssl/ca/signed
> >    cakey = /etc/puppet/ssl/ca/ca_key.pem
> >    publickeydir = /etc/puppet/ssl/public_keys
> >    passfile = /etc/puppet/ssl/private/password
> >    hostprivkey = /etc/puppet/ssl/private_keys/xxxt.pem
> >    privatekeydir = /etc/puppet/ssl/private_keys
> >    hostcsr = /etc/puppet/ssl/csr_xxxx.pem
> >    hostpubkey = /etc/puppet/ssl/public_keys/xxxx.pem
> >    certdir = /etc/puppet/ssl/certs
> >    privatedir = /etc/puppet/ssl/private
> >    hostcert = /etc/puppet/ssl/certs/xxxx.pem
> >    localcacert = /etc/puppet/ssl/certs/ca.pem
> >    reportdir = /var/puppet/reports
> >    statefile = /var/puppet/state/state.yaml
> >    httplog = /var/puppet/log/http.log
> >    report = true
> >    classfile = /var/puppet/state/classes.txt
> >    splaylimit = 1800
> >    reportserver = 10.1.2.208
> >    ca_server = 10.1.2.208
> >    localconfig = /var/puppet/state/localconfig
> >    puppetdlockfile = /var/puppet/state/puppetdlock
> >    puppetdlog = /var/puppet/log/puppetd.log
> >    ca_port = 8140
> >    reportfrom = jri...@reliantsec.net
> >    tagmap = /etc/puppet/tagmail.conf
> >    templatedir = /var/puppet/templates
> >    rrdinterval = 1800
> >    rrddir = /var/puppet/rrd
> >    rrdgraph = true
> >    fileserverconfig = /etc/puppet/fileserver.conf
> >    graph = true
> >    graphdir = /var/puppet/state/graphs
> >    clientbucketdir = /var/puppet/clientbucket
> >    logdest = /var/puppet/log/puppet.log
>
> > Thanks as always,
> > Josh--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Andrew Shafer

2008-Sep-12 17:29 UTC

head link

[Puppet Users] Re: puppetmasterd stops listening on port 8140

Josh,

When Webrick gets over a certain threshold, it just falls over.

Mongrel degrades more gracefully and can recover.

Depending on how complicated your configurations are and how long they
compile, you might need to run more than one instance of mongrel.

Regards,
Andrew

On Fri, Sep 12, 2008 at 11:09 AM, josh <dorqus@gmail.com> wrote:
>
> Andrew,
> I am using Webrick ,and yes, the process becomes unresponsive.
> I ran puppetmasterd in --no-daemonize mode, and nothing useful, after
> a certain amount of time just no more log data was being generated.
> It''s almost like it''s not reading my puppet.conf (Do I
need to call it
> puppetmasterd.conf?  From what I understand it shouldn''t matter)
>
> And yes, I''m reading on page 142 of the "Advanced
Puppet" book that
> WEBrick can''t scale well. (Thanks James for the book - I just got
it
> yesterday and it''s quite helpful).  Time to crank open mongrel and
see
> if that helps.
>
> Josh
>
> On Sep 12, 12:59 pm, "Andrew Shafer"
<and...@reductivelabs.com> wrote:
> > Josh,
> >
> > You should get more logs if you start puppetmasterd with --debug.
> >
> > Are you using Webrick or Mongrel with puppetmasterd?  (if you are
using
> > Webrick, it might be time for Mongrel)
> >
> > What is your average catalog compilation time for client requests?
> >
> > I''m not certain what you mean by ''stops
listening'', but I believe the
> > process is becoming unresponsive.
> >
> > Andrew
> >
> > On Fri, Sep 12, 2008 at 7:58 AM, josh <dor...@gmail.com> wrote:
> >
> > > Hello,
> > > I am running puppet-0.24.5 with facter-1.5.2 and ruby 1.8.6
> > > (2007-09-23 patchlevel 110) on OpenSolaris snv_91 on a Sun X2200.
> >
> > > Right now I have roughly 250 client or so talking to the
puppetmaster
> > > server, but after anywhere from a few minutes to a few hours, the
> > > puppetmaster server stops listening on port 8140, even though the
> > > puppetmasterd service is still running.
> >
> > > root@redmanager2:~> facter --version
> > > 1.5.2
> > > root@redmanager2:~> puppetmasterd --version
> > > 0.24.5
> > > root@redmanager2:~> ruby --version
> > > ruby 1.8.6 (2007-09-23 patchlevel 110) [i386-solaris2.11]
> >
> > > I''ve enabled logging for puppetmasterd via the
"logdest = /var/puppet/
> > > log/puppet.log" but I don''t see anything after
"Listening on port
> > > 8140"
> >
> > > Is there any way to either get more logging from puppetmasterd or
try
> > > and figure out why this is happening?  I''m in the middle
of a puppet
> > > rollout to roughly 800 hosts and the server needs to be stable.
> >
> > > Here is the puppet.conf:
> >
> > > [puppetmasterd]
> > >    genconfig = false
> > >    factdest = /var/puppet/facts
> > >    statedir = /var/puppet/state
> > >    libdir = /var/puppet/lib
> > >    plugindest = /var/puppet/lib
> > >    logdir = /var/puppet/log
> > >    ssldir = /etc/puppet/ssl
> > >    name = puppetmasterd
> > >    factpath = /var/puppet/facts
> > >    color = false
> > >    rundir = /var/puppet/run
> > >    pluginpath = /var/puppet/plugins
> > >    mkusers = true
> > >    bucketdir = /var/puppet/bucket
> > >    yamldir = /var/puppet/yaml
> > >    group = puppet
> > >    masterhttplog = /var/puppet/log/masterhttp.log
> > >    manifestdir = /etc/puppet/manifests
> > >    ca = true
> > >    config = /etc/puppet/puppet.conf
> > >    manifest = /etc/puppet/manifests/site.pp
> > >    user = puppet
> > >    modulepath = /etc/puppet/modules:/usr/share/puppet/modules
> > >    masterlog = /var/puppet/log/puppetmaster.log
> > >    railslog = /var/puppet/log/rails.log
> > >    caprivatedir = /etc/puppet/ssl/ca/private
> > >    capass = /etc/puppet/ssl/ca/private/ca.pass
> > >    serial = /etc/puppet/ssl/ca/serial
> > >    cadir = /etc/puppet/ssl/ca
> > >    capub = /etc/puppet/ssl/ca/ca_pub.pem
> > >    csrdir = /etc/puppet/ssl/ca/requests
> > >    autosign = /etc/puppet/autosign.conf
> > >    cert_inventory = /etc/puppet/ssl/ca/inventory.txt
> > >    cacert = /etc/puppet/ssl/ca/ca_crt.pem
> > >    cacrl = /etc/puppet/ssl/ca/ca_crl.pem
> > >    signeddir = /etc/puppet/ssl/ca/signed
> > >    cakey = /etc/puppet/ssl/ca/ca_key.pem
> > >    publickeydir = /etc/puppet/ssl/public_keys
> > >    passfile = /etc/puppet/ssl/private/password
> > >    hostprivkey = /etc/puppet/ssl/private_keys/xxxt.pem
> > >    privatekeydir = /etc/puppet/ssl/private_keys
> > >    hostcsr = /etc/puppet/ssl/csr_xxxx.pem
> > >    hostpubkey = /etc/puppet/ssl/public_keys/xxxx.pem
> > >    certdir = /etc/puppet/ssl/certs
> > >    privatedir = /etc/puppet/ssl/private
> > >    hostcert = /etc/puppet/ssl/certs/xxxx.pem
> > >    localcacert = /etc/puppet/ssl/certs/ca.pem
> > >    reportdir = /var/puppet/reports
> > >    statefile = /var/puppet/state/state.yaml
> > >    httplog = /var/puppet/log/http.log
> > >    report = true
> > >    classfile = /var/puppet/state/classes.txt
> > >    splaylimit = 1800
> > >    reportserver = 10.1.2.208
> > >    ca_server = 10.1.2.208
> > >    localconfig = /var/puppet/state/localconfig
> > >    puppetdlockfile = /var/puppet/state/puppetdlock
> > >    puppetdlog = /var/puppet/log/puppetd.log
> > >    ca_port = 8140
> > >    reportfrom = jri...@reliantsec.net
> > >    tagmap = /etc/puppet/tagmail.conf
> > >    templatedir = /var/puppet/templates
> > >    rrdinterval = 1800
> > >    rrddir = /var/puppet/rrd
> > >    rrdgraph = true
> > >    fileserverconfig = /etc/puppet/fileserver.conf
> > >    graph = true
> > >    graphdir = /var/puppet/state/graphs
> > >    clientbucketdir = /var/puppet/clientbucket
> > >    logdest = /var/puppet/log/puppet.log
> >
> > > Thanks as always,
> > > Josh
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

josh

2008-Sep-12 17:43 UTC

head link

[Puppet Users] Re: puppetmasterd stops listening on port 8140

Thanks Andrew.

I''m compiling nginx to use with mongrel right now, and I''m
going to
run four mongrel instances and see how that works out for me.

Josh


On Sep 12, 1:29 pm, "Andrew Shafer" <and...@reductivelabs.com>
wrote:> Josh,
>
> When Webrick gets over a certain threshold, it just falls over.
>
> Mongrel degrades more gracefully and can recover.
>
> Depending on how complicated your configurations are and how long they
> compile, you might need to run more than one instance of mongrel.
>
> Regards,
> Andrew
>
> On Fri, Sep 12, 2008 at 11:09 AM, josh <dor...@gmail.com> wrote:
>
> > Andrew,
> > I am using Webrick ,and yes, the process becomes unresponsive.
> > I ran puppetmasterd in --no-daemonize mode, and nothing useful, after
> > a certain amount of time just no more log data was being generated.
> > It''s almost like it''s not reading my puppet.conf (Do
I need to call it
> > puppetmasterd.conf?  From what I understand it shouldn''t
matter)
>
> > And yes, I''m reading on page 142 of the "Advanced
Puppet" book that
> > WEBrick can''t scale well. (Thanks James for the book - I just
got it
> > yesterday and it''s quite helpful).  Time to crank open
mongrel and see
> > if that helps.
>
> > Josh
>
> > On Sep 12, 12:59 pm, "Andrew Shafer"
<and...@reductivelabs.com> wrote:
> > > Josh,
>
> > > You should get more logs if you start puppetmasterd with --debug.
>
> > > Are you using Webrick or Mongrel with puppetmasterd?  (if you are
using
> > > Webrick, it might be time for Mongrel)
>
> > > What is your average catalog compilation time for client
requests?
>
> > > I''m not certain what you mean by ''stops
listening'', but I believe the
> > > process is becoming unresponsive.
>
> > > Andrew
>
> > > On Fri, Sep 12, 2008 at 7:58 AM, josh <dor...@gmail.com>
wrote:
>
> > > > Hello,
> > > > I am running puppet-0.24.5 with facter-1.5.2 and ruby 1.8.6
> > > > (2007-09-23 patchlevel 110) on OpenSolaris snv_91 on a Sun
X2200.
>
> > > > Right now I have roughly 250 client or so talking to the
puppetmaster
> > > > server, but after anywhere from a few minutes to a few
hours, the
> > > > puppetmaster server stops listening on port 8140, even
though the
> > > > puppetmasterd service is still running.
>
> > > > root@redmanager2:~> facter --version
> > > > 1.5.2
> > > > root@redmanager2:~> puppetmasterd --version
> > > > 0.24.5
> > > > root@redmanager2:~> ruby --version
> > > > ruby 1.8.6 (2007-09-23 patchlevel 110) [i386-solaris2.11]
>
> > > > I''ve enabled logging for puppetmasterd via the
"logdest = /var/puppet/
> > > > log/puppet.log" but I don''t see anything after
"Listening on port
> > > > 8140"
>
> > > > Is there any way to either get more logging from
puppetmasterd or try
> > > > and figure out why this is happening?  I''m in the
middle of a puppet
> > > > rollout to roughly 800 hosts and the server needs to be
stable.
>
> > > > Here is the puppet.conf:
>
> > > > [puppetmasterd]
> > > >    genconfig = false
> > > >    factdest = /var/puppet/facts
> > > >    statedir = /var/puppet/state
> > > >    libdir = /var/puppet/lib
> > > >    plugindest = /var/puppet/lib
> > > >    logdir = /var/puppet/log
> > > >    ssldir = /etc/puppet/ssl
> > > >    name = puppetmasterd
> > > >    factpath = /var/puppet/facts
> > > >    color = false
> > > >    rundir = /var/puppet/run
> > > >    pluginpath = /var/puppet/plugins
> > > >    mkusers = true
> > > >    bucketdir = /var/puppet/bucket
> > > >    yamldir = /var/puppet/yaml
> > > >    group = puppet
> > > >    masterhttplog = /var/puppet/log/masterhttp.log
> > > >    manifestdir = /etc/puppet/manifests
> > > >    ca = true
> > > >    config = /etc/puppet/puppet.conf
> > > >    manifest = /etc/puppet/manifests/site.pp
> > > >    user = puppet
> > > >    modulepath =
/etc/puppet/modules:/usr/share/puppet/modules
> > > >    masterlog = /var/puppet/log/puppetmaster.log
> > > >    railslog = /var/puppet/log/rails.log
> > > >    caprivatedir = /etc/puppet/ssl/ca/private
> > > >    capass = /etc/puppet/ssl/ca/private/ca.pass
> > > >    serial = /etc/puppet/ssl/ca/serial
> > > >    cadir = /etc/puppet/ssl/ca
> > > >    capub = /etc/puppet/ssl/ca/ca_pub.pem
> > > >    csrdir = /etc/puppet/ssl/ca/requests
> > > >    autosign = /etc/puppet/autosign.conf
> > > >    cert_inventory = /etc/puppet/ssl/ca/inventory.txt
> > > >    cacert = /etc/puppet/ssl/ca/ca_crt.pem
> > > >    cacrl = /etc/puppet/ssl/ca/ca_crl.pem
> > > >    signeddir = /etc/puppet/ssl/ca/signed
> > > >    cakey = /etc/puppet/ssl/ca/ca_key.pem
> > > >    publickeydir = /etc/puppet/ssl/public_keys
> > > >    passfile = /etc/puppet/ssl/private/password
> > > >    hostprivkey = /etc/puppet/ssl/private_keys/xxxt.pem
> > > >    privatekeydir = /etc/puppet/ssl/private_keys
> > > >    hostcsr = /etc/puppet/ssl/csr_xxxx.pem
> > > >    hostpubkey = /etc/puppet/ssl/public_keys/xxxx.pem
> > > >    certdir = /etc/puppet/ssl/certs
> > > >    privatedir = /etc/puppet/ssl/private
> > > >    hostcert = /etc/puppet/ssl/certs/xxxx.pem
> > > >    localcacert = /etc/puppet/ssl/certs/ca.pem
> > > >    reportdir = /var/puppet/reports
> > > >    statefile = /var/puppet/state/state.yaml
> > > >    httplog = /var/puppet/log/http.log
> > > >    report = true
> > > >    classfile = /var/puppet/state/classes.txt
> > > >    splaylimit = 1800
> > > >    reportserver = 10.1.2.208
> > > >    ca_server = 10.1.2.208
> > > >    localconfig = /var/puppet/state/localconfig
> > > >    puppetdlockfile = /var/puppet/state/puppetdlock
> > > >    puppetdlog = /var/puppet/log/puppetd.log
> > > >    ca_port = 8140
> > > >    reportfrom = jri...@reliantsec.net
> > > >    tagmap = /etc/puppet/tagmail.conf
> > > >    templatedir = /var/puppet/templates
> > > >    rrdinterval = 1800
> > > >    rrddir = /var/puppet/rrd
> > > >    rrdgraph = true
> > > >    fileserverconfig = /etc/puppet/fileserver.conf
> > > >    graph = true
> > > >    graphdir = /var/puppet/state/graphs
> > > >    clientbucketdir = /var/puppet/clientbucket
> > > >    logdest = /var/puppet/log/puppet.log
>
> > > > Thanks as always,
> > > > Josh--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Richard

2008-Sep-13 11:19 UTC

head link

[Puppet Users] Re: puppetmasterd stops listening on port 8140

On Sep 12, 9:58 am, josh <dor...@gmail.com> wrote:> Hello,
> I am running puppet-0.24.5 with facter-1.5.2 and ruby 1.8.6
> (2007-09-23 patchlevel 110) on OpenSolaris snv_91 on a Sun X2200.
>
> Right now I have roughly 250 client or so talking to the puppetmaster
> server, but after anywhere from a few minutes to a few hours, the
> puppetmaster server stops listening on port 8140, even though the
> puppetmasterd service is still running.
I had this exact same problem with a brand new installation of Puppet
and only 2 clients.  After a while, sometime minutes, Puppetmaster
just stopped listening.  No log data.  No nothing.  :/  So I installed
Mongrel, created a little Apache2 config, and told Debian how many
Mongrel processes I wanted.  It was actually very simple, much easier
than I expected.  If your running Debian Lenny you''ve got it made in
the shade.  :)

Ever since moving to Mongrel with an Apache2 proxy it has ran
perfectly.  Good luck!

Later...
  Richard
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

josh

2008-Sep-14 21:41 UTC

head link

[Puppet Users] Re: puppetmasterd stops listening on port 8140

Thanks, I tried using nginx for the proxy, but it was having SSL
issues passing the certs through (I think)  There''s already Apache2 on
the puppet server, so I just need to re-compile it for some additional
modules and then I''ll give that a shot using the documentation on the
wiki.  I wish we were running some flavor of Linux, this OpenSolaris
thing is driving me crazy.

On Sep 13, 7:19 am, Richard <rnh...@gmail.com>
wrote:> On Sep 12, 9:58 am, josh <dor...@gmail.com> wrote:
>
> > Hello,
> > I am running puppet-0.24.5 with facter-1.5.2 and ruby 1.8.6
> > (2007-09-23 patchlevel 110) on OpenSolaris snv_91 on a Sun X2200.
>
> > Right now I have roughly 250 client or so talking to the puppetmaster
> > server, but after anywhere from a few minutes to a few hours, the
> > puppetmaster server stops listening on port 8140, even though the
> > puppetmasterd service is still running.
>
> I had this exact same problem with a brand new installation of Puppet
> and only 2 clients.  After a while, sometime minutes, Puppetmaster
> just stopped listening.  No log data.  No nothing.  :/  So I installed
> Mongrel, created a little Apache2 config, and told Debian how many
> Mongrel processes I wanted.  It was actually very simple, much easier
> than I expected.  If your running Debian Lenny you''ve got it made
in
> the shade.  :)
>
> Ever since moving to Mongrel with an Apache2 proxy it has ran
> perfectly.  Good luck!
>
> Later...
>   Richard--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

josh

2008-Sep-15 15:02 UTC

head link

[Puppet Users] Re: puppetmasterd stops listening on port 8140

Looks like it''s working (for now) with Apache2 fronting four mongrel
instances.  Now I need to work on getting the proper firewall rules to
the proper machines, but that''s just me needing to think clearly.


On Sep 14, 5:41 pm, josh <dor...@gmail.com> wrote:> Thanks, I tried using nginx for the proxy, but it was having SSL
> issues passing the certs through (I think)  There''s already
Apache2 on
> the puppet server, so I just need to re-compile it for some additional
> modules and then I''ll give that a shot using the documentation on
the
> wiki.  I wish we were running some flavor of Linux, this OpenSolaris
> thing is driving me crazy.
>
> On Sep 13, 7:19 am, Richard <rnh...@gmail.com> wrote:
>
> > On Sep 12, 9:58 am, josh <dor...@gmail.com> wrote:
>
> > > Hello,
> > > I am running puppet-0.24.5 with facter-1.5.2 and ruby 1.8.6
> > > (2007-09-23 patchlevel 110) on OpenSolaris snv_91 on a Sun X2200.
>
> > > Right now I have roughly 250 client or so talking to the
puppetmaster
> > > server, but after anywhere from a few minutes to a few hours, the
> > > puppetmaster server stops listening on port 8140, even though the
> > > puppetmasterd service is still running.
>
> > I had this exact same problem with a brand new installation of Puppet
> > and only 2 clients.  After a while, sometime minutes, Puppetmaster
> > just stopped listening.  No log data.  No nothing.  :/  So I installed
> > Mongrel, created a little Apache2 config, and told Debian how many
> > Mongrel processes I wanted.  It was actually very simple, much easier
> > than I expected.  If your running Debian Lenny you''ve got it
made in
> > the shade.  :)
>
> > Ever since moving to Mongrel with an Apache2 proxy it has ran
> > perfectly.  Good luck!
>
> > Later...
> >   Richard--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Puppet users - Sep 2008 - puppetmasterd stops listening on port 8140

[Puppet Users] puppetmasterd stops listening on port 8140

[Puppet Users] Re: puppetmasterd stops listening on port 8140

[Puppet Users] Re: puppetmasterd stops listening on port 8140

[Puppet Users] Re: puppetmasterd stops listening on port 8140

[Puppet Users] Re: puppetmasterd stops listening on port 8140

[Puppet Users] Re: puppetmasterd stops listening on port 8140

[Puppet Users] Re: puppetmasterd stops listening on port 8140

[Puppet Users] Re: puppetmasterd stops listening on port 8140