Log Analysis

Log Analysis

Every action in OpManager leaves a trace(s) in the log files. There are two logs folder in OpManager. One under the OpManager directory and the other under OpManager tomcat folder.

 

The logs folder under the OpManager directory contains various logs file mentioned below:

01. alert_audit.txt

02. applnerr.txt

03. ConfChange_AdventNet_ManageEngine_OpManager.log

04. ConfChangeErr_AdventNet_ManageEngine_OpManager.log

05. discoveryLogs.txt

06. disterr.txt

07. distout.txt

08. hyperverr.txt

09. mserr.txt

10. msout.txt

11. nmserr.txt

12. nmsout.txt

13. notificationLogs.txt

14. opmanager_IntfOut.txt

15. opmanager_serverOut.txt

16. rbaerr.txt

17. stderr.txt

18. stdout.txt

19. transactionLogs.txt

20. updatemanagerlog1.txt

21. wrapper.log


Every log file has a certain size limit and upon reaching the specified size, a new file is created and is appended with a file number at the end. For example, stderr1.txt, stderr2.txt etc.

Each group of these logs, records traces for specific actions or features in OpManager. As a standard, every log file has the Date & Time entry before the trace. We will look into each group of these logs now.

01. alert_audit.txt

As the name suggests, these log files record actions/events related to OpManager alarms. Every time an alarm in triggered in OpManager an entry is made in the alert_audit files.

As you can see, the Date & Time is recorded along with the Severity Change (i.e Attention from Clear, Trouble from Attention, etc), the Device Name and the Alarm message.

02. applnerr.txt

These logs contain CLI related traces.

03. ConfChange_AdventNet_ManageEngine_OpManager.log & 04. ConfChangeErr_AdventNet_ManageEngine_OpManager.log

These logs contain entries for actions occuring during an upgrade. So, if there are any upgrade related issues, these files can be used to debug the problem.

05. discoveryLogs.txt

Very evident from the file name, these logs contain records for Discovery related actions in OpManager. When you are faced with any device/interface addition issues, you can analyze these logs.

 06. disterr.txt & 07. distout.txt

These files contain Central-Probe communication related log traces.

08. hyperverr.txt

Again, like the file name suggests, these files contain log entries for HyperV related actions.

09. mserr.txt & 10. msout.txt

11. nmserr.txt & 12. nmsout.txt

OpManager is built on WebNMS framework. These files maintain framework related logs & errors.

13. notificationLogs.txt

These logs contain records for every notification (email, SMS etc) that is being triggered from OpManager.

14. opmanager_IntfOut.txt


15. opmanager_serverErr.txt & opmanager_serverOut.txt

These contain logs related to OpManager DB's table creation, backend queries for Reports generated in OpManager. Also, any traces for debugs enabled for troubleshooting purposes are also recorded here.

16. rbaerr.txt

These contain IT Automation/Workflow related logs.

17. stderr.txt

A standard log file referred the most in OpManager. This contains traces for most of the actions done in OpManager, though there are feature specific logs (like alert_audit, notificationLogs, hyperverr etc). When ever a feature does not work as expected, you are sure to find error traces in these logs that will help you debug the issue.

18. stdout.txt

These logs are mostly used to debug issues related to Reports. The SQL query is printed in these files for every report generated in OpManager.

19. transactionLogs.txt

Records Transaction log activities if the OpManager database is on MSSQL backend.

20. updatemanagerlog.txt

These logs contain entries for actions occuring during an upgrade like the ConfChange_AdventNet_ManageEngine_OpManager.log & ConfChangeErr_AdventNet_ManageEngine_OpManager.log. Combining these 3 logs, any upgrade related issue can be debug easily.

21. wrapper.log

This log is useful to debug OpManager start-up issues.

 

The logs folder under the OpManager\tomcat directory contains the below mentioned files:

1. catalina.XXX.log

2. localhost.XXX.log

3. localhost_access_log.XXX.

Unlike the previous set of the logs where the file number is appended at the end, here it is appended with the Date. For example, catalina.2012-07-09.log & localhost.2012-07-09.log

The Catalina & localhost files record logs when the OpManager UI redirects itself to an Error page or when any Action buttons (like Add Monitors, Test Credential etc) in the UI remains inactive.

 
 

Now, having got a brief idea on the files and their logging properties, lets look at some exceptions/error traces which can be found in the logs and the steps to troubleshoot/fix them.

1. stderr.txt

11:38:54:578 AM java.sql.SQLException: Table '.opmanagerdbpolleddata' is marked as crashed and should be repaired

11:38:54:578 AM  at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:946)

11:38:54:578 AM  at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2985)

11:38:54:578 AM  at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1631)

11:38:54:578 AM  at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1723)

11:38:54:578 AM  at com.mysql.jdbc.Connection.execSQL(Connection.java:3277)

 

In the above trace, you can clearly see the message that PolledData of the OpManagerDB has crashed. This issue can be resolved by doing a Database repair. To repair the database, execute RepairDB.batfound under OpManagerin folder. If this does not resolve the issue, follow the steps from the link : http://support.opmanager.com/sd/AddSolution.sd?solID=29701

 

06:29:18:796 AM com.adventnet.nms.store.NmsStorageException: The transaction log for database 'OpManager' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

06:29:18:796 AM  at com.adventnet.management.transaction.ConnectionPool.executeUpdate(ConnectionPool.java:1798)


Here, the Transaction logs for the OpManager database is full. This issue will cause all the dials in OpManager to be greyed out and it will look like the data-collection has stopped.

You can follow the steps in the link to resolve this case:   http://support.opmanager.com/sd/AddSolution.sd?solID=24901

  


          • Related Articles

          • Changing the size of the SQL Server Express transaction log

            Question: How do I increase my SQL Server Express transaction log  size? This article provides steps to change the size of the SQL Server Express transaction log. You may want to change the log size to, for example, restrict its growth.   Solution:  ...
          • Root Cause Analysis

            RCA in OpManager is a single graph view of the events of all the plugins of OpManager. When this happens, the impact that is captured on one of the plugins takes the IT team to the root cause. This is, in other words, a single-graph correlation of ...
          • How to configure OpManager to log a ticket to Service Deskplus to a specified default site?

            Solution: Making the below changes will  create tickets with a default Site name. 1)Open the file /Opmanager/conf/SDPMSPConfig.xml in a Wordpad 2)Enter the site name between <SDP-Params>  to which Opmanager has to log tickets (it is case sensitive) ...
          • Log monitoring agent not communicating with server after enabling SSL

            Error trace in agent logs: 2016/09/20  00:22:49:235 InternetGetRequestEx :  The request is updated with the internet option security flags. 2016/09/20  00:22:49:251 InternetGetRequestEx :  Error in WinHttpSendRequest -> -2146892963 2016/09/20  ...
          • MSSQL Transaction Logs Full

            Steps to clear the Transaction logs. 1. Shutdown opmanager service. 2. Change the Recovery Model to Simple by following the steps below: Go to SQL server-->OpManagerDB properties-->Options-->Recovery Model-->Simple. (You can replace it with full mode ...