Re: [foxboro] DM Locked Up with Go-Global

Alan,

We are running 4.3, but we have the same problem when people do not exit
Exceed properly.  I found that I first have to kill the two processes
spawned by the original display manager process: dm_wp50, and
blink_task.  After killing these, the original display manager process
stops by itself.

I use this script to find them:

AW5001# more ckdm
echo " grep go_"
ps -eaf | grep go_
echo "grep dm_"
ps -eaf | grep dm_
echo "grep blink_task -f"
ps -eaf | grep 'blink_task -f'

This is the output from the script.

AW5001# ckdm
 grep go_
    root 20811 20810  0 14:11:57 pts/3    0:00 grep go_
      ia 25440     1  0   Jun 27 ?        0:00 sh -c
/opt/ia/go_dmreactor &
grep dm_
    root 20813 20810  0 14:11:57 pts/3    0:00 grep dm_
    root 25448 25440  1   Jun 27 ?       22:12 /usr/fox/wp/bin/dm_wp50
grep blink_task -f
    root 20815 20810  0 14:11:57 pts/3    0:00 grep blink_task -f
      ia 25446 25440  0   Jun 27 ?        0:03
/usr/fox/wp/bin/blink_task -f
AW5001#=20

To stop the display manager (25440), kill 25446 and 25448.  Then 25440
will go away on its own.  Type carefully!=20

Hope this works.
Don



-----Original Message-----
From: Schaff, Alan J. [mailto:Alan.Schaff@xxxxxxxxxxxxx]=20
Sent: Tuesday, 29 June, 2004 1:09 PM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: Re: [foxboro] DM Locked Up with Go-Global


Duc,
If I remember correctly we have tried killing the PID with no success.
But I will verify the next time it happens. Also, we are running version
6.5 on an AW51E.

_________________________Honeywell
Alan Schaff
Control Systems Engineer=20
Clemson Site
Phone: (864) 639-7368
Pager:  (864) 410-8723
Fax:     (864) 639-7364
E-mail: Alan.Schaff@xxxxxxxxxxxxx




-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of duc.do@xxxxxxxxxxxxxx
Sent: Tuesday, June 29, 2004 3:09 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] DM Locked Up with Go-Global


Alan,

What version of software are you running?

I ask because I remember we used to have problems like this in the
previous software version we were at (6.1, if I recall correctly) if the
DM is exited any way other than through the DM_Usage screen. We no
longer have to be that rigid now at v6.2.1.

Nonetheless, every once in a great while, there still is an issue with a
DM that has been terminated but still shown up as being used on the
DM_Usage screen. Instead of rebooting the AW or WP, we just kill the
offending process using "kill <PID>" on the command line.

To find the process ID of the DM in question, download the program
dmstatus
(dmstat.tar.Z) from the Cassandra web site.

Duc

--=20
Duc M. Do
Dow Corning Corp.
Carrollton Plant
Carrollton, KY, US


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Schaff, Alan J.
Sent: Tuesday, June 29, 2004 2:50 PM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: [foxboro] DM Locked Up with Go-Global


I have a question for all of you Go-Global users.  We are having a
problem with multiple Go-Global DM's running on a single AW.  We have 5
DM's that can run on this AW remotely using Go-Global.  We are seeing
the DM will disappear on the remote computer but the AW will not release
that DM to be used.  It's like the AW has a hold of it but it won't let
go.  I suspect it has to do with the improper shutdown of the DM but
that's another problem. The real problem is that the only way to free up
the DM is to reboot the AW!!!  We can't kill the DM or stop it via the
DM usage display.  Up to this point Foxboro hasn't given us an answer
and we are getting tired of having to reboot the AW.  Has anyone else
seen this type of behavior and if so what was the fix?

Thanks,

Alan Schaff
Control Systems Engineer=20
Honeywell Nylon



=20
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
=20
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
=20
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
=20
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
=20
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
=20
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: