FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
301 views 7 comments
by anonymous

[The bad grammar in the above title is the exact text from the error message]

Running firmware RUT9_R_00.07.02.7 (the latest?).  I have seen this at a couple random times.  Now I made it happen by clicking on the right-side bar of the STATUS -> REALTIME -> MOBILE SIGNAL page.

After clicking there, I lost the mobile connection and it did not ever reconnect.  I assume rebooting will restore it but I want to leave the unit in this state to diagnose the problem.  

Modem info:

# gsmctl -m

EC25-AF(D)

# gsmctl -k

EC25AFFDR07A09M4G_01.005.01.005

Here are the logread messages:

Wed Nov 9 20:44:34 2022 kern.notice kernel: widget configuration has been changed 

Wed Nov 9 20:45:31 2022 daemon.info unhandler[3425]: [operctl_force_connect_to_operator:658] error: Failed to connect to operator! ERROR: || 

Wed Nov 9 20:45:31 2022 daemon.info unhandler[3425]: gsm send: AT+COPS? 

Wed Nov 9 20:46:01 2022 daemon.info unhandler[3425]: gsm get some kind of error 

Wed Nov 9 20:46:01 2022 daemon.info unhandler[3425]: gsm send: AT+COPS=2 

Wed Nov 9 20:49:02 2022 daemon.info unhandler[3425]: gsm get some kind of error 

Wed Nov 9 20:49:02 2022 daemon.info unhandler[3425]: OPERCTL_ERROR_AT_EXEC_FAIL 

Wed Nov 9 20:49:02 2022 daemon.info unhandler[3425]: Job done. Failed to execute some AT commands. 

Wed Nov 9 20:49:22 2022 daemon.info gsmd[5011]: gsmd[dispatch_queue_work():900]: Modem 1-1.4 is not responding for over 500 seconds. Current request is cancelled. 

Wed Nov 9 20:49:38 2022 daemon.info unhandler[3425]: *Unsolicited id: 1-1.4 | msg: '+CREG: 0' 

Wed Nov 9 20:49:38 2022 daemon.info unhandler[3425]: *Unsolicited id: 1-1.4 | msg: '+CGREG: 0'

by anonymous

This post is similar so I wanted to add that,

a) There is no modem_updater package available on the package downloads page; and

b) I doubt this is a hardware failure because it has happened on three different RUT955 units running the same firmware (unless it is a systemic hardware defect).

1 Answer

0 votes
by anonymous

Hello,

Quite an unusual occurrence. Would be interesting to know if you can replicate it after reboot. 

Also, it might be a modem issue. 

Could you attach a troubleshoot file to your question to see compete logs, taken after the issue occurs? To generate the file, access router's WebUI, go to System -> Administration -> Troubleshoot section and download troubleshoot file from there.

Best regards,

by anonymous
I was waiting to see if anyone had suggestions of anything to do before I reboot the unit.  What do you think?
by anonymous

You could try rebooting the modem module, without having to reset the whole unit in Status -> Network -> Mobile

Could you specify the bar you clicked, which caused the disconnection?

by anonymous

I tried to post a picture of the UI widget that triggered the problem but I don't think that feature is working here.  So here is a verbal:

Near the top of the page on the right is a greater-than sign (">" white background, blue text).  Below the greater-than sign is a gear icon but I did not click on that.  

When you click on the greater-than sign, it slides out a panel with three icons: WiFi, RMS, and Mobile.  Right now, while the unit is still in the broken state, only the Mobile icon shows as blue and the other two are grayed out.  A spinner has been spinning for 10 minutes below the icons.  I believe it is spinning because it cannot access the Mobile modem because it is wedged.  (On other units a status widget displays instead of the spinner.) No messages have appeared in the logread log since I opened the widget.

Regarding the modem reset, it did not help.  Below are log messages from a time when it got interesting.  Until it logged that it cancelled the request, the web interface was 100% non-responsive.

Thu Nov 10 15:07:20 2022 daemon.info unhandler[3425]: modem_init[1-1.4][12]: reboot

Thu Nov 10 15:07:20 2022 daemon.info unhandler[3425]: modem_init[12]: modem reboot not needed.

Thu Nov 10 15:07:20 2022 daemon.info unhandler[3425]: modem_init[1-1.4][13]: AT+QCSQ=1

... (redacted due to maximum character count restriction)

Thu Nov 10 15:07:21 2022 daemon.info unhandler[3425]: Exiting modem init...

Thu Nov 10 15:07:21 2022 daemon.info unhandler[3425]: *Unsolicited id: 1-1.4 | msg: '+QIND: PB DONE'

Thu Nov 10 15:07:21 2022 daemon.info unhandler[3425]: Attempt to retrieve IMSI number...

Thu Nov 10 15:07:21 2022 daemon.info unhandler[3425]: IMSI: 310030001701104

Thu Nov 10 15:07:21 2022 daemon.info unhandler[3425]:

Thu Nov 10 15:07:21 2022 daemon.info unhandler[3425]: Checking module revision...

