At 2026-05-14-02h34m43-UTC, no more data from Sa_WI received*
- SUSP_Fb server log report
-
2026-05-14-02h34m43-UTC>WARNING-[TolmFrameBuilder::ControlMerging] frame: 1462761300.800000000: merging is triggered on timeout (internal 1462761301.161215040 > max 1462761301.160000000)
2026-05-14-02h34m43-UTC>WARNING-[TfbSubFrame::Fill] GPS: 1462761300.800000000 - Source Sa_WI: 1104/2000 missing packet(s), 0 data break(s) (missing data are at the end of the vector)
2026-05-14-02h34m44-UTC>INFO...-[TfbSourceManager::Clean] source Sa_WI (62:v07) has stopped -> waiting for data...
2026-05-14-02h34m44-UTC>INFO...-[TfbSourceManager::Reporting] Sources reporting: / nSrc: 57, missing(1): Sa_WI
2026-05-14-02h34m44-UTC>INFO...-CfgReachState> Active(Active) Ok
-
After this event the FbmAlp server complained about frames delivered too late from all the SUS Automation nodes
- FbmAlp server log report
-
2026-05-14-02h35m02-UTC>WARNING-FdFrMrgr: Could not wait longer for frame parts, output 1462761308.0, nSources=31 first:FbsAlp
2026-05-14-02h35m02-UTC>WARNING-FdFrMrgr:1462761308.0 frames from SUS_BS start to be missing (isReady)
2026-05-14-02h35m02-UTC>WARNING-FdFrMrgr:1462761308.0 frames from SUS_NI start to be missing (isReady)
2026-05-14-02h35m02-UTC>WARNING-FdFrMrgr:1462761308.0 frames from SUS_NE start to be missing (isReady)
2026-05-14-02h35m02-UTC>WARNING-FdFrMrgr:1462761308.0 frames from SUS_PR start to be missing (isReady)
2026-05-14-02h35m02-UTC>WARNING-FdFrMrgr:1462761308.0 frames from SUS_WI start to be missing (isReady)
2026-05-14-02h35m02-UTC>WARNING-FdFrMrgr:1462761308.0 frames from SUS_WE start to be missing (isReady)
2026-05-14-02h35m02-UTC>WARNING-FdFrMrgr:1462761308.0 frames from SUS_BS start to be missing (out)
2026-05-14-02h35m02-UTC>WARNING-FdFrMrgr:1462761308.0 frames from SUS_NI start to be missing (out)
2026-05-14-02h35m02-UTC>WARNING-FdFrMrgr:1462761308.0 frames from SUS_NE start to be missing (out)
2026-05-14-02h35m02-UTC>WARNING-FdFrMrgr:1462761308.0 frames from SUS_PR start to be missing (out)
2026-05-14-02h35m02-UTC>WARNING-FdFrMrgr:1462761308.0 frames from SUS_WI start to be missing (out)
2026-05-14-02h35m02-UTC>WARNING-FdFrMrgr:1462761308.0 frames from SUS_WE start to be missing (out)
2026-05-14-02h35m03-UTC>INFO...-FdFrMrgrFeed: 1462761308.0 receiving again frames from SUS_NI
2026-05-14-02h35m03-UTC>WARNING-FdFrMrgrFeed: reject too old frame (1462761308.0) from SUS_NI; last produced was 1462761317.0
2026-05-14-02h35m03-UTC>INFO...-FdFrMrgrFeed: 1462761308.0 receiving again frames from SUS_WE
2026-05-14-02h35m03-UTC>WARNING-FdFrMrgrFeed: reject too old frame (1462761308.0) from SUS_WE; last produced was 1462761317.0
2026-05-14-02h35m03-UTC>INFO...-FdFrMrgrFeed: 1462761308.0 receiving again frames from SUS_BS
-
After some investigations, restarting the SatServer allows to recover the correct running conditions for the the FbmAlp server, and the SUS Automation nodes
-
2026-05-14-06h32m16-UTC process:SatServer stopped
2026-05-14-06h32m20-UTC process:SatServer started
The Sa_WI data are still missing
