Azure IoT Edge
An Azure service that is used to deploy cloud workloads to run on internet of things (IoT) edge devices via standard containers.
567 questions
Receiving this message "Nothing to Do Dropping the message" when module to module communication is happening
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 59%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAG%3C/text%3E%3C/svg%3E)
Athira Gopinath(UST,IN)
96
Reputation points
Hi ,
As part of my research, I need to use the advantage of module to module communication facility on IoT Edge Device and send the data to upstream. If the data is sending from Module 1 to Module 2,Module 2 is showing Nothing to do Dropping the message sometime**.** Sometimes it shows **Message full .**I would like to know the reason why that log is coming . Is it because of poor network connectivity or anything related to routing .Does it require internet connection to check the logs of an IoT edge module. I have used python scripting to achieve the same.
Also would like to know the TimeToLive option in the routes. Default value is 7200 secs .What happens if I changed to 60secs??.
Please suggest some solution to resolve this issue
{count} votes
-
Sander van de Velde | MVP 32,006 Reputation points MVP2023-08-10T18:31:20.2366667+00:00 Hello Athira,
this is uncommon behavior.
Can you try this with a module written in another language like C# too?
In C#, we have to return the message response 'Completed' to have messages taken from the queue between two modules.
You can check the queue behavior using the Metrics Collector module too.
-
LeelaRajeshSayana-MSFT 14,831 Reputation points Microsoft Employee2023-08-23T21:27:02.3066667+00:00 Hi @Athira Gopinath(UST,IN) We still have not heard back from you. Just wanted to check if the response provided above was helpful? If it answers your query, please do click
Accept AnswerandYesfor the answer, as it might be beneficial to other community members reading this thread. And, if you have any further query do let us know. Thank you -
Athira Gopinath(UST,IN) 96 Reputation points
2023-09-01T02:18:55.5933333+00:00 @LeelaRajeshSayana-MSFT ,the issue is not yet resolved .We observed that the network is being stopped for a few days for IoT Edge Device. Data is sending between the modules but not sending to IoTHub as expected. But we could observed message full and nothing to do, dropping messages and device is showing offline even the ubuntu machine is connected to network. We need to do a manual restart of the machine to run the machine as expected. Please suggest some solution for the same
-
Sander van de Velde | MVP 32,006 Reputation points MVP
2023-09-01T09:34:58.9566667+00:00 Hello Athira,
How long is your edge device up and running? More than 90 days?
Did you take countermeasures for the development TLS certificate for inter-module communication?
See also the side note here.
-
Athira Gopinath(UST,IN) 96 Reputation points
2023-09-06T14:42:17.4733333+00:00 Hi,
The machine is up and running for few months actually, more than 60 days but we are switching the IoT Edge devices and IoTHub. But not turning off the ubuntu machine. We haven't taken any countermeasures for the development TLS certificate for inter-module communication .Is there any message queue limit for edge hub. Could you please provide any RCA regarding the same
-
Athira Gopinath(UST,IN) 96 Reputation points
2023-09-13T11:16:14.57+00:00 @Sander van de Velde | MVP ,I am hereby sharing the logging from console
INFO:azure.iot.device.common.mqtt_transport:publishing on $iothub/twin/GET/?$rid=6986c31d-b94b-42b7-ab57-3d945dba41ce WARNING:azure.iot.device.common.pipeline.pipeline_stages_base:Unexpected error in <azure.iot.device.common.pipeline.pipeline_stages_mqtt.MQTTTransportStage object at 0x7ff7b3a8f590>._run_op() call INFO:azure.iot.device.common.async_adapter:Callback completed with error ProtocolClientError('Message queue full.') INFO:azure.iot.device.common.async_adapter:["azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Message queue full.')\n"] ERROR:azure.iot.device.common.handle_exceptions:Exception caught in background thread. Unable to handle. WARNING:azure.iot.device.common.pipeline.pipeline_stages_base:Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_stages_base.py", line 103, in run_op self._run_op(op) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_thread.py", line 203, in wrapper return func(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_stages_mqtt.py", line 253, in _run_op self.transport.publish(topic=op.topic, payload=op.payload, callback=on_complete) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/mqtt_transport.py", line 563, in publish raise _create_error_from_rc_code(rc) azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Message queue full.') INFO:azure.iot.device.common.mqtt_transport:publishing on $iothub/twin/GET/?$rid=9d796877-c136-49e5-9818-d9f0b7293d57 WARNING:azure.iot.device.common.pipeline.pipeline_stages_base:Unexpected error in <azure.iot.device.common.pipeline.pipeline_stages_mqtt.MQTTTransportStage object at 0x7ff7b3a8f590>._run_op() call INFO:azure.iot.device.common.async_adapter:Callback completed with error ProtocolClientError('Message queue full.') INFO:azure.iot.device.common.async_adapter:["azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Message queue full.')\n"] WARNING:azure.iot.device.common.pipeline.pipeline_stages_base:Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_stages_base.py", line 103, in run_op self._run_op(op) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_thread.py", line 203, in wrapper return func(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_stages_mqtt.py", line 253, in _run_op self.transport.publish(topic=op.topic, payload=op.payload, callback=on_complete) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/mqtt_transport.py", line 563, in publish raise _create_error_from_rc_code(rc) azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Message queue full.') INFO:azure.iot.device.common.mqtt_transport:publishing on $iothub/twin/GET/?$rid=097b9778-c39f-48d6-ad74-b26e92d102d4 INFO:azure.iot.device.common.async_adapter:Callback completed with error ProtocolClientError('Message queue full.') WARNING:azure.iot.device.common.pipeline.pipeline_stages_base:Unexpected error in <azure.iot.device.common.pipeline.pipeline_stages_mqtt.MQTTTransportStage object at 0x7ff7b3a8f590>._run_op() call ERROR:azure.iot.device.common.handle_exceptions:["azure.iot.device.iothub.sync_handler_manager.HandlerManagerException: HandlerManagerException('HANDLER (CLIENT_EVENT): Error during invocation') caused by ClientError('Error in the IoTHub client')\n"] INFO:azure.iot.device.common.async_adapter:["azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Message queue full.')\n"] ERROR:azure.iot.device.common.handle_exceptions:Exception caught in background thread. Unable to handle. WARNING:azure.iot.device.common.pipeline.pipeline_stages_base:Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_stages_base.py", line 103, in run_op self._run_op(op) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_thread.py", line 203, in wrapper return func(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_stages_mqtt.py", line 253, in _run_op self.transport.publish(topic=op.topic, payload=op.payload, callback=on_complete) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/mqtt_transport.py", line 563, in publish raise _create_error_from_rc_code(rc) azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Message queue full.') INFO:azure.iot.device.common.async_adapter:Callback completed with error ProtocolClientError('Message queue full.') INFO:azure.iot.device.common.async_adapter:["azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Message queue full.')\n"] ERROR:azure.iot.device.common.handle_exceptions:["azure.iot.device.iothub.sync_handler_manager.HandlerManagerException: HandlerManagerException('HANDLER (CLIENT_EVENT): Error during invocation') caused by ClientError('Error in the IoTHub client')\n"] ERROR:azure.iot.device.common.handle_exceptions:Exception caught in background thread. Unable to handle. ERROR:azure.iot.device.common.handle_exceptions:["azure.iot.device.iothub.sync_handler_manager.HandlerManagerException: HandlerManagerException('HANDLER (CLIENT_EVENT): Error during invocation') caused by ClientError('Error in the IoTHub client')\n"] ERROR:azure.iot.device.common.handle_exceptions:Exception caught in background thread. Unable to handle. ERROR:azure.iot.device.common.handle_exceptions:["azure.iot.device.iothub.sync_handler_manager.HandlerManagerException: HandlerManagerException('HANDLER (CLIENT_EVENT): Error during invocation') caused by ClientError('Error in the IoTHub client')\n"] INFO:azure.iot.device.common.mqtt_transport:message received on $iothub/twin/res/200/?$rid=b209083f-769f-4aff-a5b7-2e87cb0263c0 INFO:azure.iot.device.common.pipeline.pipeline_stages_base:CoordinateRequestAndResponseStage(ResponseEvent): request_id b209083f-769f-4aff-a5b7-2e87cb0263c0 not found in pending list. Nothing to do. Dropping INFO:azure.iot.device.common.mqtt_transport:payload published for 23006 INFO:azure.iot.device.common.mqtt_transport:message received on devices/CNP0001/modules/idec_edgesense_uat/inputs/input1/%24.cdid=CNP0001&%24.cmid=vi_module_uat INFO:azure.iot.device.iothub.aio.async_clients:Getting twin INFO:azure.iot.device.common.mqtt_transport:publishing on $iothub/twin/GET/?$rid=5a6f9104-4071-4210-8312-ce524ecc2503 WARNING:azure.iot.device.common.pipeline.pipeline_stages_base:Unexpected error in <azure.iot.device.common.pipeline.pipeline_stages_mqtt.MQTTTransportStage object at 0x7ff7b3a8f590>._run_op() call WARNING:azure.iot.device.common.pipeline.pipeline_stages_base:Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_stages_base.py", line 103, in run_op self._run_op(op) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_thread.py", line 203, in wrapper return func(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_stages_mqtt.py", line 253, in _run_op self.transport.publish(topic=op.topic, payload=op.payload, callback=on_complete) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/mqtt_transport.py", line 563, in publish raise _create_error_from_rc_code(rc) azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Message queue full.') INFO:azure.iot.device.common.async_adapter:Callback completed with error ProtocolClientError('Message queue full.') INFO:azure.iot.device.common.async_adapter:["azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Message queue full.')\n"] ERROR:azure.iot.device.common.handle_exceptions:Exception caught in background thread. Unable to handle. ERROR:azure.iot.device.common.handle_exceptions:["azure.iot.device.iothub.sync_handler_manager.HandlerManagerException: HandlerManagerException('HANDLER (CLIENT_EVENT): Error during invocation') caused by ClientError('Error in the IoTHub client')\n"] INFO:azure.iot.device.common.mqtt_transport:message received on $iothub/twin/res/200/?$rid=fd3e26db-958d-4fee-8f89-2e8a6070b39f INFO:azure.iot.device.common.pipeline.pipeline_stages_base:CoordinateRequestAndResponseStage(ResponseEvent): request_id fd3e26db-958d-4fee-8f89-2e8a6070b39f not found in pending list. Nothing to do. Dropping INFO:azure.iot.device.common.mqtt_transport:payload published for 23007 INFO:azure.iot.device.common.mqtt_transport:message received on $iothub/twin/res/200/?$rid=b2aad4be-f3f3-4d47-a21e-3cd05aae8ad6 INFO:azure.iot.device.common.pipeline.pipeline_stages_base:CoordinateRequestAndResponseStage(ResponseEvent): request_id b2aad4be-f3f3-4d47-a21e-3cd05aae8ad6 not found in pending list. Nothing to do. Dropping INFO:azure.iot.device.common.mqtt_transport:payload published for 23008 INFO:azure.iot.device.common.mqtt_transport:message received on $iothub/twin/res/200/?$rid=df833219-fa7f-424e-9559-8b44ee8cb977 INFO:azure.iot.device.common.pipeline.pipeline_stages_base:CoordinateRequestAndResponseStage(ResponseEvent): request_id df833219-fa7f-424e-9559-8b44ee8cb977 not found in pending list. Nothing to do. Dropping INFO:azure.iot.device.common.mqtt_transport:payload published for 23009 INFO:azure.iot.device.common.mqtt_transport:message received on $iothub/twin/res/200/?$rid=f8658603-7aef-4a3c-92bb-9372dd850366 INFO:azure.iot.device.common.pipeline.pipeline_stages_base:CoordinateRequestAndResponseStage(ResponseEvent): request_id f8658603-7aef-4a3c-92bb-9372dd850366 not found in pending list. Nothing to do. Dropping INFO:azure.iot.device.common.mqtt_transport:payload published for 23010 INFO:azure.iot.device.common.mqtt_transport:message received on devices/CNP0001/modules/idec_edgesense_uat/inputs/input1/%24.cdid=CNP0001&%24.cmid=vi_module_uat INFO:azure.iot.device.iothub.aio.async_clients:Getting twin INFO:azure.iot.device.common.mqtt_transport:publishing on $iothub/twin/GET/?$rid=ef92e9e1-7edc-4b2e-8d8d-5135e728676b WARNING:azure.iot.device.common.pipeline.pipeline_stages_base:Unexpected error in <azure.iot.device.common.pipeline.pipeline_stages_mqtt.MQTTTransportStage object at 0x7ff7b3a8f590>._run_op() call WARNING:azure.iot.device.common.pipeline.pipeline_stages_base:Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_stages_base.py", line 103, in run_op self._run_op(op) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_thread.py", line 203, in wrapper return func(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_stages_mqtt.py", line 253, in _run_op self.transport.publish(topic=op.topic, payload=op.payload, callback=on_complete) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/mqtt_transport.py", line 563, in publish raise _create_error_from_rc_code(rc) azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Message queue full.') INFO:azure.iot.device.common.async_adapter:Callback completed with error ProtocolClientError('Message queue full.') INFO:azure.iot.device.common.async_adapter:["azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Message queue full.')\n"] ERROR:azure.iot.device.common.handle_exceptions:Exception caught in background thread. Unable to handle. ERROR:azure.iot.device.common.handle_exceptions:["azure.iot.device.iothub.sync_handler_manager.HandlerManagerException: HandlerManagerException('HANDLER (CLIENT_EVENT): Error during invocation') caused by ClientError('Error in the IoTHub client')\n"] INFO:azure.iot.device.common.mqtt_transport:disconnected with result code: 16 INFO:azure.iot.device.common.mqtt_transport:Forcing paho disconnect to prevent it from automatically reconnecting INFO:azure.iot.device.common.mqtt_transport:disconnected with result code: 0 INFO:azure.iot.device.common.pipeline.pipeline_stages_mqtt:MQTTTransportStage: _on_mqtt_disconnect called: ProtocolClientError('Unknown CONNACK rc==16') INFO:azure.iot.device.common.pipeline.pipeline_stages_mqtt:MQTTTransportStage: disconnection was unexpected INFO:azure.iot.device.iothub.abstract_clients:Connection State - Disconnected INFO:azure.iot.device.common.handle_exceptions:Unexpected disconnection INFO:azure.iot.device.iothub.abstract_clients:Cleared all pending method requests due to disconnect INFO:azure.iot.device.common.handle_exceptions:azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Unknown CONNACK rc==16') The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/handle_exceptions.py", line 43, in swallow_unraised_exception raise e azure.iot.device.common.transport_exceptions.ConnectionDroppedError: ConnectionDroppedError(None) caused by ProtocolClientError('Unknown CONNACK rc==16') INFO:azure.iot.device.common.pipeline.pipeline_stages_mqtt:MQTTTransportStage: _on_mqtt_disconnect called WARNING:azure.iot.device.common.pipeline.pipeline_stages_base:ReconnectStage: DisconnectEvent received while in unexpected state - WAITING_TO_RECONNECT, Connected: False INFO:azure.iot.device.common.pipeline.pipeline_stages_mqtt:MQTTTransportStage: disconnection was unexpected INFO:azure.iot.device.common.handle_exceptions:Unexpected disconnection INFO:azure.iot.device.iothub.abstract_clients:Connection State - Disconnected INFO:azure.iot.device.common.handle_exceptions:Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/handle_exceptions.py", line 43, in swallow_unraised_exception raise e azure.iot.device.common.transport_exceptions.ConnectionDroppedError: ConnectionDroppedError(None) INFO:azure.iot.device.iothub.abstract_clients:Cleared all pending method requests due to disconnect INFO:azure.iot.device.common.mqtt_transport:Connect using port 8883 (TCP) INFO:azure.iot.device.common.mqtt_transport:connected with result code: 0 INFO:azure.iot.device.common.pipeline.pipeline_stages_mqtt:_on_mqtt_connected called INFO:azure.iot.device.common.pipeline.pipeline_stages_base:CoordinateRequestAndResponseStage: ConnectedEvent: re-publishing request c31930a5-32e6-4ccc-b33d-b309696696e0 for GET twin INFO:azure.iot.device.common.pipeline.pipeline_stages_base:CoordinateRequestAndResponseStage: ConnectedEvent: re-publishing request 3f83850f-5692-4504-8a1b-6c26dc57739c for GET twin INFO:azure.iot.device.common.pipeline.pipeline_stages_base:CoordinateRequestAndResponseStage: ConnectedEvent: re-publishing request b52926a4-a201-48bd-81aa-31800180cc6a for GET twin INFO:azure.iot.device.common.mqtt_transport:publishing on $iothub/twin/GET/?$rid=c31930a5-32e6-4ccc-b33d-b309696696e0 INFO:azure.iot.device.iothub.abstract_clients:Connection State - Connected WARNING:azure.iot.device.common.pipeline.pipeline_stages_base:Unexpected error in <azure.iot.device.common.pipeline.pipeline_stages_mqtt.MQTTTransportStage object at 0x7ff7b3a8f590>._run_op() call WARNING:azure.iot.device.common.pipeline.pipeline_stages_base:Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_stages_base.py", line 103, in run_op self._run_op(op) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_thread.py", line 203, in wrapper return func(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_stages_mqtt.py", line 253, in _run_op self.transport.publish(topic=op.topic, payload=op.payload, callback=on_complete) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/mqtt_transport.py", line 563, in publish raise _create_error_from_rc_code(rc) azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Message queue full.') INFO:azure.iot.device.common.mqtt_transport:publishing on $iothub/twin/GET/?$rid=3f83850f-5692-4504-8a1b-6c26dc57739c WARNING:azure.iot.device.common.pipeline.pipeline_stages_base:Unexpected error in <azure.iot.device.common.pipeline.pipeline_stages_mqtt.MQTTTransportStage object at 0x7ff7b3a8f590>._run_op() call INFO:azure.iot.device.common.async_adapter:Callback completed with error ProtocolClientError('Message queue full.') INFO:azure.iot.device.common.async_adapter:["azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Message queue full.')\n"] ERROR:azure.iot.device.common.handle_exceptions:Exception caught in background thread. Unable to handle. WARNING:azure.iot.device.common.pipeline.pipeline_stages_base:Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_stages_base.py", line 103, in run_op self._run_op(op) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_thread.py", line 203, in wrapper return func(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_stages_mqtt.py", line 253, in _run_op self.transport.publish(topic=op.topic, payload=op.payload, callback=on_complete) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/mqtt_transport.py", line 563, in publish raise _create_error_from_rc_code(rc) azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Message queue full.') INFO:azure.iot.device.common.mqtt_transport:publishing on $iothub/twin/GET/?$rid=b52926a4-a201-48bd-81aa-31800180cc6a WARNING:azure.iot.device.common.pipeline.pipeline_stages_base:Unexpected error in <azure.iot.device.common.pipeline.pipeline_stages_mqtt.MQTTTransportStage object at 0x7ff7b3a8f590>._run_op() call INFO:azure.iot.device.common.async_adapter:Callback completed with error ProtocolClientError('Message queue full.') INFO:azure.iot.device.common.async_adapter:["azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Message queue full.')\n"] WARNING:azure.iot.device.common.pipeline.pipeline_stages_base:Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_stages_base.py", line 103, in run_op self._run_op(op) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_thread.py", line 203, in wrapper return func(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_stages_mqtt.py", line 253, in _run_op self.transport.publish(topic=op.topic, payload=op.payload, callback=on_complete) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/mqtt_transport.py", line 563, in publish raise _create_error_from_rc_code(rc) azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Message queue full.') INFO:azure.iot.device.common.async_adapter:Callback completed with error ProtocolClientError('Message queue full.') INFO:azure.iot.device.common.async_adapter:["azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Message queue full.')\n"] ERROR:azure.iot.device.common.handle_exceptions:["azure.iot.device.iothub.sync_handler_manager.HandlerManagerException: HandlerManagerException('HANDLER (CLIENT_EVENT): Error during invocation') caused by ClientError('Error in the IoTHub client')\n"] ERROR:azure.iot.device.common.handle_exceptions:Exception caught in background thread. Unable to handle. ERROR:azure.iot.device.common.handle_exceptions:["azure.iot.device.iothub.sync_handler_manager.HandlerManagerException: HandlerManagerException('HANDLER (CLIENT_EVENT): Error during invocation') caused by ClientError('Error in the IoTHub client')\n"] ERROR:azure.iot.device.common.handle_exceptions:Exception caught in background thread. Unable to handle. ERROR:azure.iot.device.common.handle_exceptions:["azure.iot.device.iothub.sync_handler_manager.HandlerManagerException: HandlerManagerException('HANDLER (CLIENT_EVENT): Error during invocation') caused by ClientError('Error in the IoTHub client')\n"] INFO:azure.iot.device.common.mqtt_transport:message received on $iothub/twin/res/200/?$rid=677454c8-11af-45c0-8d7a-719fd312e036 INFO:azure.iot.device.common.pipeline.pipeline_stages_base:CoordinateRequestAndResponseStage(ResponseEvent): request_id 677454c8-11af-45c0-8d7a-719fd312e036 not found in pending list. Nothing to do. Dropping INFO:azure.iot.device.common.mqtt_transport:payload published for 23011 INFO:azure.iot.device.common.mqtt_transport:message received on $iothub/twin/res/200/?$rid=d977b9f1-d248-4d90-bbb7-493122e3868a INFO:azure.iot.device.common.pipeline.pipeline_stages_base:CoordinateRequestAndResponseStage(ResponseEvent): request_id d977b9f1-d248-4d90-bbb7-493122e3868a not found in pending list. Nothing to do. Dropping INFO:azure.iot.device.common.mqtt_transport:payload published for 23012 INFO:azure.iot.device.common.mqtt_transport:message received on $iothub/twin/res/200/?$rid=ac578b50-866e-4fcc-a687-b61fa8fb5967 INFO:azure.iot.device.common.pipeline.pipeline_stages_base:CoordinateRequestAndResponseStage(ResponseEvent): request_id ac578b50-866e-4fcc-a687-b61fa8fb5967 not found in pending list. Nothing to do. Dropping INFO:azure.iot.device.common.mqtt_transport:payload published for 23013 INFO:azure.iot.device.common.mqtt_transport:message received on devices/CNP0001/modules/idec_edgesense_uat/inputs/input1/%24.cdid=CNP0001&%24.cmid=vi_module_uat INFO:azure.iot.device.iothub.aio.async_clients:Getting twin INFO:azure.iot.device.common.mqtt_transport:publishing on $iothub/twin/GET/?$rid=0f8095b3-8f4e-4646-a5e1-4bd5c77a15e2 WARNING:azure.iot.device.common.pipeline.pipeline_stages_base:Unexpected error in <azure.iot.device.common.pipeline.pipeline_stages_mqtt.MQTTTransportStage object at 0x7ff7b3a8f590>._run_op() call WARNING:azure.iot.device.common.pipeline.pipeline_stages_base:Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_stages_base.py", line 103, in run_op self._run_op(op) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_thread.py", line 203, in wrapper return func(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/pipeline/pipeline_stages_mqtt.py", line 253, in _run_op self.transport.publish(topic=op.topic, payload=op.payload, callback=on_complete) File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/mqtt_transport.py", line 563, in publish raise _create_error_from_rc_code(rc) azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Message queue full.') INFO:azure.iot.device.common.async_adapter:Callback completed with error ProtocolClientError('Message queue full.') INFO:azure.iot.device.common.async_adapter:["azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Message queue full.')\n"] ERROR:azure.iot.device.common.handle_exceptions:Exception caught in background thread. Unable to handle. ERROR:azure.iot.device.common.handle_exceptions:["azure.iot.device.iothub.sync_handler_manager.HandlerManagerException: HandlerManagerException('HANDLER (CLIENT_EVENT): Error during invocation') caused by ClientError('Error in the IoTHub client')\n"] INFO:azure.iot.device.common.mqtt_transport:message received on $iothub/twin/res/200/?$rid=1c50500d-b652-4b6d-9f06-5cce6492241b INFO:azure.iot.device.common.pipeline.pipeline_stages_base:CoordinateRequestAndResponseStage(ResponseEvent): request_id 1c50500d-b652-4b6d-9f06-5cce6492241b not found in pending list. Nothing to do. Dropping INFO:azure.iot.device.common.mqtt_transport:payload published for 23014 INFO:azure.iot.device.common.mqtt_transport:message received on $iothub/twin/res/200/?$rid=ec5a8b0d-5ea2-461a-925e-af9959fca1ad INFO:azure.iot.device.common.pipeline.pipeline_stages_base:CoordinateRequestAndResponseStage(ResponseEvent): request_id ec5a8b0d-5ea2-461a-925e-af9959fca1ad not found in pending list. Nothing to do. Dropping INFO:azure.iot.device.common.mqtt_transport:payload published for 23015 INFO:azure.iot.device.common.mqtt_transport:message received on $iothub/twin/res/200/?$rid=60702047-a886-4c8e-bbef-bab6c6bc681b INFO:azure.iot.device.common.pipeline.pipeline_stages_base:CoordinateRequestAndResponseStage(ResponseEvent): request_id 60702047-a886-4c8e-bbef-bab6c6bc681b not found in pending list. Nothing to do. Dropping INFO:azure.iot.device.common.mqtt_transport:payload published for 23016 INFO:azure.iot.device.common.mqtt_transport:disconnected with result code: 16 INFO:azure.iot.device.common.mqtt_transport:Forcing paho disconnect to prevent it from automatically reconnecting INFO:azure.iot.device.common.mqtt_transport:disconnected with result code: 0 INFO:azure.iot.device.common.pipeline.pipeline_stages_mqtt:MQTTTransportStage: _on_mqtt_disconnect called: ProtocolClientError('Unknown CONNACK rc==16') INFO:azure.iot.device.common.pipeline.pipeline_stages_mqtt:MQTTTransportStage: disconnection was unexpected INFO:azure.iot.device.common.handle_exceptions:Unexpected disconnection INFO:azure.iot.device.common.handle_exceptions:azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Unknown CONNACK rc==16') The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/handle_exceptions.py", line 43, in swallow_unraised_exception raise e azure.iot.device.common.transport_exceptions.ConnectionDroppedError: ConnectionDroppedError(None) caused by ProtocolClientError('Unknown CONNACK rc==16') INFO:azure.iot.device.common.pipeline.pipeline_stages_mqtt:MQTTTransportStage: _on_mqtt_disconnect called WARNING:azure.iot.device.common.pipeline.pipeline_stages_base:ReconnectStage: DisconnectEvent received while in unexpected state - WAITING_TO_RECONNECT, Connected: False INFO:azure.iot.device.common.pipeline.pipeline_stages_mqtt:MQTTTransportStage: disconnection was unexpected INFO:azure.iot.device.common.handle_exceptions:Unexpected disconnection INFO:azure.iot.device.iothub.abstract_clients:Connection State - Disconnected INFO:azure.iot.device.common.handle_exceptions:Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/azure/iot/device/common/handle_exceptions.py", line 43, in swallow_unraised_exception raise e azure.iot.device.common.transport_exceptions.ConnectionDroppedError: ConnectionDroppedError(None) INFO:azure.iot.device.iothub.abstract_clients:Cleared all pending method requests due to disconnect INFO:azure.iot.device.iothub.abstract_clients:Connection State - Disconnected INFO:azure.iot.device.iothub.abstract_clients:Cleared all pending method requests due to disconnect INFO:azure.iot.device.common.mqtt_transport:Connect using port 8883 (TCP) INFO:azure.iot.device.common.mqtt_transport:connected with result code: 0 INFO:azure.iot.device.common.pipeline.pipeline_stages_mqtt:_on_mqtt_connected called INFO:azure.iot.device.iothub.abstract_clients:Connection State - Connected INFO:azure.iot.device.common.mqtt_transport:message received on $iothub/twin/res/200/?$rid=cead3c34-9686-453a-ba42-f5d5088213c8 INFO:azure.iot.device.common.pipeline.pipeline_stages_base:CoordinateRequestAndResponseStage(ResponseEvent): request_id cead3c34-9686-453a-ba42-f5d5088213c8 not found in pending list. Nothing to do. Dropping INFO:azure.iot.device.common.mqtt_transport:payload published for 23017 INFO:azure.iot.device.common.mqtt_transport:message received on $iothub/twin/res/200/?$rid=7aa661a0-2b8d-429c-b1e3-7f7ab0fdd5ab INFO:azure.iot.device.common.pipeline.pipeline_stages_base:CoordinateRequestAndResponseStage(ResponseEvent): request_id 7aa661a0-2b8d-429c-b1e3-7f7ab0fdd5ab not found in pending list. Nothing to do. Dropping INFO:azure.iot.device.common.mqtt_transport:payload published for 23018 INFO:azure.iot.device.common.mqtt_transport:message received on devices/CNP0001/modules/idec_edgesense_uat/inputs/input1/%24.cdid=CNP0001&%24.cmid=vi_module_uat INFO:azure.iot.device.iothub.aio.async_clients:Getting twin INFO:azure.iot.device.common.mqtt_transport:publishing on $iothub/twin/GET/?$rid=5d9d9a0a-2b3f-4ace-bce5-ee2c5a151fcd INFO:azure.iot.device.common.mqtt_transport:message received on $iothub/twin/res/200/?$rid=be5254fd-cecd-4831-8f31-101b67d73f72 INFO:azure.iot.device.common.pipeline.pipeline_stages_base:CoordinateRequestAndResponseStage(ResponseEvent): request_id be5254fd-cecd-4831-8f31-101b67d73f72 not found in pending list. Nothing to do. Dropping INFO:azure.iot.device.common.mqtt_transport:payload published for 23019 INFO:azure.iot.device.common.mqtt_transport:message received on $iothub/twin/res/200/?$rid=294c4ee3-1af6-48d0-8ec5-8b900e56a462 INFO:azure.iot.device.common.pipeline.pipeline_stages_base:CoordinateRequestAndResponseStage(ResponseEvent): request_id 294c4ee3-1af6-48d0-8ec5-8b900e56a462 not found in pending list. Nothing to do. Dropping INFO:azure.iot.device.common.mqtt_transport:payload published for 23020 INFO:azure.iot.device.common.mqtt_transport:message received on $iothub/twin/res/200/?$rid=8191910a-9682-4eea-8727-9aa3f2939f48 INFO:azure.iot.device.common.pipeline.pipeline_stages_base:CoordinateRequestAndResponseStage(ResponseEvent): request_id 8191910a-9682-4eea-8727-9aa3f2939f48 not found in pending list. Nothing to do. Dropping INFO:azure.iot.device.common.mqtt_transport:payload published for 23021 INFO:azure.iot.device.common.mqtt_transport:message received on $iothub/twin/res/200/?$rid=460719e8-1eb5-429f-8e5d-bc74be79b226 INFO:azure.iot.device.common.pipeline.pipeline_stages_base:CoordinateRequestAndResponseStage(ResponseEvent): request_id 460719e8-1eb5-429f-8e5d-bc74be79b226 not found in pending list. Nothing to do. Dropping INFO:azure.iot.device.common.mqtt_transport:payload published for 23022 INFO:azure.iot.device.common.mqtt_transport:message received on devices/CNP0001/modules/idec_edgesense_uat/inputs/input1/%24.cdid=CNP0001&%24.cmid=vi_module_uat INFO:azure.iot.device.iothub.aio.async_clients:Getting twin INFO:azure.iot.device.common.mqtt_transport:publishing on $iothub/twin/GET/?$rid=fb40d747-4916-4ac0-8613-b8ffda3d8eb0 INFO:azure.iot.device.common.mqtt_transport:disconnected with result code: 16 INFO:azure.iot.device.common.mqtt_transport:Forcing paho disconnect to prevent it from automatically reconnecting INFO:azure.iot.device.common.mqtt_transport:disconnected with result code: 0 INFO:azure.iot.device.common.pipeline.pipeline_stages_mqtt:MQTTTransportStage: _on_mqtt_disconnect called: ProtocolClientError('Unknown CONNACK rc==16') INFO:azure.iot.device.common.pipeline.pipeline_stages_mqtt:MQTTTransportStage: disconnection was unexpected INFO:azure.iot.device.iothub.abstract_clients:Connection State - Disconnected INFO:azure.iot.device.common.handle_exceptions:Unexpected disconnection INFO:azure.iot.device.iothub.abstract_clients:Cleared all pending method requests due to disconnect INFO:azure.iot.device.common.handle_exceptions:azure.iot.device.common.transport_exceptions.ProtocolClientError: ProtocolClientError('Unknown CONNACK rc==16') -
LeelaRajeshSayana-MSFT 14,831 Reputation points Microsoft Employee
2023-09-14T15:56:56.4866667+00:00 Hi @Athira Gopinath(UST,IN) For a deeper investigation and immediate assistance on this issue, please file a support request @ https://aka.ms/azsupt? If you do not have access to a support plan, could you please send an email to azcommunity@microsoft.com with the below details, so that we can work closely on this matter.
Thread URL: Link to this thread.
Azure Subscription ID:
Email Subject : Attn Leela
-
LeelaRajeshSayana-MSFT 14,831 Reputation points Microsoft Employee
2023-09-21T20:56:14.8233333+00:00 Hi @Athira Gopinath(UST,IN) Just checking to see if you got a chance to review the above response and create a support ticket for this issue. Kindly share the ticket details here so we can track the issue internally. If you need any assistance creating a support ticket, kindly reach out to us through the above-mentioned email.
Sign in to comment
Sign in to answer