Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Provisioning Client timeout after failed Authentication Exception

See original GitHub issue

Context

Ubuntu Core
Python 3.8
azure-iot-device==2.9.0

Description of the issue

I’m working on a device which does not have an RTC, thus, when it first starts up, we do not have correct time. As a result, if we attempt to Provision with a certificate after we connect to the cloud, but before NTP has synced time, we get a exceptions.TlsExchangeAuthError, which is expected since the certificate’s time range will not be acceptable yet. however, we try to connect again after time syncs, and we get a different exception: ClientError('Unexpected failure') caused by ServiceError('Operation timed out before provisioning service could respond for register operation') we continue to receive this exception until we restart our application. this began to occur when we implemented the fix recommended here: https://github.com/Azure/azure-iot-sdk-python/issues/899

Console log of the issue

provisioningTimeout.log

Issue Analytics

State:
Created 2 years ago
Comments:8 (4 by maintainers)

Top GitHub Comments

1reaction

cartertinneycommented, Dec 17, 2021

@jonathon793

I have been able to repro the issue, working on figuring out what the issue is now. Will hopefully have an update for you soon.

0reactions

jonathon793commented, Jan 10, 2022

@cartertinney , yes. thank you very much

Top Results From Across the Web

Troubleshooting - SailPoint Product Documentation

Aggregation/ Test Connection fails with the following timeout error: Exception during aggregation of Object Type account on Application <application name> ...

Windows Autopilot known issues - Microsoft Learn

If the device successfully enrolls but doesn't complete provisioning after more than one hour, the device status may not be updated in the ......

Instant clone provisioning fails with vCenter Server connection ...

This issue occurs when the SSL handshake with vCenter Server is timing out. Resolution. To resolve this issue increase the SSL handshake timeout...

Sft ssh failing with timeout on port 4421 - Okta Support

Overview. When trying to sft ssh to Linux servers, the connection times out and show connecting port as 4421: error: rpc error: code...

Fixed issues | Provisioning Services 7.15

Server issues · Server communication time-out. Sometimes, login times can become excessively long (for example, greater than 2 minutes). This ...