Trends only showing a yellow flashing
Hello
I have problems with logs in 800xA version 6.
Some logs only show flashing yellow ie no log appears in the trend window.
Have checked the log summary and every log shows "passed".
I have two pairs of SG CS2 / CS3 and CS4 / CS5.
I compare Logs, DirectLogs and PercentSynchronized between the two different service providers CS2 with CS3 and CS4 with CS5
CS2 and CS3 show the same Logs and Directlogs but PercentSynchronized shows CS2 = 89% and CS3 = 84%
CS4 and CS5 show the same Logs and Directlogs but PercentSynchronized shows CS4 = 92% and CS5 = 88%
I have seen it been so for several days ie the same percentage.
Should they be 100% in a prosperous system?
mvh / otherwise
I have problems with logs in 800xA version 6.
Some logs only show flashing yellow ie no log appears in the trend window.
Have checked the log summary and every log shows "passed".
I have two pairs of SG CS2 / CS3 and CS4 / CS5.
I compare Logs, DirectLogs and PercentSynchronized between the two different service providers CS2 with CS3 and CS4 with CS5
CS2 and CS3 show the same Logs and Directlogs but PercentSynchronized shows CS2 = 89% and CS3 = 84%
CS4 and CS5 show the same Logs and Directlogs but PercentSynchronized shows CS4 = 92% and CS5 = 88%
I have seen it been so for several days ie the same percentage.
Should they be 100% in a prosperous system?
mvh / otherwise
Asked 7 months ago
Voted best answer
3
Hi,
The pending logs for the synchronisation can view in afwapplogviewer. Please find the attached image. Choose the correct server. Like this you can troubleshoot the synchronisation problem.
image
You can do the force synchronisation as follows
The pending logs for the synchronisation can view in afwapplogviewer. Please find the attached image. Choose the correct server. Like this you can troubleshoot the synchronisation problem.
image
You can do the force synchronisation as follows
- Stop the Basic History Service provider on CS1 and wait until the service is stopped.
- Open a Windows Explorer on CS1 and go to <datadisk>:\OperateITData\History\{provider ID} and remove SyncFile.dat and UpdateStorage.dat.
- Start the Basic History Service provider on CS1
- When the Basic History Service provider on CS1 enters Service mode wait 20 minutes and then stop the Basic History Service provider on CS2 and wait until the service is stopped.
- Open a Windows Explorer on CS2 go to <data disk>:\OperateITData\History\{provider ID} and remove SyncFile.dat and UpdateStorage.dat.
- Start the Basic History Service provider on CS2.
CS1 and CS2 are pairs.
Answers
1
Yellow flashing may occur if there is connectivity issue between 800xA History and connectivity/Client.
Try restart of Connecitivity/Client , if not try to restart to History Server.
Plan restart of Server without interruption of Operation.
Try restart of Connecitivity/Client , if not try to restart to History Server.
Plan restart of Server without interruption of Operation.
Answered 7 months ago
0
Hello
One update
I think it's resolved.
I used the app log viewer / listErrorLogs and there were about 40 signals / logs that were something wrong with.
I restarted the CS servers, disabled / enabled trends and providers, but it was the same error.
In the end, I removed LogConfiguration on these signals and waited for percent sync to become 100% on all providers.
Then I made new LogConfigurations on all those I had removed and waited 1 hour, I restarted all CS and all providers showed 100% synchronized.
Now it has worked in the last 18 hours so I hope everything was OK.
mvh / anders
One update
I think it's resolved.
I used the app log viewer / listErrorLogs and there were about 40 signals / logs that were something wrong with.
I restarted the CS servers, disabled / enabled trends and providers, but it was the same error.
In the end, I removed LogConfiguration on these signals and waited for percent sync to become 100% on all providers.
Then I made new LogConfigurations on all those I had removed and waited 1 hour, I restarted all CS and all providers showed 100% synchronized.
Now it has worked in the last 18 hours so I hope everything was OK.
mvh / anders
Answered 7 months ago
Add new comment