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.49k forks source link

Issues with deploying (Quickstart) IoT Edge module to Windows IoT-Core device ..solved #21915

Closed djaus2 closed 5 years ago

djaus2 commented 5 years ago

Step 2 under "View the IoT Edge runtime status" ie If you need to troubleshoot the service, retrieve the service logs. My Install worked but I thought I'd look at the logs. My install then get screwed up by doing that. After install Get-Service iotedge works but after then running Step 2 it says the service isn't running. Looking at the logs it says there was no HostName in the connection string,which isn't correct.

eg

Error 9/01/2019 12:11:15 PM error: iotedged::windows -- Error while running service. Quitting. 9/01/2019 12:11:15 PM error: edgelet_utils::logging -- The daemon could not start up successfully: Could not initialize manual provisioning client 9/01/2019 12:11:15 PM error: edgelet_utils::logging -- caused by: The Connection String is missing required parameter HostName ================== The container host is on supported build version 17763. Downloading Moby Engine... Using Moby Engine from C:\Data\Users\administrator\AppData\Local\Temp\iotedge-moby-engine.zip Downloading Moby CLI... Using Moby CLI from C:\Data\Users\administrator\AppData\Local\Temp\iotedge-moby-cli.zip Downloading IoT Edge security daemon... Using IoT Edge security daemon from C:\Data\Users\administrator\AppData\Local\Temp\iotedged-windows.zip Skipping VC Runtime installation on IoT Core. Generating config.yaml... Configured device for manual provisioning. Configured device with hostname 'minwinpcMax'. Configured device with Moby Engine URL 'npipe://./pipe/iotedge_moby_engine'. Updated system PATH. Added IoT Edge registry key. Initialized the IoT Edge service. This device is now provisioned with the IoT Edge runtime. Check the status of the IoT Edge service with `Get-Service iotedge` List running modules with `iotedge list` Display logs from the last five minutes in chronological order with Get-WinEvent -ea SilentlyContinue -FilterHashtable @{ProviderName='iotedged';LogName='application';StartTime=[datetime]::Now.AddMinutes(-5)} | Select TimeCreated, Message | Sort-Object @{Expression='TimeCreated';Descending=$false} | Format-Table -AutoSize -Wrap [192.168.0.26]: PS C:\Data\Users\administrator\Documents> Get-Service iotedge Status Name DisplayName ------ ---- ----------- Running iotedge iotedge [192.168.0.26]: PS C:\Data\Users\administrator\Documents> # Displays logs from today, newest at the bottom. [192.168.0.26]: PS C:\Data\Users\administrator\Documents> [192.168.0.26]: PS C:\Data\Users\administrator\Documents> Get-WinEvent -ea SilentlyContinue ` >> -FilterHashtable @{ProviderName= "iotedged"; >> LogName = "application"; StartTime = [datetime]::Today} | >> select TimeCreated, Message | >> sort-object @{Expression="TimeCreated";Descending=$false} | >> format-table -autosize -wrap TimeCreated Message ----------- ------- 9/01/2019 12:10:44 PM info: iotedged::app -- Starting Azure IoT Edge Security Daemon 9/01/2019 12:10:44 PM info: iotedged::app -- Version - 1.0.5 (d76e0316c6f324345d77c48a83ce836d09392699) 9/01/2019 12:10:44 PM info: iotedged::app -- Using config file: C:\ProgramData\iotedge\config.yaml 9/01/2019 12:10:44 PM info: iotedged::windows -- Starting iotedged service. 9/01/2019 12:10:44 PM info: iotedged -- Using runtime network id azure-iot-edge 9/01/2019 12:10:44 PM info: iotedged -- Initializing the module runtime... 9/01/2019 12:10:44 PM info: edgelet_docker::runtime -- Initializing module runtime... 9/01/2019 12:10:50 PM info: edgelet_docker::runtime -- Successfully initialized module runtime 9/01/2019 12:10:50 PM info: iotedged -- Configuring C:\ProgramData\iotedge as the home directory. 9/01/2019 12:10:50 PM info: iotedged -- Finished initializing the module runtime. 9/01/2019 12:10:50 PM info: iotedged -- Configuring certificates... 9/01/2019 12:10:50 PM info: iotedged -- Transparent gateway certificates not found, operating in quick start mode... 9/01/2019 12:10:50 PM info: iotedged -- Finished configuring certificates. 9/01/2019 12:10:50 PM info: iotedged -- Initializing hsm... 9/01/2019 12:11:04 PM info: iotedged -- Finished initializing hsm. 9/01/2019 12:11:04 PM info: iotedged -- Detecting if configuration file has changed... 9/01/2019 12:11:04 PM info: iotedged -- Change to configuration file detected. 9/01/2019 12:11:04 PM info: iotedged -- Removing all modules... 9/01/2019 12:11:04 PM info: iotedged -- Finished removing modules. 9/01/2019 12:11:15 PM info: iotedged -- Provisioning edge device... 9/01/2019 12:11:15 PM error: iotedged::windows -- Error while running service. Quitting. 9/01/2019 12:11:15 PM error: edgelet_utils::logging -- The daemon could not start up successfully: Could not initialize manual provisioning client 9/01/2019 12:11:15 PM error: edgelet_utils::logging -- caused by: The Connection String is missing required parameter HostName 9/01/2019 12:11:16 PM info: iotedged::app -- Using config file: C:\ProgramData\iotedge\config.yaml 9/01/2019 12:11:16 PM info: iotedged::app -- Starting Azure IoT Edge Security Daemon 9/01/2019 12:11:16 PM info: iotedged::app -- Version - 1.0.5 (d76e0316c6f324345d77c48a83ce836d09392699) 9/01/2019 12:11:16 PM info: iotedged::windows -- Starting iotedged service. 9/01/2019 12:11:16 PM info: iotedged -- Using runtime network id azure-iot-edge 9/01/2019 12:11:16 PM info: iotedged -- Initializing the module runtime... 9/01/2019 12:11:16 PM info: edgelet_docker::runtime -- Initializing module runtime... 9/01/2019 12:11:16 PM info: edgelet_docker::runtime -- Successfully initialized module runtime 9/01/2019 12:11:16 PM info: iotedged -- Finished initializing the module runtime. 9/01/2019 12:11:16 PM info: iotedged -- Configuring C:\ProgramData\iotedge as the home directory. 9/01/2019 12:11:16 PM info: iotedged -- Configuring certificates... 9/01/2019 12:11:16 PM info: iotedged -- Transparent gateway certificates not found, operating in quick start mode... 9/01/2019 12:11:16 PM info: iotedged -- Finished configuring certificates. 9/01/2019 12:11:16 PM info: iotedged -- Initializing hsm... 9/01/2019 12:11:16 PM info: iotedged -- Finished initializing hsm. 9/01/2019 12:11:16 PM info: iotedged -- Detecting if configuration file has changed... 9/01/2019 12:11:16 PM info: iotedged -- No change to configuration file detected. 9/01/2019 12:11:16 PM info: iotedged -- Obtaining workload CA succeeded. 9/01/2019 12:11:16 PM info: iotedged -- Provisioning edge device... 9/01/2019 12:11:16 PM error: iotedged::windows -- Error while running service. Quitting. 9/01/2019 12:11:16 PM error: edgelet_utils::logging -- The daemon could not start up successfully: Could not initialize manual provisioning client 9/01/2019 12:11:16 PM error: edgelet_utils::logging -- caused by: The Connection String is missing required parameter HostName 9/01/2019 12:11:18 PM info: iotedged::app -- Starting Azure IoT Edge Security Daemon …………………….………. …………………………….. Then .. [192.168.0.26]: PS C:\Data\Users\administrator\Documents> Get-Service iotedge Status Name DisplayName ------ ---- ----------- Stopped iotedge iotedge ---

