Re: [foxboro] Aim * historian server
- From: "Moore, Kenneth, Celanese/US" <ken.e.moore@xxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 27 Jul 2005 15:10:17 -0500
Thanks Patrick,
I didn't follow your advice exactly, but using the apiadmin was the way
to go.=20
Everything is running as expected now.
Best regards,
Ken Moore
Celanese Emulsions
Enoree Plant
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Den Haese, Patrick
Sent: Wednesday, July 27, 2005 9:14 AM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: Re: [foxboro] Aim * historian server
Ken,
Under /opt/aim/bin check the processes with "P" or histps checks all AIM
processes.
If you have trends your instance is up and running.
There can be 2 reasons: 1 an_init.cfg is missing (opt/windu I believe),
2 apihosts is not running.
The best thing to do is start apiadmin check if you can connect to your
server, if not -> edit server connection , disable broadcasts and add
your host with IP address. Save this and try to start your histmgr.
Hope this helps.
Patrick
Patrick Den Haese
patrick.denhaese@xxxxxxxxxxxxxxxx=20
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Moore, Kenneth, Celanese/US
Sent: 27 July, 2005 14:43
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Aim * historian server
Someone, somehow, has did something to our Aim* historian. When you try
to launch the histmgr it cannot connect to the server. If you launch the
histcfg you also get an error about no server available. If you do a ps
for hist, the collector and reductions are running, all the trends in
I/A appear to be working. It looks like we may have lost our instance.
Any and all suggestions would be most welcome.
Running I/A ver 7.0, Aim* 3.2 on a AW51F.
Thanks,
Ken Moore
Celanese Emulsions
Enoree Plant=3D20
=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
=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: