[Spacewalk-list] spacewalk eats up all connections to postgres

[Yuriy Demchenko]

I second this. same fixes (except tcp_keepalive_time, never touched it) 
helped me too.
6 days passed - no restarts needed, no issues, about 50 idle connections.
rhel 6.3, spacewalk-1.8 with stock postgresql-8.4.13

Yuriy Demchenko

On 12/12/2012 01:15 PM, Ree, Jan-Albert van wrote:
> Jan-Albert van Ree
> Linux System Administrator
> MSuG MARIN Support Group
> E mailto:J.A.v.Ree at marin.nl
> T +31 317 49 35 48M +31652598885
>
> MARIN
> 2, Haagsteeg, P.O. Box 28, 6700 AA Wageningen, The Netherlands
> T +31 317 49 39 11, F , I www.marin.nl
>
>
> It's been almost a week now and connections are around 50, with no 'idle in transaction'
> To sum it up, my fixes were
>
> - Update the postgresql jar under /usr/share/java to latest version from jdbc.postgresql.org
> - I changed TCP/IP parameters on PostgreSQL and Spacewalk machines : net.ipv4.tcp_keepalive_time = 600
> - Updated python-psycopg2
>
> I now have Spacewalk 1.8 running stable with OSAD enabled, on PostgreSQL 8.4.13 (stock ScientificLinux RPMs with minimal tuning) I'm not sure if all the above steps are actually needed but I'm listing them anyway.
> --
> Jan-Albert van Ree
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list