« Back
You are in :
Recent Topics »
OpManager »
OpManager 7 will not start new install w/ logs
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
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:
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
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
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
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
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
Gabriel
Team OpManager
Network Monitoring Software
Post Actions
Corp