Owners Manual

Troubleshooting Your Application | Troubleshooting
698 OMNM 6.5.2 User Guide
Backup/Restore/Deploy
See Backup/Restore/Deploy on page 703
• Is your FTP server installed, up and running?
• Is that FTP server on the same side of the firewall as the devices it addresses?
• Does the device support the type of backup (FTP, SFTP, TFTP) you are attempting?
• Do your authentications grant privileged access? The prompt is typically #, not > at this level
of access.
• If the device does not successfully execute the command, then either the authentication you
have used does not have permission to do such commands, or the device is configured to
prohibit their execution.
• Do FTP and TFTP servers write to the same directory, and have permissions to read/write/
execute to that directory?
Alarms/Monitors/Performance
Consult the User Guide’s recommendations, particularly for Monitoring and for Traffic Flow
Analysis. See
Alarm/Performance/Retention on page 705.
• Do you have the recommended hardware to handle the number of devices you are managing?
• Are the devices you are monitoring sending only the relevant traps to your system?
• Is your database configured correctly for the expected load? Symptoms of database
configuration inadequacies include slow performance when expanding the Resources portlet
or right-clicking on a port of a device and selecting show performance. This can also occur if
your database size has increased significantly since implementation.
Solution: For MySQL, adjust/increase the innodb_buffer_pool_size to restore performance.
Consult the User Guide for more about performance tuning such parameters in MySQL.
NOTE:
The internal event emsDBCapacity notifies you about how much of the database you have used.
• Have you tailored your monitoring to the available capacity of your hardware? Monitoring or
other functionality dependant on writing to the database may stop with error specifying
Could not get a database connection
One example of an error that appears when an active monitor which is suddenly unable to
insert data into the database
2014-04-10 11:14:47,376 490736076 ERROR
[com.dorado.broadscope.polling.PollingResultsDAOImpl]
(WorkerThread#8[71.192.23.246:58220]:) persistsPollingResults failed.
Rolling back.
com.rendion.ajl.CheckedExceptionWrapper: Could not get a database
connection.
Solution: If the database can be reached over the network and has been confirmed
operational/healthy, the configured pool allocation(s) may be exhausted. Refer to the
Installation Guide and confirm sufficient pool allocations have been configured for corepool,
jobpool, and userpool.
The
Installation Guide ’s Clustering chapter contains suggestions for properly sizing pool
values based on the number of servers in your environment. Based on this information and
your current configuration, increase pool values accordingly.