Hi all,
I´m working on AWS greengrass guides and experienced some problems during the Testing Communications section in module 4 (https://docs.aws.amazon.com/es_es/greengrass/latest/developerguide/test-comms.html), I´m not able to receive the message on the subscriber terminal window. The publisher works fine and publish the messages without problem, but once I run the subscriber I get the following:
Now we persist the connectivity/identity information...
Now proceed to the connecting flow...
2019-02-07 12:03:24,920 - AWSIoTPythonSDK.core.protocol.internal.clients - DEBUG - Initializing MQTT layer...
2019-02-07 12:03:24,928 - AWSIoTPythonSDK.core.protocol.internal.clients - DEBUG - Registering internal event callbacks to MQTT layer...
2019-02-07 12:03:24,928 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - MqttCore initialized
2019-02-07 12:03:24,928 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Client id: HelloWorld_Subscriber
2019-02-07 12:03:24,928 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Protocol version: MQTTv3.1.1
2019-02-07 12:03:24,928 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Authentication type: TLSv1.2 certificate based Mutual Auth.
2019-02-07 12:03:24,928 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Configuring certificates...
Trying to connect to core at fe80::ba27:ebff:fe9e:9e9a:8883
2019-02-07 12:03:24,928 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Configuring endpoint...
2019-02-07 12:03:24,928 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Performing sync connect...
2019-02-07 12:03:24,928 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Performing async connect...
2019-02-07 12:03:24,928 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Keep-alive: 600.000000 sec
2019-02-07 12:03:24,928 - AWSIoTPythonSDK.core.protocol.internal.workers - DEBUG - Event consuming thread started
2019-02-07 12:03:24,928 - AWSIoTPythonSDK.core.protocol.mqtt_core - DEBUG - Passing in general notification callbacks to internal client...
2019-02-07 12:03:24,928 - AWSIoTPythonSDK.core.protocol.internal.clients - DEBUG - Filling in fixed event callbacks: CONNACK, DISCONNECT, MESSAGE
2019-02-07 12:03:25,960 - AWSIoTPythonSDK.core.protocol.internal.workers - DEBUG - Cleaning up before stopping event consuming
2019-02-07 12:03:25,960 - AWSIoTPythonSDK.core.protocol.internal.workers - DEBUG - Event queue cleared
2019-02-07 12:03:25,960 - AWSIoTPythonSDK.core.protocol.internal.clients - DEBUG - Stopping network I/O thread...
2019-02-07 12:03:25,960 - AWSIoTPythonSDK.core.protocol.internal.workers - DEBUG - Network thread stopped
2019-02-07 12:03:25,960 - AWSIoTPythonSDK.core.protocol.internal.workers - DEBUG - Event callbacks cleared
2019-02-07 12:03:25,960 - AWSIoTPythonSDK.core.protocol.internal.workers - DEBUG - Event consuming thread stopped
2019-02-07 12:03:25,960 - AWSIoTPythonSDK.core.protocol.internal.workers - DEBUG - Waiting for event consumer to completely stop
2019-02-07 12:03:25,970 - AWSIoTPythonSDK.core.protocol.internal.workers - DEBUG - Exiting dispatching loop...
2019-02-07 12:03:25,980 - AWSIoTPythonSDK.core.protocol.mqtt_core - DEBUG - Event consumer stopped
Error in connect!
Type: <class 'socket.error'>
Error message:
Trying to connect to core at 192.168.137.46:8883
2019-02-07 12:03:25,980 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Configuring endpoint...
2019-02-07 12:03:25,980 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Performing sync connect...
2019-02-07 12:03:25,980 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Performing async connect...
2019-02-07 12:03:25,980 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Keep-alive: 600.000000 sec
2019-02-07 12:03:25,980 - AWSIoTPythonSDK.core.protocol.internal.workers - DEBUG - Event consuming thread started
2019-02-07 12:03:25,980 - AWSIoTPythonSDK.core.protocol.mqtt_core - DEBUG - Passing in general notification callbacks to internal client...
2019-02-07 12:03:25,980 - AWSIoTPythonSDK.core.protocol.internal.clients - DEBUG - Filling in fixed event callbacks: CONNACK, DISCONNECT, MESSAGE
2019-02-07 12:03:26,160 - AWSIoTPythonSDK.core.protocol.internal.clients - DEBUG - Starting network I/O thread...
2019-02-07 12:03:26,160 - AWSIoTPythonSDK.core.protocol.internal.workers - DEBUG - Produced [connack] event
2019-02-07 12:03:26,170 - AWSIoTPythonSDK.core.protocol.internal.workers - DEBUG - Dispatching [connack] event
2019-02-07 12:03:26,170 - AWSIoTPythonSDK.core.protocol.internal.workers - DEBUG - No need for recovery
2019-02-07 12:03:26,170 - AWSIoTPythonSDK.core.protocol.internal.clients - DEBUG - Invoking custom event callback...
2019-02-07 12:03:26,180 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Performing sync subscribe...
2019-02-07 12:03:26,180 - AWSIoTPythonSDK.core.protocol.internal.workers - DEBUG - Adding a new subscription record: 'hello/world/pubsub' qos: 0
2019-02-07 12:03:26,180 - AWSIoTPythonSDK.core.protocol.internal.clients - DEBUG - Filling in custom suback event callback...
2019-02-07 12:03:26,180 - AWSIoTPythonSDK.core.protocol.internal.workers - DEBUG - Produced [suback] event
2019-02-07 12:03:26,188 - AWSIoTPythonSDK.core.protocol.internal.workers - DEBUG - Dispatching [suback] event
2019-02-07 12:03:26,188 - AWSIoTPythonSDK.core.protocol.internal.clients - DEBUG - Invoking custom event callback...
2019-02-07 12:03:26,188 - AWSIoTPythonSDK.core.protocol.internal.clients - DEBUG - This custom event callback is for pub/sub/unsub, removing it after invocation...
2019-02-07 12:03:46,161 - AWSIoTPythonSDK.core.protocol.connection.cores - DEBUG - stableConnection: Resetting the backoff time to: 1 sec.
2019-02-07 12:03:55,486 - AWSIoTPythonSDK.core.protocol.internal.workers - DEBUG - Produced [disconnect] event
2019-02-07 12:03:55,486 - AWSIoTPythonSDK.core.protocol.connection.cores - DEBUG - backOff: current backoff time is: 1 sec.
As you can see the program stays at "Resetting the backoff time to: 1 sec" forever, I have deleted the last devices and cfreated new ones, also re-deploy the group configuration but the problem persists.
Thank you very much for any help
