Good to know it isn't just me having this issue. I agree that monitoring must play a role, since it wasn't happening in 1.6, and started when I enabled monitoring in 1.7. With osa-dispatcher turned off on the server, the issue hasn't reappeared. But I'd rather keep osa on.
How did you change the idle connection timeout in Postgresql? I admit, I don't use Postgres all that often, but I don't see any way of doing it without using something like pgpool. Am I missing something obvious? ---------- From: [email protected] [mailto:[email protected]] On Behalf Of Paul Robert Marino Sent: Friday, May 11, 2012 6:56 PM To: [email protected] Subject: Re: [Spacewalk-list] Spacewalk 1.7 Postgres out of connections Well I've worked around it by reducing the tcp heartbeat to 10 minutes in /etc/sysctl.conf and reducing the idle client timeout in postgresqls configuration. But yes there is an issue with this. I think it the monitoring that does it but I'm not sure. I can tell you the incidents of it do go up with monitoring turned on. The problem is is seems like its a shared library that isn't logging if the class goes out of scope out of the database correctly that make tracking the root cause significantly harder. I'm not familiar enough with python to figure explain how it should be fixed but in perl the DBI driver had. DESTROY method that catches if the programer forgot to logout of the database before the instance of the class goes out of scope or the application exits. It seems to me this is missing from the python postgresql driver and if that functionality could be added it would resolve the issue. _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
