The FmTrend and FmRds servers were running on the olserver114. They build the full FFL file related to their stream by scanning the online and offline storage areas. After the operations performed on the offline storage area yesterday , they became red at the VPM level even if their ffl file were updated. Note that the FmTrend_ll and FmRds_ll servers are running correctly as they scan only the online storage areas
Some investigations were made by
- disabling the file checksum check, but without any improvements
- measuring the time to access a directory :
- the command time ls -lrt /data/archive_50Hz/129 returns
- on olserver117: real 0m0.452s, user 0m0.065s, sys 0m0.195s
- on olserver114: real 1m27.009s, user 0m0.108s,sys 0m1.799s
- on olserver119: real 1m24.357s, user 0m0.064s, sys 0m1.121s
- the command time ls -lrt /data/archive_trenddata/2002 returns
- on olserver117: real 0m0.111s, user 0m0.010s, sys 0m0.027s
- on olserver114: real 0m6.092s, user 0m0.025s, sys 0m0.138s
- on olserver119: real 0m5.845s, user 0m0.002s, sys 0m0.068s
- the command time ls -lrt /data/archive_50Hz/129 returns
It appears clearly that there is some issue with the access to the archive data area from olserver114 and olserver119 .
As the olserver117 host appears to not be use, for the moment the FmTrend and the FmRds servers are now running on this host and seems to run without issue.