What is the current issue number? The only one I could find that
mentions the same problem is this , http://projects.puppetlabs.com/issues/7203.
Would any changes to my current puppet.conf (see below) make this
problem no longer an issue? I'm not suing storeconfig, and not really
sure if I need to be doing anything as far as saving the inventory
information. My setup is very basic, but right now can't run for more
than 2 or 3 days without having to restart the puppetmaster service.
[master]
certname=puppetmaster
reports = http, store
# Configure Inventory Service
facts_terminus = inventory_active_record
dbadapter = mysql
dbname = puppet_inv
dbuser = puppet_inv
dbpassword = cabb0ac9ed925867f93587ccfb147ebf15dec8a3
dbserver = localhost
dbsocket = /var/lib/mysql/mysql.sock
Thanks
- Trey
On May 21, 6:08 am, Nathan Clemons <nat...@livemocha.com> wrote:
> I'm pretty sure there is an open bug on this, I was looking around on this
> the other day. It's related to using stored configs and Puppet/ruby not
> closing the connections to the database servers.
>
> --
> Nathan Clemonshttp://www.livemocha.com
> The worlds largest online language learning community
>
>
>
>
>
>
>
> On Fri, May 20, 2011 at 10:01 PM, treydock <treyd...@gmail.com> wrote:
> > Every few days I have to restart the puppetmaster process due to this
> > error
>
> > "Could not read YAML data for node .... Too many open files".
>
> > I have 9 clients being controlled by Puppet and each one of those will
> > generate the same error once this happens. Running 'lsof' during this
> > time shows me 100's of entries like this
>
> > "puppetmas 10443 puppet 14u unix
> > 0xffff810014c7e180 17057251 socket".
>
> > The only way to remedy this is by restarting the puppetmaster
> > process. Once I restart the puppet master process it seems that a new
> > lsof entry is created and stays present for every client check.
>
> > All clients and puppetmaster are running 2.6.8 on CentOS 5.6 x64. Any
> > ideas? If more output and debug info is needed please let me know.
> > Also if switching to a mysql data store could get rid of this then
> > that would work as I was planning on it eventually.
>
> > Thanks
> > - Trey
>
> > --
> > 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+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/puppet-users?hl=en.
--
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+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
