I migrated our server to a Debian based system with MYSQL… I had no problems getting they system up and running… However, after the system runs for approx 18 to 24 hours. the MYSQL crashs with “too many connections”
In MYSQL I have it set for max_connections = 150 (I’ve even moved that to 300) To no avail…
I get to the point where MYSQL creates mysql-bin logs and will not restart until I purge these logs from the system.
The reason it’s set so high is so that I can last at least 20 hours before it crashs… Is there something I missed that causes the mysql-bin output and the “too many connections” error?
You do not need that many connections. You MySQL server is probably not configured to allow that many connections. there is no need for them to be that high. That number has nothing to do with the number of users connecting to Openfire. It is openfire’s connection to mysql to write data from teh cache to the database.
It would depend on how you have your dabase instal/configured. Openfire can be taxing on a database depending on level of use and the plugins installed. MySQL has different install configurations for the type of use. My guess is that you did not configure MySQL for robust enough settings. This does nto mean up the connection pool. Unfortunately I can not provide specifics for how to do this on your OS.
I assume that this is a fresh install, so the database schema is fine. Openfire uses Proxxol as the JDBC connection pool with 15 or 25 configured connections. Does “netstat -an|grep 3306” (change 3306 to your MySQL TCP port) return 25 connections (50 lines if you are running Openfire and MySQL on the same server) after startup and 100 connections after 10 hours?
There may be a MySQL connection timeout, setting it to 300 seconds should help a lot and cause exceptions in the Openfire error log. Do you see errors or interesting messages in the Openfire log files?