Question

Hi,

I have an RUT240 configured with a wget_reboot (ping_reboot is disabled).

For some reason, it disconnects every 30 minutes with a PING_REBOOT in the logs. 

Also, I can see a crontab setup with wget_reboot - is that something that is automatically setup or I can delete it ? 

Thanks. 

Comments

Hello, I made tests here and everything looks fine with mine. Please take a look to the information below.

- The "check_wget_reboot.sh" line is added automatically to the crontab file when the wget or ping reboot feature is enabled, so as such as you delete it, the feature won't work.

The contrab is like the "Timer for services" You can set up in the best way you need. This is a related link. https://wiki.teltonika-networks.com/view/Crontabs

- Did you see a ping reboot associated to crontab? I mean, Is appearing a line like this? 

cron.info crond[8470]: USER root pid 9708 cmd /sbin/ping_reboot 1 8.8.8.8 NULL 2 56 5 1 0 cfg01c21d

If it's, you can:

1. Erase the service line from the crontab /etc/crontabs/root and save

2. Restart luci with luci-reload or reboot the router and test again.

According with the information above, the crontab is a timer and its maybe calling a ping reboot for each 30 minutes. (But it shouldn't happen if ping reboot is disabled)

If this info won't enough to solve the issue please let us know and we can find other options.

---

All files sent. Thank you

Answer 1

Hello, I made tests here and everything looks fine with mine. Please take a look to the information below.

- The "check_wget_reboot.sh" line is added automatically to the crontab file when the wget or ping reboot feature is enabled, so as such as you delete it, the feature won't work.

The contrab is like the "Timer for services" You can set up in the best way you need. This is a related link. https://wiki.teltonika-networks.com/view/Crontabs

- Did you see a ping reboot associated to crontab? I mean, Is appearing a line like this? 

cron.info crond[8470]: USER root pid 9708 cmd /sbin/ping_reboot 1 8.8.8.8 NULL 2 56 5 1 0 cfg01c21d

If it's, you can:

1. Erase the service line from the crontab /etc/crontabs/root and save

2. Restart luci with luci-reload or reboot the router and test again.

According with the information above, the crontab is a timer and its maybe calling a ping reboot for each 30 minutes. (But it shouldn't happen if ping reboot is disabled)

If this info won't enough to solve the issue please let us know and we can find other options.

Comments

Thank you for the reply. 

I actually didn't have the ping_reboot in cron. 
I just noted that I'm seeing "request by ping reboot" messages in the logs. 

When issuing uci show ping_reboot I'm seeing that it is disabled (....enabled='0'). 
I have tried enabling it and it said it was already enabled. 

So now I have issued an enable='0' and looks like the command was accepted. Waiting now to see if the reboots are still happening. 
Will update. 

---

Hello, Ok, please let us know if the problem was solved.

Regards.

---

Hi, 

So it appears that it wasn't solved.. 

---

Hello,

Can you please download the troubleshoot file and send as a private message?

To get the file go to --> System --> Administration --> Troubleshoot --> Troubleshoot file

To send privately click on my username to go to my profile and click on send private message

I'll take a look for issues there.

Regards.

---

this is a remote router and I only have SSH access to it.

can you give me a path to that file?

---

Hello, For now the troubleshoot file is able to download just via http.

First option - (Enabling http access)

- Run this command    vi /etc/config/uhttpd and click i

- Edit the line " option enablehttp '0' " to " option enablehttp '1' "

- Press esc on your keyboard and write :wq + Enter

- Run luci-reload and you should have access to the webUI

- So go to --> System --> Administration --> Troubleshoot --> Troubleshoot file

Second option - (Getting some files from ssh)

- Please download the logread file (write logread, copy the text and paste into a .txt file)

- Download the following files withe these commands (Linux)

scp root@192.168.1.1:/log/log.db ~/Desktop

scp root@192.168.1.1:/etc/config/ping_reboot ~/Desktop

scp -r root@192.168.1.1:/etc/config/periodic_reboot ~/Desktop

scp -r root@192.168.1.1:/etc/config/wget_reboot ~/Desktop

Or get them via winscp https://wiki.teltonika-networks.com/view/How_to_upload_and_download_files_from_the_router_(Windows)%3F

If you can access to the webui and get the troubleshoot file is better because it brings some additional information to understand what's going on there.

Anything please let me know.

Regards.

Answer 2

Hello, according with the files you sent to me, your set up seems right.

As I said above, without the troubleshoot file we can't get all the information we need to help you, but try with this one. I'll test the both features for a few time and see if the issue appears here.

The first and important step is to upgrade your firmware to the last one. Most issues are being solved with firmware updates.

https://wiki.teltonika-networks.com/view/RUT240_Firmware_Downloads

If it doesn't solve, go to /etc/config/ping_reboot and erase all the lines, after that make a luci-reload.

The feature ping_reboot should be disable at all.

The last option is to enable the http access and send us the troubleshoot file to get all the information.

Please let me know if it helped.

Regards.

Comments

Hello Oscar, 

We have managed to recreate this problem on another local router, after upgrading it's firmware. 
I will have the troubleshoot file tomorrow and will send it for your review. 

FYI, we have managed to stop this problem from happening by disabling the wget_reboot and enabling the ping_reboot. 
Maybe this is a problem with wget and it just logs as a ping_reboot request ? .. 

---

Hello, we have managed to recreate the problem and RnD made a new firmware to solve the issue.

It'll be released in the new public firmware, but I'll send you via private message to solve your specific problem.

Regards.