You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issues of this repository and believe that this is not a duplicate.
What happened?
Upon MQTT broker restart, the Gateway Bridge does sometime not reconnect, event when disconnection is detected. However, it still tries to publish event and acts as everything was fine.
What did you expect?
The Gateway Bridge tries indefinitely to reconnect when it's not connected.
Steps to reproduce this issue
Steps:
Run a MQTT server
Run the gateway bridge
Restart the MQTT server
Check the gateway bridge logs
Note: the issue does not occur at each run
Could you share your log output?
usergw: user used to connect teh ChripStack Gateway Bridge
user: user used to connect a generic MQTT client (MQTT explorer)
1. QOS 0, no reconnect
Broker log
1643881421: mosquitto version 2.0.14 starting
1643881421: Config loaded from /mosquitto/config/mosquitto.conf.
1643881421: Opening ipv4 listen socket on port 1883.
1643881421: Opening ipv6 listen socket on port 1883.
1643881421: mosquitto version 2.0.14 running
1643881452: New connection from 10.10.236.191:60420 on port 1883.
1643881452: New client connected from 10.10.236.191:60420 as mqtt-explorer-3b35f5df (p2, c1, k60, u'user').
1643881610: New connection from 10.10.236.191:32794 on port 1883.
1643881612: New client connected from 10.10.236.191:32794 as auto-18F89536-7318-88C0-E8CC-A3C179A59AEC (p2, c1, k30, u'usergw').
### BROKER RESTART REQUEST
1643881631: mosquitto version 2.0.14 terminating
1643881633: mosquitto version 2.0.14 starting
1643881633: Config loaded from /mosquitto/config/mosquitto.conf.
1643881633: Opening ipv4 listen socket on port 1883.
1643881633: Opening ipv6 listen socket on port 1883.
1643881633: mosquitto version 2.0.14 running
1643881663: New connection from 10.10.236.191:59894 on port 1883.
1643881663: New client connected from 10.10.236.191:59894 as mqtt-explorer-3b35f5df (p2, c1, k60, u'user').
[integration.mqtt.auth.generic]
# MQTT servers.## Configure one or multiple MQTT server to connect to. Each item must be in# the following format: scheme://host:port where scheme is tcp, ssl or ws.
server="ssl://broker-url:1883"# Connect with the given username (optional)
username="usergw"# Connect with the given password (optional)
password="password"
2. QOS 1, no reconnect on longer duration
Broker log
1643882847: mosquitto version 2.0.14 starting
1643882847: Config loaded from /mosquitto/config/mosquitto.conf.
1643882847: Opening ipv4 listen socket on port 1883.
1643882847: Opening ipv6 listen socket on port 1883.
1643882847: mosquitto version 2.0.14 running
1643882871: New connection from 10.10.236.191:34416 on port 1883.
1643882871: Client mqtt-explorer-3b35f5df disconnected, not authorised.
[integration.mqtt.auth.generic]
# MQTT servers.## Configure one or multiple MQTT server to connect to. Each item must be in# the following format: scheme://host:port where scheme is tcp, ssl or ws.
server="ssl://broker-url:1883"# Connect with the given username (optional)
username="usergw"# Connect with the given password (optional)
password="password"
qos=1
Workaround
Use terminate_on_connect_error=true and supervise the gateway bridge with 'monit'.
Your Environment
ChirpStack Gateway Bridge: v3.13.2
Mosquitto: v2.0.14
The text was updated successfully, but these errors were encountered:
What happened?
Upon MQTT broker restart, the Gateway Bridge does sometime not reconnect, event when disconnection is detected. However, it still tries to publish event and acts as everything was fine.
What did you expect?
The Gateway Bridge tries indefinitely to reconnect when it's not connected.
Steps to reproduce this issue
Steps:
Note: the issue does not occur at each run
Could you share your log output?
usergw
: user used to connect teh ChripStack Gateway Bridgeuser
: user used to connect a generic MQTT client (MQTT explorer)1. QOS 0, no reconnect
Broker log
Gateway Bridge log
Gateway Bridge Configuration
2. QOS 1, no reconnect on longer duration
Broker log
Gateway Bridge log
Gateway Bridge Configuration
Workaround
Use
terminate_on_connect_error=true
and supervise the gateway bridge with 'monit'.Your Environment
The text was updated successfully, but these errors were encountered: