Re: [foxboro] Commit procedure after initial install

Steve.....it is a benign message. It would appear that this AW51E does not
host the Device Monitor package. During any committal install you will see
in the pkg.XXXXXXXXXXX file an attempt to create a device monitor file.
Apparently your box does not host DevMon.

Also of note ...you mention that you always have to bypass on previously
installed packages. This usually indicates that you are passing a day 0
committal thru your already installed stations. This can be dangerous.

Your commit diskette should say DONE for all previously installed packages
and in your case only the new FBM's should say NOTYET......

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Murray, Steve
Sent: Thursday, January 27, 2005 11:51 AM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: [foxboro] Commit procedure after initial install

Hi All,

  I added a few FBMs using sysdef (on a NT workstation), created a commit
disk, and started the "Install_AW" on an AW51E.

  The AW51E was not the host of the new FBMs, but I ran the commit on it
first as a test case.

  I choose "bypass" for each of the previously installed packages and did
not get any errors in the install logs.

  I then did a remote install to the host AW51B for the new FBMs and also
choose "bypass" for each of the previously installed packages.

  I have the following warning in the installation log:

16:30 ------ OS6AW1 Running Post-Process Script. . .Warning

and the following in the package init log:

/opt/fox/OS6AW1/install/post_S6AW1: /opt/fox/ADMON/install/bld_dmf: not
found
Creating Device Monitor Configuration File ... FAILURE
Edit of OS config file ... Done
Checking for patches to install ...
done

  I tried a remote install on another AW51B with the same warning and devmon
file failure, so I did a local install on it and got the exact same warning.

  The directory /opt/fox/ADMON/install/ does not exist on the first AW51E,
and only contains the file "request" on the two AW51Bs that gave me the
warnings.  The request file contains the timestamp from the last major
upgrade in 2001.

  A quick review of the logs from previous installs show the same devmon
file failure has happened on some of my other AWs in the past.

  Is it something serious or benign?

  What is the right procedure for running the commit disk through all of the
AWs & WPs in the plant?  

  Should I be clicking on the "bypass" option for previously installed
packages or re-install them each time I run the commit disk?

  Should I even be trying to do remote installs?

  The sysdef and the software installation manuals don't seem to address
minor changes - only day 0 installs.

  I am running IA version 6.1 with a mix of AW51Bs, WP51Bs, and two AW51Es.

  Thanks for any tips,

Steve Murray
Asarco

*

This e-mail and any files transmitted with it are the property of Americas
Mining Corporation and/or its affiliates, are confidential, and are intended
solely for the use of 
the individual or entity to whom this e-mail is addressed. If you are not a
named recipient or otherwise have reason to believe that you have received
this message in error, 
please notify the sender and delete this message immediately from your
computer. Any other use, retention, dissemination forwarding, printing or
copying of this e-mail is 
strictly prohibited.  Although this email and any attachments are believed
to be free of any virus or other defect that might affect any computer
system into which it is 
received, and opened, it is the responsibility of the recipient to ensure
that it is virus free and no responsibility is accepted by Americas Mining
Corporation and/or its 
affiliates for any loss or damage arising in any way from its use

This e-mail has been scanned and cleared by MailMarshal 
www.marshalsoftware.com

*
 
 
_______________________________________________________________________
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
 
 
 
_______________________________________________________________________
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: