WIKIABOUT

FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

Most popular tags

rut955 rut240 rut950 rutx11 rms vpn to openvpn wifi not sms trb140 firmware connection - ipsec on rutx12 rutx09 modbus
We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.

RUT240 shutting down after few hours/days

0 votes
142 views 0 comments
by anonymous
Out of a hundred or so units in the field, we have 2 RUT240's that are behaving in a strange way. We brought them back to the office, connected them to the wired ethernet and are observing what's going on. Both unit boot up normally and also connect to RMS, but after few hours/days, they seem to shut down or crash and require a power cycling to bring them back to action. The power indicator LED is on but no other lights are active.

One unit is RUT2_R_00.07.03.1, the other RUT2_R_00.07.03.2, factory settings. The same behavior was observed with earlier firmwares as well.

Other units seem to not suffer from this problem, but having a few in the fleet non-responsive after some time has dramatic impact on our edge devices uptime and maintenance.

How can we debug what's going on?

1 Answer

0 votes
by anonymous

Hello,

You can try several things:

  • Restore the device to factory defaults. Please check this page for more details: https://wiki.teltonika-networks.com/view/RUT240_Device_Recovery_Options.
  • Reset the device via bootloader menu. Detailed instructions are provided here: https://wiki.teltonika-networks.com/view/RUT2xx_Firmware_via_The_Bootloader_Menu.
  • Enable logging to flash memory, so that logs are saved after device reboot. In the WebUI, navigate to System -> Administration -> Troubleshoot page. Set Save log in option to Flash memory. Then, after a device reboot generate a troubleshoot file from the same page Troubleshoot section. The logs in the file might provide more insight into the issue. Attach the file by editing your question.
  • Access router via CLI/SSH and set /proc/sys/kernel/panic_on_oops value to 0. Login to the router via SSH and enter the following command:
    • printf 0 > /proc/sys/kernel/panic_on_oops

Best regards,