SCADAComm stop attempt to reconnect when communication failed

[jkb]

Hello,
I have been testing the latest version of rapidscada with KPMQTT. I found out that scadacomm (KPLogics) stop reconnecting after several retries. The only way to recover is to restart the service. Is that correct behavior?

Best regards,
jkb.

[Mikhail]

Hi,

Please provide logs where we can see it.

[jkb]

Hi Mikhail,
After looking at the code further. It is KpMQTT implementation that does not reconnect and resubscribe to MQTT Broker once the communication failed.

here is the log by the way.

2018-12-12 17:00:20 Communication session with the Device 42 “MQTT Driver”, type: KpMQTT
2018-12-12 17:00:20 Error communicating with the device: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine.

2018-12-12 17:00:20 Communication session with the Device 42 “MQTT Driver”, type: KpMQTT
2018-12-12 17:00:20 Error communicating with the device: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine.

2018-12-12 17:00:21 Communication session with the Device 42 “MQTT Driver”, type: KpMQTT
2018-12-12 17:00:21 Error communicating with the device: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine.

2018-12-12 17:00:21 Communication session with the Device 42 “MQTT Driver”, type: KpMQTT
2018-12-12 17:00:21 Error communicating with the device: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine.

2018-12-12 17:00:21 Communication session with the Device 42 “MQTT Driver”, type: KpMQTT
2018-12-12 17:00:21 Error communicating with the device: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine.

2018-12-12 17:00:21 Communication session with the Device 42 “MQTT Driver”, type: KpMQTT
2018-12-12 17:00:21 Error communicating with the device: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine.

2018-12-12 17:00:21 Communication session with the Device 42 “MQTT Driver”, type: KpMQTT
2018-12-12 17:00:21 Error communicating with the device: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine.

2018-12-12 17:00:22 Communication session with the Device 42 “MQTT Driver”, type: KpMQTT
2018-12-12 17:00:22 Error communicating with the device: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine.

2018-12-12 17:00:22 Communication session with the Device 42 “MQTT Driver”, type: KpMQTT
2018-12-12 17:00:22 Error communicating with the device: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine.

2018-12-12 17:00:23 Communication session with the Device 42 “MQTT Driver”, type: KpMQTT
2018-12-12 17:00:23 Error communicating with the device: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine.

2018-12-12 17:00:23 Communication session with the Device 42 “MQTT Driver”, type: KpMQTT
2018-12-12 17:00:23 Error communicating with the device: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine.

2018-12-12 17:00:24 Communication session with the Device 42 “MQTT Driver”, type: KpMQTT
2018-12-12 17:00:24 Error communicating with the device: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine.

2018-12-12 17:00:24 Communication session with the Device 42 “MQTT Driver”, type: KpMQTT
2018-12-12 17:00:24 Error communicating with the device: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine.

2018-12-12 17:00:24 Communication session with the Device 42 “MQTT Driver”, type: KpMQTT
2018-12-12 17:00:24 Error communicating with the device: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine.

2018-12-12 17:00:24 Communication session with the Device 42 “MQTT Driver”, type: KpMQTT
2018-12-12 17:00:24 Error communicating with the device: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine.

2018-12-12 17:00:24 Communication session with the Device 42 “MQTT Driver”, type: KpMQTT
2018-12-12 17:00:24 Error communicating with the device: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine.

2018-12-12 17:00:25 Communication session with the Device 42 “MQTT Driver”, type: KpMQTT
2018-12-12 17:00:25 Error communicating with the device: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine.

2018-12-12 17:00:25 Communication session with the Device 42 “MQTT Driver”, type: KpMQTT
2018-12-12 17:00:25 Error communicating with the device: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine.

Thanks.

[Mikhail]

An established connection was aborted by the software in your host machine.

May be an MQTT bus initiates disconnect. I’m not sure, because the author of the driver is bersim. You can try asking him or debug the driver by yourself. Also you can involve me in debugging on commercial base.

[jkb]

posted to him in the github. no reply so far. I did some small changes to the code to have it reconnect. It works like a charm.

[Mikhail]

If you send me an email to info@ , I will forward your message to bersim.

[jkb]

sorry for late reply. just emailed to info@

[Mikhail]

OK, I added the author to email thread. Hope he will answer.

[Author]

Posts