Os -2 Unit has experienced an internal warning during startup and is restarting

Hardware
1
0 0x0100002c STARTUP Fired WARNING Unit has experienced an internal warning during startup and is restarting. 29356256850
1 0x0100002c STARTUP Cleared WARNING Unit has experienced an internal warning during startup and is restarting. Cleared by reinitialization. 29357565643
2 0x0100002c STARTUP Fired WARNING Unit has experienced an internal warning during startup and is restarting. 57040715128
3 0x0100002c STARTUP Cleared WARNING Unit has experienced an internal warning during startup and is restarting. Cleared by reinitialization. 57042005488
4 0x0100002c STARTUP Fired WARNING Unit has experienced an internal warning during startup and is restarting. 87130550808
5 0x0100002c STARTUP Cleared WARNING Unit has experienced an internal warning during startup and is restarting. Cleared by reinitialization. 87131914902
6 0x0100002c STARTUP Fired WARNING Unit has experienced an internal warning during startup and is restarting. 114340101523
7 0x0100002c STARTUP Cleared WARNING Unit has experienced an internal warning during startup and is restarting. Cleared by reinitialization. 114343253687
8 0x0100002c STARTUP Fired WARNING Unit has experienced an internal warning during startup and is restarting. 141765050091
9 0x0100002c STARTUP Cleared WARNING Unit has experienced an internal warning during startup and is restarting. Cleared by reinitialization. 141766432619
10 0x0100002c STARTUP Fired WARNING Unit has experienced an internal warning during startup and is restarting. 169247290616
11 0x0100002c STARTUP Cleared WARNING Unit has experienced an internal warning during startup and is restarting. Cleared by reinitialization. 16924859941
  • i am getting issue like this and i am able to ping the lidar ip and opening the web page but no scans are coming
    ouster-cli source 169.168.168.120 viz
    Contacting sensor 169.168.168.120…
    Will change udp_dest from ‘169.168.168.80’ to automatically detected ‘169.168.168.83’…
    Initializing connection to sensor 169.168.168.120 on lidar port 7504 with udp dest ‘169.168.168.83’…
    [2026-01-04 23:23:07.079] [ouster::sensor] [info] Opening port: 7503
    [2026-01-04 23:23:07.079] [ouster::sensor] [info] Opening port: 7504
    GL Renderer: NVIDIA Tegra Orin (nvgpu)/integrated
    GL Version: 3.3.0 NVIDIA 540.3.0 (GLSL: 3.30 NVIDIA via Cg compiler)
    Press ‘?’ while viz window is focused to print key bindings
    INFO:viz-logger:Starting processing thread…
    INFO:viz-logger:Starting rendering loop…
    Error: No valid scans received within 1.0s from sensor 169.168.168.120 using udp destination 169.168.168.83 on port 7504.
    INFO:viz-logger:Done rendering loop
    INFO:viz-logger:Joining processing thread
    jetson@ubuntu:~$
2

Hello Ganesh,

Could you please connect to the Ouster Tech Support portal here and create a case ? Please do not forget to provide us with your lidar’s diagnostic file.

The Ouster Tech Support team will do their best to support you quickly.

Thank you very much.

3

Hey Ganesh,

I think that I once had similar start up problems.
The OS2 would start spinning but restarts, therefore stops spinning and starts all over again.

I “solved” it by configuring it to 10Hz. Then it would boot correct and only after set it to 20Hz.
As it only appeard when starting directly into 20Hz mode.

Is it similar for you?

Best regards

Philipp

4

Hi Philipp,

What you describe sounds like unintended behavior but I’m glad you found a workaround. Thanks for sharing.

Would you be willing to share more about the environmental and use case conditions that caused this? Or a diagnostic file of the failed startup? You can submit this information directly at https://support.ouster.com/ if you’d prefer. We may use it to improve our products further.