My GL-X3000 keeps turing off after about 5 minutes

Great! I am also using the exact same set of service/features as you.

Then lets first establish your connection using the Manual Setup button. You may need to re-enable the Tracking on the Cellular interface in order to make the connection succeeds. After a successful connection, disable it immediately.

Once the connection is successfully established, log into the modem and execute the following commands (copy and paste):

service avahi-daemon stop && service avahi-daemon disable
service carrier-monitor stop && service carrier-monitor disable
service cron stop && service cron disable
service ddns stop && service ddns disable
service gl-cloud stop && service gl-cloud disable
service gl-tertf stop && service gl-tertf disable
service gl-update-logo stop && service gl-update-logo disable
service gl_clients stop && service gl_clients disable
service gl_ipv6 stop && service gl_ipv6 disable
service gl_nas_diskmanager stop && service gl_nas_diskmanager disable
service gl_nas_sys stop && service gl_nas_sys disable
service gl_nas_sys_dl stop && service gl_nas_sys_dl disable
service gl_nas_sys_up stop && service gl_nas_sys_up disable
service gl_tethering stop && service gl_tethering disable
service gl_timer stop && service gl_timer disable
service minidlna stop && service minidlna disable
service modem_signal stop && service modem_signal disable
service nfsd stop && service nfsd disable
service parental_control stop && service parental_control disable
service repeater stop && service repeater disable
service rpcbind stop && service rpcbind disable
service rtty stop && service rtty disable
service samba4 stop && service samba4 disable
service sms_manager stop && service sms_manager disable
service smstools3 stop && service smstools3 disable
service tailscale stop && service tailscale disable
service tor stop && service tor disable
service vsftpd stop && service vsftpd disable
service webdav_ser stop && service webdav_ser disable
service zerotier stop && service zerotier disable
/etc/init.d/gl-tertf disable

Note! Please review the services’ names, if you spot any service that you use (e.g. Samba) you can skip disabling it!

Once you execute the above commands, share the result of the following commands:

service | grep running
service | grep disabled
ps | grep -v '\['

I did the above and the modem NOT only stopped disconnects, but became so blazing fast! The CPU and RAM have become less used.

1 Like

See my result after doing the steps I shared above:

… and the modem did not disconnect for a few days!

Awesome that sounds promising :slight_smile:

A few of the commands were not found but most of the services have been disabled:

running services:

disabled:

ps:

Speed test :joy:
image

As you can see from your ps output, although you disabled the Tracking service, its process was still running - this is a bug!

Please kill the following processes as well:

modem_manager.lua
mwan3rtmon
mwan3track

… and speed test again at: https://openspeedtest.com/

Please execute also:
netstat -tuplna

Now the connection will be very stable unless your ISP disconnects you or the electricity gets interrupted :slight_smile:

Ah very nicely spotted! Initially I only killed whatever process was called trace. Thanks!

ps:

speedtest:

netstat:

Looks :+1:. Keep monitoring your connection uptime.

Please note that umount service has to be enabled to avoid filesystem issues:

service umount enable && service umount start

I was mid zoom session with a client and it stopped working again :(. This time the device had all the lights still on but wasn’t responsive. Had to unplug it and plug it back in - the interesting thing; when I was able to get back on the admin UI I saw it set itself to ‘SIM 2’ which is not in use. After a bit it did switch itself back automatically to ‘SIM 1’.

I’ll go through the services again and make sure to follow your steps above and enable umount. Not sure why that was in a disable state.

Thanks for all your help btw, been incredibly helpful!

Check out the logs. Make sure to use Manual Setup for the connection.

Reboot the modem and execute all the above steps.

Please note that mine has the same exact configs and working without issues. I am using the latest firmware for your information.

This happens after you disable a bunch of related services. So you need to restart it as the last command.

Crash Logs:

<2>[  940.020543] Kernel BUG at do_undefinstr+0x2e8/0x2f8 [verbose debug info unavailable]
<2>[  940.025142] Kernel BUG at do_undefinstr+0x2e8/0x2f8 [verbose debug info unavailable]
<0>[  940.029742] Internal error: Oops - BUG: 0 [#1] SMP

System Log: spotting a lot of these now

Thu Feb 15 16:28:16 2024 daemon.notice netifd: modem_0001 (11389): [02-15_16:26:15:919] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
Thu Feb 15 16:28:16 2024 daemon.notice netifd: modem_0001 (11389): [02-15_16:26:15:920] call_end_reason is 1
Thu Feb 15 16:28:16 2024 daemon.notice netifd: modem_0001 (11389): [02-15_16:26:15:920] call_end_reason_type is 2
Thu Feb 15 16:28:16 2024 daemon.notice netifd: modem_0001 (11389): [02-15_16:26:15:920] call_end_reason_verbose is 210
Thu Feb 15 16:28:16 2024 daemon.notice netifd: modem_0001 (11389): [02-15_16:26:15:920] try to requestSetupDataCall 60 second later
Thu Feb 15 16:28:16 2024 daemon.notice netifd: modem_0001 (11389): [02-15_16:27:15:968] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
Thu Feb 15 16:28:16 2024 daemon.notice netifd: modem_0001 (11389): [02-15_16:27:15:968] call_end_reason is 1
Thu Feb 15 16:28:16 2024 daemon.notice netifd: modem_0001 (11389): [02-15_16:27:15:968] call_end_reason_type is 2
Thu Feb 15 16:28:16 2024 daemon.notice netifd: modem_0001 (11389): [02-15_16:27:15:968] call_end_reason_verbose is 210
Thu Feb 15 16:28:16 2024 daemon.notice netifd: modem_0001 (11389): [02-15_16:27:15:968] try to requestSetupDataCall 60 second later

PS: The list of services you previously recommended to disable also includes service umount stop && service umount disable that’s why it was disabled :stuck_out_tongue:

Interestingly umount wont actually start.

I’ll reset the entire box later today :man_shrugging:

Yes, that’s normal :slight_smile: - the same output I have. It starts as a process - not a service - and then closes again after remounting the filesystem.



# service | grep umount
/etc/init.d/umount            	  disabled	   stopped

My fault! It should not be!

As for the logs, I did not have either of the crash or system errors you shared. I think it’s better to flash the modem again with latest firmware and then follow what we did today.

Yeah that will be my only hope at this stage. Will need to find time to, as I do get my 45-120 minutes before a crash and can work a bit :joy: - thanks a lot for your help

1 Like

@zxp did you get this resolved? I’ve been struggling with the exact same issue with crashes occurring about every 2 hours. I have yet to find a working solution