Log File
| Log Print | Reason | Steps to troubleshoot |
cantcreatetable.txt
|
| During every start up Probe/Central creates some tables. This error occurs when it cannot contact the database to create the tables.
| Follow the troubleshooting steps provided for DB Server failed error.
|
classnotfound.txt
| Unable to load cryptix.jce.provider.Cryptix
Cryptojava.lang.ClassNot
FoundException: cryptix.jce.provider.
CryptixCrypto
| Harmless.
| Can be ignored. |
connectionlost.txt
| Connection lost with the Central Server[mgt-tchx-opman.srv.redstone-isp.net:443] at Mon Jul 20 09:00:08 BST 2009
| A. Central Server's NAT/Public IP address may have changed
B. Could be a SSL issue
C. Network/Internet/Firewall issue
Ensure whether there the probe is communicating with the central:
1. telnet to the central server from the probe server using the command telnet ip <central's ip address>
2. If the telnet connection is established, then the probe is communicating with the Central. If not, then there is a failure in the connection.
or
From the Probe server, open the central web client. If you could open, then the Probe is communicating with the Central and vice versa.
| A: In the probe Open the NOCServer
Details.xml file [\probe\conf]. Then change the NOCServerName field with the new Central's NAT/Public IP. Now restart the Probe service. Also follow the steps given in "B" [SSL issue].
B:
Click here to troubleshoot if you have changed the Central's NAT/Public IP
C:
Verify your internet, network & firewall settings
|
connection
timedout.txt | java.io.IOException: Connection timed out: connect | Harmless print.
| Can be ignored. |
dbserverfailed.txt
| DBServer Faied
| A. Some table could have been corrupted
B. Could be due to pdlastvalues issue
C. Database port occupied by some other application
| A: Follow the troubleshooting steps provided for tablecorrupt.txt
B: Click here to know the steps to troubleshoot.
C: Change DB port. Change in port.properties file
|
| dmsiswaiting.txt | DMS is waiting for registration from the Central Server | Probe could not able to communicate with the Central due to
A. Central IP could be wrongly mentioned in the NOCServerDetails.xml file in the probe under conf directory
B. Network/Internet issue
C. Firewall port could be blocked
D. Could be a SSL issue
| Follow the trouble shooting steps A and B of connectionlost.txt
|
dmsalreadyexists.txt
| DMS already exists
| A. This error occurs when you use the same name and key of a deleted Probe to a new Probe.
B. When you re-initialize the database of the Probe [\probe\bin\
reinitialize_dms.bat].
| Create a new Probe with a unique name.
|
exceptionin
startid.txt
| Exception while setting the startID
|
| Contact us.
|
gracefullyshutting
downopmanager.txt
| Failed to establish connection with web server. Gracefully shutting down OpManager
| A. This error occurs when the Central/Probe fails to connect with the Apache web server.
B. Java.exe or some other application could have occupied the port 443.
C. Could be due to the SSL issue
| A:
1. Verify whether the local IP or Name of the Central is mentioned correctly against the APACHE_SERVER
_NAME field in the serverparameters
.conf file [\central\conf]. If not then correct it accordingly. If the error occurs in Probe, then check whether the Probe's local IP or Name is mentioned in serverparameters.
conf file [\probe\conf]
B:
1. Terminate java.exe application and try to start the Central/Probe.
2. If still the same error is received, then Change the Web server Port of the Central/Probe.
C:
1. Generate SSL Certificate using ssl_gen.bat [\central\bin] on the Central Server and restart the Central Server
2. Copy the https.truststore file [\central\conf] and replace it with the one in the Probe [\probe\conf].
3. Now Restart the Probe.
If the problem still exists, then contact us.
|
interrupt.txt
| Interrupt signal received shutting down opmanager
| Some one has terminated the Central service
| Start the Central service
|
| info.txt | Central build number <build number> is not compatible with Probe build number <build number>. Hence shutting down the probe | There might be a mismatch in build number between the Central and the Probe.
| 1. Check the build number of the Probe and the Central.
2. Upgrade the Probe to the Central's build number.
|
lastfileid.txt
| The file lastFileID.txt is not present
| The lastFileID.txt is a text file which contains the ID of the last file that is sent to the Central for data processing. This error occurs when this text file gets corrupted.
| Please contact us.
|
mysqlerrfile.txt
| 090727 19:24:55 [Warning] Aborted connection 23 to db: 'centraldb' user: 'root' host: 'localhost' (Got an error reading communication packets)
| Harmless print.
| Can be ignored. |
outofmemory.txt
| OutOfMemoryError: Java heap space
| This could be due to insufficient hardware resources
| 1. Visit our System Requirements page and check whether you have configured enough resources.
2. Go through the Java heap table to know the RAM size and the Heap Space it can handle. Also it provides the steps to increase the Java Heap size.
|
| pdlastvalues.txt | Exception while getting MetaDataInfo : Incorrect file format 'pdlastvalues3'
java.sql.SQLException: Incorrect file format 'pdlastvalues3'
Could be warm start pdLastValues already exist - Table 'pdlastvalues2' already exists |
| Click here to know the steps to troubleshoot.
|
probeconnected.txt
| <Probe name> Probe has connected with properties
| Harmless print.
| Can be ignored. |
problemininitializing
module.txt | PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.startnms.
NmsMainFE | Harmless print.
| Can be ignored. |
sslexception.txt
| Exception occured while checking ssl communication sun.security.validator.
ValidatorException: PKIX path building failed: sun.security.provider
.certpath.SunCertPath
BuilderException: unable to find valid certification path to requested target | This occurs when you have any SSL certificate issue. This is common in the Probe side.
| Copy the https.truststore file [\central\conf] and replace it with the existing file in the Probe [\probe\conf].
|
start-stop.txt
| Wrapper Stopped
STATUS | wrapper | 2009/07/29 16:57:54 |
| Central or Probe service has been stopped manually.
| Start the respective service using StartOpManger
Server.bat [Central or Probe \bin]
|
| statefilecorrupt.txt | State File corrupted DataID.dmp | Central Process the files sent by the Probes one by one. If suddenly it receives a huge load of files, then it may miss a file to process. If such thing happens, then this error occurs.
| Move the DataID.dmp file [central\state\communication\lowpriority or probe\state\communication\lowpriority] to some other location and restart the Probe service.
|
tablealready
exists.txt
| Table Already exists : Table 'statsdata_hourly8_2009' already exists
Table Already Exists . Assuming Warm Start of server
| Harmless print.
| Can be ignored. |
tablecorrupt.txt
| Exception while getting MetaDataInfo : Can't find file: 'event' (errno: 2)
java.sql.SQLException: Can't find file: 'event' (errno: 2)
Debug Message is Can't find file: 'ManagedObject' (errno: 2)
com.adventnet.nms.store.
NmsStorageException: Can't find file: 'ManagedObject' (errno: 2)
| Some tables might have got corrupted.
| 1. Stop the Central or Probe Service.
2. Execute ReparitDB.bat [\central\bin or \probe\bin].
3. Start the Central or Probe Service.
|
unabletoconnect
tocentral.txt
| Unable to connect to UpdateManagerServer in <device name/ip> The SmartUpdate option in server may be disabled in server side
| This occurs when the Central server is down or the connectivity between the Probe and the Central is down.
| Verify the Central Server and the Connectivity between the Probe and the Central.
|
unabletostart
MySQL.txt
| Unable to start Mysql daemon
| MySQL service could not able start at the Central or Probe
| Start the respective service using StartMySQL.bat [Central or Probe \bin] |
