8752 questions

10397 answers

16334 comments

15442 members

0 votes
69 views 25 comments
by

After my TRB141 device runs fine for a few days. I always seem to get this error:

/usr/lib/lua/5.1/luci/dispatcher.lua:330: /etc/config/luci seems to be corrupt, unable to find section 'main'
stack traceback:
	[C]: in function 'assert'
	/usr/lib/lua/5.1/luci/dispatcher.lua:330: in function 'dispatch'
	/usr/lib/lua/5.1/luci/dispatcher.lua:130: in function </usr/lib/lua/5.1/luci/dispatcher.lua:129>

And after rebooting it is fine again. What could be the issue?
It is freshly installed and updated.

1 Answer

0 votes
by
Hello,

Which firmware version are you using on your TRB141? Also, could you send me a troubleshoot file from your router once the issue appears?

Regards.
by
Thank you for the response.

Now it seems that I can't connect to web interface anymore.

SSH still works.

Is there any way I can reset the device from SSH with keeping my configuration?

This device is 100 km from my location and I can't get physical access to it.
by
Reboot does not solve the WebUI issue temporarily?
by
No, I can't connect to WebUI anymore. Just SSH
by

The service seems to be running.

2251 root      4324 S    /usr/sbin/uhttpd -f -h /www -r TRB141 -x /cgi-bin -u /ubus -t 600 -T 30 -k 20 -A 1 -n 3 -N 100 -p 0.0.0.0:80 -C /etc/uhttpd.crt -K /etc/uhttpd.key -s 0.0

by
Do you have a configuration backup of your device? If you do you could restore the device by uploading backup.
by

You could try to generate the backup from your current configuration by using the command:

sysupgrade -b /tmp/backup

And then use command to restore the configuration from backup:

sysupgrade -r /tmp/backup.tar.gz

by

Unfortunately no, but could I get a backup from SSH and then restore?

Thank you i see you already gave me a hint.

But now I have this issue:

-sh: sysupgrade: not found

by
Yes, follow my instructions above.
by

It doesn't have the sysupgrade ?

-sh: sysupgrade: not found

by

I sincerely apologize. For TRB devices it should be sysup.

by

It seems to have completely different options:

sysup - utility for system upgrading. Usage:

sysup [options] package

Options:

    -h | --help                print this page

    -o | --validate-only       validate the upgrade package and exit

    -k | --keep-settings-only  check if keep settings is possible and exit

    -V | --verbose             print debug messages

    -S | --syslog              write logs to syslog

by
Well, then there is no option just to reset the router. Anyway, you have not mentioned which firmware you are using at this moment? I will look into our collection of issues and check if there was anything similar to this.
by
I'm really not sure. Probably 06.xx. Is there any way to check from CLI ?
by
Is there any way to reset the device remotely and enable remote SSH WebUI access at the same time?
by
I could generate a backup from different device? And load it in this device?
by

Unfortunately, no.

One thing that comes up to mind is to download the latest firmware version from https://wiki.teltonika-networks.com/view/TRB141_Firmware_Downloads

And upload it to the router via SCP. Guide how to upload files using SCP: https://wiki.teltonika-networks.com/view/Upload_%26_Download_Files_from_RutOS

And use sysup command once again with the keep settings option.

Regards.

by
Also, you could generate backup and upload it to this router if the other device is identical to this one.
by

Yes I was just about to try upgrading:

Am I doing something wrong here?

root@TRB141:~# sysup -o TRB1_R_00.07.00_WEBUI.bin

[Severity ] Message

[Error    ] Failed to open the upgrade pacakge

[Crit     ] Failed to initialize the system upgrade context

by
Please check if file path is correct, also try other argument options such as -k
by

Yes path is correct.

root@TRB141:~# sysup -k /home/root/TRB1_R_00.07.00_WEBUI.bin

[Severity ] Message

[Error    ] Failed to open the upgrade pacakge

[Crit     ] Failed to initialize the system upgrade context

root@TRB141:~# ls -la

drwx------    1 root     root           464 Sep 29 10:47 .

drwxr-xr-x    1 root     root           224 Dec 19  2019 ..

-rw-------    1 root     root           647 Sep 29 10:55 .ash_history

-rw-r--r--    1 root     root      19272559 Sep 29 10:48 TRB1_R_00.07.00_WEBUI.bin

by
I have tested it on my own device and it worked well. Unfortunately, you will need to manually reset the device and configure/update it again. If the issue reproduces, I am afraid that you will need to return the device for repairs.
by
Allright.

Thank you for all the assistance !
by
Please inform me how it goes. I will keep researching this issue.
by

So miraculasly this device came online tonight.

Firmware version is TRB1410_R_00.01.06.1.

Looking at system logs it is FULL of this message:

Wed Sep 29 16:49:05 2021 kern.err kernel: [31579.696691] i2c-msm-v2 78b6000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:1) mode:FIFO slv_addr:0x18 MSTR_STS:0x0d1300c8 OPER:0x00000090

Wed Sep 29 16:49:06 2021 kern.err kernel: [31580.711444] i2c-msm-v2 78b6000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:1 tx:0) mode:FIFO slv_addr:0x18 MSTR_STS:0x0d1300c8 OPER:0x00000010

Wed Sep 29 16:49:06 2021 kern.err kernel: [31580.726658] i2c-msm-v2 78b6000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:1) mode:FIFO slv_addr:0x18 MSTR_STS:0x0d1300c8 OPER:0x00000090

Wed Sep 29 16:49:07 2021 kern.err kernel: [31581.741251] i2c-msm-v2 78b6000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:1 tx:0) mode:FIFO slv_addr:0x18 MSTR_STS:0x0d1300c8 OPER:0x00000010

Wed Sep 29 16:49:07 2021 kern.err kernel: [31581.756416] i2c-msm-v2 78b6000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:1) mode:FIFO slv_addr:0x18 MSTR_STS:0x0d1300c8 OPER:0x00000090

Wed Sep 29 16:49:08 2021 kern.err kernel: [31582.771442] i2c-msm-v2 78b6000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:1 tx:0) mode:FIFO slv_addr:0x18 MSTR_STS:0x0d1300c8 OPER:0x00000010

by
I would recommend to cleanly re-install firmware to your device without keeping settings as soon as you will be able to.