trend status yollow blinking
i meet a problem when changed the minimum value for trend storage from 3 sec to 2 sec in the log configuration liberary thats just for test, then log modified all files on the system but after checked a trend i found the status yollow blinking and no history, after waiting and waiting i decided to restart connectivity server 1 after login i found all worked out hhhhhhh worth it.
now the question.
there was any possible action i had to do without restarting cs1? also why trend operates only from connectivity server 1?
Voted best answer
Restart the History Services.
Disable/enable the services in the configuration tab. Wait for them to fully stop before enabling again. If you have redundant history servers do them one at a time and wait for the service to synchronize before stopping the other.
Major changes to history often "upset" history logging. Restarting the services is an easy way to fix many problems.
Yellow Blink in the Trend display status indicates the trace in the trend trying to read history values continously. And it seems the BasicHistory service (AdvHtHistorySrv) is busy doing something.
Check the "ActiveAdviseRequests" value in the Provider Metrics of the Basic History service.
If you restart Primary CS swicthover to Secondary takes 2 seconds, during these 2 sec Data Collectors may loose data, this can be avoided by proper CS affinity configuration