Re: [foxboro] Remove autostart of legacy servers?
- From: Kevin FitzGerrell <fitzgerrell@xxxxxxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Fri, 17 Mar 2006 22:09:47 +1300
Hi Dave,
Thanks for the reply.
I'm still using the AW as a remote collector, but no longer want it to
be a legacy server.
I don't have an ipname_for_r_servers file, but fetchdog and ipchisti are
still started on reboot, and dog.log is predictably large and full of
errors.
I could remove /opt/aim/ and /opt/windu and re-install the remote
collector and anything else using windu, but I'd prefer a less drastic
approach.
Regards,
Kevin FitzGerrell
Carter Holt Harvey, Ltd.
+64 27 460 9994
Hicks, David wrote:
> Kevin,
>
> If you have workstations that are no longer serving historian interface be
> it remote or local you should remove the AIMHISTORIAN line from the
> /usr/fox/bin/fox_apps.dat file. Also the go_AIMHISTORIAN script should also
> be removed. Conversally, if you need to stop the legacy historian you would
> remove the AHXXXX entry from the same file. These start up the hist server
> processes as well as the ipchisti process. If you have the same historian
> name running under the different ipchisti processes this can cause problems
> with data collection and where the data is stored.
>
> If by chance you are still serving historian interface local or remote, but
> have changed the location of the collector, you should remove the file
> ipname_for_r_servers. By removing this entry the start_server does not know
> which remote server to communicate with, thus will not start to remote
> historian collector.
>
> Hope this helps
>
> Dave Hicks
> Invensys Systems, Inc
> david.hicks@xxxxxxxxxxxxxxxx
>
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx
> To: foxboro@xxxxxxxxxxxxx
> Sent: 3/16/06 10:24 PM
> Subject: [foxboro] Remove autostart of legacy servers?
>
> Hi all,
>
> Anyone have any idea to remove the auto-startup of legacy servers on an
> AW?
>
> We've got a network with 4 AW51Es running remote collectors for an
> off-platform
> AIM* instance. We moved the legacy server function from one AW to
> another, but
> it looks like once you've run:
> start_server RFH {ipname}
> on a workstation it writes something into the Bristol windu registry
> that causes
> ipchisti and fetchdog to automatically start each time the workstation
> reboots.
>
> Now, whenever the workstation that originally had the legacy servers
> reboots it
> starts fetchdog and ipchisti.
>
> I had a CAR in on this with Foxboro for a couple years and never got it
> resolved.
>
> Any ideas anyone?
>
> I tried to run the windu regedit to have a look at the registry, but it
> gives an
> error:
> ld.so.1: regedit: fatal: libgen.so.1: open failed: No such file or
> directory
>
> Regards,
>
> Kevin FitzGerrell
> Carter Holt Harvey, Ltd.
> +64 27 460 9994
>
>
> _______________________________________________________________________
> 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:
