I've noticed the same thing with our puppetmaster server.
We're still in testing so dramatic changes to puppet.conf are not a
problem. But commenting lines out doesn't fix the problem, it just turns on
the feature that was being broken by too many files being open.
Trey: We've been testing on
I don't know how helpful this would be but for now I think I found a
"workaround" of sorts for my small environment.
I commented out the following in my puppet.conf...
facts_terminus = inventory_active_record
dbadapter = mysql
dbname = puppet_inv
dbuser = puppet_in
Nathan Clemons wrote:
> http://projects.puppetlabs.com/issues/3238 is the issue I was
> thinking of, but 3693 is probably a duplicate of that.
>
> These bugs have been open a really long time. Outside of lowering
> the MySQL timeout value, are there any workarounds for this problem?
> I can't reall
http://projects.puppetlabs.com/issues/3238 is the issue I was thinking of,
but 3693 is probably a duplicate of that.
These bugs have been open a really long time. Outside of lowering the MySQL
timeout value, are there any workarounds for this problem? I can't really
understand how Zynga can be man
treydock wrote:
> 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.
https://bugzilla.redhat.com/show_bug.cgi?id=572722 and
http://projects.puppetlabs.com/issues/3693 are both relevant here.
I'd lo
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
