Open HugoFolcher opened 1 year ago
In case, we wait gnss data for init, the software can't react to SIGNAL:
12:09:46 DEBUG Phasemeter: GNSS, ts 1679051385507904405 12:09:46 DEBUG Phasemeter: INT , ts 1679051386000000000 12:09:46 DEBUG Phasemeter: phase_error: -492095595ns 12:09:47 DEBUG UBX-TIM-SVIN: dur: 814, meanX 420386803, meanZ 16332503, meanZ 477796615, meanV 348072, obs 790, valid 0, active 1 12:09:47 DEBUG GNSS data: Fix 3D (5), Fix ok: True, satellites num 32, survey in error: 0.59, antenna status: 2, valid 1, time 1679051387, leapm_seconds 18, leap_notify 0, lsChange 0, timeToLsChange -40993787, lsSet: True, QErr(n) 0, qErr(n-1) 0 12:09:47 WARN Could not tai time from gnss, please check GNSS Configuration if this message keeps appearing more than 25 minutes
Probably in init state we can't kill the soft properly otherwise init can last forever whitout proper gnss conditions orwhitout mro lockness
Finally there is a timeout but maybe we could do better oscillatord@ocp0.service: State 'stop-sigterm' timed out. Killing.
oscillatord@ocp0.service: State 'stop-sigterm' timed out. Killing.
In case, we wait gnss data for init, the software can't react to SIGNAL:
Probably in init state we can't kill the soft properly otherwise init can last forever whitout proper gnss conditions orwhitout mro lockness
Finally there is a timeout but maybe we could do better
oscillatord@ocp0.service: State 'stop-sigterm' timed out. Killing.