-
Notifications
You must be signed in to change notification settings - Fork 72
tedge connect shows errors but connection is successful #3235
Copy link
Copy link
Closed
Description
Describe the bug
Trying to connect the tegde version 1.3.1 fails:
Sending packets to check connection. This may take up to 2 seconds.
ERROR: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })
Warning: Bridge has been configured, but Cumulocity connection check failed.
ERROR: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })
We run a version of the tedge-container-bundle
We test on 4 different systems.
The error occurs only on two systems. On the other two it works.
To Reproduce
The error happen independant of the used bridge: builtin or mosquitto.
Expected behavior
The command tedge connect should complete successfully.
buildin log info:
builtin_tedge_connect_c8y.log
builtin_tedge_mqtt_sub_hash.log
builtin_tedge_config_list.log
mosquitto log info:
mos_tedge_config_list.log
mos_tedge_connect_c8y.log
mos_tedge_mqtt_sub_hash.log
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working