That seems to have done the trick. Any idea what might be eating up all of the connections? Or is the default just set too low?
Thanks for your help on this.
Thanks,
Gavin
PostgreSQL Deadlocks
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: PostgreSQL Deadlocks
By default persistent connections are made, if you have more than a handful of users that connect & have your XI open this could do it, especially if they are on a dashboard page with many items constantly refreshing in the background.
The default for MySQL is pretty low too, you may want to consider adding the following to /etc/my.cnf and then restarting mysqld
The default for MySQL is pretty low too, you may want to consider adding the following to /etc/my.cnf and then restarting mysqld
Code: Select all
max_connections=500Re: PostgreSQL Deadlocks
Great, thanks for that. That would probably explain the 'cannot connect to database' errors we've seen in CCM.
We haven't any reoccurrence of the deadlock errors since making the change, so I think that problem is now solved.
Thanks for your help, this can be closed off.
Gavin
We haven't any reoccurrence of the deadlock errors since making the change, so I think that problem is now solved.
Thanks for your help, this can be closed off.
Gavin