Document Details

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

djaus2 commented 5 years ago

Silly me: Don't include the quotes

djaus2 commented 5 years ago

I suggest that in the picture showing what to copy don't include the quotes in the rectangle.

djaus2 commented 5 years ago

Now got: [192.168.0.26]: PS C:\Data\Users\administrator\Documents> Get-Service iotedge

Status Name DisplayName

Running iotedge iotedge

djaus2 commented 5 years ago

Not out of the woods yet:

9/01/2019 12:30:35 PM info: iotedged::app -- Starting Azure IoT Edge Security Daemon 9/01/2019 12:30:35 PM info: iotedged::app -- Version - 1.0.5 (d76e0316c6f324345d77c48a83ce836d09392699) 9/01/2019 12:30:35 PM info: iotedged::app -- Using config file: C:\ProgramData\iotedge\config.yaml 9/01/2019 12:30:35 PM info: iotedged::windows -- Starting iotedged service. 9/01/2019 12:30:35 PM info: iotedged -- Using runtime network id azure-iot-edge 9/01/2019 12:30:35 PM info: iotedged -- Initializing the module runtime... 9/01/2019 12:30:35 PM info: edgelet_docker::runtime -- Initializing module runtime... 9/01/2019 12:30:35 PM info: edgelet_docker::runtime -- Successfully initialized module runtime 9/01/2019 12:30:35 PM info: iotedged -- Finished initializing the module runtime. 9/01/2019 12:30:35 PM info: iotedged -- Configuring C:\ProgramData\iotedge as the home directory. 9/01/2019 12:30:35 PM info: iotedged -- Configuring certificates... 9/01/2019 12:30:35 PM info: iotedged -- Finished configuring certificates. 9/01/2019 12:30:35 PM info: iotedged -- Initializing hsm... 9/01/2019 12:30:35 PM info: iotedged -- Finished initializing hsm. 9/01/2019 12:30:35 PM info: iotedged -- Detecting if configuration file has changed... 9/01/2019 12:30:35 PM info: iotedged -- No change to configuration file detected. 9/01/2019 12:30:35 PM info: iotedged -- Obtaining workload CA succeeded. 9/01/2019 12:30:35 PM info: iotedged -- Provisioning edge device... 9/01/2019 12:30:35 PM error: edgelet_utils::logging -- The daemon could not start up successfully: Could not initialize manual provisioning client 9/01/2019 12:30:35 PM error: edgelet_utils::logging -- caused by: The Connection String is missing required parameter HostName 9/01/2019 12:33:21 PM info: iotedged::app -- Using config file: C:\ProgramData\iotedge\config.yaml 9/01/2019 12:33:21 PM info: iotedged::app -- Starting Azure IoT Edge Security Daemon 9/01/2019 12:33:21 PM info: iotedged::app -- Version - 1.0.5 (d76e0316c6f324345d77c48a83ce836d09392699) 9/01/2019 12:33:21 PM info: iotedged::windows -- Starting iotedged service. 9/01/2019 12:33:21 PM info: iotedged -- Using runtime network id azure-iot-edge 9/01/2019 12:33:21 PM info: iotedged -- Initializing the module runtime... 9/01/2019 12:33:21 PM info: edgelet_docker::runtime -- Initializing module runtime... 9/01/2019 12:33:22 PM info: edgelet_docker::runtime -- Successfully initialized module runtime 9/01/2019 12:33:22 PM info: iotedged -- Finished initializing the module runtime. 9/01/2019 12:33:22 PM info: iotedged -- Configuring C:\ProgramData\iotedge as the home directory. 9/01/2019 12:33:22 PM info: iotedged -- Configuring certificates... 9/01/2019 12:33:22 PM info: iotedged -- Transparent gateway certificates not found, operating in quick start mode... 9/01/2019 12:33:22 PM info: iotedged -- Finished configuring certificates. 9/01/2019 12:33:22 PM info: iotedged -- Initializing hsm... 9/01/2019 12:33:36 PM info: iotedged -- Removing all modules... 9/01/2019 12:33:36 PM info: iotedged -- Change to configuration file detected. 9/01/2019 12:33:36 PM info: iotedged -- Finished initializing hsm. 9/01/2019 12:33:36 PM info: iotedged -- Detecting if configuration file has changed... 9/01/2019 12:33:36 PM info: iotedged -- Finished removing modules. 9/01/2019 12:33:41 PM info: iotedged -- Provisioning edge device... 9/01/2019 12:33:41 PM info: provisioning::provisioning -- Manually provisioning device "myEdgeDevice" in hub "myhub137.azure-devices.net" 9/01/2019 12:33:41 PM info: iotedged -- Finished provisioning edge device. 9/01/2019 12:33:41 PM info: iotedged -- Starting management API... 9/01/2019 12:33:41 PM info: iotedged -- Starting workload API... 9/01/2019 12:33:41 PM info: edgelet_core::watchdog -- Starting watchdog with 60 second frequency... 9/01/2019 12:33:41 PM info: iotedged -- Listening on unix:///C:/ProgramData/iotedge/mgmt/sock with 1 thread for management API. 9/01/2019 12:33:41 PM info: iotedged -- Listening on unix:///C:/ProgramData/iotedge/workload/sock with 1 thread for workload API. 9/01/2019 12:33:41 PM info: edgelet_core::watchdog -- Checking edge runtime status 9/01/2019 12:33:41 PM info: edgelet_core::watchdog -- Creating and starting edge runtime module edgeAgent 9/01/2019 12:33:41 PM info: edgelet_core::watchdog -- Updating identity for module $edgeAgent 9/01/2019 12:33:41 PM info: edgelet_docker::runtime -- Pulling image mcr.microsoft.com/azureiotedge-agent:1.0...

