8298 questions

9759 answers

15542 comments

13863 members

0 votes
488 views 4 comments
by

Hi there,

We have a few RUT955s and they are all rebooting after being connected to the mobile network for 10 minutes exactly (not dependent on device on-time). This is the first time we've started using these devices. 

It is using Telstra (APN: telstra.internet), and Band 28 by default (Automatic). I've tried with 3G but there is no signal for it.

It's running the latest firmware (RUT9XX_R_00.06.05.3) and has only Zerotier, RMS and NTP activated on it (no user scripts). Other than that it is a stock config. 

Looking at the logs, there is no indication of what is causing it to reboot:

Thu Mar  5 08:34:45 2020 local1.info gsmd[2230]: gsmd send: 'AT+QCSQ' (8)
Thu Mar  5 08:34:45 2020 local1.info gsmd[2230]: gsmd get: '+QCSQ: "LTE",66,-94,144,-9' (26)
Thu Mar  5 08:34:45 2020 local1.info gsmd[2230]: gsmd send: 'AT+CREG?' (9)
Thu Mar  5 08:34:45 2020 local1.info gsmd[2230]: gsmd get: '+CREG: 2,1,"3020","81DF20D",7' (29)
Thu Mar  5 08:34:48 2020 local1.info gsmd[2230]: gsmd send: 'AT+QCSQ' (8)
Thu Mar  5 08:34:48 2020 local1.info gsmd[2230]: gsmd get: '+QCSQ: "LTE",59,-94,124,-9' (26)
Thu Mar  5 08:34:48 2020 local1.info gsmd[2230]: gsmd send: 'AT+CREG?' (9)
Thu Mar  5 08:34:48 2020 local1.info gsmd[2230]: gsmd get: '+CREG: 2,1,"3020","81DF20D",7' (29)
Thu Mar  5 08:34:50 2020 local1.info gsmd[2230]: gsmd send: 'AT+QCSQ' (8)
Thu Mar  5 08:34:50 2020 local1.info gsmd[2230]: gsmd get: '+QCSQ: "LTE",65,-94,144,-9' (26)
Thu Mar  5 08:34:50 2020 local1.info gsmd[2230]: gsmd send: 'AT+CREG?' (9)
Thu Mar  5 08:34:50 2020 local1.info gsmd[2230]: gsmd get: '+CREG: 2,1,"3020","81DF20D",7' (29) <-- now the device reboots
Mon Aug 26 06:20:19 2019 kern.warn kernel: [   17.500000] mmc_spi spi0.1: ASSUMING 3.2-3.4 V slot power
Mon Aug 26 06:20:22 2019 kern.info kernel: [   20.550000] mmc_spi spi0.1: SD/MMC host mmc0, no DMA, no WP, no poweroff
Mon Aug 26 06:20:22 2019 kern.warn kernel: [   20.550000] mmc_spi spi0.1: no support for card's volts
Mon Aug 26 06:20:22 2019 kern.err kernel: [   20.550000] mmc0: error -22 whilst initialising SDIO card
Mon Aug 26 06:20:22 2019 kern.warn kernel: [   20.550000] mmc_spi spi0.1: no support for card's volts
Mon Aug 26 06:20:22 2019 kern.err kernel: [   20.550000] mmc0: error -22 whilst initialising SD card
Mon Aug 26 06:20:22 2019 kern.warn kernel: [   20.550000] mmc_spi spi0.1: no support for card's volts
Mon Aug 26 06:20:22 2019 kern.err kernel: [   20.550000] mmc0: error -22 whilst initialising MMC card
Mon Aug 26 16:20:23 2019 kern.info kernel: [   21.300000] usb 1-1.4: new high-speed USB device number 4 using ehci-platform
Mon Aug 26 16:20:23 2019 kern.info kernel: [   21.420000] option 1-1.4:1.0: GSM modem (1-port) converter detected
Mon Aug 26 16:20:23 2019 kern.info kernel: [   21.420000] usb 1-1.4: GSM modem (1-port) converter now attached to ttyUSB0
Mon Aug 26 16:20:23 2019 kern.info kernel: [   21.430000] option 1-1.4:1.1: GSM modem (1-port) converter detected
Mon Aug 26 16:20:23 2019 kern.info kernel: [   21.440000] usb 1-1.4: GSM modem (1-port) converter now attached to ttyUSB1
Mon Aug 26 16:20:23 2019 kern.info kernel: [   21.450000] option 1-1.4:1.2: GSM modem (1-port) converter detected
Mon Aug 26 16:20:23 2019 kern.info kernel: [   21.450000] usb 1-1.4: GSM modem (1-port) converter now attached to ttyUSB2
Mon Aug 26 16:20:23 2019 kern.info kernel: [   21.460000] option 1-1.4:1.3: GSM modem (1-port) converter detected
Mon Aug 26 16:20:23 2019 kern.info kernel: [   21.470000] usb 1-1.4: GSM modem (1-port) converter now attached to ttyUSB3
Mon Aug 26 16:20:23 2019 kern.info kernel: [   21.490000] qmi_wwan 1-1.4:1.4: cdc-wdm0: USB WDM device
Mon Aug 26 16:20:23 2019 kern.info kernel: [   21.490000] qmi_wwan 1-1.4:1.4: Quectel EC21&EC25&EC20 R2.0 work on RawIP mode
Mon Aug 26 16:20:23 2019 kern.info kernel: [   21.500000] qmi_wwan 1-1.4:1.4 wwan0: register 'qmi_wwan' at usb-ehci-platform-1.4, WWAN/QMI device, a2:41:e1:f8:54:0f
Mon Aug 26 16:20:26 2019 user.emerg syslog: Warning: Failed to connect to ubus
Mon Aug 26 16:20:26 2019 user.emerg syslog: Warning: Unable to locate ipset utility, disabling ipset support
Mon Aug 26 16:20:26 2019 user.emerg syslog: Warning: Section @zone[0] (lan) cannot resolve device of network 'lan'
Mon Aug 26 16:20:26 2019 user.emerg syslog: Warning: Section @zone[1] (wan) cannot resolve device of network 'ppp'
Mon Aug 26 16:20:26 2019 user.emerg syslog: Warning: Section @zone[1] (wan) cannot resolve device of network 'wan'
Mon Aug 26 16:20:26 2019 user.emerg syslog: Warning: Section 'vpn_zone' cannot resolve device of network 'vpn'
Mon Aug 26 16:20:26 2019 user.emerg syslog: Warning: Section 'l2tp_zone' cannot resolve device of network 'l2tp'
Mon Aug 26 16:20:26 2019 user.emerg syslog: Warning: Section 'pptp_zone' cannot resolve device of network 'pptp'
Mon Aug 26 16:20:26 2019 user.emerg syslog: Warning: Section 'gre_zone' cannot resolve device of network 'gre'
Mon Aug 26 16:20:26 2019 user.emerg syslog: Warning: Section 'hotspot' cannot resolve device of network 'hotspot'
Mon Aug 26 16:20:26 2019 user.emerg syslog: Warning: Section 'sstp' cannot resolve device of network 'sstp'
Mon Aug 26 16:20:26 2019 user.emerg syslog: Warning: Section 'zero_zone' cannot resolve device of network 'zero'
Mon Aug 26 16:20:26 2019 user.emerg syslog: Warning: Option @rule[14]._name is unknown
Mon Aug 26 16:20:26 2019 user.emerg syslog: Warning: Option @rule[15]._name is unknown
Mon Aug 26 16:20:26 2019 user.emerg syslog: Warning: Option @rule[16]._name is unknown
Mon Aug 26 16:20:26 2019 user.emerg syslog: Warning: Option @rule[17]._name is unknown

The time goes back to normal later on once the NTP server reconnects.

 I can PM troubleshoot files.

by
I'll just add to say that this does not happen when connected to the internet using the WAN port.

1 Answer

0 votes
by
Hello,

please generate the troubleshoot file and send to me via private message.
Best answer
by
I've sent it to your PMs.

One extra note, I've taken the backup file and put the config onto a device in the office that is powered using the supplied wall plug, connected to band 28 also. The one in the office is not having any issues.

The only other difference (other than location) between the two sites is the power supply. The one on site is connected to a 12V supply. I also tried a 12V supply in the office and that is working fine.
by
Hello,

Perhaps you could connect at least one product with this issue to your office and see if the issue recurs?
by
I think we've figured out the problem (unrelated to the RUT955).

None of the devices in the office exhibited the same behaviour, and we've attributed it to a misconfigured IP watchdog device that was restarting the power supply every 10 minutes.

Thanks!