DFM 3.2.0 problems - fails to start

Answered Question
Jul 26th, 2009
User Badges:

DFM 3.2.0 is failing to start under Solaris.


I get the following under High Severity Alerts.

"An exception occurred.Please check the AAD.log file for further details."


The Critical Message Window under CS shows this:

"Processes DfmBroker are down"


AAD.log and pdshow attached.



Correct Answer by Joe Clarke about 7 years 11 months ago

Ye, tcp/9002 is in use by another process. You must free up this port, then restart dmgtd.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Joe Clarke Sun, 07/26/2009 - 16:48
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Post the /opt/CSCOpx/objects/smarts/local/logs/brstart.log. This is most likely due to a port conflict. DFM requires tcp/9002 to be available.

Correct Answer
Joe Clarke Sun, 07/26/2009 - 17:53
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Ye, tcp/9002 is in use by another process. You must free up this port, then restart dmgtd.

eidumsigfrid Sun, 07/26/2009 - 20:27
User Badges:

Ok managed to free up the port, restarted dmgtd, still no luck.


Decided to delete NMSROOT\log\pidm.log, restarted dmgtd and it worked.

Actions

This Discussion