iotedge list doesn't show the edge agent running:

[192.168.0.26]: PS C:\Data\Users\administrator\Documents> Get-Service iotedge

Status Name DisplayName

Running iotedge iotedge

[192.168.0.26]: PS C:\Data\Users\administrator\Documents> iotedge list NAME STATUS DESCRIPTION CONFIG

djaus2 commented 5 years ago

Did fresh install . Now: [192.168.0.26]: PS C:\Data\Users\administrator\Documents> iotedge list NAME STATUS DESCRIPTION CONFIG Still no edge agent.

Logs:

[192.168.0.26]: PS C:\Data\Users\administrator\Documents> Get-WinEvent -ea SilentlyContinue -FilterHashtable @{ProviderName='iotedged';LogName='application';StartTime=[datetime]::Now.AddMinutes(-5)} | Select TimeCreated, Message | Sort-Object @{Expression='TimeCreated';Descending=$false} | Format-Table -AutoSize -Wrap

TimeCreated Message

9/01/2019 12:50:54 PM info: iotedged::app -- Starting Azure IoT Edge Security Daemon 9/01/2019 12:50:54 PM info: iotedged::app -- Version - 1.0.5 (d76e0316c6f324345d77c48a83ce836d09392699) 9/01/2019 12:50:54 PM info: iotedged::app -- Using config file: C:\ProgramData\iotedge\config.yaml 9/01/2019 12:50:54 PM info: iotedged::windows -- Starting iotedged service. 9/01/2019 12:50:54 PM info: iotedged -- Using runtime network id azure-iot-edge 9/01/2019 12:50:54 PM info: iotedged -- Initializing the module runtime... 9/01/2019 12:50:54 PM info: edgelet_docker::runtime -- Initializing module runtime... 9/01/2019 12:50:57 PM info: edgelet_docker::runtime -- Successfully initialized module runtime 9/01/2019 12:50:57 PM info: iotedged -- Finished initializing the module runtime. 9/01/2019 12:50:57 PM info: iotedged -- Configuring C:\ProgramData\iotedge as the home directory. 9/01/2019 12:50:57 PM info: iotedged -- Configuring certificates... 9/01/2019 12:50:57 PM info: iotedged -- Transparent gateway certificates not found, operating in quick start mode... 9/01/2019 12:50:57 PM info: iotedged -- Finished configuring certificates. 9/01/2019 12:50:57 PM info: iotedged -- Initializing hsm... 9/01/2019 12:51:13 PM info: iotedged -- Finished initializing hsm. 9/01/2019 12:51:13 PM info: iotedged -- Detecting if configuration file has changed... 9/01/2019 12:51:13 PM info: iotedged -- Change to configuration file detected. 9/01/2019 12:51:13 PM info: iotedged -- Removing all modules... 9/01/2019 12:51:13 PM info: iotedged -- Finished removing modules. 9/01/2019 12:51:22 PM info: iotedged -- Provisioning edge device... 9/01/2019 12:51:22 PM info: provisioning::provisioning -- Manually provisioning device "myEdgeDevice" in hub "myhub137.azure-devices.net" 9/01/2019 12:51:22 PM info: iotedged -- Finished provisioning edge device. 9/01/2019 12:51:22 PM info: iotedged -- Starting management API... 9/01/2019 12:51:22 PM info: iotedged -- Starting workload API... 9/01/2019 12:51:22 PM info: edgelet_core::watchdog -- Starting watchdog with 60 second frequency... 9/01/2019 12:51:22 PM info: iotedged -- Listening on unix:///C:/ProgramData/iotedge/mgmt/sock with 1 thread for management API. 9/01/2019 12:51:22 PM info: iotedged -- Listening on unix:///C:/ProgramData/iotedge/workload/sock with 1 thread for workload API. 9/01/2019 12:51:22 PM info: edgelet_core::watchdog -- Checking edge runtime status 9/01/2019 12:51:22 PM info: edgelet_core::watchdog -- Creating and starting edge runtime module edgeAgent 9/01/2019 12:51:23 PM info: edgelet_core::watchdog -- Updating identity for module $edgeAgent 9/01/2019 12:51:23 PM info: edgelet_docker::runtime -- Pulling image mcr.microsoft.com/azureiotedge-agent:1.0... 9/01/2019 12:52:20 PM info: edgelet_http::logging -- [mgmt] - - - [2019-01-09 01:52:20.188249900 UTC] "GET /modules?api-version=2018-06-28 HTTP/1.1" 200 OK 14 "-" "iotedge/0.1.0" pid(1384)

