Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Service restart for C2D messaging subscribe fail #3

Open
MWGMorningwood opened this issue Dec 15, 2023 · 0 comments
Open

Service restart for C2D messaging subscribe fail #3

MWGMorningwood opened this issue Dec 15, 2023 · 0 comments

Comments

@MWGMorningwood
Copy link

MWGMorningwood commented Dec 15, 2023

Description

Subscribe for c2d failed. Not enabling feature
After a service restart, Successfully enabled feature:c2d

Re-creation

I have not been able to re-create this yet after five deployments. It only happened on the first.
I'll keep an eye on it and post back here if it happens again or close it out if it does not.

Logs

disconnected with result code: 7
Enabling feature:c2d...
subscribing to devices/dae41526-ba44-489a-aa80-a16eccdec904/messages/devicebound/# with qos 1
Subscribe for c2d failed.  Not enabling feature
Forcing paho disconnect to prevent it from automatically reconnecting
Callback completed with error The client is not currently connected.
MQTTTransportStage: _on_mqtt_disconnect called: The connection was lost.
['azure.iot.device.common.transport_exceptions.NoConnectionError: The client is not currently connected.\n']

Proposed resolution

Look for subscribe for c2d failed and auto-restart service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant