search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.31k stars 21.5k forks source link

Device Sim Error? #29161

Closed Rob-Otics closed 5 years ago

Rob-Otics commented 5 years ago

I've been trying to deploy locally for a few days now following this guide but have had very little luck, whilst the services start in visual studio fine I have the following errors on the webservices:

DeviceTelemtry: Diagnostics IsHealthy false Message "Status code: 0; Response: An error occurred while sending the request. - A connection with the server could not be established"

ASAManager:Config
IsHealthy false Message "DeviceSimulation check failed"

Config: DeviceSimulation
IsHealthy false Message "ERROR:Unable to use Storage"

The device sim start up using docker has had a few errors that I've managed to rectify but is still reporting the following:

devicesimulation_1 | [ERROR][2019-04-10 14:14:36.151][WebService.8955e47b-82f3-4f18-8085-a1c323102c29][AuthMiddleware:InitializeTokenValidationAsync] Failed to setup OpenId Connect, {"e":{"ExceptionFullName":"System.InvalidOperationException","ExceptionMessage":"IDX10803: Unable to obtain configuration from: '.well-known/openid-configuration'.","StackTrace":" at Microsoft.IdentityModel.Protocols.ConfigurationManager1.&lt;GetConfigurationAsync&gt;d__24.MoveNext()\n--- End of stack trace from previous location where exception was thrown ---\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\n at Microsoft.Azure.IoTSolutions.DeviceSimulation.WebService.Auth.AuthMiddleware.&lt;InitializeTokenValidationAsync&gt;d__15.MoveNext() in /home/azureiotpcs/vsts-agent/_work/46/s/WebService/Auth/AuthMiddleware.cs:line 204","Source":"Microsoft.IdentityModel.Protocols","Data":{},"InnerException":{"ExceptionFullName":"System.ArgumentException","ExceptionMessage":"IDX10108: The address specified is not valid as per HTTPS scheme. Please specify an https address for security reasons. If you want to test with http address, set the RequireHttps property on IDocumentRetriever to false.\nParameter name: .well-known/openid-configuration","StackTrace":" at Microsoft.IdentityModel.Protocols.HttpDocumentRetriever.&lt;GetDocumentAsync&gt;d__8.MoveNext()\n--- End of stack trace from previous location where exception was thrown ---\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\n at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1.ConfiguredTaskAwaiter.GetResult()\n at Microsoft.IdentityModel.Protocols.OpenIdConnect.OpenIdConnectConfigurationRetriever.<GetAsync>d3.MoveNext()\n--- End of stack trace from previous location where exception was thrown ---\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\n at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1.ConfiguredTaskAwaiter.GetResult()\n at Microsoft.IdentityModel.Protocols.ConfigurationManager1.<GetConfigurationAsync>d24.MoveNext()","Source":"Microsoft.IdentityModel.Protocols","Data":{},"InnerException":null}}}The devicesimulation service gives the following error when using "docker-compose up",

it also appears to be ignoring the env-vars set in both device and docker-compose.yml

any help would be appreciated.

Document details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Alberto-Vega commented 5 years ago

@Rob-amrc Would you please open an issue on the repository for the sample code? https://github.com/Azure/azure-iot-pcs-remote-monitoring-dotnet/issues

Rob-Otics commented 5 years ago

@Alberto-Vega-MSFT I've opened an issue as requested.

Thanks.

Alberto-Vega commented 5 years ago

Thanks, I see your issue on their repo https://github.com/Azure/azure-iot-pcs-remote-monitoring-dotnet/issues/159 We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.