djaus2 commented 5 years ago

So how do I manually start the edgeagent?

AshokPeddakotla-MSFT commented 5 years ago

@djaus2 Thanks for the feedback! We are currently investigating and will update you shortly.

djaus2 commented 5 years ago

Also in this tutorial it says "If it's a Windows computer, enable the containers feature. In the start bar, navigate to Turn Windows features on or off and check the box next to Containers." How do you do that with Win 10 IOT-Core? Or is it automatically on with IoT-Core? Using a MinnowboardMax in x64 mode. thx

djaus2 commented 5 years ago

Just did a complete re-setup from the top (of this page) and still get no edgeAgent module running.

Another issue, once you perform the first step in "Remove the IoT Edge runtime" docker is removed so the following commands that use docker don't work.

djaus2 commented 5 years ago

Also iotedge restart edgeAgent fails [192.168.0.26]: PS C:> iotedge restart edgeAgent iotedge : A module runtime error occurred

djaus2 commented 5 years ago

We'll get to the bottom of this. Looks like its pulling the image but then it can't use it:

9/01/2019 9:55:29 PM info: edgelet_core::watchdog -- Checking edge runtime status 9/01/2019 9:55:29 PM info: edgelet_core::watchdog -- Creating and starting edge runtime module edgeAgent 9/01/2019 9:55:29 PM info: edgelet_core::watchdog -- Updating identity for module $edgeAgent 9/01/2019 9:55:29 PM info: edgelet_docker::runtime -- Pulling image mcr.microsoft.com/azureiotedge-agent:1.0... 9/01/2019 9:56:44 PM info: edgelet_docker::runtime -- Successfully pulled image mcr.microsoft.com/azureiotedge-agent:1.0 9/01/2019 9:56:44 PM info: edgelet_docker::runtime -- Creating module edgeAgent... 9/01/2019 9:56:44 PM warn: edgelet_utils::logging -- Could not create module edgeAgent 9/01/2019 9:56:44 PM warn: edgelet_utils::logging -- caused by: No such image: mcr.microsoft.com/azureiotedge-agent:1.0

