Latest RutOS installed (TRB1_R_00.07.07.1).
The TRB140 seems to go offline always after 2 days and 12 hours.
What could be the reason?
Nothing configured yet, except one client accesing the internet.
SIM is operational on carrier console.
Does not react on SMS messages at all.
Only way to recover the device is powercycle.
Plkease help.
Daniel
Hi,
If the device does not respond to SMS messages, it is most likely out of power. Is the device in a remote location, or can you access it locally? If you can access it locally, please check if the device’s LEDs are oON after 2 days and 12 hours, and if they are, which LEDs are ON exactly. Additionally, does the device always turn off after 2 days and 12 hours? Could you also provide logs from the past few days? You can access them in the device’s web UI under System → Maintenance → Event logs.
Best regards,
Hello Marijus,
Thanks for your reply.
The device was under power the whole time. When I visited the site, I found the LED changing from 2G to 3G to 4G and back to 2G, 3G, 4g, etc… The LED’s on the signal level were off.
After cycling the power (2024-06-10 08:12), the device came up again. Shortly afterwards the device was connected to RMS and another while later it turned to Online.
Looking at the received SMS messages, I did find all my status and reboot messages there, saved on the SIM card. The carrier subscription does not allow me to send SMS from the device itself, just receiving. The SMS setup is to reboot by device password and from any number. So, the device should have rebooted, even if it cannot send an SMS reply. Correct?
I did a manual check once again just now. SMS reboot worked this time.
Looking at the Event log, I found this here:
At 2024-06-10 08:12 I powercycled the device
At 2024-06-10 09:00:26, I changed the config to do a reboot after unsuccessful pings. I also added a daily reboot at 00:01
I did not touch the device afterwards.
What concerns me are the constant:
|198|2024-06-10 11:13:37|Health checker|IPv4 connectivity restored|
|197|2024-06-10 11:12:37|Health checker|IPv4 connectivity started to fail|
(I checked back with the carrier and they claim that connetivity to the SIM was stable.)
This also happened before the complete loss of connection around
|165|2024-06-09 01:04:36|Mobile Data|Mobile data disconnected (internal modem)|
This was in the middle of the night, no outside influence.
| 201 | 2024-06-10 13:22:52 | Health checker | IPv4 connectivity started to fail |
|---|---|---|---|
| 200 | 2024-06-10 13:21:50 | Health checker | IPv4 connectivity restored |
| 199 | 2024-06-10 13:20:50 | Health checker | IPv4 connectivity started to fail |
| 198 | 2024-06-10 11:13:37 | Health checker | IPv4 connectivity restored |
| 197 | 2024-06-10 11:12:37 | Health checker | IPv4 connectivity started to fail |
| 196 | 2024-06-10 09:12:34 | CONFIG | events_reporting configuration has been changed |
| 195 | 2024-06-10 09:08:25 | Health checker | IPv4 connectivity restored |
| 194 | 2024-06-10 09:07:25 | Health checker | IPv4 connectivity started to fail |
| 193 | 2024-06-10 09:00:53 | CONFIG | periodic_reboot configuration has been changed |
| 192 | 2024-06-10 09:00:26 | CONFIG | periodic_reboot configuration has been changed |
| 191 | 2024-06-10 09:00:18 | CONFIG | ping_reboot configuration has been changed |
| 190 | 2024-06-10 08:59:22 | Health checker | IPv4 connectivity restored |
| 189 | 2024-06-10 08:58:37 | Web UI | Password auth succeeded for admin on HTTP from 127.0.0.1 |
| 188 | 2024-06-10 08:58:22 | Health checker | IPv4 connectivity started to fail |
| 187 | 2024-06-10 08:39:18 | Health checker | IPv4 connectivity restored |
| 186 | 2024-06-10 08:38:18 | Health checker | IPv4 connectivity started to fail |
| — | — | — | — |
| 185 | 2024-06-10 08:27:15 | Health checker | IPv4 connectivity restored |
| 184 | 2024-06-10 08:25:10 | Health checker | IPv4 connectivity started to fail |
| 183 | 2024-06-10 08:23:11 | SSH | Password auth succeeded for root on SSH from 192.168.2.8:61987 |
| 182 | 2024-06-10 08:23:11 | IP Block | IP blocking entry (192.168.2.8 → 192.168.2.1:22) deleted. |
| 181 | 2024-06-10 08:22:57 | IP Block | Failed connection from IP 192.168.2.8 to 192.168.2.1, attempt 3/10 (SSH). |
| 180 | 2024-06-10 08:22:56 | IP Block | Failed connection from IP 192.168.2.8 to 192.168.2.1, attempt 2/10 (SSH). |
| 179 | 2024-06-10 08:22:48 | IP Block | Failed connection from IP 192.168.2.8 to 192.168.2.1, attempt 1/10 (SSH). |
| 178 | 2024-06-10 08:14:07 | Health checker | IPv4 connectivity restored |
| 177 | 2024-06-10 08:13:25 | Web UI | Password auth succeeded for admin on HTTP from 192.168.2.8 |
| 176 | 2024-06-10 08:13:07 | Health checker | DNS resolution restored |
| 175 | 2024-06-10 08:13:05 | Health checker | IPv4 connectivity started to fail |
| 174 | 2024-06-10 08:12:56 | Startup | Device startup after unexpected shutdown |
| 173 | 2024-06-10 08:12:06 | Network Operator | Connected to DR DR operator (internal modem) |
| 172 | 2024-06-10 08:12:06 | Network Type | Joined LTE network (internal modem) |
| 171 | 2024-06-10 08:12:06 | Mobile Data | Mobile data connected (internal modem) |
| [power cycled the system here] | |||
| 170 | 2024-06-09 02:12:53 | Switch Events | Port speed for port LAN1 changed to 1000 baseT |
| 169 | 2024-06-09 02:12:53 | Switch Events | Port link state of port LAN1 changed to UP |
| 168 | 2024-06-09 01:07:43 | Mobile Data | Mobile data disconnected (internal modem) |
| 167 | 2024-06-09 01:04:44 | Health checker | DNS resolution started to fail |
| 166 | 2024-06-09 01:04:39 | Health checker | IPv4 connectivity started to fail |
| 165 | 2024-06-09 01:04:36 | Mobile Data | Mobile data disconnected (internal modem) |
| 164 | 2024-06-08 20:34:16 | Health checker | IPv4 connectivity restored |
| 163 | 2024-06-08 20:33:16 | Health checker | IPv4 connectivity started to fail |
| 162 | 2024-06-08 20:29:11 | Health checker | IPv4 connectivity restored |
| 161 | 2024-06-08 20:27:09 | Health checker | IPv4 connectivity started to fail |
| 160 | 2024-06-08 20:25:07 | Health checker | IPv4 connectivity restored |
| 159 | 2024-06-08 20:23:05 | Health checker | IPv4 connectivity started to fail |
| 158 | 2024-06-08 20:18:02 | Health checker | IPv4 connectivity restored |
| 157 | 2024-06-08 20:17:02 | Health checker | IPv4 connectivity started to fail |
| 156 | 2024-06-08 20:15:00 | Health checker | IPv4 connectivity restored |
| 155 | 2024-06-08 20:13:59 | Health checker | IPv4 connectivity started to fail |
| 154 | 2024-06-08 20:10:57 | Health checker | IPv4 connectivity restored |
| 153 | 2024-06-08 20:09:57 | Health checker | IPv4 connectivity started to fail |
| 152 | 2024-06-08 20:05:54 | Health checker | IPv4 connectivity restored |
| 151 | 2024-06-08 20:04:54 | Health checker | IPv4 connectivity started to fail |
| 150 | 2024-06-08 08:22:53 | Health checker | IPv4 connectivity restored |
| 149 | 2024-06-08 08:21:53 | Health checker | IPv4 connectivity started to fail |
| 148 | 2024-06-08 05:52:39 | Health checker | IPv4 connectivity restored |
| 147 | 2024-06-08 05:50:37 | Health checker | IPv4 connectivity started to fail |
| 146 | 2024-06-07 23:13:01 | Health checker | IPv4 connectivity restored |
| 145 | 2024-06-07 23:12:01 | Health checker | IPv4 connectivity started to fail |
| 144 | 2024-06-07 22:21:54 | Health checker | IPv4 connectivity restored |
| 143 | 2024-06-07 22:20:54 | Health checker | IPv4 connectivity started to fail |
I do not have any written evidence about 2 days and 12 hours. In the previous cases, I simply reset the whole configuration because I assumed I made an error in the configuration.
Now I have changed the configuration by rebooting every night, including when ping fails.
Hello,
Thank you for providing all this information. It looks like we’ll need the troubleshoot file to look deeper into this issue. Since it contains private information, we’ll handle it on a separate platform. Instructions for accessing it have been sent to the email you registered for this forum.
Additionally, please ensure the troubleshoot file is taken from the device experiencing SMS sending issues before any reboots are performed.
Best regards,
Marijus
This topic was automatically closed after 15 days. New replies are no longer allowed.