JRM is down

Answered Question
Aug 12th, 2009

Hi eam


JRM service is not coming up..plse find the atached error message.


regrds

Vaibhav

Correct Answer by Joe Clarke about 7 years 6 months ago

Check to make sure 172.28.100.10 is still the correct IP address for this server. If not, update the entries in gatekeeper.cfg, then restart Daemon Manager.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Joe Clarke Thu, 08/20/2009 - 21:53

You did not post the jrm.log. I'm also not sure why you're trying to reinitialize the cmf database. At this point, that seems to be overkill, and may not fix the underlying problem.

vaibhav-g Thu, 08/20/2009 - 22:20

Hi Clark


we will soon provide you the JRM.logs


Regards

Vaibhav

vaibhav-g Fri, 08/21/2009 - 06:58

Hi Clark


I have alredy attached the JRM.log file

plse help me..


Regards

Vaibhav

Joe Clarke Fri, 08/21/2009 - 07:05

Jrm appears to be working just fine. Was the hostname on this server changed? Post the output of the command:


pdreg -l CTMJrmServer


And the NMSROOT\lib\classpath\md.properties file. Additionally, it appears Daemon Manager has been up since 8/6. Simply restarting may get things back in sync.

Joe Clarke Sun, 08/23/2009 - 21:41

This looks good assuming the hostname of the server is ciscolms. Is this problem still occurring? Have you tried restarting Daemon Manager? It could simply be a timing issue.

vaibhav-g Mon, 08/24/2009 - 00:03

Hi Clark


we have tried to restart the daemon manger service but still we are facing same issue.Plse find the attached file for hostname.


Regards

Vaibhav



Joe Clarke Mon, 08/24/2009 - 07:08

Post the output of the DOS SET command, and the NMSROOT/MDC/tomcat/logs/stdout.log.

Joe Clarke Tue, 08/25/2009 - 08:23

Post screenshots of the Services control panel showing all of the CiscoWorks services. Additionally, the pdshow appears truncated. Run:


pdshow > pdshow.txt


Then post the pdshow.txt.

Joe Clarke Wed, 08/26/2009 - 07:54

The services look okay, but the pdshow is still truncated. Did you run:


pdshow > pdshow.txt


That will capture the entire output.

Joe Clarke Wed, 08/26/2009 - 23:03

The RmeGatekeeper is down. Post the output of netstat -a -n -o -b from the server as well as the RmeGatekeeper.log.

Joe Clarke Thu, 08/27/2009 - 08:50

Your netstat output is truncated. Run this command:


netstat -a -n -o -b > netstat.txt


Then post the netstat.txt. One of the ports required by RmeGatekeeper is in use by another process.

Joe Clarke Thu, 08/27/2009 - 22:08

There was something bound to one of the RmeGatekeeper ports, but all the ports appear to be free now. You should be able to restart the RmeGatekeeper, and have it stay up. Try running:


pdexec RmeGatekeeper


Then verify it stays in a running state. If so, restart Daemon Manager, and that should allow all of the daemons to resync.

vaibhav-g Fri, 08/28/2009 - 00:09

Hi Clark


Tried to start the RmeGatekeeper but it does not stay up and get down in few minutes.


Regards

Vaibhav

Correct Answer
Joe Clarke Mon, 08/31/2009 - 08:37

Check to make sure 172.28.100.10 is still the correct IP address for this server. If not, update the entries in gatekeeper.cfg, then restart Daemon Manager.

vaibhav-g Mon, 08/31/2009 - 09:18

Hi Clark


thanks for your response, i will check the same and upadte you,


If i found different Ip than i need to replace that IP address in Gatekeeper.cfg file, Plse confirm


Regards

Vaibhav

vaibhav-g Wed, 09/02/2009 - 07:24

Hi Clark


Thanks a ton..yes their was a IP conflict issue.Now issue was resolved by replacing the same..


Thanks again


Regards

Vaibhav

Actions

This Discussion