Joe Clarke Thu, 07/23/2009 - 09:17

Post the output of the pdshow command and screenshots of the Services control panel showing all of the CiscoWorks services.

Joe Clarke Thu, 07/23/2009 - 10:30

Have you enabled a firewall on this server? Can you telnet to localhost port 9009?

jain.nitin Thu, 07/23/2009 - 10:42

No we did not do anything. I checked windows firewall is off & firewall services were running I disabled it now but still its not working.. I am able to telnet to localhost on port 9009. its giving me blinking cursor when i press enter it goes into next line...

it seems working telnet to localhost on port 9009

Joe Clarke Thu, 07/23/2009 - 11:04

It looks like you changed the hostname of this server. TomcatMonitor is trying to connect to cisco1, and this is failing.

jain.nitin Thu, 07/23/2009 - 11:07

we did not change it..there is separate team for server administration..might be they have done it..its customer network are just what should be the workaround

jain.nitin Thu, 07/23/2009 - 11:43

I have changed the server name to cisco1 but still its not working...

jain.nitin Thu, 07/23/2009 - 11:50

also just to update you i am getting login screen & when I type user name & password n try to login then its give me forbidden error

Joe Clarke Thu, 07/23/2009 - 13:40

Assuming they changed the hostname back to cisco1, and that was the original hostname of the server when CiscoWorks was installed, then have the customer reboot. That should get the services to start again.

If the hostname of the server is now different from when CiscoWorks was installed, they will need to run the NMSROOT/bin/ script to change the hostname within LMS.

jain.nitin Thu, 07/23/2009 - 16:03

I have changed hostname back to cisco1 which was the origional one when cisco LMS was installed of lms server but its not working at all..any suggesion

Joe Clarke Thu, 07/23/2009 - 17:08

Post the new pdshow, stdout.log, stderr.log, and TomcatMonitor.log.

Joe Clarke Thu, 07/23/2009 - 18:32

It looks like there is a problem with the System Identity User account. If you cannot log in, you will need to regenerate this account from the command line. To get this procedure, open a service request with TAC.


This Discussion