kgremban commented 5 years ago

@djaus2 There's a lot going on in this issue and I'm going to try and address everything you've mentioned, but if I forgot any pieces please let me know.

For unblocking your most recent status update, I've heard from some other users that the current installation bits are buggy on IoT Core. Download https://raw.githubusercontent.com/alextnewman/iotedge/3b87d6805fed1e2bdc74dc6f2d3f45cfea328b3e/scripts/windows/setup/IotEdgeSecurityDaemon.ps1 and save it locally on your machine, then use the --OfflineInstallation flag to point to that file during installation. For more information, see https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-windows#offline-installation. I think that was the solution in the other issue that you were pointed to.

For your comments regarding clarity around the steps in this quickstart, I will update the red box around the connection string to not include the quotation marks. In the step where you're instructed to paste the connection string, it does specify that no quotation marks should be included. If you didn't think that was clear enough, I can try to make that more apparent. For the uninstallation steps, you're correct that the docker commands don't work after uninstalling moby. That's a holdover from our previous version that didn't include the moby runtime, so you had to manually delete the container images from your machine. Now that's taken care of as part of the installation script, so I'll just remove those steps.

djaus2 commented 5 years ago

Still not getting any love out of this. Have tried various combinations. NB --OfflineInstallation is not an option
and --OfflineInstallationPath is for the zip files

