MT-6000 - daemon.debug

Hello

Since the last firmware update for the Flint 2 (version 4.8.3), I’ve noticed constant daemon.debug entries appearing in the system log:

Fri Oct 24 06:59:26 2025 daemon.debug sms_manager: (sms_manage.c:339) get sms bus fail, try again after 5s

Fri Oct 24 06:59:27 2025 daemon.debug glc: (common.c:194) Get the modem bus list is [1-2,2-1]

Fri Oct 24 06:59:27 2025 daemon.debug glc: (common.c:194) Get the modem bus list is [1-2,2-1]

Fri Oct 24 06:59:30 2025 daemon.debug glc: (common.c:194) Get the modem bus list is [1-2,2-1]

Fri Oct 24 06:59:30 2025 daemon.debug glc: (common.c:194) Get the modem bus list is [1-2,2-1]

Fri Oct 24 06:59:31 2025 daemon.debug sms_manager: (common.c:194) Get the modem bus list is [1-2,2-1]

Fri Oct 24 06:59:31 2025 daemon.debug sms_manager: (sms_manage.c:339) get sms bus fail, try again after 5s

Any guidence for this?

Thank you

The messages come from sms_manager and glc, which handle 4G/5G modem detection. They keep polling the USB bus even if no modem is connected, causing those “get sms bus fail” entries to appear constantly.

It’s harmless — doesn’t affect performance or stability.

1 Like

Hi

We’ve checked the MT6000 ou our end with firmware version 4.8.3 and did not observe such messages in the logs.

Could you please confirm whether you’re currently using an external cellular module, or if you had previously used one and retained configuration after upgrading the firmware?

The last time I used was back in April when my regular Internet was down.

Used my phone to connect to mobile Internet and then connect to my router using USB port.

USB tethering should not be related to the issue.

Perhaps try restoring the device to factory settings to see if that resolves the problem.
Repair network or reset - GL.iNet Router Docs 4

Thanks!

As soon as possible i will try the factory reset but for now, if i /etc/init.d/sms_manager stop the log stops.

1 Like