21:00 UTC ITF found in SCIENCE
23:27 UTC Data loss (attached pic.): FbmFFE process stopped abruptly as it did at 16:00 (pic.1 from #67587). Restarted from VPM.
5:00 UTC ITF left in SCIENCE
Guard Tours (UTC)
- 21:38
23:03 - 23:38
1:03 - 1:39
3:13 - 3:48
The data loss around 2025-08-29-16h00m16s-UTC is due to the fact that SUSP_Fb was unable to transmit its frames to the FBmFFE server :
2025-08-28-16h00m16-UTC>WARNING-FdFrMrgr: Could not wait longer for frame parts, output 1440432025.8, nSources=15 first:SSFS_Fb
2025-08-28-16h00m16-UTC>WARNING-FdFrMrgr:1440432025.8 frames from SUSP_Fb start to be missing (isReady)
2025-08-28-16h00m16-UTC>WARNING-FdFrMrgr:1440432025.8 frames from SUSP_Fb start to be missing (out)
2025-08-28-16h00m16-UTC>INFO...-CfgReachState> Active(Active) Ok
The data loss around 23h27m37s-UTC is due to the crash of the FbmFFE server:
[Fri Aug 29 01:08:45 2025] FdIOServer.exe[32038]: segfault at 16ad ip 00007f44ac0e88de sp 00007fffc39d2120 error 4 in libframel.so.8.47.1[7f44ac0d6000+5b000] (Note: The timestamp could be inaccurate!)
The FbmFFEDy server, reading the FbmFFE shared memory, reports the following messages
2025-08-28-23h27m53-UTC>INFO...-CfgReachState> Active(Active) Ok
2025-08-28-23h30m18-UTC>INFO...-InputDir: first file to open after a scan:/dev/shm/VirgoOnline/FbmFFE/V1FFE-1440459035d-e.gwf
2025-08-28-23h30m18-UTC>WARNING-FdIOGetFrame: miss 165.2 seconds between 1440458870.4 and 1440459035.6
2025-08-28-23h30m18-UTC>INFO...-Input frames are back; gps=1440459035 latency=0.5
According the FmStol01 monitoring , there is a missing data during 170s from GPS1440458870 (2025-08-28-23h27m32-UTC) to GPS1440459040 (2025-08-28-23h30m32-UTC)
