Re: [foxboro] Commit procedure after initial install

QF11581 was one of the culprits that would put ADMON (AP20)directory on a 51
box

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Kevin FitzGerrell
Sent: Thursday, January 27, 2005 3:12 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Commit procedure after initial install

Steve,

I'm not sure exactly where the /opt/fox/ADMON directories came from, but I
find
them on nearly all A and B boxes I've worked with.  I've always assumed they
were introduced via one of the devmon quick fixes, and not corrected because
the
package log files are slightly cryptic.

I failed to mention that after you've removed the /opt/fox/ADMON directories
you
should recommit, but you probably figured that.

The failure to create the device monitor configuration file often does not
show
up for years -- I noticed it first on a site where several months after
changing
the name of a COM10, alarms suddenly stopped going to it.  The device
monitor
master had shifted to a workstation with the ADMON directory (and so had an
out
of date device monitor configuration file).  

Regards,

Kevin FitzGerrell
Systems Engineer
Foxboro New Zealand
------------------------------------
Tel:  +64 (9) 573 7690
Fax:  +64 (9) 573 7691

Quoting "Murray, Steve" <SMurray@xxxxxxxxxx>:

> Hi Kevin,
> 
>  The /opt/fox/ADMON directory was created in every existing AW & WP in
> April 2001, which is when we had our last IA upgrade. The only file in
> this
> directory is a script called "request".
> 
>  I added the two AW51E's after 2001, and they do not have the
> /opt/fox/ADMON directory. 
> 
>  I will try deleting the /opt/fox/ADMON directory on one of the
> machines
> and try again.
> 
>  If I did commits & reconciles more often I'd probably know what I was
> doing . . .
> 
>  Thanks for your help,
> 
>  Steve Murray
>  Asarco
> 
> -----Original Message-----
> From: Kevin FitzGerrell [mailto:fitzgerrell@xxxxxxxxxxxxxxx]
> Sent: Thursday, January 27, 2005 10:55
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] Commit procedure after initial install
> 
> 
> Steve,
> 
> There shouldn't be an /opt/fox/ADMON directory on any 51 series. The 
> device monitor is package ADM6, not ADMON on 51s.
> 
> If the directory /opt/fox/ADMON exists, your device monitor 
> configuration file will not be created, and you will get the FAILED 
> message in your package log.
> 
> You should remove this directory on the two B boxes where you noticed 
> the message and check all your other workstations (AW and WP) for the 
> same problem.
> 
> If there have been any changes like moving an alarm printer, adding 
> workstations, or changing device names, these failures can create a 
> problem where the device monitor configuration files differ between 
> workstations. When the current device monitor master is rebooted for 
> some reason, another workstation assumes mastership. If it's device 
> monitor configuration file is different, alarms may not go to the 
> specified devices.
> 
> If you're having to bypass software packages, I'd assume you haven't 
> reconciled your system definition since the last Day0. It's better to 
> have all the installed packages marked DONE in sysdef than to bypass on
> 
> install.
> 
> I do remote committals regularly on large sites. My only recommendation
> 
> with remote installs is to exit the INSTALL_AW or INSTALL_WP screen 
> after each remote committal, otherwise you end up daisy chaining remote
> 
> connections, which really slows things down.
> 
> On your AW51E box, consider re-installing the ADM6 package.
> If it should be running device monitor, consider doing the following:
> Run: dm_recon t (transfer DevMon to this station)
> wait about 30 seconds
> Next: dm_recon d (dump current status)
> Check the resulting file: cs_dm.current and see if all is correct
> If all is ok: run: dm_reconn (refresh info for control stations).
> 
> Regards,
> 
> Kevin FitzGerrell
> Systems Engineer
> Foxboro New Zealand
> +64 9 573 7690
> +64 27 284 5570
> 
> Murray, Steve wrote:
> > 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
>  
> ----------------------------------------------------------------------
> ------
> ----
> This e-mail message has been scanned for Viruses and Content 
> and cleared by MailMarshal. If this is spam please forward 
> this message to spam@xxxxxxxxxx so that we may evaluate it 
> and block future messages.
> -------------------------------------------------------------
> ---------------
> ----
> 
> *
> 
> 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
 
 
 
_______________________________________________________________________
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: