LMS 2.6 - CS 3.0.5 RME 4.0.5: ConfigMgmtServer

yjdabear · ‎01-09-2008

Just noticed all the inventory-related RME jobs have been failing:

Protocol ==> Unknown / Not Applicable

CM0051 Unable to connect to ConfigMgmtSever process Cause: Problem while establishing connection with the server, CTMConnection: Action: Please restart ConfigMgmtSever process.

ConfigMgmtServer Administrator has shut down this server 0 -113 0 11/05/07 10:02:57 01/07/08 11:11:38

Process= ConfigMgmtServer

State = Administrator has shut down this server

Pid = 0

RC = -113

Signo = 0

Start = 11/05/07 10:02:57

Stop = 01/07/08 11:11:38

Core = Not applicable

Info = Application started by administrator request.

Based on the above, I'm attaching the ICServerUI.log.

Would restarting ConfigMgmtServer be it, or should this warrant deeper investigation?

Joe Clarke · ‎01-09-2008

The dcmaservice.log and the daemons.log (Solaris) or ConfigMgmtServer.log (Windows) would have more details as to why the server is down.

yjdabear · ‎01-09-2008

The dcmaservices.log has a last-mod timestamp of 10:42am, before ConfigMgmtServer stopped. This appears to correspond to the time when I deleted a decommissioned device from DCR:

[ Mon Jan 07 06:54:05 EST 2008 ],INFO ,[Thread-150377],com.cisco.nm.rmeng.util.

rmedaa.RMEDeviceContext,getSshCmdSvc,791,inside getSshCmdSvc

[ Mon Jan 07 06:54:13 EST 2008 ],INFO ,[Thread-150377],com.cisco.nm.rmeng.util.

rmedaa.RMEDeviceContext,getSshCmdSvc,798,SSH2 is running

[ Mon Jan 07 06:55:16 EST 2008 ],INFO ,[Thread-150377],com.cisco.nm.rmeng.util.

rmedaa.RMEDeviceContext,getCmdSvc,763,Inside RMEDeviceContext's getCmdSvc

[ Mon Jan 07 06:55:16 EST 2008 ],INFO ,[Thread-150377],com.cisco.nm.rmeng.util.

rmedaa.RMEDeviceContext,getCmdSvc,768,Protocol and Platforms passed = TELNET , R

ME_PIX

[ Mon Jan 07 06:55:16 EST 2008 ],INFO ,[Thread-150377],com.cisco.nm.rmeng.util.

rmedaa.RMEDeviceContext,getCmdSvc,772,trying for Telnet

[ Mon Jan 07 06:55:21 EST 2008 ],ERROR,[Thread-150377],com.cisco.nm.rmeng.dcma.

configmanager.ConfigManager,updateArchiveForDevice,638,PRIMARY RUNNING Config fe

tch Failed for fwsm1backup

[ Mon Jan 07 10:42:52 EST 2008 ],INFO ,[Thread-2763],com.cisco.nm.rmeng.dcma.co

nfigmanager.ConfigManager,deleteDevice,300,Deleting 1 devices

Joe Clarke · ‎01-09-2008

What about the dmgtd.log? I don't see any errors here.

yjdabear · ‎01-09-2008

Doesn't look very interesting to me:

Joe Clarke · ‎01-09-2008

No. I see no reason why ConfigMgmtServer stopped. Perhaps someone killed it. But I would expect to see it dying on some signal in daemons.log. In any event, restarting it should help. If not, you will nee to restart dmgtd.

yjdabear · ‎01-09-2008

Does pidm.log show any additional light?

Could you also take a look at my other outstanding issue: "RME 4.0.5: Syslog Records - Default purge job"?