Ignacio,
Yes, the racing condition that sometimes happens between Checkpoint Spy
and the IA system itself can cause problems, and that's why Ricardo
introduced the wait.dat file to slow down Checkpoint Spy. Hope you have
pinpointed the source of your problem.
Regards,
Duc
On 2020-12-08 03:25 PM, QUEIROLO, IGNACIO ESTEBAN wrote:
Thanks Duc! I think that now is working fine. I am testing it doing
some checkpoints from System Manager and I see the files you
mentioned. At the first try, the file .configx had only 4 lines for
one CP. So, I added a delay of 60 seconds to the file wait.dat in
D:\opt\foxray\login folder and I checkpointed again the same CP, and
this time the file contains much more information.
Regards,
Ignacio
-----Mensaje original-----
De: Duc M Do <duc@xxxxxxxxxx>
Enviado el: martes, 8 de diciembre de 2020 17:04
Para: foxboro@xxxxxxxxxxxxx
CC: foxboro-bounce@xxxxxxxxxxxxx; QUEIROLO, IGNACIO ESTEBAN
<ignacio.queirolo@xxxxxxx>
Asunto: Re: [foxboro] System Auditor missing block
Ignacio,
The source(s) of your problem can be one (or more) of several:
1. Like Philip Pulas mentioned, the Checkpoint Spy on your CP host may
not be running, or running but not functioning properly. If you're
running Solaris, then Checkpoint Spy is started as a daemon. Run 'ps
-eaf' to see if it's running. If you're on Windows, Checkpoint Spy is
a service and is started automatically upon the AW booting up; check
the list of services to see if it's running.
2. A week ago, Matt Gunter had a somewhat similar problem with his
Foxray/SA installation, and it turns out the data transfer between the
data collector (AW) and the SA server failed. You can try manually
running an ftp session between your AW and the SA server to make sure
ftp is still functioning correctly.
3. Check the directories where the collected data are kept on the AW
(/opt/foxray/login/SYSTEMX, HLBLX, and PLBX), these files are
aggregated here before being transferred to the SA server, then
deleted. If you see a large collection of files here, that's a
telltale sign that the data transfer is not happening properly.
4. Likewise, check the directory on the SA server where it keeps the
data sent by the AWs. This should be below your installed SA
directory, something like $FOXRAY\<network>\SYSTEMX, HLBLX, and PLBX.
There can be multiple files with the extension .configx and .ready,
but these should not be older than the interval that slow_import.bat
is scheduled to run (ie. if slow_import.bat is run three times a day
at equal intervals, these files normally should not be older than 8
hours). If there are a collection of files here, then your import
batch file is not functioning properly, or the database updating
component, Update_Foxray.exe, is not working properly.
Hopefully this simple troubleshooting guide helps you.
Duc
Two months ago, I have added a new block to a DCS with System Auditor
(SA) and the new block does not appear in SA database. Any thoughts?
Thanks in advance.
Ignacio