djaus2 commented 5 years ago

Got there a little later: 192.168.0.26]: PS C:> iotedge list NAME STATUS DESCRIPTION CONFIG edgeAgent running Up a minute mcr.microsoft.com/azureiotedge-agent:1.0 [192.168.0.26]: PS C:> :)

Had to be patient a let everything spin up. If I did iotedge list after it says it was finished got nothing. But I followed the logs (using the last 5 minutes script as suggested in at end of install) and tracked things, there were updates such as:

11/01/2019 12:30:16 AM info: edgelet_http::logging -- [mgmt] - - - [2019-01-10 13:30:16.840405400 UTC] "GET /modules?api-version=2018-06-28 HTTP/1.1" 200 OK 14 "-" "iotedge/0.1.0" pid(2068) 11/01/2019 12:30:23 AM info: edgelet_docker::runtime -- Successfully pulled image mcr.microsoft.com/azureiotedge-agent:1.0 11/01/2019 12:30:23 AM info: edgelet_docker::runtime -- Creating module edgeAgent... 11/01/2019 12:30:23 AM info: edgelet_docker::runtime -- Successfully created module edgeAgent 11/01/2019 12:30:23 AM info: edgelet_docker::runtime -- Starting module edgeAgent... 11/01/2019 12:30:34 AM info: edgelet_docker::runtime -- Successfully started module edgeAgent 11/01/2019 12:30:34 AM info: edgelet_core::watchdog -- Checking edge runtime status 11/01/2019 12:30:35 AM info: edgelet_core::watchdog -- Edge runtime is running. 11/01/2019 12:30:35 AM info: edgelet_core::watchdog -- Checking edge runtime status 11/01/2019 12:30:35 AM info: edgelet_core::watchdog -- Edge runtime is running. 11/01/2019 12:30:35 AM info: edgelet_core::watchdog -- Checking edge runtime status 11/01/2019 12:30:35 AM info: edgelet_core::watchdog -- Edge runtime is running. 11/01/2019 12:30:35 AM info: edgelet_core::watchdog -- Checking edge runtime status 11/01/2019 12:30:35 AM info: edgelet_core::watchdog -- Edge runtime is running. 11/01/2019 12:30:52 AM info: edgelet_http::logging -- [work] - - - [2019-01-10 13:30:52.368344200 UTC] "POST /modules/%24edgeAgent/genid/636826297145554933/sign?api-version=2018-06-28 HTTP/1.1" 200 OK 57 "-" "-" pid(1340) 11/01/2019 12:30:52 AM info: edgelet_docker::runtime -- Querying system info... 11/01/2019 12:30:52 AM info: edgelet_docker::runtime -- Successfully queried system info 11/01/2019 12:30:52 AM info: edgelet_http::logging -- [mgmt] - - - [2019-01-10 13:30:52.913101500 UTC] "GET /systeminfo?api-version=2018-06-28 HTTP/1.1" 200 OK 105 "-" "-" pid(1340) 11/01/2019 12:30:53 AM info: edgelet_http::logging -- [mgmt] - - - [2019-01-10 13:30:53.682280100 UTC] "GET /modules?api-version=2018-06-28 HTTP/1.1" 200 OK 446 "-" "-" pid(1340) 11/01/2019 12:31:01 AM info: edgelet_http::logging -- [mgmt] - - - [2019-01-10 13:31:01.406089100 UTC] "GET /modules?api-version=2018-06-28 HTTP/1.1" 200 OK 446 "-" "-" pid(1340) 11/01/2019 12:31:06 AM info: edgelet_http::logging -- [mgmt] - - - [2019-01-10 13:31:06.451893700 UTC] "GET /modules?api-version=2018-06-28 HTTP/1.1" 200 OK 446 "-" "-" pid(1340) 11/01/2019 12:31:08 AM info: edgelet_core::watchdog -- Checking edge runtime status 11/01/2019 12:31:08 AM info: edgelet_core::watchdog -- Edge runtime is running. 11/01/2019 12:31:11 AM info: edgelet_http::logging -- [mgmt] - - - [2019-01-10 13:31:11.526429800 UTC] "GET /modules?api-version=2018-06-28 HTTP/1.1" 200 OK 446 "-" "-" pid(1340) 11/01/2019 12:31:16 AM info: edgelet_http::logging -- [mgmt] - - - [2019-01-10 13:31:16.570070 UTC] "GET /modules?api-version=2018-06-28 HTTP/1.1" 200 OK 446 "-" "-" pid(1340) 11/01/2019 12:31:21 AM info: edgelet_http::logging -- [mgmt] - - - [2019-01-10 13:31:21.663869300 UTC] "GET /modules?api-version=2018-06-28 HTTP/1.1" 200 OK 446 "-" "-" pid(1340) 11/01/2019 12:31:26 AM info: edgelet_http::logging -- [mgmt] - - - [2019-01-10 13:31:26.702851200 UTC] "GET /modules?api-version=2018-06-28 HTTP/1.1" 200 OK 446 "-" "-" pid(1340) 11/01/2019 12:31:31 AM info: edgelet_http::logging -- [mgmt] - - - [2019-01-10 13:31:31.750583900 UTC] "GET /modules?api-version=2018-06-28 HTTP/1.1" 200 OK 446 "-" "-" pid(1340) 11/01/2019 12:31:36 AM info: edgelet_http::logging -- [mgmt] - - - [2019-01-10 13:31:36.794530600 UTC] "GET /modules?api-version=2018-06-28 HTTP/1.1" 200 OK 446 "-" "-" pid(1340)

