WIKIABOUT

FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

Most popular tags

rut955 rut240 rut950 rutx11 rms vpn to openvpn wifi not sms trb140 firmware connection - ipsec on rutx12 rutx09 modbus
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.

Getting this "luci seems to be corrupt" error often.

0 votes
677 views 25 comments
by anonymous

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 anonymous
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.
Show 20 previous comments
by anonymous
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 anonymous
Allright.

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

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 anonymous
I would recommend to cleanly re-install firmware to your device without keeping settings as soon as you will be able to.