Stability of gateway

Wireless Connectivity Ultra-Wideband
1

Hi All,

Looking for clarification and some understanding of the working of the gateway when using MQTT.

Few observation,

  • Sometimes the gateway becomes unresponsive i.e it doesn’t transmit the data to the server. If I restart it, the data starts coming. Attaching some logs for the same.
Sun  6 Dec 13:19:23 IST 2020
Starting daemon mosquitto with command '/usr/local/sbin/mosquitto' and options '-c /etc/mosquitto/mosquitto.conf'...

1607240964: mosquitto version 1.5.1 starting
1607240964: Config loaded from /etc/mosquitto/mosquitto.conf.
1607240964: Opening ipv4 listen socket on port 1884.
1607240964: Opening ipv6 listen socket on port 1884.
1607240964: Opening websockets listen socket on port 15675.
1607240964: Opening ipv4 listen socket on port 1883.
1607240964: Opening ipv6 listen socket on port 1883.
1607365459: New client connected from xx.xx.xx.xx as leapsWebClient576942814 (c1, k60, u'').
1607365468: Socket error on client leapsWebClient576942814, disconnecting.

Mon  7 Dec 23:55:35 IST 2020
Stopping daemon mosquitto...

1607365535: mosquitto version 1.5.1 terminating

Mon  7 Dec 23:56:09 IST 2020
Starting daemon mosquitto with command '/usr/local/sbin/mosquitto' and options '-c /etc/mosquitto/mosquitto.conf'...

1607365569: mosquitto version 1.5.1 starting
1607365569: Config loaded from /etc/mosquitto/mosquitto.conf.
1607365569: Opening ipv4 listen socket on port 1884.
1607365569: Opening ipv6 listen socket on port 1884.
1607365569: Opening websockets listen socket on port 15675.
1607365569: Opening ipv4 listen socket on port 1883.
1607365569: Opening ipv6 listen socket on port 1883.

Tue  8 Dec 00:42:37 IST 2020
Stopping daemon mosquitto...`

What happened in the above-mentioned case is that gateway stopped transmitting data at around 13:20 on the 6th and then when I restarted the gateway at 23:56 on the 7th, it started transmitting data.

  • Sometimes the tags become unresponsive, they stop transmitting iot-data or the location and the only way to get it working is to reset it somehow, since manual reset is not an option, I use other means to reset it, question is, why and how it becomes unresponsive.

  • Most of the time, when the tag is not in the range of transmitters, the MQTT servers keep receiving the last known location in the location topic for that tag. Sometimes it keeps happening for days.

Any insight into this highly helpful.

Thanks.

1 Like
2

I have monitored the situation closely and I have seen that, whenever gateway stops reading data from the tags, the following error gets logged in daemon.log.

2020-12-25 01:37:06.347 ERROR [494] [leaps::io::dev::on_input_error@353] error reading /dev/dwm0, 0 bytes read, 0 bytes parsed
2020-12-25 01:40:01.750 ERROR [494] [leaps::io::dev::on_input_error@353] error reading /dev/dwm0, 0 bytes read, 0 bytes parsed
2020-12-25 01:40:25.351 ERROR [494] [leaps::io::dev::on_input_error@353] error reading /dev/dwm0, 0 bytes read, 0 bytes parsed
2020-12-25 01:41:55.753 ERROR [494] [leaps::io::dev::on_input_error@353] error reading /dev/dwm0, 0 bytes read, 0 bytes parsed
2020-12-25 01:43:15.354 ERROR [494] [leaps::io::dev::on_input_error@353] error reading /dev/dwm0, 0 bytes read, 0 bytes parsed

Can anyone help me understand this and how I can get rid of this?