Can you please help me with the below,
Where is the log file stored, if the secondary of a collective misses an event-synch for a PI Tag?
Thanks & Regards,
Per the liveLibrary: PI Server
If the secondary server could not process a particular event, examine the pirepl_syncfailurereport.txt file in the .../pi/log directory.
This file contains detailed information about the record that the secondary server could not process, including the individual fields in the record. The secondary server only generates the file when it fails to process a record. The server does not generate the file for other reasons, such as for missed events or unavailable subsystems. The server automatically removes the file when the secondary server synchronizes with the primary server
Waiting for your help, please let me know the details.
The application responsible for sending the data to multiple members of a PI Collective, is the PI Buffer Subsystem. The data isn't synchronize between members, it's fanned by the PI Buffer Subsystem.
With this in mind, has this point received data before on the secondary or is this a new PI Point? If it's new, than the data stream (interface, connector, custom application, etc...) isn't going through the PI Buffer Subsystem or there is an issue at that layer. I would recommend looking at the logs on the node were the data is coming from.
Thanks, Sebastien, I have read a few of your other replies related to this topic and agree that the data will be fanned to both the members of the collective by only the buffer-subsystem and the collective manager has no role to play, but how would one conclude that data is not fanned to one of the collective members or there was an error while fanning the data to one of the collective members or how can one confirm that data is being fanned to all the collective members? (Is it only possible through the buffering manager).
Buffering manager will show you if the data is being fanned or if it's caught in the buffer queue. Logs on the Data Archive will tell you if an issue happened from the time the data was received to when it is placed in the Archives. If there is a buffering issue, the logs on the node where pibufss is installed would help pin point the issue.
I hadn't refreshed my page so I didn't see Dan's answer until after I posted. It seems like we had a very different understanding of your issue. Could you perhaps share more details on what the issue is (screenshots, etc...).
Thanks, Sebastien, Would be following Dan's reply as that is more close to my query, But pls do respond to your first comment.
Additional to the above answers, you can set up a performance counters to understand whether your collective is in sync or not and configure the notifications for the same. Then you action it accordingly based on logs.
Retrieving data ...