Cisco Works- Down Processes

Answered Question
Sep 19th, 2008
User Badges:

All,

I am just starting to configure Cisco Works I am in Common Services and I have some downed processes, they are listed below. Does anyone know what could be causing the downed services?



Down Processes: EPMDbMonitor, NOSServer, CmfDbMonitor, FHServer, IPMProcess, SyslogAnalyzer, CTMJrmServer, Interactor1, DFMCTMStartup, EDS-GCF, IPMOGSServer, CMFOGSServer, DFMOGSServer, DataPurge, INVDbMonitor, ChangeAudit, NetShowMgr, InventoryCollector, CampusOGSServer, Interactor, TISServer, NCTemplateMgr, jrm, UTManager, ConfigMgmtServer, DCRServer, ICServer, EssentialsDM, InventoryCollector1, TomcatMonitor, PTMServer, RMEDbMonitor, RMEOGSServer, IpmDbMonitor, FHDbMonitor, OpsxmlDbMonitor



Mario

Correct Answer by Joe Clarke about 8 years 10 months ago

Yeah, everything is hosed. Your problem is most likely due to a socket starvation issue triggered by a DLL conflict with DFM. If you upgrade to LMS 3.0.1 followed by DFM 3.0.3, this problem will go away. As a workaround, you can periodically restart Daemon Manager whenever the problem occurs.


LMS 3.0.1 can be downloaded from http://www.cisco.com/cgi-bin/tablebuild.pl/lms301 , and the DFM 3.0.3 service pack can be obtained via Common Services > Software Center > Software Update.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Joe Clarke Fri, 09/19/2008 - 08:04
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Please post the output of the pdshow command.

mrashby Fri, 09/19/2008 - 08:37
User Badges:

I had to add it as an attachment because it is over the character limit so I can't post it in the body of the message. So please see the attachment.



Joe Clarke Fri, 09/19/2008 - 08:40
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

What version of DFM do you have installed?

mrashby Fri, 09/19/2008 - 08:43
User Badges:

The DFM version and patch level is 3.0.0

Also I can't use the group admin in common services it is telling me "Error in communicating with Group Administration Server. It may be down or not yet up. Please make sure that the Group Administration Server is up and running, then refresh the page."

Correct Answer
Joe Clarke Fri, 09/19/2008 - 08:54
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Yeah, everything is hosed. Your problem is most likely due to a socket starvation issue triggered by a DLL conflict with DFM. If you upgrade to LMS 3.0.1 followed by DFM 3.0.3, this problem will go away. As a workaround, you can periodically restart Daemon Manager whenever the problem occurs.


LMS 3.0.1 can be downloaded from http://www.cisco.com/cgi-bin/tablebuild.pl/lms301 , and the DFM 3.0.3 service pack can be obtained via Common Services > Software Center > Software Update.

mrashby Mon, 09/22/2008 - 11:21
User Badges:

J,

Thanks that update cleared things up. This is what I have now


Critical Message Window:

CiscoWorks Folder Utilization is 6%


Processes DFMCTMStartup, DataPurge are down

Log files ESSMonitor.log exceeded the recommended size limit


Joe Clarke Mon, 09/22/2008 - 12:10
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Looks like you're in good shape. The DFMCTMStartup and DataPurge processes are allowed to be down (and typically are). The fact that they show up as critical here is a bug.


If you want to keep log file disk space utilization down, consider implementing logrot. Search the Common Services online help (or this forum) for more on configuring logrot.pl.

Actions

This Discussion