Thu Nov 10 15:07:22 2022 daemon.info unhandler[3425]: Module revision: EC25AFFDR07A09M4G

Thu Nov 10 15:07:22 2022 daemon.info unhandler[3425]: [oper_subsys_init:97] error: Don't get option "operlist" from config

Thu Nov 10 15:07:22 2022 daemon.info unhandler[3425]: active_sim:  |1|

Thu Nov 10 15:07:22 2022 daemon.info unhandler[3425]: pdp:         |1|

Thu Nov 10 15:07:22 2022 daemon.info unhandler[3425]: pdp_type:    |1|

Thu Nov 10 15:07:22 2022 daemon.info unhandler[3425]: auto_apn:    |1|

Thu Nov 10 15:07:22 2022 daemon.info unhandler[3425]: force_apn:   |0|

Thu Nov 10 15:07:22 2022 daemon.info unhandler[3425]: mcc:         |310|

Thu Nov 10 15:07:22 2022 daemon.info unhandler[3425]: mnc:         |030|

Thu Nov 10 15:07:22 2022 daemon.info unhandler[3425]: volte:       |0|

Thu Nov 10 15:07:22 2022 daemon.info unhandler[3425]: service_mode:|1|

Thu Nov 10 15:07:22 2022 daemon.info unhandler[3425]: Attempt to fetch APN list...

Thu Nov 10 15:07:22 2022 daemon.info unhandler[3425]: Getting APN list from database

Thu Nov 10 15:07:22 2022 daemon.info unhandler[3425]: APN Fetch is done.

Thu Nov 10 15:07:22 2022 daemon.info unhandler[3425]: gsm send: AT+CFUN?

Thu Nov 10 15:07:22 2022 daemon.info unhandler[3425]: gsm get: `+CFUN: 1`

Thu Nov 10 15:07:24 2022 daemon.info unhandler[3425]: gsm send: AT+COPS?

Thu Nov 10 15:07:24 2022 daemon.info unhandler[3425]: gsm get: `+COPS: 1`

Thu Nov 10 15:07:24 2022 daemon.info unhandler[3425]: Connecting to: 310410

Thu Nov 10 15:09:29 2022 kern.notice kernel: widget configuration has been changed

Thu Nov 10 15:09:36 2022 kern.notice kernel: widget configuration has been changed

Thu Nov 10 15:09:36 2022 kern.notice kernel: overview configuration has been changed

Thu Nov 10 15:09:37 2022 kern.notice kernel: overview configuration has been changed

Thu Nov 10 15:09:37 2022 kern.notice kernel: overview configuration has been changed

Thu Nov 10 15:09:37 2022 kern.notice kernel: overview configuration has been changed

Thu Nov 10 15:10:24 2022 daemon.info unhandler[3425]: [operctl_force_connect_to_operator:658] error: Failed to connect to operator! ERROR: ||

Thu Nov 10 15:10:24 2022 daemon.info unhandler[3425]: gsm send: AT+COPS?

Thu Nov 10 15:10:54 2022 daemon.info unhandler[3425]: gsm get some kind of error

Thu Nov 10 15:10:54 2022 daemon.info unhandler[3425]: gsm send: AT+COPS=2

Thu Nov 10 15:13:54 2022 daemon.info unhandler[3425]: gsm get some kind of error

Thu Nov 10 15:13:54 2022 daemon.info unhandler[3425]: OPERCTL_ERROR_AT_EXEC_FAIL

Thu Nov 10 15:13:54 2022 daemon.info unhandler[3425]: Job done. Failed to execute some AT commands.

Thu Nov 10 15:15:45 2022 daemon.info gsmd[5011]: gsmd[dispatch_queue_work():900]: Modem 1-1.4 is not responding for over 500 seconds. Current request is cancelled.

by anonymous

One of the log messages above says, "modem reboot not needed," as if the software overruled my request to reboot the modem.  Is there a way to use the gsmctl program on the command line to send an AT command to force the reboot, regardless?

by anonymous

Images need to be uploaded first, by pressing the image icon in comment formatting tools.

There is a command to shutdown the modem:

  • gsmctl -D

which, according to the description, after the command is executed, the modem will stay shut off up to a maximum of 60 s. and will then start up again.

Also, are you using manual operator selection in Network -> Mobile -> Network operators?

by anonymous

I rebooted the unit and the problem persisted: it stopped searching for mobile networks to connect to.

I then performed a factory reset and found the problem was gone: it connected to the mobile network automatically.  One strange thing: after the factory reset it was still running RUT9_R_00.07.02.7 but the page for restricting the operator was no longer in the mobile setup menu.  Maybe this difference is indicative of a bad configuration that led to the original problem?

I then opened that slide-out status panel and the unit immediately disconnected from the mobile network.  But, in this case, a modem reset re-established the mobile connection.  I posted a separate question, MOBILE DISCONNECTS WHEN YOU OPEN SLIDE-OUT STATUS PANEL, since this was easily reproducible but not the more serious problem identified in this post.