Issue with cron errors on GL6500

This GL6500 is connected to the internet via ethernet only, there are no other connections. But looking in the logs, I’m seeing an endless stream of the following errors

Sat Apr 18 09:40:00 2026 cron.err crond[9153]: USER root pid 9770 cmd /usr/bin/modem_sim_status_check.sh
Sat Apr 18 09:40:00 2026 cron.err crond[9153]: USER root pid 9771 cmd sleep 10; /usr/bin/modem_sim_status_check.sh
Sat Apr 18 09:40:00 2026 cron.err crond[9153]: USER root pid 9772 cmd sleep 20; /usr/bin/modem_sim_status_check.sh
Sat Apr 18 09:40:00 2026 cron.err crond[9153]: USER root pid 9774 cmd sleep 30; /usr/bin/modem_sim_status_check.sh
Sat Apr 18 09:40:00 2026 cron.err crond[9153]: USER root pid 9777 cmd sleep 40; /usr/bin/modem_sim_status_check.sh
Sat Apr 18 09:40:00 2026 cron.err crond[9153]: USER root pid 9778 cmd sleep 50; /usr/bin/modem_sim_status_check.sh

When looking in both the Admin panel/system log, the LUCI scheduled tasks and via ssh, doing a “crontab -e”, there is nothing with regard to this “modem_sim_status_check.sh” being run via cron. I mean the root crontab is EMPTY. I am very familiar with cron scheduling on other Linux distros, but OpenWRT’s implementation is apparently different/confusing. What am I missing?

Ok… I see this version of OpenWrt goes its own way with cron.. Pray tell how does one edit this crontab? cat’ing the “root” file in the /tmp/gl_crontabs/root shows these unneeded scripts running continually. Doing the standard “crontab -e” as root gives me an empty file… I’m rapidly wishing I’d stayed with my Asus router and Freshtomato firmware, despite needing the 2.5Gb ethernet ports which sold me on this router. When checking the OpenWrt KB, it indicates that (stock) OpenWrt adheres to the standard crontab.. Is there some unseen reason WHY this version of OpenWRT goes its own way on many things?

Hi,

Some features (SDK) in the GL firmware are owe-developed by us, schedule tasks about GL features are managed centrally in /etc/gl_crontabs/crontabs.d/.

Probably the router used a Cellular Modem or Tethering connection before, and the firmware will execute this schedule.

Since the GL firmware provides SSH access, if you are sure will not use any connection related to the Cellular Modem, you can disable this task.

This is a brand new unit, taken out of the shrink wrap, so I would be wondering how it could have ever been used for cellular modem tethering. What is the command to edit this oddball crontab, since the standard /usr/bin/crontab doesn’t work for this.. Also, before posting this question, I searched your knowledgebase to see if this info was there.. Couldn’t find it anywhere. If you people want to change the standard ways to do things on your version of OpenWrt, PLEASE put info in your kb to explain what you’ve done, for those of us who are familar with STANDARD Linux. Just my .00000000000001BTC.

This is a bit strange — a new device that hasn't used tethering so shouldn't execute this.
:astonished_face:

Please try resetting the router and check again.

Yes, that's an excellent suggestion!
The KB was just created and we'll gradually improve it, thanks for the suggestions!