Closed smcd253 closed 6 years ago
asergaz
commented
6 years ago @smcd253 thank you for your feedback. Can you please specify the doc that your are following? Will it be this one? https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-linux-arm
smcd253
commented
6 years ago @sergaz-msft that's the one! apologies for not referencing it earlier
asergaz
commented
6 years ago Thanks for confirming no worries :). What version of Linux are you using? Please note the supported platforms here.
smcd253
commented
6 years ago I'm running Raspbian-stretch Kernel 4.14
veyalla
commented
6 years ago @smcd253 Presume you have updated the connection string in the config.yaml?
If yes, what is the output of journalctl -u iotedge --no-pager --no-full
smcd253
commented
6 years ago @veyalla I will let you know as soon as I get home tonight. Don't have my rPi at work with me.
manchejs0
commented
6 years ago I'm having the same issue.
@veyalla I can give you what my output is:
"iotedge.service: Main process exited, code=existed, status=127/n/a iotedge.service: Unit entered failed state. iotedge.service: Failed with result 'exit-code'. iotedge.service: service hold-of time over, scheduling restart. Stopped Azure IoT Edge daemon. iotedge.service: Start request repeated too quickly. Failed to start Azure IoT Edge daemon."
veyalla
commented
6 years ago @manchejs0 Is this the full output of journalctl -u iotedge --no-pager --no-full?
manchejs0
commented
6 years ago @veyalla Yes
manchejs0
commented
6 years ago @veyalla well, to be specific it also says in the first line that it Started Azure IoT Edge daemon, but nothing else
veyalla
commented
6 years ago @manchejs0 what about journalctl -u iotedge (SHIFT+G will scroll to the bottom)?
manchejs0
commented
6 years ago @veyalla
Same stuff. I'm sorry, but I notice the OP is running Raspbian, whereas I'm having this issue on Ubuntu 16.04 (still arm architecture, as it is also a Raspberry Pi)
veyalla
commented
6 years ago I see good to know. What is the output of systemctl status docker?
manchejs0
commented
6 years ago @veyalla Looks fine, but there is this:
"level=warning msg="Your kernel does not support cgroup rt runtime" level=warning msg="Unable to find cpuset cgroup in mounts" "level=warning msg="mountpoint for pids not found"
veyalla
commented
6 years ago @manchejs0 We don't officially support Ubuntu on ARM, so this has not been tested on our end. @myagley Any idea?
smcd253
commented
6 years ago @veyalla here's my output after running journalctl -u iotedge --no-pager --no-full
Jul 01 21:17:19 spencerpi iotedged[1206]: 2018-07-02T04:17:19Z [INFO] - Starting Azure IoT Edge Security Daemon Jul 01 21:17:19 spencerpi iotedged[1206]: 2018-07-02T04:17:19Z [INFO] - Version - 1.0.0 (52ef77db24126bf473265fc…a2dd6b)Jul 01 21:17:19 spencerpi iotedged[1206]: 2018-07-02T04:17:19Z [INFO] - Using config file: /etc/iotedge/config.yaml Jul 01 21:17:19 spencerpi iotedged[1206]: 2018-07-02T04:17:19Z [INFO] - Using runtime network id azure-iot-edge Jul 01 21:17:19 spencerpi iotedged[1206]: 2018-07-02T04:17:19Z [INFO] - Initializing the module runtime... Jul 01 21:17:19 spencerpi iotedged[1206]: 2018-07-02T04:17:19Z [INFO] - Finished initializing the module runtime. Jul 01 21:17:19 spencerpi iotedged[1206]: 2018-07-02T04:17:19Z [INFO] - Configuring /var/lib/iotedge as the home…ectory.Jul 01 21:17:19 spencerpi iotedged[1206]: 2018-07-02T04:17:19Z [INFO] - Configuring certificates... Jul 01 21:17:19 spencerpi iotedged[1206]: 2018-07-02T04:17:19Z [INFO] - Transparent gateway certificates not fou…mode...Jul 01 21:17:19 spencerpi iotedged[1206]: 2018-07-02T04:17:19Z [INFO] - Finished configuring certificates. Jul 01 21:17:19 spencerpi iotedged[1206]: 2018-07-02T04:17:19Z [INFO] - Initializing hsm... Jul 01 21:17:19 spencerpi iotedged[1206]: 2018-07-02T04:17:19Z [INFO] - Finished initializing hsm. Jul 01 21:17:19 spencerpi iotedged[1206]: 2018-07-02T04:17:19Z [INFO] - Detecting if configuration file has changed... Jul 01 21:17:19 spencerpi iotedged[1206]: 2018-07-02T04:17:19Z [INFO] - No change to configuration file detected. Jul 01 21:17:19 spencerpi iotedged[1206]: 2018-07-02T04:17:19Z [INFO] - Provisioning edge device... Jul 01 21:17:19 spencerpi iotedged[1206]: 2018-07-02T04:17:19Z [ERR!] - A provisioning error occurred. Jul 01 21:17:19 spencerpi systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE Jul 01 21:17:19 spencerpi systemd[1]: iotedge.service: Unit entered failed state. Jul 01 21:17:19 spencerpi systemd[1]: iotedge.service: Failed with result 'exit-code'. Jul 01 21:17:20 spencerpi systemd[1]: iotedge.service: Service hold-off time over, scheduling restart. Jul 01 21:17:20 spencerpi systemd[1]: Stopped Azure IoT Edge daemon. Jul 01 21:17:20 spencerpi systemd[1]: iotedge.service: Start request repeated too quickly. Jul 01 21:17:20 spencerpi systemd[1]: Failed to start Azure IoT Edge daemon. Jul 01 21:17:20 spencerpi systemd[1]: iotedge.service: Unit entered failed state. Jul 01 21:17:20 spencerpi systemd[1]: iotedge.service: Failed with result 'exit-code'.
my config.yaml provisioning section is set up as follows:
provisioning:
source: "manual"
device_connection_string: "<HostName=SMcD-rPiHub.azure-devices.net;DeviceId=rPiEdge;SharedAccessKey=\<key-value>\=>"
with two spaces as the indent for source: and device_connection_string:
I copied the connection string directly from my IoTHub portal for device rPiEdge
veyalla
commented
6 years ago @smcd253 The issue is the angle braces in your connection string. Please remove the < and > from the string.
Also, treat the connection string as a password and do not share publicly. I suggest you delete the device after you confirm it is working.
smcd253
commented
6 years ago @veyalla sounds good. I regenerated the key.
deleting the angle braces from the connection string did not work. I'm getting the same output for
journalctl -u iotedge --no-pager --no-full
as above
veyalla
commented
6 years ago Presume you restarted the service after updating config.yaml? sudo systemctl restart iotedge
smcd253
commented
6 years ago I did not.
But it looks like that worked!
However, I just got the following error:
Jul 02 21:16:10 spencerpi iotedged[12899]: 2018-07-03T04:16:10Z [WARN] - Error in watchdog when checking for edge runtime status: Jul 02 21:16:10 spencerpi iotedged[12899]: 2018-07-03T04:16:10Z [WARN] - Identity error Jul 02 21:16:10 spencerpi iotedged[12899]: 2018-07-03T04:16:10Z [WARN] - caused by: IoT Hub service error Jul 02 21:16:10 spencerpi iotedged[12899]: 2018-07-03T04:16:10Z [WARN] - caused by: Core error Jul 02 21:16:10 spencerpi iotedged[12899]: 2018-07-03T04:16:10Z [WARN] - caused by: Service error: [401 Unauthorized] {"Message":"ErrorCode:IotHubUnauthorizedAccess;Unauthorized","ExceptionMessage":"Tracking ID:04a19ea6f6e8424b915e2dac10be80b3-G:6-TimeStamp:07/03/2018 04:16:10"}
Shall I open up a new issue for this?
veyalla
commented
6 years ago @smcd253 Perhaps the regenerated key is tripping things up. Can you start a with a fresh device to rule that out?
smcd253
commented
6 years ago @veyalla sure, created a new device, ran restart, and here's the output of journalctl (among the service 401 error messages and what not):
Jul 02 21:10:28 spencerpi systemd[1]: Stopping Azure IoT Edge daemon... Jul 02 21:10:28 spencerpi iotedged[11662]: 2018-07-03T04:10:28Z [INFO] - Received SIGTERM, starting shutdown Jul 02 21:10:28 spencerpi iotedged[11662]: 2018-07-03T04:10:28Z [INFO] - Stopping edge runtime module edgeAgent Jul 02 21:10:28 spencerpi iotedged[11662]: 2018-07-03T04:10:28Z [WARN] - Container not found Jul 02 21:10:28 spencerpi iotedged[11662]: 2018-07-03T04:10:28Z [ERR!] - Edgelet core error Jul 02 21:10:28 spencerpi systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE Jul 02 21:10:28 spencerpi systemd[1]: Stopped Azure IoT Edge daemon. Jul 02 21:10:28 spencerpi systemd[1]: iotedge.service: Unit entered failed state. Jul 02 21:10:28 spencerpi systemd[1]: iotedge.service: Failed with result 'exit-code'. Jul 02 21:10:28 spencerpi systemd[1]: Started Azure IoT Edge daemon.
Edgelet core error seems to be new
veyalla
commented
6 years ago Yeah, we'll need to look into that. For now, please try:
sudo systemctl stop iotedge
docker rm -f $(docker ps -aq)
sudo systemctl start iotedge
thorpebt
commented
6 years ago Hi, this may or may not add to the conversation. I was having the same issue to start so I disabled restart on failure. Now I'm getting an error about missing libssl.so.1.0.2. My pi has Openssl 1.1 installed, but iotedge doesn't seem to support this. You might see if you have the same results.
pi:~ $ sudo systemctl cat iotedge.service
# /lib/systemd/system/iotedge.service
[Unit]
Description=Azure IoT Edge daemon
After=network-online.target iotedge.socket iotedge.mgmt.socket
Requires=network-online.target iotedge.socket iotedge.mgmt.socket
Documentation=man:iotedged(8)
[Service]
ExecStart=/usr/bin/iotedged -c /etc/iotedge/config.yaml
KillMode=process
TimeoutStartSec=600
TimeoutStopSec=40
#Restart=on-failure
User=iotedge
Group=iotedge
[Install]
WantedBy=multi-user.target
Also=iotedge.socket iotedge.mgmt.socket
pi:~ $ sudo systemctl daemon-reload
pi:~ $ sudo systemctl restart iotedge
pi:~ $ sudo systemctl status iotedge
● iotedge.service - Azure IoT Edge daemon
Loaded: loaded (/lib/systemd/system/iotedge.service; enabled)
Active: failed (Result: exit-code) since Tue 2018-07-03 13:27:47 EDT; 1s ago
Docs: man:iotedged(8)
Process: 16540 ExecStart=/usr/bin/iotedged -c /etc/iotedge/config.yaml (code=exited, status=127)
Main PID: 16540 (code=exited, status=127)
Jul 03 13:27:47 PATH-RPi-MosquittoSRV systemd[1]: Started Azure IoT Edge daemon.
Jul 03 13:27:47 PATH-RPi-MosquittoSRV iotedged[16540]: /usr/bin/iotedged: error while loading shared libraries: libssl.so.1.0.2: cannot open shared object file: No such file or directory
Jul 03 13:27:47 PATH-RPi-MosquittoSRV systemd[1]: iotedge.service: main process exited, code=exited, status=127/n/a
Jul 03 13:27:47 PATH-RPi-MosquittoSRV systemd[1]: Unit iotedge.service entered failed state.@thorpebt Are you running Raspbian-stretch on your Pi?
thorpebt
commented
6 years ago @veyalla Yes, it was jesse upgraded to stretch.
veyalla
commented
6 years ago @thorpebt Since you upgraded to stretch, can you try:
sudo apt-get update
sudo apt-get upgradeAdding @darobs @damonbarry for some suggestions if that doesn't work.
thorpebt
commented
6 years ago @veyalla Tried both, I'm not sure there's a repository available for Openssl 1.0.2 for Raspbian. It exists in the Jesse-backports for ARMv7, but not ARM6 for which Raspbian is compiled. [Source is a slightly dated stackexchange post: https://raspberrypi.stackexchange.com/questions/66782/how-to-install-openssl-1-0-2-on-raspberry-pi3/66788] I have yet to successfully build it on Raspbian-stretch.
darobs
commented
6 years ago Hello @thorpebt,
If you are using the Raspbian stretch repository, there is a libssl1.0.2 package you can install.
I had thought that (by default) once you had done the apt-get upgrade, it would have installed libssl1.0.2 as a part of updating opensll1.0. I have underestimated the annoyance of upgrading a distribution.
On my Pi (installed as a new system from Stretch),
$ cat /etc/apt/sources.list
deb http://raspbian.raspberrypi.org/raspbian/ stretch main contrib non-free rpi
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://raspbian.raspberrypi.org/raspbian/ stretch main contrib non-free rpi
$ dpkg --status libssl1.0.2
Package: libssl1.0.2
Status: install ok installed
[…]So, you should be able to install libssl1.0.2 by running sudo apt-get install libssl1.0.2.
smcd253
commented
6 years ago FIXED IT!
I was running Docker CE and, given the instructions, thought it'd be fine to skip on the Moby-based engine for now. Turns out this was not the case.
I completely re-flashed my device and installed the moby-based container and now it all works great.
Christian Pop from the client sdk team helped me figure this out.
asergaz
commented
6 years ago @smcd253 glad that you finally made it through :)!
I was running Docker CE and, given the instructions, thought it'd be fine to skip on the Moby-based engine for now. Turns out this was not the case.
I understand that the walkthrough leads to that assumption (no need to have Moby-based engine on non-production environments). @kgremban can we add a note on the document that in some scenarios Moby-based engine needs to be installed? @veyalla if you believe that is not the case let us know.
@CIPop thank you for helping here :).
@thorpebt I am about to close this issue. If you are still having issues can you open a new one?
Thank you all!
veyalla
commented
6 years ago I don't believe this is a Moby vs Docker issue. I think the system got into some bad state because of all the different things we tried. We can close for now and can re-visit if there are more reports of Docker not working.
asergaz
commented
6 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.
thorpebt
commented
6 years ago @darobs @sergaz-msft I apologize for the delay, we were off yesterday in the USA and apparently I've hijacked this thread because my issue appears to be unrelated.
Raspbian did not find a repository for libssl1.0.2 so I flashed a fresh build of stretch instead of upgrading. It's now working fine.
Shachar1
commented
6 years ago Hi, @sergaz-msft, @veyalla I'm having the same problem -
iotedge.service - Azure IoT Edge daemon Loaded: loaded (/lib/systemd/system/iotedge.service; enabled) Active: failed (Result: start-limit) since Wed 2018-07-11 07:18:30 UTC; 4s ago Docs: man:iotedged(8) Process: 30178 ExecStart=/usr/bin/iotedged -c /etc/iotedge/config.yaml (code=exited, status=127) Main PID: 30178 (code=exited, status=127)
I've used this link - https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-linux-arm
I've installed Moby-Engine.
Changed the connection string in the config.yaml
sudo systemctl restart iotedge
running journalctl -u iotedge --no-pager --no-full: No journal files were found.
sudo iotedge list: An error in the management http client occurred. caused by: Hyper error caused by: Connection reset by peer (os error 104)
journalctl -u iotedge: No journal files were found.
systemctl status docker: docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled) Active: active (running) since Tue 2018-07-10 06:34:23 UTC; 24h ago Docs: https://docs.docker.com Main PID: 22741 (dockerd) CGroup: /system.slice/docker.service ├─22741 /usr/bin/dockerd -H fd:// └─22749 docker-containerd --config /var/run/docker/containerd/containerd.toml
I've also tried to create a new IoT edge device and do the process again.
Kernel Version - Linux dex 4.4.38-v7+
Thanks
asergaz
commented
6 years ago @Shachar1 your issue is slight different than the initial reported one. Can you create a new issue to start fresh? You can reference this one on the newly created issue.
Thank you!
scottjreece
commented
6 years ago Hello, I'm having the same issue with libssl.so.1.0.2 missing on a Moxa ARM device. Is there a solution to this besides wiping the device? It's running Debian GNU/Linux 8 (jessie)
Thanks!
veyalla
commented
6 years ago Adding @darobs if he has any suggestions.
darobs
commented
6 years ago Hello @scottjreece,
Sorry, we don't have a package release that will support jessie.
We might be able to find workarounds for some of the issues you'll encounter, but this isn't the best thread to work all that out. If you would like to pursue this further, please create an issue on the IoT Edge Github page.
sympthom
commented
6 years ago I've experiencing the same problem, the Azure IoT Edge demon doesn't start. Here is the output:
ubuntu@gateway:~$ sudo iotedge list An error in the management http client occurred. caused by: Hyper error caused by: Connection refused (os error 111)
ubuntu@gateway:~$ sudo systemctl status iotedge
● iotedge.service - Azure IoT Edge daemon Loaded: loaded (/lib/systemd/system/iotedge.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Sat 2018-07-28 12:57:53 UTC; 3min 23s ago Docs: man:iotedged(8) Process: 27665 ExecStart=/usr/bin/iotedged -c /etc/iotedge/config.yaml (code=exited, status=127) Main PID: 27665 (code=exited, status=127)
Jul 28 12:57:53 gateway systemd[1]: iotedge.service: Unit entered failed state. Jul 28 12:57:53 gateway systemd[1]: iotedge.service: Failed with result 'exit-code'. Jul 28 12:57:53 gateway systemd[1]: iotedge.service: Service hold-off time over, scheduling restart. Jul 28 12:57:53 gateway systemd[1]: Stopped Azure IoT Edge daemon. Jul 28 12:57:53 gateway systemd[1]: iotedge.service: Start request repeated too quickly. Jul 28 12:57:53 gateway systemd[1]: Failed to start Azure IoT Edge daemon.
ubuntu@gateway:~$ sudo systemctl cat iotedge.service
[Unit] Description=Azure IoT Edge daemon After=network-online.target iotedge.socket iotedge.mgmt.socket Requires=network-online.target iotedge.socket iotedge.mgmt.socket Documentation=man:iotedged(8)
[Service] ExecStart=/usr/bin/iotedged -c /etc/iotedge/config.yaml KillMode=process TimeoutStartSec=600 TimeoutStopSec=40 Restart=on-failure User=iotedge Group=iotedge
[Install] WantedBy=multi-user.target Also=iotedge.socket iotedge.mgmt.socket ubuntu@gateway:~$
JaimeB1793
commented
6 years ago Hello all,
I´m completelly new in the world of IoT and was trying to get involved with Azure Edge. following the tutorial (https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-linux-arm) I get the error shown:
$ systemctl status iotedge ● iotedge.service - Azure IoT Edge daemon Loaded: loaded (/lib/systemd/system/iotedge.service; enabled) Active: failed (Result: start-limit) since Fri 2018-09-14 13:32:04 UTC; 39s ago Docs: man:iotedged(8) Process: 6932 ExecStart=/usr/bin/iotedged -c /etc/iotedge/config.yaml (code=exited, status=127) Main PID: 6932 (code=exited, status=127)
I'm running in a raspberry Pi 3:
armv71 PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)" NAME="Raspbian GNU/Linux" VERSION_ID="8" VERSION="8 (jessie)"
asergaz
commented
6 years ago @JaimeB1793 thank you for your feedback! As @darobs mentioned we don't have a package release that will support jessie. Please create an issue on the IoT Edge Github page.
Thanks a lot.
nitinjain999
commented
6 years ago Oct 09 16:53:15 Pi1 iotedged[1820]: 2018-10-09T14:53:15Z [INFO] - Initializing hsm... Oct 09 16:53:15 Pi1 iotedged[1820]: 2018-10-09T14:53:15Z [INFO] - Finished initializing hsm. Oct 09 16:53:15 Pi1 iotedged[1820]: 2018-10-09T14:53:15Z [INFO] - Detecting if configuration file has changed... Oct 09 16:53:15 Pi1 iotedged[1820]: 2018-10-09T14:53:15Z [INFO] - No change to configuration file detected. Oct 09 16:53:15 Pi1 iotedged[1820]: 2018-10-09T14:53:15Z [INFO] - Obtaining workload CA succeeded. Oct 09 16:53:15 Pi1 iotedged[1820]: 2018-10-09T14:53:15Z [INFO] - Provisioning edge device... Oct 09 16:53:15 Pi1 systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE Oct 09 16:53:15 Pi1 systemd[1]: iotedge.service: Unit entered failed state. Oct 09 16:53:15 Pi1 systemd[1]: iotedge.service: Failed with result 'exit-code'. Oct 09 16:53:15 Pi1 systemd[1]: iotedge.service: Service hold-off time over, scheduling restart. Oct 09 16:53:15 Pi1 systemd[1]: Stopped Azure IoT Edge daemon. Oct 09 16:53:15 Pi1 systemd[1]: Started Azure IoT Edge daemon. Oct 09 16:53:15 Pi1 iotedged[1827]: 2018-10-09T14:53:15Z [INFO] - Starting Azure IoT Edge Security Daemon Oct 09 16:53:15 Pi1 iotedged[1827]: 2018-10-09T14:53:15Z [INFO] - Version - 1.0.2 (f6fcdb2e24ac2af977e748e9f2b8a37245b92738) Oct 09 16:53:15 Pi1 iotedged[1827]: 2018-10-09T14:53:15Z [INFO] - Using config file: /etc/iotedge/config.yaml Oct 09 16:53:15 Pi1 iotedged[1827]: 2018-10-09T14:53:15Z [INFO] - Using runtime network id azure-iot-edge Oct 09 16:53:15 Pi1 iotedged[1827]: 2018-10-09T14:53:15Z [INFO] - Initializing the module runtime... Oct 09 16:53:16 Pi1 iotedged[1827]: 2018-10-09T14:53:16Z [INFO] - Finished initializing the module runtime. Oct 09 16:53:16 Pi1 iotedged[1827]: 2018-10-09T14:53:16Z [INFO] - Configuring /var/lib/iotedge as the home directory. Oct 09 16:53:16 Pi1 iotedged[1827]: 2018-10-09T14:53:16Z [INFO] - Configuring certificates... Oct 09 16:53:16 Pi1 iotedged[1827]: 2018-10-09T14:53:16Z [INFO] - Transparent gateway certificates not found, operating in quick start mode... Oct 09 16:53:16 Pi1 iotedged[1827]: 2018-10-09T14:53:16Z [INFO] - Finished configuring certificates. Oct 09 16:53:16 Pi1 iotedged[1827]: 2018-10-09T14:53:16Z [INFO] - Initializing hsm... Oct 09 16:53:16 Pi1 iotedged[1827]: 2018-10-09T14:53:16Z [INFO] - Finished initializing hsm. Oct 09 16:53:16 Pi1 iotedged[1827]: 2018-10-09T14:53:16Z [INFO] - Detecting if configuration file has changed... Oct 09 16:53:16 Pi1 iotedged[1827]: 2018-10-09T14:53:16Z [INFO] - No change to configuration file detected. Oct 09 16:53:16 Pi1 iotedged[1827]: 2018-10-09T14:53:16Z [INFO] - Obtaining workload CA succeeded. Oct 09 16:53:16 Pi1 iotedged[1827]: 2018-10-09T14:53:16Z [INFO] - Provisioning edge device... Oct 09 16:53:16 Pi1 systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE Oct 09 16:53:16 Pi1 systemd[1]: iotedge.service: Unit entered failed state. Oct 09 16:53:16 Pi1 systemd[1]: iotedge.service: Failed with result 'exit-code'. Oct 09 16:53:16 Pi1 systemd[1]: iotedge.service: Service hold-off time over, scheduling restart. Oct 09 16:53:16 Pi1 systemd[1]: Stopped Azure IoT Edge daemon. Oct 09 16:53:16 Pi1 systemd[1]: Started Azure IoT Edge daemon. Oct 09 16:53:16 Pi1 iotedged[1834]: 2018-10-09T14:53:16Z [INFO] - Starting Azure IoT Edge Security Daemon Oct 09 16:53:16 Pi1 iotedged[1834]: 2018-10-09T14:53:16Z [INFO] - Version - 1.0.2 (f6fcdb2e24ac2af977e748e9f2b8a37245b92738) Oct 09 16:53:16 Pi1 iotedged[1834]: 2018-10-09T14:53:16Z [INFO] - Using config file: /etc/iotedge/config.yaml Oct 09 16:53:16 Pi1 iotedged[1834]: 2018-10-09T14:53:16Z [INFO] - Using runtime network id azure-iot-edge Oct 09 16:53:16 Pi1 iotedged[1834]: 2018-10-09T14:53:16Z [INFO] - Initializing the module runtime... Oct 09 16:53:16 Pi1 iotedged[1834]: 2018-10-09T14:53:16Z [INFO] - Finished initializing the module runtime. Oct 09 16:53:16 Pi1 iotedged[1834]: 2018-10-09T14:53:16Z [INFO] - Configuring /var/lib/iotedge as the home directory. Oct 09 16:53:16 Pi1 iotedged[1834]: 2018-10-09T14:53:16Z [INFO] - Configuring certificates... Oct 09 16:53:16 Pi1 iotedged[1834]: 2018-10-09T14:53:16Z [INFO] - Transparent gateway certificates not found, operating in quick start mode... Oct 09 16:53:16 Pi1 iotedged[1834]: 2018-10-09T14:53:16Z [INFO] - Finished configuring certificates. Oct 09 16:53:16 Pi1 iotedged[1834]: 2018-10-09T14:53:16Z [INFO] - Initializing hsm... Oct 09 16:53:16 Pi1 iotedged[1834]: 2018-10-09T14:53:16Z [INFO] - Finished initializing hsm. Oct 09 16:53:16 Pi1 iotedged[1834]: 2018-10-09T14:53:16Z [INFO] - Detecting if configuration file has changed... Oct 09 16:53:16 Pi1 iotedged[1834]: 2018-10-09T14:53:16Z [INFO] - No change to configuration file detected. Oct 09 16:53:16 Pi1 iotedged[1834]: 2018-10-09T14:53:16Z [INFO] - Obtaining workload CA succeeded. Oct 09 16:53:16 Pi1 iotedged[1834]: 2018-10-09T14:53:16Z [INFO] - Provisioning edge device... Oct 09 16:53:16 Pi1 systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE Oct 09 16:53:16 Pi1 systemd[1]: iotedge.service: Unit entered failed state. Oct 09 16:53:16 Pi1 systemd[1]: iotedge.service: Failed with result 'exit-code'. Oct 09 16:53:16 Pi1 systemd[1]: iotedge.service: Service hold-off time over, scheduling restart. Oct 09 16:53:16 Pi1 systemd[1]: Stopped Azure IoT Edge daemon. Oct 09 16:53:16 Pi1 systemd[1]: Started Azure IoT Edge daemon. Oct 09 16:53:16 Pi1 iotedged[1842]: 2018-10-09T14:53:16Z [INFO] - Starting Azure IoT Edge Security Daemon Oct 09 16:53:16 Pi1 iotedged[1842]: 2018-10-09T14:53:16Z [INFO] - Version - 1.0.2 (f6fcdb2e24ac2af977e748e9f2b8a37245b92738) Oct 09 16:53:16 Pi1 iotedged[1842]: 2018-10-09T14:53:16Z [INFO] - Using config file: /etc/iotedge/config.yaml Oct 09 16:53:16 Pi1 iotedged[1842]: 2018-10-09T14:53:16Z [INFO] - Using runtime network id azure-iot-edge Oct 09 16:53:16 Pi1 iotedged[1842]: 2018-10-09T14:53:16Z [INFO] - Initializing the module runtime... Oct 09 16:53:16 Pi1 iotedged[1842]: 2018-10-09T14:53:16Z [INFO] - Finished initializing the module runtime. Oct 09 16:53:16 Pi1 iotedged[1842]: 2018-10-09T14:53:16Z [INFO] - Configuring /var/lib/iotedge as the home directory. Oct 09 16:53:16 Pi1 iotedged[1842]: 2018-10-09T14:53:16Z [INFO] - Configuring certificates... Oct 09 16:53:16 Pi1 iotedged[1842]: 2018-10-09T14:53:16Z [INFO] - Transparent gateway certificates not found, operating in quick start mode... Oct 09 16:53:16 Pi1 iotedged[1842]: 2018-10-09T14:53:16Z [INFO] - Finished configuring certificates. Oct 09 16:53:16 Pi1 iotedged[1842]: 2018-10-09T14:53:16Z [INFO] - Initializing hsm... Oct 09 16:53:16 Pi1 iotedged[1842]: 2018-10-09T14:53:16Z [INFO] - Finished initializing hsm. Oct 09 16:53:16 Pi1 iotedged[1842]: 2018-10-09T14:53:16Z [INFO] - Detecting if configuration file has changed... Oct 09 16:53:16 Pi1 iotedged[1842]: 2018-10-09T14:53:16Z [INFO] - No change to configuration file detected. Oct 09 16:53:16 Pi1 iotedged[1842]: 2018-10-09T14:53:16Z [INFO] - Obtaining workload CA succeeded. Oct 09 16:53:16 Pi1 iotedged[1842]: 2018-10-09T14:53:16Z [INFO] - Provisioning edge device... Oct 09 16:53:16 Pi1 systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE Oct 09 16:53:16 Pi1 systemd[1]: iotedge.service: Unit entered failed state. Oct 09 16:53:16 Pi1 systemd[1]: iotedge.service: Failed with result 'exit-code'. Oct 09 16:53:16 Pi1 systemd[1]: iotedge.service: Service hold-off time over, scheduling restart. Oct 09 16:53:16 Pi1 systemd[1]: Stopped Azure IoT Edge daemon. Oct 09 16:53:16 Pi1 systemd[1]: iotedge.service: Start request repeated too quickly. Oct 09 16:53:16 Pi1 systemd[1]: Failed to start Azure IoT Edge daemon. Oct 09 16:53:16 Pi1 systemd[1]: iotedge.service: Unit entered failed state. Oct 09 16:53:16 Pi1 systemd[1]: iotedge.service: Failed with result 'exit-code'. Oct 09 16:53:37 Pi1 systemd[1]: Started Azure IoT Edge daemon. Oct 09 16:53:37 Pi1 iotedged[1860]: 2018-10-09T14:53:37Z [INFO] - Starting Azure IoT Edge Security Daemon Oct 09 16:53:37 Pi1 iotedged[1860]: 2018-10-09T14:53:37Z [INFO] - Version - 1.0.2 (f6fcdb2e24ac2af977e748e9f2b8a37245b92738) Oct 09 16:53:37 Pi1 iotedged[1860]: 2018-10-09T14:53:37Z [INFO] - Using config file: /etc/iotedge/config.yaml Oct 09 16:53:37 Pi1 iotedged[1860]: 2018-10-09T14:53:37Z [INFO] - Using runtime network id azure-iot-edge Oct 09 16:53:37 Pi1 iotedged[1860]: 2018-10-09T14:53:37Z [INFO] - Initializing the module runtime... Oct 09 16:53:37 Pi1 iotedged[1860]: 2018-10-09T14:53:37Z [INFO] - Finished initializing the module runtime. Oct 09 16:53:37 Pi1 iotedged[1860]: 2018-10-09T14:53:37Z [INFO] - Configuring /var/lib/iotedge as the home directory. Oct 09 16:53:37 Pi1 iotedged[1860]: 2018-10-09T14:53:37Z [INFO] - Configuring certificates... Oct 09 16:53:37 Pi1 iotedged[1860]: 2018-10-09T14:53:37Z [INFO] - Transparent gateway certificates not found, operating in quick start mode... Oct 09 16:53:37 Pi1 iotedged[1860]: 2018-10-09T14:53:37Z [INFO] - Finished configuring certificates. Oct 09 16:53:37 Pi1 iotedged[1860]: 2018-10-09T14:53:37Z [INFO] - Initializing hsm... Oct 09 16:53:37 Pi1 iotedged[1860]: 2018-10-09T14:53:37Z [INFO] - Finished initializing hsm. Oct 09 16:53:37 Pi1 iotedged[1860]: 2018-10-09T14:53:37Z [INFO] - Detecting if configuration file has changed... Oct 09 16:53:37 Pi1 iotedged[1860]: 2018-10-09T14:53:37Z [INFO] - No change to configuration file detected. Oct 09 16:53:37 Pi1 iotedged[1860]: 2018-10-09T14:53:37Z [INFO] - Obtaining workload CA succeeded. Oct 09 16:53:37 Pi1 iotedged[1860]: 2018-10-09T14:53:37Z [INFO] - Provisioning edge device... Oct 09 16:53:37 Pi1 systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE Oct 09 16:53:37 Pi1 systemd[1]: iotedge.service: Unit entered failed state. Oct 09 16:53:37 Pi1 systemd[1]: iotedge.service: Failed with result 'exit-code'. Oct 09 16:53:37 Pi1 systemd[1]: iotedge.service: Service hold-off time over, scheduling restart. Oct 09 16:53:37 Pi1 systemd[1]: Stopped Azure IoT Edge daemon. Oct 09 16:53:37 Pi1 systemd[1]: Started Azure IoT Edge daemon. Oct 09 16:53:37 Pi1 iotedged[1870]: 2018-10-09T14:53:37Z [INFO] - Starting Azure IoT Edge Security Daemon Oct 09 16:53:37 Pi1 iotedged[1870]: 2018-10-09T14:53:37Z [INFO] - Version - 1.0.2 (f6fcdb2e24ac2af977e748e9f2b8a37245b92738) Oct 09 16:53:37 Pi1 iotedged[1870]: 2018-10-09T14:53:37Z [INFO] - Using config file: /etc/iotedge/config.yaml Oct 09 16:53:37 Pi1 iotedged[1870]: 2018-10-09T14:53:37Z [INFO] - Using runtime network id azure-iot-edge Oct 09 16:53:37 Pi1 iotedged[1870]: 2018-10-09T14:53:37Z [INFO] - Initializing the module runtime... Oct 09 16:53:37 Pi1 iotedged[1870]: 2018-10-09T14:53:37Z [INFO] - Finished initializing the module runtime. Oct 09 16:53:37 Pi1 iotedged[1870]: 2018-10-09T14:53:37Z [INFO] - Configuring /var/lib/iotedge as the home directory. Oct 09 16:53:37 Pi1 iotedged[1870]: 2018-10-09T14:53:37Z [INFO] - Configuring certificates... Oct 09 16:53:37 Pi1 iotedged[1870]: 2018-10-09T14:53:37Z [INFO] - Transparent gateway certificates not found, operating in quick start mode... Oct 09 16:53:37 Pi1 iotedged[1870]: 2018-10-09T14:53:37Z [INFO] - Finished configuring certificates. Oct 09 16:53:37 Pi1 iotedged[1870]: 2018-10-09T14:53:37Z [INFO] - Initializing hsm... Oct 09 16:53:37 Pi1 iotedged[1870]: 2018-10-09T14:53:37Z [INFO] - Finished initializing hsm. Oct 09 16:53:37 Pi1 iotedged[1870]: 2018-10-09T14:53:37Z [INFO] - Detecting if configuration file has changed... Oct 09 16:53:37 Pi1 iotedged[1870]: 2018-10-09T14:53:37Z [INFO] - No change to configuration file detected. Oct 09 16:53:37 Pi1 iotedged[1870]: 2018-10-09T14:53:37Z [INFO] - Obtaining workload CA succeeded. Oct 09 16:53:37 Pi1 iotedged[1870]: 2018-10-09T14:53:37Z [INFO] - Provisioning edge device... Oct 09 16:53:37 Pi1 systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE Oct 09 16:53:37 Pi1 systemd[1]: iotedge.service: Unit entered failed state. Oct 09 16:53:37 Pi1 systemd[1]: iotedge.service: Failed with result 'exit-code'. Oct 09 16:53:37 Pi1 systemd[1]: iotedge.service: Service hold-off time over, scheduling restart. Oct 09 16:53:37 Pi1 systemd[1]: Stopped Azure IoT Edge daemon. Oct 09 16:53:37 Pi1 systemd[1]: Started Azure IoT Edge daemon. Oct 09 16:53:37 Pi1 iotedged[1877]: 2018-10-09T14:53:37Z [INFO] - Starting Azure IoT Edge Security Daemon Oct 09 16:53:37 Pi1 iotedged[1877]: 2018-10-09T14:53:37Z [INFO] - Version - 1.0.2 (f6fcdb2e24ac2af977e748e9f2b8a37245b92738) Oct 09 16:53:37 Pi1 iotedged[1877]: 2018-10-09T14:53:37Z [INFO] - Using config file: /etc/iotedge/config.yaml Oct 09 16:53:37 Pi1 iotedged[1877]: 2018-10-09T14:53:37Z [INFO] - Using runtime network id azure-iot-edge Oct 09 16:53:37 Pi1 iotedged[1877]: 2018-10-09T14:53:37Z [INFO] - Initializing the module runtime... Oct 09 16:53:38 Pi1 iotedged[1877]: 2018-10-09T14:53:38Z [INFO] - Finished initializing the module runtime. Oct 09 16:53:38 Pi1 iotedged[1877]: 2018-10-09T14:53:38Z [INFO] - Configuring /var/lib/iotedge as the home directory. Oct 09 16:53:38 Pi1 iotedged[1877]: 2018-10-09T14:53:38Z [INFO] - Configuring certificates... Oct 09 16:53:38 Pi1 iotedged[1877]: 2018-10-09T14:53:38Z [INFO] - Transparent gateway certificates not found, operating in quick start mode... Oct 09 16:53:38 Pi1 iotedged[1877]: 2018-10-09T14:53:38Z [INFO] - Finished configuring certificates. Oct 09 16:53:38 Pi1 iotedged[1877]: 2018-10-09T14:53:38Z [INFO] - Initializing hsm... Oct 09 16:53:38 Pi1 iotedged[1877]: 2018-10-09T14:53:38Z [INFO] - Finished initializing hsm. Oct 09 16:53:38 Pi1 iotedged[1877]: 2018-10-09T14:53:38Z [INFO] - Detecting if configuration file has changed... Oct 09 16:53:38 Pi1 iotedged[1877]: 2018-10-09T14:53:38Z [INFO] - No change to configuration file detected. Oct 09 16:53:38 Pi1 iotedged[1877]: 2018-10-09T14:53:38Z [INFO] - Obtaining workload CA succeeded. Oct 09 16:53:38 Pi1 iotedged[1877]: 2018-10-09T14:53:38Z [INFO] - Provisioning edge device... Oct 09 16:53:38 Pi1 systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE Oct 09 16:53:38 Pi1 systemd[1]: iotedge.service: Unit entered failed state. Oct 09 16:53:38 Pi1 systemd[1]: iotedge.service: Failed with result 'exit-code'. Oct 09 16:53:38 Pi1 systemd[1]: iotedge.service: Service hold-off time over, scheduling restart. Oct 09 16:53:38 Pi1 systemd[1]: Stopped Azure IoT Edge daemon. Oct 09 16:53:38 Pi1 systemd[1]: Started Azure IoT Edge daemon. Oct 09 16:53:38 Pi1 iotedged[1884]: 2018-10-09T14:53:38Z [INFO] - Starting Azure IoT Edge Security Daemon Oct 09 16:53:38 Pi1 iotedged[1884]: 2018-10-09T14:53:38Z [INFO] - Version - 1.0.2 (f6fcdb2e24ac2af977e748e9f2b8a37245b92738) Oct 09 16:53:38 Pi1 iotedged[1884]: 2018-10-09T14:53:38Z [INFO] - Using config file: /etc/iotedge/config.yaml Oct 09 16:53:38 Pi1 iotedged[1884]: 2018-10-09T14:53:38Z [INFO] - Using runtime network id azure-iot-edge Oct 09 16:53:38 Pi1 iotedged[1884]: 2018-10-09T14:53:38Z [INFO] - Initializing the module runtime... Oct 09 16:53:38 Pi1 iotedged[1884]: 2018-10-09T14:53:38Z [INFO] - Finished initializing the module runtime. Oct 09 16:53:38 Pi1 iotedged[1884]: 2018-10-09T14:53:38Z [INFO] - Configuring /var/lib/iotedge as the home directory. Oct 09 16:53:38 Pi1 iotedged[1884]: 2018-10-09T14:53:38Z [INFO] - Configuring certificates... Oct 09 16:53:38 Pi1 iotedged[1884]: 2018-10-09T14:53:38Z [INFO] - Transparent gateway certificates not found, operating in quick start mode... Oct 09 16:53:38 Pi1 iotedged[1884]: 2018-10-09T14:53:38Z [INFO] - Finished configuring certificates. Oct 09 16:53:38 Pi1 iotedged[1884]: 2018-10-09T14:53:38Z [INFO] - Initializing hsm... Oct 09 16:53:38 Pi1 iotedged[1884]: 2018-10-09T14:53:38Z [INFO] - Finished initializing hsm. Oct 09 16:53:38 Pi1 iotedged[1884]: 2018-10-09T14:53:38Z [INFO] - Detecting if configuration file has changed... Oct 09 16:53:38 Pi1 iotedged[1884]: 2018-10-09T14:53:38Z [INFO] - No change to configuration file detected. Oct 09 16:53:38 Pi1 iotedged[1884]: 2018-10-09T14:53:38Z [INFO] - Obtaining workload CA succeeded. Oct 09 16:53:38 Pi1 iotedged[1884]: 2018-10-09T14:53:38Z [INFO] - Provisioning edge device... Oct 09 16:53:38 Pi1 systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE Oct 09 16:53:38 Pi1 systemd[1]: iotedge.service: Unit entered failed state. Oct 09 16:53:38 Pi1 systemd[1]: iotedge.service: Failed with result 'exit-code'. Oct 09 16:53:38 Pi1 systemd[1]: iotedge.service: Service hold-off time over, scheduling restart. Oct 09 16:53:38 Pi1 systemd[1]: Stopped Azure IoT Edge daemon. Oct 09 16:53:38 Pi1 systemd[1]: Started Azure IoT Edge daemon. Oct 09 16:53:38 Pi1 iotedged[1891]: 2018-10-09T14:53:38Z [INFO] - Starting Azure IoT Edge Security Daemon Oct 09 16:53:38 Pi1 iotedged[1891]: 2018-10-09T14:53:38Z [INFO] - Version - 1.0.2 (f6fcdb2e24ac2af977e748e9f2b8a37245b92738) Oct 09 16:53:38 Pi1 iotedged[1891]: 2018-10-09T14:53:38Z [INFO] - Using config file: /etc/iotedge/config.yaml Oct 09 16:53:38 Pi1 iotedged[1891]: 2018-10-09T14:53:38Z [INFO] - Using runtime network id azure-iot-edge Oct 09 16:53:38 Pi1 iotedged[1891]: 2018-10-09T14:53:38Z [INFO] - Initializing the module runtime... Oct 09 16:53:38 Pi1 iotedged[1891]: 2018-10-09T14:53:38Z [INFO] - Finished initializing the module runtime. Oct 09 16:53:38 Pi1 iotedged[1891]: 2018-10-09T14:53:38Z [INFO] - Configuring /var/lib/iotedge as the home directory. Oct 09 16:53:38 Pi1 iotedged[1891]: 2018-10-09T14:53:38Z [INFO] - Configuring certificates... Oct 09 16:53:38 Pi1 iotedged[1891]: 2018-10-09T14:53:38Z [INFO] - Transparent gateway certificates not found, operating in quick start mode... Oct 09 16:53:38 Pi1 iotedged[1891]: 2018-10-09T14:53:38Z [INFO] - Finished configuring certificates. Oct 09 16:53:38 Pi1 iotedged[1891]: 2018-10-09T14:53:38Z [INFO] - Initializing hsm... Oct 09 16:53:38 Pi1 iotedged[1891]: 2018-10-09T14:53:38Z [INFO] - Finished initializing hsm. Oct 09 16:53:38 Pi1 iotedged[1891]: 2018-10-09T14:53:38Z [INFO] - Detecting if configuration file has changed... Oct 09 16:53:38 Pi1 iotedged[1891]: 2018-10-09T14:53:38Z [INFO] - No change to configuration file detected. Oct 09 16:53:38 Pi1 iotedged[1891]: 2018-10-09T14:53:38Z [INFO] - Obtaining workload CA succeeded. Oct 09 16:53:38 Pi1 iotedged[1891]: 2018-10-09T14:53:38Z [INFO] - Provisioning edge device... Oct 09 16:53:38 Pi1 systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE Oct 09 16:53:38 Pi1 systemd[1]: iotedge.service: Unit entered failed state. Oct 09 16:53:38 Pi1 systemd[1]: iotedge.service: Failed with result 'exit-code'. Oct 09 16:53:38 Pi1 systemd[1]: iotedge.service: Service hold-off time over, scheduling restart. Oct 09 16:53:38 Pi1 systemd[1]: Stopped Azure IoT Edge daemon. Oct 09 16:53:38 Pi1 systemd[1]: iotedge.service: Start request repeated too quickly. Oct 09 16:53:38 Pi1 systemd[1]: Failed to start Azure IoT Edge daemon. Oct 09 16:53:38 Pi1 systemd[1]: iotedge.service: Unit entered failed state. Oct 09 16:53:38 Pi1 systemd[1]: iotedge.service: Failed with result 'exit-code'. Oct 09 16:53:53 Pi1 systemd[1]: Started Azure IoT Edge daemon. Oct 09 16:53:53 Pi1 iotedged[1928]: 2018-10-09T14:53:53Z [INFO] - Starting Azure IoT Edge Security Daemon Oct 09 16:53:53 Pi1 iotedged[1928]: 2018-10-09T14:53:53Z [INFO] - Version - 1.0.2 (f6fcdb2e24ac2af977e748e9f2b8a37245b92738) Oct 09 16:53:53 Pi1 iotedged[1928]: 2018-10-09T14:53:53Z [INFO] - Using config file: /etc/iotedge/config.yaml Oct 09 16:53:53 Pi1 iotedged[1928]: 2018-10-09T14:53:53Z [INFO] - Using runtime network id azure-iot-edge Oct 09 16:53:53 Pi1 iotedged[1928]: 2018-10-09T14:53:53Z [INFO] - Initializing the module runtime... Oct 09 16:53:54 Pi1 iotedged[1928]: 2018-10-09T14:53:54Z [INFO] - Finished initializing the module runtime. Oct 09 16:53:54 Pi1 iotedged[1928]: 2018-10-09T14:53:54Z [INFO] - Configuring /var/lib/iotedge as the home directory. Oct 09 16:53:54 Pi1 iotedged[1928]: 2018-10-09T14:53:54Z [INFO] - Configuring certificates... Oct 09 16:53:54 Pi1 iotedged[1928]: 2018-10-09T14:53:54Z [INFO] - Transparent gateway certificates not found, operating in quick start mode... Oct 09 16:53:54 Pi1 iotedged[1928]: 2018-10-09T14:53:54Z [INFO] - Finished configuring certificates. Oct 09 16:53:54 Pi1 iotedged[1928]: 2018-10-09T14:53:54Z [INFO] - Initializing hsm... Oct 09 16:53:54 Pi1 iotedged[1928]: 2018-10-09T14:53:54Z [INFO] - Finished initializing hsm. Oct 09 16:53:54 Pi1 iotedged[1928]: 2018-10-09T14:53:54Z [INFO] - Detecting if configuration file has changed... Oct 09 16:53:54 Pi1 iotedged[1928]: 2018-10-09T14:53:54Z [INFO] - No change to configuration file detected. Oct 09 16:53:54 Pi1 iotedged[1928]: 2018-10-09T14:53:54Z [INFO] - Obtaining workload CA succeeded. Oct 09 16:53:54 Pi1 iotedged[1928]: 2018-10-09T14:53:54Z [INFO] - Provisioning edge device... Oct 09 16:53:54 Pi1 systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE Oct 09 16:53:54 Pi1 systemd[1]: iotedge.service: Unit entered failed state. Oct 09 16:53:54 Pi1 systemd[1]: iotedge.service: Failed with result 'exit-code'. Oct 09 16:53:54 Pi1 systemd[1]: iotedge.service: Service hold-off time over, scheduling restart. Oct 09 16:53:54 Pi1 systemd[1]: Stopped Azure IoT Edge daemon. Oct 09 16:53:54 Pi1 systemd[1]: Started Azure IoT Edge daemon. Oct 09 16:53:54 Pi1 iotedged[1939]: 2018-10-09T14:53:54Z [INFO] - Starting Azure IoT Edge Security Daemon Oct 09 16:53:54 Pi1 iotedged[1939]: 2018-10-09T14:53:54Z [INFO] - Version - 1.0.2 (f6fcdb2e24ac2af977e748e9f2b8a37245b92738) Oct 09 16:53:54 Pi1 iotedged[1939]: 2018-10-09T14:53:54Z [INFO] - Using config file: /etc/iotedge/config.yaml Oct 09 16:53:54 Pi1 iotedged[1939]: 2018-10-09T14:53:54Z [INFO] - Using runtime network id azure-iot-edge Oct 09 16:53:54 Pi1 iotedged[1939]: 2018-10-09T14:53:54Z [INFO] - Initializing the module runtime... Oct 09 16:53:54 Pi1 iotedged[1939]: 2018-10-09T14:53:54Z [INFO] - Finished initializing the module runtime. Oct 09 16:53:54 Pi1 iotedged[1939]: 2018-10-09T14:53:54Z [INFO] - Configuring /var/lib/iotedge as the home directory. Oct 09 16:53:54 Pi1 iotedged[1939]: 2018-10-09T14:53:54Z [INFO] - Configuring certificates... Oct 09 16:53:54 Pi1 iotedged[1939]: 2018-10-09T14:53:54Z [INFO] - Transparent gateway certificates not found, operating in quick start mode... Oct 09 16:53:54 Pi1 iotedged[1939]: 2018-10-09T14:53:54Z [INFO] - Finished configuring certificates. Oct 09 16:53:54 Pi1 iotedged[1939]: 2018-10-09T14:53:54Z [INFO] - Initializing hsm... Oct 09 16:53:54 Pi1 iotedged[1939]: 2018-10-09T14:53:54Z [INFO] - Finished initializing hsm. Oct 09 16:53:54 Pi1 iotedged[1939]: 2018-10-09T14:53:54Z [INFO] - Detecting if configuration file has changed... Oct 09 16:53:54 Pi1 iotedged[1939]: 2018-10-09T14:53:54Z [INFO] - No change to configuration file detected. Oct 09 16:53:54 Pi1 iotedged[1939]: 2018-10-09T14:53:54Z [INFO] - Obtaining workload CA succeeded. Oct 09 16:53:54 Pi1 iotedged[1939]: 2018-10-09T14:53:54Z [INFO] - Provisioning edge device... Oct 09 16:53:54 Pi1 systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE Oct 09 16:53:54 Pi1 systemd[1]: iotedge.service: Unit entered failed state. Oct 09 16:53:54 Pi1 systemd[1]: iotedge.service: Failed with result 'exit-code'. Oct 09 16:53:54 Pi1 systemd[1]: iotedge.service: Service hold-off time over, scheduling restart. Oct 09 16:53:54 Pi1 systemd[1]: Stopped Azure IoT Edge daemon. Oct 09 16:53:54 Pi1 systemd[1]: Started Azure IoT Edge daemon. Oct 09 16:53:54 Pi1 iotedged[1946]: 2018-10-09T14:53:54Z [INFO] - Starting Azure IoT Edge Security Daemon Oct 09 16:53:54 Pi1 iotedged[1946]: 2018-10-09T14:53:54Z [INFO] - Version - 1.0.2 (f6fcdb2e24ac2af977e748e9f2b8a37245b92738) Oct 09 16:53:54 Pi1 iotedged[1946]: 2018-10-09T14:53:54Z [INFO] - Using config file: /etc/iotedge/config.yaml Oct 09 16:53:54 Pi1 iotedged[1946]: 2018-10-09T14:53:54Z [INFO] - Using runtime network id azure-iot-edge Oct 09 16:53:54 Pi1 iotedged[1946]: 2018-10-09T14:53:54Z [INFO] - Initializing the module runtime... Oct 09 16:53:54 Pi1 iotedged[1946]: 2018-10-09T14:53:54Z [INFO] - Finished initializing the module runtime. Oct 09 16:53:54 Pi1 iotedged[1946]: 2018-10-09T14:53:54Z [INFO] - Configuring /var/lib/iotedge as the home directory. Oct 09 16:53:54 Pi1 iotedged[1946]: 2018-10-09T14:53:54Z [INFO] - Configuring certificates... Oct 09 16:53:54 Pi1 iotedged[1946]: 2018-10-09T14:53:54Z [INFO] - Transparent gateway certificates not found, operating in quick start mode... Oct 09 16:53:54 Pi1 iotedged[1946]: 2018-10-09T14:53:54Z [INFO] - Finished configuring certificates. Oct 09 16:53:54 Pi1 iotedged[1946]: 2018-10-09T14:53:54Z [INFO] - Initializing hsm... Oct 09 16:53:54 Pi1 iotedged[1946]: 2018-10-09T14:53:54Z [INFO] - Finished initializing hsm. Oct 09 16:53:54 Pi1 iotedged[1946]: 2018-10-09T14:53:54Z [INFO] - Detecting if configuration file has changed... Oct 09 16:53:54 Pi1 iotedged[1946]: 2018-10-09T14:53:54Z [INFO] - No change to configuration file detected. Oct 09 16:53:54 Pi1 iotedged[1946]: 2018-10-09T14:53:54Z [INFO] - Obtaining workload CA succeeded. Oct 09 16:53:54 Pi1 iotedged[1946]: 2018-10-09T14:53:54Z [INFO] - Provisioning edge device... Oct 09 16:53:54 Pi1 systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE Oct 09 16:53:54 Pi1 systemd[1]: iotedge.service: Unit entered failed state. Oct 09 16:53:54 Pi1 systemd[1]: iotedge.service: Failed with result 'exit-code'. Oct 09 16:53:54 Pi1 systemd[1]: iotedge.service: Service hold-off time over, scheduling restart. Oct 09 16:53:54 Pi1 systemd[1]: Stopped Azure IoT Edge daemon. Oct 09 16:53:54 Pi1 systemd[1]: Started Azure IoT Edge daemon. Oct 09 16:53:54 Pi1 iotedged[1953]: 2018-10-09T14:53:54Z [INFO] - Starting Azure IoT Edge Security Daemon Oct 09 16:53:54 Pi1 iotedged[1953]: 2018-10-09T14:53:54Z [INFO] - Version - 1.0.2 (f6fcdb2e24ac2af977e748e9f2b8a37245b92738) Oct 09 16:53:54 Pi1 iotedged[1953]: 2018-10-09T14:53:54Z [INFO] - Using config file: /etc/iotedge/config.yaml Oct 09 16:53:54 Pi1 iotedged[1953]: 2018-10-09T14:53:54Z [INFO] - Using runtime network id azure-iot-edge Oct 09 16:53:54 Pi1 iotedged[1953]: 2018-10-09T14:53:54Z [INFO] - Initializing the module runtime... Oct 09 16:53:54 Pi1 iotedged[1953]: 2018-10-09T14:53:54Z [INFO] - Finished initializing the module runtime. Oct 09 16:53:54 Pi1 iotedged[1953]: 2018-10-09T14:53:54Z [INFO] - Configuring /var/lib/iotedge as the home directory. Oct 09 16:53:54 Pi1 iotedged[1953]: 2018-10-09T14:53:54Z [INFO] - Configuring certificates... Oct 09 16:53:54 Pi1 iotedged[1953]: 2018-10-09T14:53:54Z [INFO] - Transparent gateway certificates not found, operating in quick start mode... Oct 09 16:53:54 Pi1 iotedged[1953]: 2018-10-09T14:53:54Z [INFO] - Finished configuring certificates. Oct 09 16:53:54 Pi1 iotedged[1953]: 2018-10-09T14:53:54Z [INFO] - Initializing hsm... Oct 09 16:53:54 Pi1 iotedged[1953]: 2018-10-09T14:53:54Z [INFO] - Finished initializing hsm. Oct 09 16:53:54 Pi1 iotedged[1953]: 2018-10-09T14:53:54Z [INFO] - Detecting if configuration file has changed... Oct 09 16:53:54 Pi1 iotedged[1953]: 2018-10-09T14:53:54Z [INFO] - No change to configuration file detected. Oct 09 16:53:54 Pi1 iotedged[1953]: 2018-10-09T14:53:54Z [INFO] - Obtaining workload CA succeeded. Oct 09 16:53:54 Pi1 iotedged[1953]: 2018-10-09T14:53:54Z [INFO] - Provisioning edge device... Oct 09 16:53:54 Pi1 systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE Oct 09 16:53:54 Pi1 systemd[1]: iotedge.service: Unit entered failed state. Oct 09 16:53:54 Pi1 systemd[1]: iotedge.service: Failed with result 'exit-code'. Oct 09 16:53:54 Pi1 systemd[1]: iotedge.service: Service hold-off time over, scheduling restart. Oct 09 16:53:54 Pi1 systemd[1]: Stopped Azure IoT Edge daemon. Oct 09 16:53:54 Pi1 systemd[1]: Started Azure IoT Edge daemon. Oct 09 16:53:54 Pi1 iotedged[1960]: 2018-10-09T14:53:54Z [INFO] - Starting Azure IoT Edge Security Daemon Oct 09 16:53:54 Pi1 iotedged[1960]: 2018-10-09T14:53:54Z [INFO] - Version - 1.0.2 (f6fcdb2e24ac2af977e748e9f2b8a37245b92738) Oct 09 16:53:54 Pi1 iotedged[1960]: 2018-10-09T14:53:54Z [INFO] - Using config file: /etc/iotedge/config.yaml Oct 09 16:53:54 Pi1 iotedged[1960]: 2018-10-09T14:53:54Z [INFO] - Using runtime network id azure-iot-edge Oct 09 16:53:55 Pi1 iotedged[1960]: 2018-10-09T14:53:54Z [INFO] - Initializing the module runtime... Oct 09 16:53:55 Pi1 iotedged[1960]: 2018-10-09T14:53:55Z [INFO] - Finished initializing the module runtime. Oct 09 16:53:55 Pi1 iotedged[1960]: 2018-10-09T14:53:55Z [INFO] - Configuring /var/lib/iotedge as the home directory. Oct 09 16:53:55 Pi1 iotedged[1960]: 2018-10-09T14:53:55Z [INFO] - Configuring certificates... Oct 09 16:53:55 Pi1 iotedged[1960]: 2018-10-09T14:53:55Z [INFO] - Transparent gateway certificates not found, operating in quick start mode... Oct 09 16:53:55 Pi1 iotedged[1960]: 2018-10-09T14:53:55Z [INFO] - Finished configuring certificates. Oct 09 16:53:55 Pi1 iotedged[1960]: 2018-10-09T14:53:55Z [INFO] - Initializing hsm... Oct 09 16:53:55 Pi1 iotedged[1960]: 2018-10-09T14:53:55Z [INFO] - Finished initializing hsm. Oct 09 16:53:55 Pi1 iotedged[1960]: 2018-10-09T14:53:55Z [INFO] - Detecting if configuration file has changed... Oct 09 16:53:55 Pi1 iotedged[1960]: 2018-10-09T14:53:55Z [INFO] - No change to configuration file detected. Oct 09 16:53:55 Pi1 iotedged[1960]: 2018-10-09T14:53:55Z [INFO] - Obtaining workload CA succeeded. Oct 09 16:53:55 Pi1 iotedged[1960]: 2018-10-09T14:53:55Z [INFO] - Provisioning edge device... Oct 09 16:53:55 Pi1 systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE Oct 09 16:53:55 Pi1 systemd[1]: iotedge.service: Unit entered failed state. Oct 09 16:53:55 Pi1 systemd[1]: iotedge.service: Failed with result 'exit-code'. Oct 09 16:53:55 Pi1 systemd[1]: iotedge.service: Service hold-off time over, scheduling restart. Oct 09 16:53:55 Pi1 systemd[1]: Stopped Azure IoT Edge daemon. Oct 09 16:53:55 Pi1 systemd[1]: iotedge.service: Start request repeated too quickly. Oct 09 16:53:55 Pi1 systemd[1]: Failed to start Azure IoT Edge daemon. Oct 09 16:53:55 Pi1 systemd[1]: iotedge.service: Unit entered failed state. Oct 09 16:53:55 Pi1 systemd[1]: iotedge.service: Failed with result 'exit-code'.
yashapatel786
commented
5 years ago I was running Docker CE and, given the instructions, thought it'd be fine to skip on the Moby-based engine for now. Turns out this was not the case.
I understand that the walkthrough leads to that assumption (no need to have Moby-based engine on non-production environments). @kgremban can we add a note on the document that in some scenarios Moby-based engine needs to be installed? @veyalla if you believe that is not the case let us know.
@CIPop thank you for helping here :).
@thorpebt I am about to close this issue. If you are still having issues can you open a new one?
Thank you all!] (https://github.com/MicrosoftDocs/azure-docs/issues/11046#issuecomment-402411440)
Having the same issue in starting IoT edge daemon. Please refer to this issue : https://github.com/Azure/iotedge/issues/940
tynevi
commented
4 months ago @smcd253 - One of your comments contained an Azure IoT Device Connection String which was flagged in secret scanning. I have replaced it with "key-value" in the comment. We recommend that you revoke existing connection strings and replace with new ones.
So I've gotten all the way to the point where I need to verify successful installation of IoT Edge daemon, and it's failing with the following output:
pi@spencerpi:~ $ sudo systemctl status iotedge ● iotedge.service - Azure IoT Edge daemon Loaded: loaded (/lib/systemd/system/iotedge.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2018-07-01 17:53:12 PDT; 7s ago Docs: man:iotedged(8) Process: 9632 ExecStart=/usr/bin/iotedged -c /etc/iotedge/config.yaml (code=exited, status=1/FAILURE) Main PID: 9632 (code=exited, status=1/FAILURE) CPU: 60ms
Jul 01 17:53:12 spencerpi systemd[1]: iotedge.service: Failed with result 'exit-code'. Jul 01 17:53:12 spencerpi systemd[1]: iotedge.service: Service hold-off time over, scheduling restart. Jul 01 17:53:12 spencerpi systemd[1]: Stopped Azure IoT Edge daemon. Jul 01 17:53:12 spencerpi systemd[1]: iotedge.service: Start request repeated too quickly. Jul 01 17:53:12 spencerpi systemd[1]: Failed to start Azure IoT Edge daemon. Jul 01 17:53:12 spencerpi systemd[1]: iotedge.service: Unit entered failed state. Jul 01 17:53:12 spencerpi systemd[1]: iotedge.service: Failed with result 'exit-code'.
I'm running docker version 18.05.0-ce.
Thoughts?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.