Need help troubleshooting CiscoWorks on Solaris

Unanswered Question
Jul 20th, 2009

Thanks for the help in advance...

We've just recently installed our CiscoWorks on Solaris. We've had it justlong enough to configure all of our network devices into the database and start some use.

Unfortunately, we had a power outage in our building where our backup power also failed. The server crashed very unceremoniously. The server itself came back up with no issues, but we are unable to reach CiscoWorks with a browser. There were no fsck's to be done and all services up and running.

I've checked the support page for troubleshooting guides. There's one for CiscoWorks for Windows, but nothing for CiscoWorks for Solaris. Maybe I'm just not looking in the right place?

The error message from the browser (firefox):

Though the site seems valid, the browser was unable to establish a connection.

I have one Cisco process up:

root 678 1 3 13:53:52 ? 95:19 /opt/CSCOpx/objects/dmgt/dmgtd.sol

No apache processes.

We don't have another working server that I can use to compare with.

Any hints or starting points are greatly appreciated! Thanks!

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Joe Clarke Mon, 07/20/2009 - 11:57

Post the /opt/CSCOpx/MDC/etc/regdaemon.xml file, the daemons.log, and the dmgtd.log.

evannerash Mon, 07/20/2009 - 12:36

That's a lot of info, so I'll give you what should be the relevant info.

[email protected] # more daemons.log

ERROR: open file dmgtd failedWARNING: dmgtd exiting now: (thread:1 sig:15)

INFO >>>>>>>>>>>>>>>>>>>>>>>>>>>>> REACTOR thread (tid=1) exited; rc=1.

ERROR: open file dmgtd failed

[email protected] #

Two messages in dmgtd.log from 7/15/09 when it was started back up:

Jul 15 14:33:01 CiscoWorks dmgt[683]: [ID 921214] #3001:TYPE=INFO:Us

ing port: tcp/42340.

Jul 15 14:33:01 CiscoWorks dmgt[683]: [ID 215912] #3003:TYPE=INFO:No

application started at start time.

(nothing else until today when I rebooted)

The /opt/CSCOpx/MDC/etc/regdaemon.xml is attached.


Joe Clarke Mon, 07/20/2009 - 12:57

Post the /opt/CSCOpx/objects/dmgt/dmgtd.conf along with the ls -l output of the dmgt directory.

evannerash Mon, 07/20/2009 - 13:03

Here's the ls -la:

[email protected] # ls -la /opt/CSCOpx/objects/dmgt/

total 1018

drwxr-x--- 3 casuser casusers 10 Jul 15 14:32 .

drwxrwxr-x 28 casuser casusers 28 May 29 11:35 ..

-rw-r----- 1 casuser casusers 0 May 28 19:52 Cri.log

-rw-r----- 1 root root 0 Jul 12 00:00 dmgtd.conf

-rw-r----- 1 casuser casusers 44305 Jul 12 00:00 dmgtd.conf.backup

-rwxr-x--- 1 casuser casusers 316032 Jun 15 2008 dmgtd.sol

-rw-r----- 1 casuser casusers 9387 May 29 10:46 _nsdb_root

-rwxr-x--- 2 casuser casusers 60660 Jun 15 2008 pdcmd.sol

drwxr-xr-x 2 casuser casusers 2 Jul 20 13:53 ready

-rw------- 1 casuser casusers 1933 Jul 11 23:55 sadiags.xml

[email protected] #

It looks like the dmgtd.conf file was backed up and emptied out 3 days before the crash. I'll attach the dmgtd.conf.backup file.



Joe Clarke Mon, 07/20/2009 - 13:17

That's the problem. Copy dmgtd.conf.backup to dmgtd.conf, then restart dmgtd, and you should be good to go. Make sure dmgtd.conf is owned by casuser:casusers.


This Discussion