Re: [foxboro] SysMon error messages

Duc,

Regarding your second error message:

2007-03-27 13:35:54 30AW01 Process =3D3D smon_ech VENK   000008 Exec =3D
format
error /usr/fox/sp/sta_sw.cfg

I saw that message on one our P92's (XP AW) at v8.2 after I manually
killed the smon tasks and tried to manually restart these tasks (I was
restarting it incorrectly).  I thought a reboot would help, but it
didn't.  Though I hadn't run a commit through recently, I had to run the
latest through again to fix the /usr/fox/sp/sta_sw.cfg file.  I set the
ASMDW7 SMDH For WP/AW (XP) software status to PCHANG and made a new
commit diskette.  After running the commit through again, I no longer
got this message.

That might be something to try if it is an option to run a commit
through it.

Thanks,
Philip Pulas
Tesoro
Martinez, CA

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of duc.do@xxxxxxxxxxxxxx
Sent: Tuesday, March 27, 2007 12:35 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] SysMon error messages

Hi list,

I'm stumped over a couple of unrelated error message from SysMon.

The first one:

2007-03-27 13:27:59 30AW01 Error Protocol FXM_SS 000007 FXM - A critical
child process died 000C46EA3BE8

was the last message produced before the P91 (XP AW) workstation
spontaneously rebooted. It's at v8.2 with all the latest XP security
patches (up to the Feb 20, 2007 patches). I couldn't find anything on
the CSC Web site searching for FXM_SS or FXM. Any clue?

(Kevin Fitzgerrell's pet peeve about lack of documentation for error
messages is mine, too!)


The second one:

2007-03-27 13:35:54 30AW01 Process =3D3D smon_ech VENK   000008 Exec =3D
format
error /usr/fox/sp/sta_sw.cfg

came in while the same P91 box booted up. Looking back through the
SysMon log, we saw this same error message the last three times it
booted up (since early Feb), but not before that. The file sta_sw.cfg
was created by SysDef, and the last time we did any software install
and/or committal was back in Nov '06. So the timing when this error
started to appear doesn't make sense. Any thought?

Thanks!

Duc

--=3D20
Duc M. Do
DCS Group, Carrollton Plant
Dow Corning Corporation
Carrollton, KY, US


=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: