cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
849
Views
0
Helpful
8
Replies

Processess not working

nawas
Level 4
Level 4

I cannot bring up the GUI, it says page cannot be found. When I try to
stop/start the daemon I get the following error

$ cd /

$ cd etc/init.d

$ sudo ./dmgtd stop

Password:

Daemon Management is not running.

INFO : Stopping DBEngine processes registered to Daemon Manager

WARNING: Daemon Manager could not stop DBEngine processes.

WARNING: Please run the command "/opt/CSCOpx/bin/dbstop.pl all"

WARNING: to stop DBEngine processes manually.

ps -ef | grep CSCOpx

casuser 20940     1   0   Sep 25 ?         177:03 /opt/CSCOpx/objects/db/bin64/dbsrv10 -x tcpip{HOST=localhost;DOBROADCAST=NO;Ser

casuser 20996     1   0   Sep 25 ?         141:39 /opt/CSCOpx/objects/db/bin64/dbsrv10 -x tcpip{HOST=localhost;DOBROADCAST=NO;Ser

casuser 20986     1   0   Sep 25 ?        1115:38 /opt/CSCOpx/objects/db/bin64/dbsrv10 -x tcpip{HOST=localhost;DOBROADCAST=NO;Ser

casuser 21093     1   0   Sep 25 ?         230:50 /opt/CSCOpx/objects/db/bin64/dbsrv10 -x tcpip{HOST=localhost;DOBROADCAST=NO;Ser

Please advise how do I fix this.

Thanks.

8 Replies 8

nawas
Level 4
Level 4

Anyone know how do I fix this problem?

yjdabear
VIP Alumni
VIP Alumni

Have you followed the advice dmgtd spit out: run the command "/opt/CSCOpx/bin/dbstop.pl all"? That usually does the trick, in LMS 3.1, for me.

Yes, I did this but that didn't help, please see below

/opt/CSCOpx/bin/dbstop.pl all
    Stopping database engine aniEng
SQL Anywhere Command File Hiding Utility Version 10.0.1.3830

    Stopping database engine ipmEng
SQL Anywhere Command File Hiding Utility Version 10.0.1.3830

    Stopping database engine cmfEng
SQL Anywhere Command File Hiding Utility Version 10.0.1.3830

    Stopping database engine opsxmlEng
SQL Anywhere Command File Hiding Utility Version 10.0.1.3830

    Stopping database engine rmengEng
SQL Anywhere Command File Hiding Utility Version 10.0.1.3830

ps -ef | grep CSCOpx
casuser 20940     1   0   Sep 25 ?         177:06 /opt/CSCOpx/objects/db/bin64/dbsrv10 -x tcpip{HOST=localhost;DOBROADCAST=NO;Ser
casuser 20996     1   0   Sep 25 ?         141:42 /opt/CSCOpx/objects/db/bin64/dbsrv10 -x tcpip{HOST=localhost;DOBROADCAST=NO;Ser
casuser 20986     1   0   Sep 25 ?        1115:42 /opt/CSCOpx/objects/db/bin64/dbsrv10 -x tcpip{HOST=localhost;DOBROADCAST=NO;Ser
muhamns  1578 25316   0 11:10:21 pts/2       0:00 grep CSCOpx
casuser 21093     1   0   Sep 25 ?         230:52 /opt/CSCOpx/objects/db/bin64/dbsrv10 -x tcpip{HOST=localhost;DOBROADCAST=NO;Ser

Looks like only one of the five DBs was shut down. What does "/usr/ucb/ps auxww | grep dbsrv" show?

My notes says after "dbstop.pl all", the rest of the casuser processes could be terminated with "kill -TERM". However, I'd be wary of using it, since the issue with the dmgtd of LMS 2.x was fixed. Which version of LMS are you running?

I was able to kill the process able to restart daemon but my GUI is still not coming up. I see the daemons.log is copying into daemonsbackup.log and it is making sever very slugish.

$ ls -l dae*
-rw-rw----   1 casuser  casusers 92525097638 Nov 30 13:27 daemons.log
-rw-rw----   1 casuser  casusers 28840427520 Nov 30 13:38 daemonsbackup.log
$ ls -l dae*
-rw-rw----   1 casuser  casusers 92525097638 Nov 30 13:27 daemons.log
-rw-rw----   1 casuser  casusers 42261807104 Nov 30 13:43 daemonsbackup.log
$ ls -l dae*
-rw-rw----   1 casuser  casusers 92525097638 Nov 30 13:27 daemons.log
-rw-rw----   1 casuser  casusers 48628760576 Nov 30 13:46 daemonsbackup.log
$
$ ls -l dae*
-rw-rw----   1 casuser  casusers 92525097638 Nov 30 13:27 daemons.log
-rw-rw----   1 casuser  casusers 62721622016 Nov 30 13:51 daemonsbackup.log

I've never seen such huge daemons.log files.

I think you might want to look into what it's reporting in there.

Here're mine:

-rw-rw----   1 casuser  casusers 32968409 Nov 30 14:01 daemons.log
-rw-rw----   1 casuser  casusers 665205514 Nov 16 13:55 daemonsbackup.log

Finally i was able to login but several processes are down and I'm not able to and CiscoWorks is really sluggish. Any advise what to look at?

I have checked the daemons.log but now it is not very huge, I treid to rotate daemonsbackup.log but it didn't help either.

-rw-rw----   1 casuser  casusers   57838 Nov 30 14:42 daemons.log
-rw-rw----   1 casuser  casusers 92525097638 Nov 30 13:27 daemonsbackup.log

I have opened a TAC case but TAC Engineer doesn't seem to be very helpful or knowledgeable. Anyone here can advise?

I think it is strange, when I tried to read daemonbackup.log most of the file is empty lines but the file size is still 92GB. Any clue?

Do we have Joe Clark here who can look at my post?

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: