TRB245 modbusgwd crashing

I’m running multiple types of teltonikas.

This is the first time I’ve encountered problems with the tcp to rs485 gateway.

This is the log output of a faulty device:

Sun Jan 21 20:48:32 2024 kern.notice kernel: rs_modbus configuration has been changed
Sun Jan 21 20:48:32 2024 kern.notice kernel: firewall configuration has been changed
Sun Jan 21 20:48:33 2024 local1.info modbusgwd[11970]: modbusgwd started.
Sun Jan 21 20:48:33 2024 local1.info modbusgwd[11970]: serial port ‘/dev/rs485’ open, baudrate ‘19200 8N1’.
Sun Jan 21 20:48:33 2024 kern.info kernel: [ 2675.085188] do_page_fault(): sending SIGSEGV to modbusgwd for invalid write access to 00000000
Sun Jan 21 20:48:33 2024 kern.info kernel: [ 2675.094206] epc = 00403a5c in modbusgwd[400000+9000]
Sun Jan 21 20:48:33 2024 kern.info kernel: [ 2675.099392] ra = 00403a20 in modbusgwd[400000+9000]
Sun Jan 21 20:48:39 2024 local1.info modbusgwd[12038]: modbusgwd started.
Sun Jan 21 20:48:39 2024 local1.info modbusgwd[12038]: serial port ‘/dev/rs485’ open, baudrate ‘19200 8N1’.
Sun Jan 21 20:48:39 2024 kern.info kernel: [ 2681.192386] do_page_fault(): sending SIGSEGV to modbusgwd for invalid write access to 00000000
Sun Jan 21 20:48:39 2024 kern.info kernel: [ 2681.201395] epc = 00403a5c in modbusgwd[400000+9000]
Sun Jan 21 20:48:39 2024 kern.info kernel: [ 2681.206609] ra = 00403a20 in modbusgwd[400000+9000]

Which the loops forever…

I have multiple identical setups, a working one has this logged:

Sun Jan 21 20:49:29 2024 kern.notice kernel: rs_modbus configuration has been changed
Sun Jan 21 20:49:30 2024 kern.notice kernel: firewall configuration has been changed
Sun Jan 21 20:49:31 2024 local1.info modbusgwd[8491]: modbusgwd started.
Sun Jan 21 20:49:31 2024 local1.info modbusgwd[8491]: serial port ‘/dev/rs485’ open, baudrate ‘19200 8N1’.
Sun Jan 21 20:49:31 2024 local1.info modbusgwd[8491]: start listening on ‘10.9.7.12:502’.

1 Like

Hi,

In this line :

kern.info kernel: [ 2675.085188] do_page_fault(): sending SIGSEGV to modbusgwd for invalid write access to 00000000

It indicates that a process tried to write to the memory address ‘00000000,’ causing a memory access violation. It’s important to note that Modbus address 0 is reserved for broadcast communication.

Please review your device’s settings for Modbus gateway and if they differ from working ones because this is likely the cause of the issue.

Best regards,

Marijus

This is is logged without even trying to write to any address. It’s just starting the modbus tcp to serial service from the gui.

As you also can see from the logs, the non-working unit fails to even open the port at the ip address to even allow something to start writing.

A segmentation fault is about the gateway program it self an has nothing to do with the modbus address.
This is a bug in the firmware.

I realise that this is the community support forum, and therefore do not expect to be able to submit at bug-report here.
Where can I file a bug report? Teltonika does not seem to have a bug-tracker of any kind.

1 Like

Hi @duzk ,

Could you please share details about the firmware used in TRB245 devices that are working and the ones encountering errors? This information would be very helpful in investigating the issue.

Regards,

Marijus

Hi @nuxvomica ,

We shouldn’t hastily label an issue as a bug, especially when some devices are functioning correctly while others are not. As mentioned earlier, it might be a specific firmware issue. We need to conduct a thorough investigation before concluding whether it is a bug and deciding to forward it to R&D.

Regards,

Marijus

Hi @Marijus ,

you will find my details for this problem under:

best regards

I have tried both latest TRB2_R_00.07.06.3 and version TRB2_R_00.07.06.1 and they both are affected on the device. I have other TRB245 running both of these and they do work.

We are experiencing the same error messages since our RUT956 upgrade from
RUT9M_R_00.07.05.4 to RUT9M_R_00.07.06.3

Fri Feb  2 12:38:17 2024 local1.info modbusgwd[25103]: modbusgwd started.
Fri Feb  2 12:38:17 2024 local1.info modbusgwd[25103]: serial port '/dev/rs485' open, baudrate '9600 8N1'.
Fri Feb  2 12:38:17 2024 kern.info kernel: [65305.118392] do_page_fault(): sending SIGSEGV to modbusgwd for invalid write access to 00000000
Fri Feb  2 12:38:17 2024 kern.info kernel: [65305.127224] epc = 0040412c in modbusgwd[400000+9000]
Fri Feb  2 12:38:17 2024 kern.info kernel: [65305.132871] ra  = 004040f0 in modbusgwd[400000+9000]

Before the update the communication had been working with the same configuration for the last year.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.