This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(294.40000000000003, 3%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDP%3C/text%3E%3C/svg%3E)
OOBE failed with a timeout the first try, but managed to get the Percept running after a second try. However, the WebStreamModule will not start and the logs show the following:
<4> 2021-06-17 06:55:46.031 +00:00 [WRN] - Reconcile failed because of the an exception
System.AggregateException: One or more errors occurred. (Error calling Create module WebStreamModule: Could not create module WebStreamModule
caused by: Could not create module WebStreamModule
caused by: error creating overlay mount to /var/lib/docker/overlay2/e19952fd6555d43e61e2bcb0404a4ec7d3d8fb972f33c507a735796645055550-init/merged: too many levels of symbolic links)
---> Microsoft.Azure.Devices.Edge.Agent.Edgelet.EdgeletCommunicationException- Message:Error calling Create module WebStreamModule: Could not create module WebStreamModule
caused by: Could not create module WebStreamModule
caused by: error creating overlay mount to /var/lib/docker/overlay2/e19952fd6555d43e61e2bcb0404a4ec7d3d8fb972f33c507a735796645055550-init/merged: too many levels of symbolic links, StatusCode:500, at: at Microsoft.Azure.Devices.Edge.Agent.Edgelet.Version_2020_07_07.ModuleManagementHttpClient.HandleException(Exception exception, String operation) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Edgelet/version_2020_07_07/ModuleManagementHttpClient.cs:line 232
at Microsoft.Azure.Devices.Edge.Agent.Edgelet.Versioning.ModuleManagementHttpClientVersioned.Execute[T](Func`1 func, String operation) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Edgelet/versioning/ModuleManagementHttpClientVersioned.cs:line 146
at Microsoft.Azure.Devices.Edge.Agent.Edgelet.Version_2020_07_07.ModuleManagementHttpClient.CreateModuleAsync(ModuleSpec moduleSpec) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Edgelet/version_2020_07_07/ModuleManagementHttpClient.cs:line 100
at Microsoft.Azure.Devices.Edge.Agent.Core.LoggingCommandFactory.LoggingCommand.ExecuteAsync(CancellationToken token) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Core/LoggingCommandFactory.cs:line 67
at Microsoft.Azure.Devices.Edge.Agent.Core.Commands.GroupCommand.ExecuteAsync(CancellationToken token) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Core/commands/GroupCommand.cs:line 35
at Microsoft.Azure.Devices.Edge.Agent.Core.LoggingCommandFactory.LoggingCommand.ExecuteAsync(CancellationToken token) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Core/LoggingCommandFactory.cs:line 67
at Microsoft.Azure.Devices.Edge.Agent.Core.PlanRunners.OrderedRetryPlanRunner.ExecuteAsync(Int64 deploymentId, Plan plan, CancellationToken token) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Core/planrunners/OrdererdRetryPlanRunner.cs:line 83
--- End of inner exception stack trace ---
at Microsoft.Azure.Devices.Edge.Agent.Core.PlanRunners.OrderedRetryPlanRunner.<>c.<ExecuteAsync>b__7_0(List`1 f) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Core/planrunners/OrdererdRetryPlanRunner.cs:line 115
at Microsoft.Azure.Devices.Edge.Agent.Core.PlanRunners.OrderedRetryPlanRunner.ExecuteAsync(Int64 deploymentId, Plan plan, CancellationToken token) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Core/planrunners/OrdererdRetryPlanRunner.cs:line 115
at Microsoft.Azure.Devices.Edge.Agent.Core.Agent.ReconcileAsync(CancellationToken token) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Core/Agent.cs:line 203
at Microsoft.Azure.Devices.Edge.Agent.Core.Agent.ReconcileAsync(CancellationToken token) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Core/Agent.cs:line 203
@David Packman sorry to hear that. Just making sure you are following the steps here and got stuck on "View your dev kit video stream and deploy a sample model" ?
https://learn.microsoft.com/en-us/azure/azure-percept/quickstart-percept-dk-set-up#view-your-dev-kit-video-stream-and-deploy-a-sample-model
Also can you confirm if you are owning a Private Preview Kit and you did update to the latest software as explained here?
https://github.com/microsoft/Azure-Percept-Private-Preview/blob/main/update-your-devkit-today/private-preview-update-instructions.md
Thanks!
Yes, I followed the steps from the whole article, including that subsection.
No, this is not a private preview kit and I already deployed an OTA update with the latest version for the device.
Thanks for asking!
![](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(92.8, 22%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
@David Packman - I am investigating this and will let you know if I have any other questions along the way. Thanks.
Thank you for looking into it and for the update! It's fine if the final recommendation is just to reset the device to factory settings, I haven't been able to really do anything with it yet other than set it up for OTA update. :)
Just checking to see if you found anything out or if I should try resetting the device to factory settings, if that's possible?
...is it possible? :)
Thanks!
@David Packman sorry for the delay here. There is a way to reset the device by USB flashing it. You can find those instructions at https://learn.microsoft.com/en-us/azure/azure-percept/how-to-update-via-usb
Thanks!
I'll go with that and see if I can get through the setup that way. Thanks!
Hi @David Packman , sorry for the delayed response. This issue is still being investigated by the product team but we have yet to figure out a root cause. As @António Sérgio Azevedo mentioned the only know work around is to re-flash the device over USB.
If you haven't flashed the device yet, perhaps you could grab a few more logs?
SSH into the device and run:
If you're able to get them, send them to me at [hidden]
Sorry, I had already flashed the device and it's working great now. Thanks!
Glad to hear you are now able to use Azure Percept and follow the great tutorials out there :). Thank you so much for all your time!
Remember: