OpManager 7 will not start new install w/ logs

by 
 on 26-Feb-2008 01:09 AM.
  in  OpManager 
Hello, I cannot get OPManager to start. This is a new install of v7. I was looking through the logs on the server, and it was referencing an active network connection that we do not use for "normal" traffic. Is there a way to specify what network adapter it uses?

Any help would be appriciated!!!!
Thank you
Mike

errors in the stderr6.txt and wrapper are:

PM (OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : make_sock: could not bind to address 0.0.0.0:8060

AND

PM No response from the Primary Server as it may not be running. Unable to connect.java.rmi.ConnectException: Connection refused to host: XX.XX.X.XX; nested exception is:
java.net.ConnectException: Connection refused: connect

AND

PM ##### PROBLEM IN INITIALIZING MODULE class com.adventnet.nms.eventdb.EventMgr #####





Here is the wrapper log
STATUS | wrapper | 2008/02/26 16:11:27 | --> Wrapper Started as Service
STATUS | wrapper | 2008/02/26 16:11:28 | Launching a JVM...
INFO | jvm 1 | 2008/02/26 16:11:30 | Wrapper (Version 3.1.1) http://wrapper.tanukisoftware.org
INFO | jvm 1 | 2008/02/26 16:11:30 |
INFO | jvm 1 | 2008/02/26 16:11:31 | This evaluation copy is valid for 29 days
INFO | jvm 1 | 2008/02/26 16:11:31 | inside addon check
INFO | jvm 1 | 2008/02/26 16:11:43 | taryIconProps {DefaultMenuItem=Status, ApplicationName=OpManager, Menu=[{Id=Status, DisplayName=&OpManager Status, RunProcess=ShowOpManagerStatus}, {Id=StartClient, DisplayName=Start &Client, RunProcess=StartOpManagerWebClient}, {Id=ShutDownServer, DisplayName=Sh&ut Down Server, RunProcess=ShutdownOpManager}], EnableIcon=images/logo16x16_green.png, DisableIcon=images/logo16x16_gray.png, ToolTipText=ProductName, MainProcess=StartOpManager}
INFO | jvm 1 | 2008/02/26 16:11:43 | Windows 2003
INFO | jvm 1 | 2008/02/26 16:11:43 | application_name OpManager
INFO | jvm 1 | 2008/02/26 16:11:43 | startAndRun
INFO | jvm 1 | 2008/02/26 16:11:43 | menuName &OpManager Status RunProcess ShowOpManagerStatus
INFO | jvm 1 | 2008/02/26 16:11:43 | menuName Start &Client RunProcess StartOpManagerWebClient
INFO | jvm 1 | 2008/02/26 16:11:43 | menuName Sh&ut Down Server RunProcess ShutdownOpManager
INFO | jvm 1 | 2008/02/26 16:11:43 | setProcessInProgress true
INFO | jvm 1 | 2008/02/26 16:11:48 | Checking for the availablity of the Primary Server in the Database. Found an entry.
INFO | jvm 1 | 2008/02/26 16:11:48 |
INFO | jvm 1 | 2008/02/26 16:11:48 | Trying to connect to the Primary Server at XX.XX.X.XX. This may take 4 seconds.
INFO | jvm 1 | 2008/02/26 16:11:48 |
INFO | jvm 1 | 2008/02/26 16:11:48 | Please wait .
INFO | jvm 1 | 2008/02/26 16:11:49 | .
INFO | jvm 1 | 2008/02/26 16:11:51 | .
INFO | jvm 1 | 2008/02/26 16:11:52 |
INFO | jvm 1 | 2008/02/26 16:11:52 | No response from the Primary Server as it may not be running. Unable to connect.
INFO | jvm 1 | 2008/02/26 16:11:52 |
INFO | jvm 1 | 2008/02/26 16:11:52 | Primary Server may not have been properly shutdown in the last run, resulting in the Database not being properly updated.
INFO | jvm 1 | 2008/02/26 16:11:52 |
INFO | jvm 1 | 2008/02/26 16:11:52 | Starting up as Primary Server and correcting the Server information in the Database.
INFO | jvm 1 | 2008/02/26 16:11:52 |
INFO | jvm 1 | 2008/02/26 16:11:52 |
INFO | jvm 1 | 2008/02/26 16:11:52 | Starting AdventNet ManageEngine Server Modules, please wait
INFO | jvm 1 | 2008/02/26 16:11:55 | Process : DBServer [ FAILED ]
INFO | jvm 1 | 2008/02/26 16:11:55 |
INFO | jvm 1 | 2008/02/26 16:11:55 |
INFO | jvm 1 | 2008/02/26 16:11:55 |
INFO | jvm 1 | 2008/02/26 16:11:55 | Process : StartTelnetClient [ Started ]
INFO | jvm 1 | 2008/02/26 16:11:55 | Process : OpManagerStatusProcess [ Started ]
INFO | jvm 1 | 2008/02/26 16:11:55 | Process : AuthMgr [ Started ]
INFO | jvm 1 | 2008/02/26 16:11:55 | Process : DataMgmtRPI [ Started ]
INFO | jvm 1 | 2008/02/26 16:11:55 | Process : NmsPolicyMgr [ Started ]
INFO | jvm 1 | 2008/02/26 16:11:56 | Process : OpManagerRunApacheExeModule [ Started ]
INFO | jvm 1 | 2008/02/26 16:11:56 | Process : NMSMServer [ Started ]
INFO | jvm 1 | 2008/02/26 16:11:56 | Process : NmsAuthManager [ Started ]
INFO | jvm 1 | 2008/02/26 16:11:56 | Process : UserConfigProcess [ Started ]
INFO | jvm 1 | 2008/02/26 16:11:56 | Process : NmsAuthenticationManager [ Started ]
INFO | jvm 1 | 2008/02/26 16:11:56 | Process : CLIFactoryBinder [ Started ]
INFO | jvm 1 | 2008/02/26 16:11:56 | Process : SetSecurityProperty [ Started ]
INFO | jvm 1 | 2008/02/26 16:11:57 | Process : NMSSAServer [ Started ]
INFO | jvm 1 | 2008/02/26 16:12:01 | Process : RunJSPModule [ Started ]
STATUS | wrapper | 2008/02/26 16:14:45 | <-- Wrapper Stopped
  • No status
Hi Mike,

Open the file "httpd.conf" under "OpManager\apache\conf\backup" with wordpad > search for "ServerName APACHE_SERVER_NAME " , update the required server IP address with proper port (ServerName xx.xx.xx.xx:80) , save the file and restart the OpManager server.

If issue persist, post your contact information in our Support Portal we will call and assist you.

Regards,
Rex
Tried the following:

Open the file "httpd.conf" under "OpManager\apache\conf\backup" with wordpad > search for "ServerName APACHE_SERVER_NAME " , update the required server IP address with proper port (ServerName xx.xx.xx.xx:80) , save the file and restart the OpManager server.


This did not help the situation. From the logs, i can gather that it looks to contact the database, but the databse returned an IP address of a network connection that the opmanager apache server is not listening on. I have submitted my contact informiaton on the opmanager support site as directed.

Thanks
Mike
Hi Mike,

It was pleasure talking to you. During the web conference we found the issue was due to SQL backend credentials.

Once we set that, it started working.

If any issues, let us know.

Regards,
Rex
Hi, i have the same problem with MSp Center plus central server, that it is happened after a unexpected shutdown (power issue)

What do you mean for "we found the issue was due to SQL backend credentials.

Once we set that, it started working."

Where and with what i can correct this informations?

Thanks a lot,

Andrea Ceffa


Re: OpManager 7 will not start new install w/ logs

by 
(Moderator)
 on 04-Feb-2010 01:21 AM
Hi Andrea,

Power outage in a MySQL environment may result in a database corruption. Please run RepairDB.bat which is under /bin directory. Wait until it says "Press any key to continue...." and start the service again.

Note: We have a separate discussion site for MSP and you can use that for further queries.

Gabriel
Team OpManager
Network Monitoring Software
Post Actions
Statistics
  • 5
     Replies
  • 758
     Views
  • 0
     Followers
Tags for the post
No tags available for this topic.
© 2009 Corp. All rights reserved. Trademarks | Privacy Policy | Site Map | Contact Us | Careers

Edit Link Delete Link

Edit Link Delete Link

LoadingImage