The Storage Manager Collector service is responsible for collecting data from proxy agents and transferring any collected information to the database. When customers add additional devices to Storage Manager, this can cause additional database connection request to the database. It is possible that the collector will not be able to store information in the database due to too many connections. I will discuss how to get around this issue.

 

Note: Storage Manager versions 5.6 and newer use MariaDB. For previous versions, MySQL is used. For versions prior to 5.6, substitute MySQL for MariaDB in the following instructions.

 

First we need to check the collector log file to see what messages are being generated. The collector log file can be found in the following location:

 

  • Windows - %Program Files%\SolarWinds\Storage Manager Server\webapps\ROOT\logs

 

  • Linux - /opt/Storage_Manager_Server/webapps/ROOT/logs

 

The file name is called mod.adm.collect.Collector.log.

 

When viewing this file look for the following error:

 

[Collect list digestor] Non-recoverable database error [08004]:
com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Data source rejected establishment of connection, message from server: "Too many connections"

 

The error tells us there are too many connections trying to hit the database at once.

 

To fix this issue requires modifying the database configuration file called my.cnf. This file can be found in the following location:

 

  • Windows - %Program Files%\SolarWinds\Storage Manager Server\mariadb

 

  • Linux - /opt/Storage_Manager_Server/mariadb

 

Open the my.cnf file with a text editor and search for the entry max_connections=. The default value is 400. Change it to 600, save the file and restart the Storage Manager services including the database service.

 

Note: Do not exceed 600 when changing this value.