Nb My PowerShell command was:

"C:\iotedge\IotEdgeSecurityDaemon.ps1" | Invoke-Expression; Install-SecurityDaemon -Manual -ContainerOs Windows

djaus2 commented 5 years ago

Also another NB: The downloaded script worked without any editing.

djaus2 commented 5 years ago

Kelly Thanks for your help.

Sent from my Windows 10 device

From: Kelly Gremban notifications@github.com Sent: Thursday, January 10, 2019 7:27:23 AM To: MicrosoftDocs/azure-docs Cc: David Jones; Mention Subject: Re: [MicrosoftDocs/azure-docs] Check on logs mucks up iotedge service (#21915)

@djaus2https://github.com/djaus2 There's a lot going on in this issue and I'm going to try and address everything you've mentioned, but if I forgot any pieces please let me know.

For unblocking your most recent status update, I've heard from some other users that the current installation bits are buggy on IoT Core. Download https://raw.githubusercontent.com/alextnewman/iotedge/3b87d6805fed1e2bdc74dc6f2d3f45cfea328b3e/scripts/windows/setup/IotEdgeSecurityDaemon.ps1 and save it locally on your machine, then use the --OfflineInstallation flag to point to that file during installation. For more information, see https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-windows#offline-installation. I think that was the solution in the other issue that you were pointed to.

For your comments regarding clarity around the steps in this quickstart, I will update the red box around the connection string to not include the quotation marks. In the step where you're instructed to paste the connection string, it does specify that no quotation marks should be included. If you didn't think that was clear enough, I can try to make that more apparent. For the uninstallation steps, you're correct that the docker commands don't work after uninstalling moby. That's a holdover from our previous version that didn't include the moby runtime, so you had to manually delete the container images from your machine. Now that's taken care of as part of the installation script, so I'll just remove those steps.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/21915#issuecomment-452823782, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AL9NEapbmjVASiwHXCSYYikX5gMeAAdhks5vBlCqgaJpZM4Z2ljK.

djaus2 commented 5 years ago

So the upshots are:

kgremban commented 5 years ago

@djaus2 I updated the quickstarts this morning and attempted to address your feedback about not realizing that after the installation is complete it still takes a while for the service to start up, with the new line:

It may take a few minutes for the installation to complete and the IoT Edge agent module to start, especially if you are using a device with limited capacity or internet access.

As for the installation issues on IoT Core, I'm not going to document those steps because that's a product bug that should be resolved soon.

Is there anything else that I can do from a documentation standpoint, or is this issue resolved?

djaus2 commented 5 years ago

Ok done, thx

asergaz commented 5 years ago

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.