Re: [foxboro] DM Locked Up with Go-Global
- From: "Schaff, Alan J." <Alan.Schaff@xxxxxxxxxxxxx>
- To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 29 Jun 2004 13:09:29 -0700
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
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
--
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
Honeywell Nylon
_______________________________________________________________________
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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
_______________________________________________________________________
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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
_______________________________________________________________________
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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
