One other thing I noticed, /etc/sysconfig/puppet was rewritten with default values on the hosts that are experiencing this issue. I killed the proc, then wrote the values that I use on the working agents, but I continue to get the same error message. Is there anyone else that has seen this? I've been at it for a while, I cannot figure this out.
On Wednesday, October 3, 2012 11:32:48 PM UTC-7, Will S. G. wrote: > > I'm running puppet on CentOS 6.3 x86_64: > > - facter.i386 1:1.6.12-2.el6 @puppet > - puppet.noarch 2.7.19-1.el6 @puppet > - ruby-shadow.x86_64 1.4.1-13.el6 @puppet > > Puppetmaster: > > - facter.x86_64 1:1.6.12-2.el6 @puppet > - hiera.noarch 1.0.0-2.el6 @puppet > - puppet.noarch 2.7.19-1.el6 @puppet > - puppet-dashboard.noarch 1.2.11-1.el6 @puppet > - puppet-server.noarch 2.7.19-1.el6 @puppet > - ruby-mysql.x86_64 2.8.2-1.el6 @puppet > - ruby-shadow.x86_64 1.4.1-13.el6 @puppet > > I keep getting seeing the following error on my puppet agent: > > Wed Oct 03 23:25:43 -0700 2012 Puppet (notice): Starting Puppet client > version 2.7.19 > Wed Oct 03 23:26:11 -0700 2012 Puppet (notice): Caught TERM; calling stop > Wed Oct 03 23:26:16 -0700 2012 Puppet (notice): Reopening log files > Wed Oct 03 23:26:55 -0700 2012 Puppet (err): Could not retrieve catalog > from remote server: Error 400 on SERVER: could not obtain a database > connection within 5 seconds. The max pool size is currently 5; consider > increasing it. > > I can't seem to figure out what's wrong. What's even more weird is that > only some of the agents are displaying this error. > > Any suggestions? > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/YgPRAfFabIMJ. 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.
