Greetings ,
Can we deploy this code on a Simulated IOT Edge running on a Windows /Linux docker container (on my laptop) ? If so can you please mention the point at the code/files that needs to be modified .

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ X] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

I am trying to redirect video camera output from windows 10 to the Camera Capture module - is this supported, if yes, whats the procedure

Any log messages given by the failure

cv2.error: OpenCV(4.0.0) /io/opencv/modules/imgproc/src/resize.cpp:3784: error: (-215:Assertion failed) !ssize.empty() in function 'resize'

Expected/desired behavior

OS and Version?

Windows 10

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Deploy amd64 solution on a Windows 10 simulated IoT Edge Device.

Any log messages given by the failure

The camera-capture module will crash on runtime with no logging. All the other modules run with logging available.

PS C:\WINDOWS\system32> iotedge logs camera-capture
PS C:\WINDOWS\system32>

PS C:\WINDOWS\system32> iotedge list
NAME                      STATUS           DESCRIPTION            CONFIG
edgeHub                   running          Up an hour             mcr.microsoft.com/azureiotedge-hub:1.0
image-classifier-service  running          Up an hour             fcscontainers.azurecr.io/imageclassifierservice:0.2.4-amd64
camera-capture            stopped          Stopped 4 minutes ago  fcscontainers.azurecr.io/cameracapture:0.2.7-test-amd64
edgeAgent                 running          Up an hour             mcr.microsoft.com/azureiotedge-agent:1.0

Expected/desired behavior

A running camera-capture container with logging on a windows 10 device with docker installed (followed the instructions on Windows).

OS and Version?

Windows 10

Versions

Docker Version 17.12.0-ce-win47 (15139)
VS Code version 1.27
PowerShell version 5.1.16299.611

Mention any other details that might be useful

Can't provide detailed info because there is no logging available.
Docker engine is set to Linux containers.

---

Thanks! We'll be in touch soon.

When using your own model, the code in predict.py removes the last character of the last label in labels.txt, so any message that is sent through and used directly in the sense-hat display module is missing the last letter of the final classification.

The issue is in the code, line 35 that reads from the labels.txt file and writes to the labels array:

l = l[:-1]

This removes the last character of the last label.

Changing line 35 to the following seems to provide the correct label output
l = l.strip()

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

1. Create own model using CustomVision.ai

2. Export DockerFile

3. Copy labels.txt and model.pb to ImageClassifierService module in solution

4. Change version of image-classifier-service in deployment.template.json

5. Build and Push

6. Create deployment for single device

7. Show images as required

8. Output for last label is missing the final letter

Any log messages given by the failure

Expected/desired behavior

Labels should be preserved.

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Raspbian Stretch

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

• download the complete project
• build and push
• deploy and check logs

Any log messages given by the failure

Caused by op 'conv1/conv1', defined at:
File "/usr/lib/python3.5/threading.py", line 882, in _bootstrap
self._bootstrap_inner()
File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner
self.run()
File "/usr/lib/python3.5/threading.py", line 862, in run
self._target(*self._args, **self._kwargs)
File "/usr/lib/python3.5/socketserver.py", line 625, in process_request_thread
self.finish_request(request, client_address)
File "/usr/lib/python3.5/socketserver.py", line 354, in finish_request
self.RequestHandlerClass(request, client_address, self)
File "/usr/lib/python3.5/socketserver.py", line 681, in init
self.handle()
File "/usr/local/lib/python3.5/dist-packages/werkzeug/serving.py", line 293, in handle
rv = BaseHTTPRequestHandler.handle(self)
File "/usr/lib/python3.5/http/server.py", line 422, in handle
self.handle_one_request()
File "/usr/local/lib/python3.5/dist-packages/werkzeug/serving.py", line 328, in handle_one_request
return self.run_wsgi()
File "/usr/local/lib/python3.5/dist-packages/werkzeug/serving.py", line 270, in run_wsgi
execute(self.server.app)
File "/usr/local/lib/python3.5/dist-packages/werkzeug/serving.py", line 258, in execute
application_iter = app(environ, start_response)
File "/usr/local/lib/python3.5/dist-packages/flask/app.py", line 2309, in call
return self.wsgi_app(environ, start_response)
File "/usr/local/lib/python3.5/dist-packages/flask/app.py", line 2292, in wsgi_app
response = self.full_dispatch_request()
File "/usr/local/lib/python3.5/dist-packages/flask/app.py", line 1813, in full_dispatch_request
rv = self.dispatch_request()
File "/usr/local/lib/python3.5/dist-packages/flask/app.py", line 1799, in dispatch_request
return self.view_functionsrule.endpoint
File "app.py", line 41, in predict_image_handler
results = predict_image(img)
File "/app/predict.py", line 56, in predict_image
tf.import_graph_def(graph_def, name='')
File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/util/deprecation.py", line 507, in new_func
return func(*args, **kwargs)
File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/importer.py", line 442, in import_graph_def
_ProcessNewOps(graph)
File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/importer.py", line 235, in _ProcessNewOps
for new_op in graph._add_new_tf_operations(compute_devices=False): # pylint: disable=protected-access
File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/ops.py", line 3433, in _add_new_tf_operations
for c_op in c_api_util.new_tf_operations(self)
File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/ops.py", line 3433, in
for c_op in c_api_util.new_tf_operations(self)
File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/ops.py", line 3325, in _create_op_from_tf_operation
ret = Operation(c_op, self)
File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/ops.py", line 1801, in init
self._traceback = tf_stack.extract_stack()

NotFoundError (see above for traceback): No registered '_FusedConv2D' OpKernel for CPU devices compatible with node node conv1/conv1 (defined at /app/predict.py:56)
. Registered:

 [[node conv1/conv1 (defined at /app/predict.py:56) ]]

2019-03-10 14:44:50.408362: E tensorflow/core/common_runtime/executor.cc:624] Executor failed to create kernel. Not found: No registered '_FusedConv2D' OpKernel for CPU devices compatible with node {{node conv1/conv1}}
. Registered:

Expected/desired behavior

The image classifier should be able to classify images... ;)

OS and Version?

Building and pushing from Win 10. Running edge device is Rpi 3+

Versions

Mention any other details that might be useful

The camera capture fails because it cannot create the socket to the image-classifier service.

This might be useful: tensorflow/tensorflow#24732

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [x] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

launch template on Visual Studio

Any log messages given by the failure

There are errors in deployment json file: data.modulesContent.$edgeAgent['properties.desired'].modules['camera-capture'].settings.createOptions should be string

Expected/desired behavior

To upload correctly

OS and Version?

Linux 19.0 and Visual Studio Code (Jan 2020 release)

Versions

Mention any other details that might be useful

I think you need to make the details like this...
"{\"HostConfig\":{\"PortBindings\":{\"5012/tcp\":[{\"HostPort\":\"5012\"}]},\"Binds\":[\"/dev/video0:/dev/video0\"],\"Devices\":[{\"PathOnHost\":\"/dev/video0\",\"PathInContainer\":\"/dev/video0\",\"CgroupPermissions\":\"mrw\"}]}}"
Or something that works and looks nice (very hard to see what is going on in that string). Also I think the file needs to be in a folder named config.

---

Thanks! We'll be in touch soon.

OS: raspberry pi3
steps:

Get started
To deploy the solution on a Raspberry Pi 3
test on raspberry pi3
1.Clone this sample
2.Update the .env file with the values for your container registry and make sure that your docker engine has access to it (create azure container registry and docker login in my pc)
3.build camera-capture module failed
docker login -u czgacr -p UFQdRXaH4z/qIUVlAIFj191GzGF0GJtj czgacr.azurecr.io
docker build -f Dockerfile.arm32v7 -t czgacr.azurecr.io/cameracapture:0.2.8-arm32v7 .

Please provide us with the following information:

This issue is for a: (mark with an x)

- [X ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Any log messages given by the failure

TypeError: 'NoneType' object is not iterable

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Windows 10

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Set up raspberry pi like in the discriptions (using Raspbian buster desktop), build and push IoT edge solution (VS code on Windows 10), deploy to raspberry pi, see modules "sensehat-display" and "image-classifier-service" fail (terminal "sudo iotedge list"), see logs of the two modules (terminal "sudo iotedge logs "

Any log messages given by the failure

From Module image classifier service:

Traceback (most recent call last):
File "app.py", line 10, in
from PIL import Image
File "/usr/local/lib/python3.7/site-packages/PIL/Image.py", line 93, in
from . import _imaging as core
ImportError: libxcb.so.1: cannot open shared object file: No such file or directory

From Module sensehat-display:

Traceback (most recent call last):
File "./main.py", line 14, in
import DisplayManager
File "/DisplayManager.py", line 1, in
import sense_hat
File "/usr/local/lib/python3.5/dist-packages/sense_hat/init.py", line 2, in
from .sense_hat import SenseHat, SenseHat as AstroPi
File "/usr/local/lib/python3.5/dist-packages/sense_hat/sense_hat.py", line 14, in
from PIL import Image # pillow
File "/usr/local/lib/python3.5/dist-packages/PIL/Image.py", line 93, in
from . import _imaging as core
ImportError: libxcb.so.1: cannot open shared object file: No such file or directory

Expected/desired behavior

no log errors :D

OS and Version?

Windows 10, Linux (raspbian buster)

Versions

Mention any other details that might be useful

Tried this multiple times with fresh installs of the pi, on pi3 and pi4

---

Thanks! We'll be in touch soon.

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

To deploy the solution on an x64 PC
From your mac or PC:

1. Clone this sample
2. Update the .env file with the values for your container registry and make sure that your docker engine has access to it
3. Rename the deployment.template.json file into deployment.template.RPI.json
4. Rename the deployment.template.test-amd64.json file into deployment.template.json
5. Build the entire solution by right-clicking on the deployment.template.json file and select Build and push IoT Edge Solution (this can take a while...especially to build numpy and pillow...)
6. Deploy the solution to your device by right-clicking on the config/deployment.json file, select Create Deployment for Single device and choose your targeted device

Any log messages given by the failure

PS C:\WINDOWS\system32> iotedge logs -f camera-capture
Could not convert string to bool.
Could not convert string to bool.
Could not convert string to bool.
Could not convert string to bool.

camera-capture failed Failed (1) 16 seconds ago tuomastest.azurecr.io/cameracapture:0.2.7test-amd64

Expected/desired behavior

Container Running

OS and Version?

Windows 10 Enterprise Version 1803

Versions

Docker version 18.09.0, build 4d60db4
iotedge 1.0.4 (2835ac47fbb944ba628a5cfe812ff394768842e0)
using Docker Linux container

Mention any other details that might be useful

I am trying to use my laptop camera to feed the camera-capture module and then send the frames to a Custom Vision API (Object detection so this will not be running on the edge, because it is not available).

Thank you for your help :)
Kind Regards
Haroun

Please provide us with the following information:

This issue is for a: (mark with an x)

- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Right click deployment.template.json --> click "Build IoT Edge Solution"

Any log messages given by the failure

Expected/desired behavior

Successful build

OS and Version?

Windows 10 Enterprise, Version 1709, OS Build 16299.551

Versions

VS Code v1.24.0, Docker version 18.03.1-ce, build 9ee9f40

Mention any other details that might be useful

1. The SenseHatDisplay and CameraCapture modules have both built successfully; I am only having problems with the ImageClassifierService module.
2. I've tried to build on two different networks (one was a mobile hotspot, the other was a corporate network with a proxy that I haven't had problems with in the past) and received the same error when trying with both networks.

Thank you in advance for your help!

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Use Pi camera

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful

Hello, does this work with the pi camera module (not usb)?

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

1.Clone the repo.
2.Update .env file with my container registry.
3.Build the entire solution by right-clicking on the deployment.template.json file
4.Right-click on the config/deployment.json.

Any log messages given by the failure

no message but the gui of VS Code shows "Run IoT Solution In Simulator"

Expected/desired behavior

Expected "Create Deployment for Single device" menu

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Windows10-Home, VS Code 1.64.1, raspbian stretch

Versions

Mention any other details that might be useful

According to the build&Push log, build was finished and pushed.
It says "The push refers to repository [my-name-registry.azurecr.io/imageclassifierservice]"

The last lines of the log:
9cb9d745cb43: Pushed
f27384c73acf: Pushed
0.2.17-arm32v7: digest: sha256:f10e607cb58dfb2ac660385530e545f81031b1e4db74b5efb37796ed159d47f5 size: 7011

When I checked my registry in Azure Portal, Activity Log menu does not show any log.
I can see three repositories: cameracapture, imageclassifierservice, sensehatdisplay.

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Clone this sample
Update the .env file with the values for your container registry and make sure that your docker engine has access to it
3.Build the entire solution by opening the control palette (Ctrl+Shift+P), select Build and push IoT Edge Solution (this can take a while...especially to build numpy and pillow...) and select the deployment.test-amd64.template.json manifest file
4.Deploy the solution to your device by right-clicking on the config/deployment.json file, select Create Deployment for Single device and choose your targeted device
verify module image-classifier-service are not running.
create module image-classifier-service failed in docker.

Any log messages given by the failure

upsquared@UP2:$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
2153c5a76718 mycapreg.azurecr.io/cameracapture:0.2.8-test-amd64 "python3 -u ./main.py" 6 minutes ago Up 2 seconds 0.0.0.0:5012->5012/tcp camera-capture
e8a3815db9c2 mcr.microsoft.com/azureiotedge-hub:1.0 "/bin/sh -c 'echo "$…" 25 minutes ago Up 4 seconds 443/tcp, 5671/tcp, 8883/tcp edgeHub
0cf73814128b mcr.microsoft.com/azureiotedge-agent:1.0 "/bin/sh -c 'echo "$…" 7 days ago Up 12 seconds edgeAgent
upsquared@UP2:$ sudo docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
2153c5a76718 mycapreg.azurecr.io/cameracapture:0.2.8-test-amd64 "python3 -u ./main.py" 6 minutes ago Up 9 seconds 0.0.0.0:5012->5012/tcp camera-capture
e8a3815db9c2 mcr.microsoft.com/azureiotedge-hub:1.0 "/bin/sh -c 'echo "$…" 25 minutes ago Up 10 seconds 443/tcp, 5671/tcp, 8883/tcp edgeHub
e7fae1986de1 mycapreg.azurecr.io/imageclassifierservice:0.2.5-amd64 "/bin/sh -c 'python …" 25 minutes ago Exited (132) 4 minutes ago image-classifier-service
0cf73814128b mcr.microsoft.com/azureiotedge-agent:1.0 "/bin/sh -c 'echo "$…" 7 days ago Up 19 seconds edgeAgent
upsquared@UP2:$ sudo docker logs -f image-classifier-service --tail 200
Illegal instruction (core dumped)
Illegal instruction (core dumped)
Illegal instruction (core dumped)
Illegal instruction (core dumped)
Illegal instruction (core dumped)
Illegal instruction (core dumped)
Illegal instruction (core dumped)
Illegal instruction (core dumped)
upsquared@UP2:$ sudo systemctl stop iotedge

upsquared@UP2:$ sudo docker run -it --rm mycapreg.azurecr.io/imageclassifierservice:0.2.5-amd64
Illegal instruction (core dumped)
upsquared@UP2:$ sudo docker run -it --rm mycapreg.azurecr.io/imageclassifierservice:0.2.5-amd64 bash

___ /________________________________ / /______ __
__ / _ _ _ __ _ / __ _ / / __ / __ _ | /| / /
_ / / / / / /( )/ // / / _ __/ _ / / // / |/ |/ /
// ___/// //// _/// // // _/__/|__/

WARNING: You are running this container as root, which can cause new files in
mounted volumes to be created as the root user on your host machine.

To avoid this, run the container by specifying your user's userid:

$ docker run -u $(id -u):$(id -g) args...

root@4a0538a0028b:/app# python3
Python 3.6.8 (default, Aug 20 2019, 17:12:48)
[GCC 8.3.0] on linux

import tensorflow as tf
Illegal instruction (core dumped)

Expected/desired behavior

OS and Version?

Linux ubuntu 18.04

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

1. Install Edge Runtime on Raspberry Pi 4.
2. Restarted Raspi and checked iotedge list with these results.
   
3. Checked on Azure Portal, IoT Hub and then Edge Devices and seeing these errors :
   

Any log messages given by the failure

Let me know if there is a log that would help.

Expected/desired behavior

I expected Edge Agent and Edge Hub to run on bootup of the Pi.

OS and Version?

Raspdian running on a Pi4

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Build IoT Edge Solution in Visual Studio Code (v1.25.1) on "deployment.template.json"

Any log messages given by the failure

Step 4/12 : RUN apt-get install -y libboost-python1.55.0
---> Running in c6...
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package libboost-python1.55.0
E: Couldn't find any package by regex 'libboost-python1.55.0'
The command '/bin/sh -c apt-get install -y libboost-python1.55.0' returned a non-zero code: 100

Expected/desired behavior

Successful build.

OS and Version?

Windows 10

Versions

latest

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

building camera module fail with back compatibility issue.

[ 9/12] RUN pip3 install --index-url=https://www.piwheels.org/simple -r arm32v7-requirements.txt:
#13 3.059 DEPRECATION: Python 3.5 reached the end of its life on September 13th, 2020. Please upgrade your Python as Python 3.5 is no longer maintained. pip 21.0 will drop support for Python 3.5 in January 2021. pip 21.0 will remove support for this functionality.

VSCode: 1.31.1
OS: windows10

steps:

Get started

To deploy the solution on a Raspberry Pi 3

From my windows PC:

1. Clone this sample
2. Update the .env file with the values for your container registry and make sure that your docker engine has access to it (create azure container registry and docker login in my pc)
3. Build the entire solution by right-clicking on the deployment.template.json file and select Build and push IoT Edge Solution (this can take a while...especially to build open-cv, numpy and pillow...)

Issue 1: It need to run 3 docker file for CameraCapture.arm32v7 & SenseHatDisplay.arm32v7 & ImageClassifierService.arm32v7 image,
When build CameraCapture.arm32v7 docker file , step5,6,7 will take 6 hours , only 70% compiled in 4 and a half hours, it is so slow. Can we improve performance for arm32v7 template?

4. Deploy the solution to your device by right-clicking on the config/deployment.json file, select Create Deployment for Single device and choose your targeted device

From my Raspberry pi 3
1.set up edge runtime for pi3
https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-linux-arm
2. setup my edge device connection string
HostName=czghub0214.azure-devices.net;DeviceId=pidevice;SharedAccessKey=orj1Nx1+UuALUIhjWijfm7gpOURAxk4il1Ai42nRR5U=

3. docker login in azure container registry
4. create camera-capture module failed after create deployment for single device on windows pc

• VSCode Version: 1.31.0
• OS Version: ubuntu 18.04
• Extension Version: 1.10.0-rc

Steps to Reproduce:

1. Clone this sample
2. Update the .env file with the values for your container registry and make sure that your docker engine has access to it
3. Build the entire solution by opening the control palette (Ctrl+Shift+P), select Build and push IoT Edge Solution (this can take a while...especially to build numpy and pillow...) and select the deployment.test-amd64.template.json manifest file (it includes a test video file to simulate a camera)
4. Deploy the solution to your device by right-clicking on the config/deployment.json file, select Create Deployment for Single device and choose your targeted device
5. Monitor the messages being sent to the Cloud by right-clicking on your device from the VS Code IoT Edge Extension and select Start Monitoring D2C Message

now D2C message can be send successfully, but it has some errors in edgeAgent logs

iot@iot-Lenovo:~$ sudo docker logs edgeAgent -f
[2019-02-15 03:32:38 : Starting Edge Agent
[02/15/2019 03:32:38.926 AM] Edge Agent Main()
2019-02-15 03:32:39.131 +00:00 [INF] - Starting module management agent.
2019-02-15 03:32:39.290 +00:00 [INF] - Version - 1.0.6.19913336 (8288bc9bd6f6e15295fea506cd3f99d7f6347a6a)
2019-02-15 03:32:39.290 +00:00 [INF] -
█████╗ ███████╗██╗ ██╗██████╗ ███████╗
██╔══██╗╚══███╔╝██║ ██║██╔══██╗██╔════╝
███████║ ███╔╝ ██║ ██║██████╔╝█████╗
██╔══██║ ███╔╝ ██║ ██║██╔══██╗██╔══╝
██║ ██║███████╗╚██████╔╝██║ ██║███████╗
╚═╝ ╚═╝╚══════╝ ╚═════╝ ╚═╝ ╚═╝╚══════╝

██╗ ██████╗ ████████╗ ███████╗██████╗ ██████╗ ███████╗
██║██╔═══██╗╚══██╔══╝ ██╔════╝██╔══██╗██╔════╝ ██╔════╝
██║██║ ██║ ██║ █████╗ ██║ ██║██║ ███╗█████╗
██║██║ ██║ ██║ ██╔══╝ ██║ ██║██║ ██║██╔══╝
██║╚██████╔╝ ██║ ███████╗██████╔╝╚██████╔╝███████╗
╚═╝ ╚═════╝ ╚═╝ ╚══════╝╚═════╝ ╚═════╝ ╚══════╝

2019-02-15 03:32:39.437 +00:00 [INF] - Edge agent attempting to connect to IoT Hub via Amqp_Tcp_Only...
2019-02-15 03:32:40.511 +00:00 [INF] - Created persistent store at /tmp/edgeAgent
2019-02-15 03:32:42.975 +00:00 [INF] - Edge agent connected to IoT Hub via Amqp_Tcp_Only.
2019-02-15 03:32:44.070 +00:00 [INF] - Deployment config in edge agent's desired properties is empty.
2019-02-15 03:32:44.079 +00:00 [ERR] - Error refreshing edge agent configuration from twin.
Microsoft.Azure.Devices.Edge.Agent.Core.ConfigSources.ConfigEmptyException: This device has an empty configuration for the edge agent. Please set a deployment manifest.
at Microsoft.Azure.Devices.Edge.Agent.IoTHub.EdgeAgentConnection.UpdateDeploymentConfig() in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.IoTHub/EdgeAgentConnection.cs:line 233
at Microsoft.Azure.Devices.Edge.Agent.IoTHub.EdgeAgentConnection.RefreshTwinAsync() in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.IoTHub/EdgeAgentConnection.cs:line 194
2019-02-15 03:32:44.653 +00:00 [INF] - Updated reported properties
2019-02-15 03:35:07.787 +00:00 [INF] - Plan execution started for deployment 2
2019-02-15 03:35:07.816 +00:00 [INF] - Executing command: "Command Group: (
[Create module image-classifier-service]
[Start module image-classifier-service]
)"
2019-02-15 03:35:07.818 +00:00 [INF] - Executing command: "Create module image-classifier-service"
2019-02-15 03:37:25.136 +00:00 [ERR] - Executing command for operation ["create"] failed.
System.Threading.Tasks.TaskCanceledException: A task was canceled.
at Microsoft.Azure.Devices.Edge.Util.Uds.HttpBufferedStream.ReadLineAsync(CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpBufferedStream.cs:line 62
at Microsoft.Azure.Devices.Edge.Util.Uds.HttpRequestResponseSerializer.SetResponseStatusLine(HttpResponseMessage httpResponse, HttpBufferedStream bufferedStream, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpRequestResponseSerializer.cs:line 119
at Microsoft.Azure.Devices.Edge.Util.Uds.HttpRequestResponseSerializer.DeserializeResponse(HttpBufferedStream bufferedStream, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpRequestResponseSerializer.cs:line 65
at Microsoft.Azure.Devices.Edge.Util.Uds.HttpUdsMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpUdsMessageHandler.cs:line 36
at System.Net.Http.HttpClient.FinishSendAsyncUnbuffered(Task1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts) at Microsoft.Azure.Devices.Edge.Agent.Edgelet.GeneratedCode.EdgeletHttpClient.CreateModuleAsync(String api_version, ModuleSpec module, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Edgelet/generatedCode/EdgeletHttpClient.cs:line 270 at Microsoft.Azure.Devices.Edge.Agent.Edgelet.ModuleManagementHttpClient.Execute[T](Func1 func, String operation)
at Microsoft.Azure.Devices.Edge.Agent.Edgelet.ModuleManagementHttpClient.CreateModuleAsync(ModuleSpec moduleSpec) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Edgelet/ModuleManagementHttpClient.cs:line 91
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 60
2019-02-15 03:37:25.226 +00:00 [ERR] - Executing command for operation ["Command Group: (
[Create module image-classifier-service]
[Start module image-classifier-service]
)"] failed.
System.Threading.Tasks.TaskCanceledException: A task was canceled.
at Microsoft.Azure.Devices.Edge.Util.Uds.HttpBufferedStream.ReadLineAsync(CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpBufferedStream.cs:line 62
at Microsoft.Azure.Devices.Edge.Util.Uds.HttpRequestResponseSerializer.SetResponseStatusLine(HttpResponseMessage httpResponse, HttpBufferedStream bufferedStream, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpRequestResponseSerializer.cs:line 119
at Microsoft.Azure.Devices.Edge.Util.Uds.HttpRequestResponseSerializer.DeserializeResponse(HttpBufferedStream bufferedStream, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpRequestResponseSerializer.cs:line 65
at Microsoft.Azure.Devices.Edge.Util.Uds.HttpUdsMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpUdsMessageHandler.cs:line 36
at System.Net.Http.HttpClient.FinishSendAsyncUnbuffered(Task1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts) at Microsoft.Azure.Devices.Edge.Agent.Edgelet.GeneratedCode.EdgeletHttpClient.CreateModuleAsync(String api_version, ModuleSpec module, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Edgelet/generatedCode/EdgeletHttpClient.cs:line 270 at Microsoft.Azure.Devices.Edge.Agent.Edgelet.ModuleManagementHttpClient.Execute[T](Func1 func, String operation)
at Microsoft.Azure.Devices.Edge.Agent.Edgelet.ModuleManagementHttpClient.CreateModuleAsync(ModuleSpec moduleSpec) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Edgelet/ModuleManagementHttpClient.cs:line 91
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 60
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 60
2019-02-15 03:37:25.229 +00:00 [ERR] - Step failed in deployment 2, continuing execution. Failure when running command Command Group: (
[Create module image-classifier-service]
[Start module image-classifier-service]
). Will retry in 00s.
2019-02-15 03:37:25.230 +00:00 [INF] - Executing command: "Command Group: (
[Create module edgeHub]
[Start module edgeHub]
)"
2019-02-15 03:37:25.230 +00:00 [INF] - Executing command: "Create module edgeHub"
2019-02-15 03:37:35.503 +00:00 [INF] - Executing command: "Start module edgeHub"
2019-02-15 03:37:37.193 +00:00 [INF] - Executing command: "Command Group: (
[Create module camera-capture]
[Start module camera-capture]
)"
2019-02-15 03:37:37.193 +00:00 [INF] - Executing command: "Create module camera-capture"
2019-02-15 03:39:12.173 +00:00 [INF] - Executing command: "Start module camera-capture"
2019-02-15 03:39:13.837 +00:00 [INF] - Plan execution ended for deployment 2
2019-02-15 03:39:13.839 +00:00 [ERR] - Edge agent plan execution failed.
System.AggregateException: One or more errors occurred. (A task was canceled.) ---> System.Threading.Tasks.TaskCanceledException: A task was canceled.
at Microsoft.Azure.Devices.Edge.Util.Uds.HttpBufferedStream.ReadLineAsync(CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpBufferedStream.cs:line 62
at Microsoft.Azure.Devices.Edge.Util.Uds.HttpRequestResponseSerializer.SetResponseStatusLine(HttpResponseMessage httpResponse, HttpBufferedStream bufferedStream, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpRequestResponseSerializer.cs:line 119
at Microsoft.Azure.Devices.Edge.Util.Uds.HttpRequestResponseSerializer.DeserializeResponse(HttpBufferedStream bufferedStream, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpRequestResponseSerializer.cs:line 65
at Microsoft.Azure.Devices.Edge.Util.Uds.HttpUdsMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpUdsMessageHandler.cs:line 36
at System.Net.Http.HttpClient.FinishSendAsyncUnbuffered(Task1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts) at Microsoft.Azure.Devices.Edge.Agent.Edgelet.GeneratedCode.EdgeletHttpClient.CreateModuleAsync(String api_version, ModuleSpec module, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Edgelet/generatedCode/EdgeletHttpClient.cs:line 270 at Microsoft.Azure.Devices.Edge.Agent.Edgelet.ModuleManagementHttpClient.Execute[T](Func1 func, String operation)
at Microsoft.Azure.Devices.Edge.Agent.Edgelet.ModuleManagementHttpClient.CreateModuleAsync(ModuleSpec moduleSpec) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Edgelet/ModuleManagementHttpClient.cs:line 91
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 60
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 60
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 87
--- End of inner exception stack trace ---
at Microsoft.Azure.Devices.Edge.Agent.Core.PlanRunners.OrderedRetryPlanRunner.<>c.b__7_0(List1 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 116 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 132 ---> (Inner Exception #0) System.Threading.Tasks.TaskCanceledException: A task was canceled. at Microsoft.Azure.Devices.Edge.Util.Uds.HttpBufferedStream.ReadLineAsync(CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpBufferedStream.cs:line 62 at Microsoft.Azure.Devices.Edge.Util.Uds.HttpRequestResponseSerializer.SetResponseStatusLine(HttpResponseMessage httpResponse, HttpBufferedStream bufferedStream, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpRequestResponseSerializer.cs:line 119 at Microsoft.Azure.Devices.Edge.Util.Uds.HttpRequestResponseSerializer.DeserializeResponse(HttpBufferedStream bufferedStream, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpRequestResponseSerializer.cs:line 65 at Microsoft.Azure.Devices.Edge.Util.Uds.HttpUdsMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpUdsMessageHandler.cs:line 36 at System.Net.Http.HttpClient.FinishSendAsyncUnbuffered(Task1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts)
at Microsoft.Azure.Devices.Edge.Agent.Edgelet.GeneratedCode.EdgeletHttpClient.CreateModuleAsync(String api_version, ModuleSpec module, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Edgelet/generatedCode/EdgeletHttpClient.cs:line 270
at Microsoft.Azure.Devices.Edge.Agent.Edgelet.ModuleManagementHttpClient.Execute[T](Func`1 func, String operation)
at Microsoft.Azure.Devices.Edge.Agent.Edgelet.ModuleManagementHttpClient.CreateModuleAsync(ModuleSpec moduleSpec) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Edgelet/ModuleManagementHttpClient.cs:line 91
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 60
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 60
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 87<---

2019-02-15 03:39:13.870 +00:00 [WRN] - Reconcile failed because of the an exception
System.AggregateException: One or more errors occurred. (A task was canceled.) ---> System.Threading.Tasks.TaskCanceledException: A task was canceled.
at Microsoft.Azure.Devices.Edge.Util.Uds.HttpBufferedStream.ReadLineAsync(CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpBufferedStream.cs:line 62
at Microsoft.Azure.Devices.Edge.Util.Uds.HttpRequestResponseSerializer.SetResponseStatusLine(HttpResponseMessage httpResponse, HttpBufferedStream bufferedStream, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpRequestResponseSerializer.cs:line 119
at Microsoft.Azure.Devices.Edge.Util.Uds.HttpRequestResponseSerializer.DeserializeResponse(HttpBufferedStream bufferedStream, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpRequestResponseSerializer.cs:line 65
at Microsoft.Azure.Devices.Edge.Util.Uds.HttpUdsMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpUdsMessageHandler.cs:line 36
at System.Net.Http.HttpClient.FinishSendAsyncUnbuffered(Task1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts) at Microsoft.Azure.Devices.Edge.Agent.Edgelet.GeneratedCode.EdgeletHttpClient.CreateModuleAsync(String api_version, ModuleSpec module, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Edgelet/generatedCode/EdgeletHttpClient.cs:line 270 at Microsoft.Azure.Devices.Edge.Agent.Edgelet.ModuleManagementHttpClient.Execute[T](Func1 func, String operation)
at Microsoft.Azure.Devices.Edge.Agent.Edgelet.ModuleManagementHttpClient.CreateModuleAsync(ModuleSpec moduleSpec) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Edgelet/ModuleManagementHttpClient.cs:line 91
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 60
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 60
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 87
--- End of inner exception stack trace ---
at Microsoft.Azure.Devices.Edge.Agent.Core.PlanRunners.OrderedRetryPlanRunner.<>c.b__7_0(List1 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 116 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 132 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 143 ---> (Inner Exception #0) System.Threading.Tasks.TaskCanceledException: A task was canceled. at Microsoft.Azure.Devices.Edge.Util.Uds.HttpBufferedStream.ReadLineAsync(CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpBufferedStream.cs:line 62 at Microsoft.Azure.Devices.Edge.Util.Uds.HttpRequestResponseSerializer.SetResponseStatusLine(HttpResponseMessage httpResponse, HttpBufferedStream bufferedStream, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpRequestResponseSerializer.cs:line 119 at Microsoft.Azure.Devices.Edge.Util.Uds.HttpRequestResponseSerializer.DeserializeResponse(HttpBufferedStream bufferedStream, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpRequestResponseSerializer.cs:line 65 at Microsoft.Azure.Devices.Edge.Util.Uds.HttpUdsMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpUdsMessageHandler.cs:line 36 at System.Net.Http.HttpClient.FinishSendAsyncUnbuffered(Task1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts)
at Microsoft.Azure.Devices.Edge.Agent.Edgelet.GeneratedCode.EdgeletHttpClient.CreateModuleAsync(String api_version, ModuleSpec module, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Edgelet/generatedCode/EdgeletHttpClient.cs:line 270
at Microsoft.Azure.Devices.Edge.Agent.Edgelet.ModuleManagementHttpClient.Execute[T](Func`1 func, String operation)
at Microsoft.Azure.Devices.Edge.Agent.Edgelet.ModuleManagementHttpClient.CreateModuleAsync(ModuleSpec moduleSpec) in /home/vsts/work/1/s/edge-agent/src/Microsoft.Azure.Devices.Edge.Agent.Edgelet/ModuleManagementHttpClient.cs:line 91
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 60
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 60
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 87<---

2019-02-15 03:39:14.291 +00:00 [INF] - Updated reported properties
2019-02-15 03:39:19.331 +00:00 [INF] - Module 'camera-capture' scheduled to restart after 10s (05s left).
2019-02-15 03:39:19.337 +00:00 [INF] - Plan execution started for deployment 2
2019-02-15 03:39:19.338 +00:00 [INF] - Executing command: "Command Group: (
[Stop module image-classifier-service]
[Start module image-classifier-service]
[Saving image-classifier-service to store]
)"
2019-02-15 03:39:19.338 +00:00 [INF] - Executing command: "Stop module image-classifier-service"
2019-02-15 03:39:19.359 +00:00 [INF] - Executing command: "Start module image-classifier-service"
2019-02-15 03:39:20.898 +00:00 [INF] - Executing command: "Saving image-classifier-service to store"
2019-02-15 03:39:20.904 +00:00 [INF] - Plan execution ended for deployment 2
2019-02-15 03:39:21.330 +00:00 [INF] - Updated reported properties
2019-02-15 03:39:26.342 +00:00 [INF] - Plan execution started for deployment 2
2019-02-15 03:39:26.342 +00:00 [INF] - Executing command: "Command Group: (
[Stop module camera-capture]
[Start module camera-capture]
[Saving camera-capture to store]
)"
2019-02-15 03:39:26.342 +00:00 [INF] - Executing command: "Stop module camera-capture"
2019-02-15 03:39:26.343 +00:00 [INF] - Executing command: "Start module camera-capture"
2019-02-15 03:39:27.912 +00:00 [INF] - Executing command: "Saving camera-capture to store"
2019-02-15 03:39:27.912 +00:00 [INF] - Plan execution ended for deployment 2
2019-02-15 03:39:28.330 +00:00 [INF] - Updated reported properties
2019-02-15 03:39:33.763 +00:00 [INF] - Updated reported properties

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Upon invoking "Build IoT Edge Solution" command from VS Code

Any log messages given by the failure

Sending build context to Docker daemon 12.08MB
Step 1/12 : FROM mohaseeb/raspberrypi3-python-opencv:latest
Get https://registry-1.docker.io/v2/mohaseeb/raspberrypi3-python-opencv/manifests/latest: unauthorized: incorrect username or password

Expected/desired behavior

Build should succeed

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Windows 10, VSCode 1.25.1, Docker for Windows Community Edition Version 18.06.0-ce-win72 (19098)
Channel: stable

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

• [ x] bug report
• feature request
• documentation issue or request
• regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

I'm trying to run this demo on a linux PC and I've created an container registry and uploaded both containers (Image and camera) and also a Linux VM to use as a device. For some reason when I deploy the IoT Edge solution the camera module never starts, even the container does not start or throw any error. And when I start to monitor D2C messages, nothing happens.

Any log messages given by the failure

OS and Version?

Ubuntu 16.04

I am confused about the document of deploying the solution on Raspberry Pi 3.
The doc tell user to build and push IoT edge solution on my mac or windows PC.
Why not from my raspberry pi ? or we need to build modules on my remote raspberry pi.

Can you confirm bellow steps are right ?

Test step:
To deploy the solution on a Raspberry Pi 3

From your mac or PC:

1. Clone this sample and open it in VS Code (VS Code should install edge extension)
2. Open VS Code user setting, enable environment variables for the command executor and Azure IoT Edge terminals by adding the snippet below. In my case, my Pi’s IP is 192.168.86.74, you need change that with your IP or you can also use hostname.

3. Reload VS Code window. Type and run Reload Window in Command Palette.
4. We will soon use Raspberry Pi to build module images, switch your IoT Edge Default Platform to arm32v7 in the status bar.

5. Update the .env file with the values for your container registry
6. Right-clicking on the deployment.template.json file and select Build and push IoT Edge Solution
7. Deploy the solution to your device by right-clicking on the config/deployment.json file, select Create Deployment for Single device and choose your targeted device
8. Monitor the messages being sent to the Cloud by right-clicking on your device from the VS Code IoT Edge Extension and select Start Monitoring D2C Message
   Note: To stop Device to Cloud (D2C) monitoring, use the Azure IoT Hub: Stop monitoring D2C messages command from the Command Palette (Ctrl+Shift+P).

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ x] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Is it possible to increase the FPS of the ImageServer to 30 so looks like a live stream ?
If this will not be implemented could you give directions on how to change the code in order to achieve this?

Would be a great feature to demonstrate custom vision.

OS and Version?

Rasbian 9.6

Versions

Mention any other details that might be useful

Please provide us with the following information:

This issue is for a: (mark with an x)

- [X ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

install this demo on bare new RPi3

Any log messages given by the failure

pi@rpisharon:~ $ sudo docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
dc54b64af863 microsoft/azure-cli "/bin/sh -c bash" 5 minutes ago Exited (1) 5 minutes ago determined_pasteur
d66e9433493a mcr.microsoft.com/azureiotedge-hub:1.0 "/bin/sh -c 'echo "$…" About an hour ago Up 19 minutes 443/tcp, 5671/tcp, 8883/tcp edgeHub
18982ed826da iotmtcilacr.azurecr.io/imageclassifierservice:0.2.0-amd64 "/bin/sh -c 'python …" About an hour ago Exited (1) 2 minutes ago image-classifier-service
f7a8bffe4a31 iotmtcilacr.azurecr.io/cameracapture:0.2.6-test-amd64 "python -u ./main.py" About an hour ago Exited (1) 2 minutes ago camera-capture
617c9c9ff941 mcr.microsoft.com/azureiotedge-agent:1.0 "/bin/sh -c 'echo "$…" About an hour ago Up 20 minutes edgeAgent
pi@rpisharon:~ $ sudo docker logs f7
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
pi@rpisharon:~ $ sudo docker logs 18
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"
standard_init_linux.go:190: exec user process caused "exec format error"

Expected/desired behavior

both modules should run

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Linux rpisharon 4.14.52-v7+ #1123 SMP Wed Jun 27 17:35:49 BST 2018 armv7l GNU/Linux

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

This issue is for a: (mark with an x)

- [X ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

https://dev.to/azure/creating-an-image-recognition-solution-with-azure-iot-edge-and-azure-cognitive-services-4n5i
https://dev.to/azure/azure-iot-edge-on-raspberry-pi-buster-plus-tips-for-raspberry-pi-4-22nn#installing-docker-on-raspbian-buster
Push the camera-capture and image-classifier-service to raspberry-pi.

Any log messages given by the failure

sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a2eeea4a7001 kenteken.azurecr.io/imageclassifierservice:0.2.5-arm32v7 "/usr/bin/entry.sh p…" 2 hours ago Up About an hour 80/tcp image-classifier-service
f9b9823deb86 kenteken.azurecr.io/cameracapture:0.2.8-arm32v7 "python3 -u ./main.py" 3 hours ago Up About an hour 0.0.0.0:5012->5012/tcp camera-capture
316723a7676f mcr.microsoft.com/azureiotedge-hub:1.0 "/bin/sh -c 'echo "$…" 36 hours ago Up About an hour 443/tcp, 5671/tcp, 8883/tcp edgeHub
20d6fbb3cd59 mcr.microsoft.com/azureiotedge-agent:1.0 "/bin/sh -c 'echo "$…" 40 hours ago Up About an hour edgeAgent

sudo docker logs camera-capture
__sendFrameForProcessing Excpetion -HTTPConnectionPool(host='image-classifier-service', port=80): Max retries exceeded with url: /image (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x6c6b07f0>: Failed to establish a new connection: [Errno -2] Name or service not known',))

Visual Studio Code : Start monitoring message arrived in built-in endpoint for device
IoTHubMonitor] Start monitoring message arrived in built-in endpoint for device [rpi] ...
[IoTHubMonitor] Created partition receiver [0] for consumerGroup [$Default]
[IoTHubMonitor] Created partition receiver [1] for consumerGroup [$Default]
[IoTHubMonitor] [10:38:20 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.000009690000297268853,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:38:20 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.000008469999556837138,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:38:29 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.000005110000074637355,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:38:29 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.000004510000053414842,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:38:37 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.0000071800000114308205,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:38:37 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.000007529999948019395,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:38:46 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.000009389999831910245,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:38:46 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.000009870000212686136,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:38:54 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.00001024999983201269,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:38:54 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.0000071200001912075095,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:39:03 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.000008170000000973232,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:39:03 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.000004009999884146964,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:39:11 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.000005689999852620531,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:39:12 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.000005859999873791821,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:39:20 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.0000057399997785978485,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:39:21 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.000004980000085197389,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:39:29 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.000009530000170343556,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:39:29 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.000009170000339508988,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:39:38 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.000010460000339662656,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:39:38 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.0000042100000428035855,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:39:46 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.000006509999820991652,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:39:47 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.000008390000402869191,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:39:55 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.0000052099999265919905,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:39:56 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.0000061499999901570845,
"Tag": "banaa"
}
]
[IoTHubMonitor] [10:40:04 AM] Message received from [rpi/camera-capture]:
[
{
"Probability": 0.000006320000011328375,
"Tag": "banaa"
}
]

Expected/desired behavior

When holding a banana or apple in front of the camera. it should be detected.

OS and Version?

Raspbian Buster on PI with docker and container raspbian stretch.
Visual studio code on ubuntu 18

Mention any other details that might be useful

It's my first post. so sorry if not everything is filled in correct.
Trying to build an image recognition with a pi and camera.
When I enable monitoring endpoint I get a continue tagged images while nothing is in front. The same with the log messages with the failure. No recognition at all.
In Azure on IoT hub. Edges are all succesfully deployed.

---

Thanks! We'll be in touch soon.

Can the following readme be added to the repo or an external link provided?

I deployed this solution over 30 times, with success, on my Raspberry Pi 3 over several months now. Just recently (this week) when i build and deployed the solution again the "ImageClassifierService" won't process any images anymore. Tested it with postman and it returns "Error processing image".

If i look at the logs of the module it say's:

/usr/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: compiletime version 3.4 of module 'tensorflow.python.framework.fast_tensor_util' does not match runtime version 3.5
return f(*args, **kwds)

/usr/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: builtins.type size changed, may indicate binary incompatibility. Expected 432, got 412
return f(*args, **kwds)

WARNING:tensorflow:From /app/predict.py:28: FastGFile.init (from tensorflow.python.platform.gfile) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.gfile.GFile.

Loading model...Success!
Loading labels...2 found. Success!

• Serving Flask app "app" (lazy loading)
• Environment: production
  WARNING: Do not use the development server in a production environment.
  Use a production WSGI server instead.
• Debug mode: off
• Running on http://0.0.0.0:80/ (Press CTRL+C to quit)

2019-03-08 01:52:14.047760: E tensorflow/core/common_runtime/executor.cc:624] Executor failed to create kernel. Not found: No registered '_FusedConv2D' OpKernel for CPU devices compatible with node {{node conv1/conv1}} Registered: "no registered kernels"

Can anybody help me with this? I downloaded and rebuild the entire solution a couple of times with no success.

Is it maybe because tensorflow just released a new build and in arm32v7-requirements.txt there is no version specified for tensorflow? I'm guessing tensorflow 1.13.1 is giving problems and tensorflow 1.12.0 works. Not tested yet.

I tried to use my exported custom vision file and followed this guide
https://docs.microsoft.com/en-us/azure/iot-edge/tutorial-deploy-custom-vision#prerequisites

1. the export zip did not generate azureml folder
2. docker file declares pip install flask

Log when build and push
{
Looking in indexes: https://www.piwheels.org/simple
Collecting flask
Downloading https://www.piwheels.org/simple/flask/Flask-1.1.2-py2.py3-none-any.whl (94 kB)
ERROR: Could not find a version that satisfies the requirement pillow (from versions: none)
ERROR: No matching distribution found for pillow
The command '/bin/sh -c pip install flask pillow --index-url 'https://www.piwheels.org/simple'' returned a non-zero code: 1
}

I build and pushed it anyway and deployed in iot edge. camcapture and classifier are deployed but no report from device. device reports edgeagent and edgehub. Im guessing this error is the reason my modules aren't showing in my raspi

Dear our current project it is developed 100% on C#language and Windows 10 IoT Core.
Any one has migrated current project to C# language.
Any alert about run this way?

Thanks
Kind regards

Please provide us with the following information:

This issue is for a: (mark with an x)

- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Only difference in the project as opposed to what was demonstrated in the YouTube video is that I am using an on-board camera on the Raspi3

Any log messages given by the failure

OpenCV(3.4.1) Error: Assertion failed (ssize.width > 0 && ssize.height > 0) in resize, file /opencv/opencv-3.4.1/modules/imgproc/src/resize.cpp, line 4044
Original frame size: 0x0
Frame rate (FPS): 0
Frame number: 1
Time to capture (+ straighten up) a frame: 0 ms
Traceback (most recent call last):
File "./main.py", line 125, in
main(VIDEO_PATH, IMAGE_PROCESSING_ENDPOINT, IMAGE_PROCESSING_PARAMS, SHOW_VIDEO, VERBOSE, LOOP_VIDEO, CONVERT_TO_GRAY, RESIZE_WIDTH, RESIZE_HEIGHT, ANNOTATE)
File "./main.py", line 94, in main
cameraCapture.start()
File "/CameraCapture.py", line 162, in start
preprocessedFrame = cv2.resize(frame, (self.resizeWidth, self.resizeHeight))
cv2.error: OpenCV(3.4.1) /opencv/opencv-3.4.1/modules/imgproc/src/resize.cpp:4044: error: (-215) ssize.width > 0 && ssize.height > 0 in function resize

Expected/desired behavior

It seems that the OpenCV2 module is not detecting an input camera stream. Not sure if I am using an on-board camera as opposed to a USB Camera is the problem.

In any case, I am using the test video: AppleAndBanana.mp4. Here are my createOptions:
Camera Capture Azure IoT Edge Module. Press Ctrl-C to exit.
Initialising the camera capture with the following parameters:

• Video path: /home/pi/share/AppleAndBanana.mp4
• Image processing endpoint: http://127.0.0.1:80/
• Image processing params: ""
• Show video: False
• Loop video: True
• Convert to gray: False
• Resize width: 256
• Resize height: 256
• Annotate: False
• Send processing results to hub: True

OS and Version?

Raspberry Pi3 with VS Code
For the camera capture module, I am pulling the image from ebertraacr.azurecr.io/cameracapture:0.2.5-arm32v7

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Annotate function does not work for object detection, video stream will no be displayed if you set annotate to TRUE.

Minimal steps to reproduce

Set annotate Attribute to True in CameraCapture.py
Add "ANNOTATE":{"value": "True"} to CameraCapture module env ind deployment.template.json

Any log messages given by the failure

No logs but inside the Code there is a TODO:

Expected/desired behavior

Should Display Object Detection Boundry Box on Image Server

OS and Version?

Rasbian 9.6

Versions

Mention any other details that might be useful

I had to change the dockerfile of the CameraCapture module for it to work

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Clone repo
Change deployment.template.json to AMD64 version
Build and push IoT solution
Let containers run and see image-classifier-service fails
iotedge logs image-classifier-service

Any log messages given by the failure

Traceback (most recent call last):
File "app.py", line 15, in
from predict import initialize, predict_image, predict_url
File "/app/predict.py", line 22, in
graph_def = tf.GraphDef()
AttributeError: module 'tensorflow' has no attribute 'GraphDef'

Expected/desired behavior

It works with included Dockerfile

OS and Version?

Ubuntu 18.04 and Windows

Versions

Mention any other details that might be useful

Can be fixed by changing the Dockerfile to use a different base image and then install fixed tensorflow 1.12.0 and then including the various apt install for python dependencies.
#FROM tensorflow/tensorflow:latest-py3
FROM ubuntu:xenial

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Attempt to use Docker container downloaded from Custom Vision, with general compact model

Any log messages given by the failure

2021-04-25 04:52:59.069641: module 'mscviplib' has no attribute 'GetImageMetadata'
calling

Expected/desired behavior

Should run inference on a photo or URL

OS and Version?

NAME="Ubuntu"
VERSION="18.04.5 LTS (Bionic Beaver)"

Versions

Most recent version of mscviplib

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [X] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Deployment to Raspberry Pi 4

Any log messages given by the failure

Expected/desired behavior

Expect to follow the process as described to deploy a custom vision solution to an RPi 4. Are there known issues with deployment to a RPi 4?

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Raspian 4.19

Versions

Mention any other details that might be useful

This is just an inquiry as to any known issues. Is there a plan to update this demo to use RPi4?:

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [X] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Train and export a new model in Custom Vision
Try to run this model using the ImageClassifer module

Any log messages given by the failure

Expected/desired behavior

Works as before

Versions

Mention any other details that might be useful

New models exported as Tensorflow .pb files appear to know have an input layer size of 224 whereas previously this was 227. In this code the 227 is hardcoded in so newly exported models have stopped working.

Have this issue fixed in my code and will create a pull request. Fix is to extend initialize() to use the shape of the input layer:

def initialize():
    print('Loading model...',end=''),
    with tf.gfile.GFile(filename, 'rb') as f:
        graph_def.ParseFromString(f.read())
        tf.import_graph_def(graph_def, name='')
        input_tensor = tf.get_default_graph().get_tensor_by_name("Placeholder:0")
        network_input_size = int(input_tensor.get_shape()[1])
        print("Adjusted network input size to " + str(network_input_size))
    print('Success!')
    print('Loading labels...', end='')
    with open(labels_filename, 'rt') as lf:
        for l in lf:
            l = l[:-1]
            labels.append(l)
    print(len(labels), 'found. Success!')

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [x] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Any log messages given by the failure

Expected/desired behavior

Thank you for the great repo! The new SDK azure-iot-device not azure-iot-device-client supports and suggests using async requests. It would be great to get the repo updated for the new release. (I am struggling to get it to work).

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

SenseHatDisplay --> module.json --> Build IoT Edge Image Module

Any log messages given by the failure

Sending build context to Docker daemon 22.02kB
Step 1/13 : FROM resin/raspberrypi3-debian:stretch
---> 6e243c4c7eeb
Step 2/13 : RUN [ "cross-build-start" ]
---> Using cache
---> 72b842a27eb4
Step 3/13 : RUN apt-get update && apt-get upgrade && apt-get install -y python3 python3-pip wget build-essential
libjpeg-dev python3-dev zlib1g-dev
---> Using cache
---> 620b8d6a5315
Step 4/13 : COPY /build/arm32v7-requirements.txt ./
---> Using cache
---> b97a1d0258c5
Step 5/13 : RUN pip3 install --upgrade pip
---> Running in ce3ea1127d29
Exception:
Traceback (most recent call last):
File "/usr/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/connectionpool.py", line 594, in urlopen
chunked=chunked)
File "/usr/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/connectionpool.py", line 350, in _make_request
self._validate_conn(conn)
File "/usr/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/connectionpool.py", line 837, in validate_conn
conn.connect()
File "/usr/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/connection.py", line 323, in connect
ssl_context=context)
File "/usr/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/util/ssl.py", line 324, in ssl_wrap_socket
return context.wrap_socket(sock, server_hostname=server_hostname)
File "/usr/lib/python3.5/ssl.py", line 385, in wrap_socket
_context=self)
File "/usr/lib/python3.5/ssl.py", line 760, in init
self.do_handshake()
File "/usr/lib/python3.5/ssl.py", line 996, in do_handshake
self._sslobj.do_handshake()
File "/usr/lib/python3.5/ssl.py", line 641, in do_handshake
self._sslobj.do_handshake()
OSError: [Errno 0] Error

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pip/basecommand.py", line 215, in main
status = self.run(options, args)
File "/usr/lib/python3/dist-packages/pip/commands/install.py", line 353, in run
wb.build(autobuilding=True)
File "/usr/lib/python3/dist-packages/pip/wheel.py", line 749, in build
self.requirement_set.prepare_files(self.finder)
File "/usr/lib/python3/dist-packages/pip/req/req_set.py", line 380, in prepare_files
ignore_dependencies=self.ignore_dependencies))
File "/usr/lib/python3/dist-packages/pip/req/req_set.py", line 487, in _prepare_file
req_to_install, finder)
File "/usr/lib/python3/dist-packages/pip/req/req_set.py", line 428, in _check_skip_installed
req_to_install, upgrade_allowed)
File "/usr/lib/python3/dist-packages/pip/index.py", line 465, in find_requirement
all_candidates = self.find_all_candidates(req.name)
File "/usr/lib/python3/dist-packages/pip/index.py", line 423, in find_all_candidates
for page in self._get_pages(url_locations, project_name):
File "/usr/lib/python3/dist-packages/pip/index.py", line 568, in _get_pages
page = self._get_page(location)
File "/usr/lib/python3/dist-packages/pip/index.py", line 683, in _get_page
return HTMLPage.get_page(link, session=self.session)
File "/usr/lib/python3/dist-packages/pip/index.py", line 792, in get_page
"Cache-Control": "max-age=600",
File "/usr/share/python-wheels/requests-2.12.4-py2.py3-none-any.whl/requests/sessions.py", line 501, in get
return self.request('GET', url, **kwargs)
File "/usr/lib/python3/dist-packages/pip/download.py", line 386, in request
return super(PipSession, self).request(method, url, *args, **kwargs)
File "/usr/share/python-wheels/requests-2.12.4-py2.py3-none-any.whl/requests/sessions.py", line 488, in request
resp = self.send(prep, **send_kwargs)
File "/usr/share/python-wheels/requests-2.12.4-py2.py3-none-any.whl/requests/sessions.py", line 609, in send
r = adapter.send(request, **kwargs)
File "/usr/share/python-wheels/CacheControl-0.11.7-py2.py3-none-any.whl/cachecontrol/adapter.py", line 47, in send
resp = super(CacheControlAdapter, self).send(request, **kw)
File "/usr/share/python-wheels/requests-2.12.4-py2.py3-none-any.whl/requests/adapters.py", line 423, in send
timeout=timeout
File "/usr/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/connectionpool.py", line 643, in urlopen
_stacktrace=sys.exc_info()[2])
File "/usr/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/util/retry.py", line 315, in increment
total -= 1
TypeError: unsupported operand type(s) for -=: 'Retry' and 'int'
The command '/bin/sh -c pip3 install --upgrade pip' returned a non-zero code: 2

Expected/desired behavior

Successful build ;-)

OS and Version?

Windows 10 (10.0.14393)

Versions

Visual Studio Code (v1.25.1), Docker for Windows 18.06.0-ce-win72 (19098), Alpine:latest,
Latest Commit (c317891)

Mention any other details that might be useful

Failed 2 times (for arm32v7).

---

Thanks! We'll be in touch soon.

This issue is for a:

- [X] bug report 
- [ ] feature request
- [ ] documentation issue or request
- [X] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Build the arm32v7 Docker file. It will pull the latest version of Raspbian (Buster) from balenalib. The docker file will fail to build when it gets to the piwheels packages, which doesn't have Buster support yet.

Any log messages given by the failure

Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting opencv-python
  ERROR: Could not find a version that satisfies the requirement opencv-python (from versions: none)
ERROR: No matching distribution found for opencv-python

Expected/desired behavior

Docker build completes

OS and Version?

Windows 10. Raspbian Buster

Details

As I was writing up this issue I noticed that the piwheels maintainer added Buster support over the weekend. However, I think it makes sense for the sample to specify a version/tag of Raspbian in the Docker file so others don't run into the problem I did last week - that of a failing build due to out-of-date dependencies.

When I do build and push to IoT hub from VS Code. I get the following error:

E: You don't have enough free space in /var/cache/apt/archives/.

I did df-h on my Raspberry device and got the following:

Filesystem Size Used Avail Use% Mounted on
/dev/root 30G 5.1G 23G 19% /
devtmpfs 460M 0 460M 0% /dev
tmpfs 464M 13M 452M 3% /dev/shm
tmpfs 464M 36M 429M 8% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 464M 0 464M 0% /sys/fs/cgroup
/dev/mmcblk0p1 44M 22M 22M 51% /boot
tmpfs 93M 4.0K 93M 1% /run/user/1000

so it does not seems like I do not have space.
the version of Raspbian is :
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
Also I am trying to push from VS code installed on Windows 10.

Any help will be appreciate it.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [X ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

OS and Version?

Windows 10.
Docker 18.09.2
VS Code 1.32.3
VS 2017 Enterprise 15.8.1

Minimal steps to reproduce

I´m gettingan error when trying to build the solution and it seems to be related to CamerCapture module. If i try Docker build one-by-one SenseHatDisplay and ImageClassifier complets without errors.

First steps I´ve done to get forward is to replace "resin/raspberrypi3-python:2.7" with "balenalib/raspberrypi3-python:2.7"(resin repository seems to be deprecated?) and changed verison libboost-python to 1.58.0(got a version not found error).

Any log messages given by the failure

The log output is quite large, but I´ve tried to provied the most important parts here:

Failed building wheel for numpy
Running setup.py clean for numpy
Complete output from command /usr/local/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-install-WbCL8L/numpy/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" clean --all:
Running from numpy source directory.

setup.py clean is not supported, use one of the following instead:

- `git clean -xdf` (cleans all files)
- `git clean -Xdf` (cleans all versioned files, doesn't touch
                    files that aren't checked into the git repo)

Add --force to your command to use it anyway if you must (unsupported).

Failed cleaning build dir for numpy
Failed to build numpy
Installing collected packages: numpy, certifi, idna, chardet, urllib3, requests, azure-iothub-device-client
Running setup.py install for numpy: started
Running setup.py install for numpy: finished with status 'error'
Complete output from command /usr/local/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-install-WbCL8L/numpy/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-record-QYzXl2/install-record.txt --single-version-externally-managed --compile:
Running from numpy source directory.

Note: if you need reliable uninstall behavior, then install
with pip instead of using `setup.py install`:

  - `pip install .`       (from a git repo or downloaded source
                           release)
  - `pip install numpy`   (last NumPy release on PyPi)

........

  source = func(extension, build_dir)
  File "numpy/core/setup.py", line 667, in get_mathlib_info
    raise RuntimeError("Broken toolchain: cannot link a simple C program")
RuntimeError: Broken toolchain: cannot link a simple C program

----------------------------------------

Command "/usr/local/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-install-WbCL8L/numpy/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-record-QYzXl2/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-install-WbCL8L/numpy/
The command '/bin/sh -c pip install --upgrade pip && pip install --upgrade setuptools && pip install -r arm32v7-requirements.txt' returned a non-zero
code: 1

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [X] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

OS and Version?

Raspberry Pi3 Arm32

I couldnt get the CameraCapture module to send images to a listening ImageClassifier module by sending to the container hostname (http://imageClassifier:80/image)

Further digging into docker inspect azure-iot-edge reveals a gateway IP Address into the config of iotEdge runtime

"Config":[{"Subnet": "172.18.0.0/16","Gateway":"172.18.0.1"}]

What this means and changes into my createOptions of my CameraCapture module to reflect that the image processing endpoint is actually the gateway address
{"Env":["VIDEO_PATH=./AppleAndBanana.mp4","IMAGE_PROCESSING_ENDPOINT=http://172.18.0.1:80/image","VERBOSE=TRUE","RESIZE_WIDTH=256","RESIZE_HEIGHT=256"]}

From there, communications between both modules happen smoothly.

Not sure if there is a better way to do this but this is a workaround for now.

---

Thanks! We'll be in touch soon.

• [x ] documentation issue or request

Minimal steps to reproduce

I have installed an azure cli container on my pi following https://github.com/gtrifonov/raspberry-pi-alpine-azure-cli. This works great. I'm trying to develop a demo for a class where students will only have a pi - which i can't get VS to run on. What does VS do when you right click launch it? If it is an az cli command, I could just run it from the container.

Any log messages given by the failure

I tried using the RPI.json template as a deployment but got the following error
# az iot edge deployment create --content deployment.template.RPI.json --deployment-id texas
--login "HostName=myiothub.azure-devices.net;SharedAccessKeyName=iothubowner;DeviceId=mydeviceid;SharedAccessKey=redacted"

but it errors with

Unauthorized
I was able to get this working but doing an az login and using --hub-name myhubname instead of --login string`
However, nothing is running on my PI. Still missing a step.

Expected/desired behavior

I would expect there to be an azure cli method for deploying the template in case VS is not available.

OS and Version?

Laptop is a Mac. PI is raspbian 3+ B.

Versions

Pulling latest github default branch

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Cloned the sample, updated env, built and pushed the deployment.template.json, created the deployment for my edge device. Modules are being deployed to the device but it seems like the Camera Capture Module can't establish a connection to the Image Classifier Service.

Any log messages given by the failure

Camera Capture Module:

Python 2.7.15 (default, Jun 22 2018, 18:43:23)
[GCC 4.9.2]

Camera Capture Azure IoT Edge Module. Press Ctrl-C to exit.
ImageServer::Started.
Error: Time:Tue Dec 4 17:41:14 2018 File:/usr/sdk/src/c/c-utility/adapters/tlsio_openssl.c Func:send_handshake_bytes Line:661 error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Error: Time:Tue Dec 4 17:41:14 2018 File:/usr/sdk/src/c/c-utility/adapters/tlsio_openssl.c Func:send_handshake_bytes Line:661 error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Error: Time:Tue Dec 4 17:41:16 2018 File:/usr/sdk/src/c/c-utility/adapters/tlsio_openssl.c Func:send_handshake_bytes Line:661 error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Error: Time:Tue Dec 4 17:41:20 2018 File:/usr/sdk/src/c/c-utility/adapters/tlsio_openssl.c Func:send_handshake_bytes Line:661 error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Error: Time:Tue Dec 4 17:41:28 2018 File:/usr/sdk/src/c/c-utility/adapters/tlsio_openssl.c Func:send_handshake_bytes Line:661 error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Error: Time:Tue Dec 4 17:41:44 2018 File:/usr/sdk/src/c/c-utility/adapters/tlsio_openssl.c Func:send_handshake_bytes Line:661 error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

Expected/desired behavior

Running custom vision service.

OS and Version?

Raspbian stretch 9.6

Mention any other details that might be useful

It seems like the SenseHatDisplay module is not pushed to the Azure Container Registry and therefore can't be found by the Edge Device. However, I don't have such a display on my pi anyway so I don't really care about that module.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Services section of Readme and "To deploy the solution on a Raspberry Pi 3"
I cannot find how to create an Azure Container Registry for this specific environment in detail.
I found
https://docs.microsoft.com/en-us/azure/container-registry/container-registry-get-started-portal
but it is for hello-world image.
Could you tell me how to prepare Custom Vision project in detail.

Any log messages given by the failure

nothing and just question

Expected/desired behavior

instruction in detail

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Windows8.1 and Raspbian stretch(9) and not with SenseHat

Versions

Mention any other details that might be useful

I searched any other method for my question but nothing appeared. Sorry for making this issue.

---

Thanks! We'll be in touch soon.

Hi,

when i try to build and push the solution i get error:

Sending build context to Docker daemon 12.09MB
Step 1/12 : FROM resin/raspberrypi3-python:2.7
Get https://registry-1.docker.io/v2/resin/raspberrypi3-python/manifests/2.7: unauthorized: incorrect username or password

Please help.

moduleContent should be updated to modulesContent in deployment.template.json and deployment.test-amd64.template.json

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ X] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Just wondering how many FPS did you have on a raspberry pi 3 b + ?

To deploy the solution on an x64 PC
From my ubuntu 18.04:

1. Clone this sample
2. Update the .env file with the values for your container registry and make sure that your docker engine has access to it
   3.Build the entire solution by opening the control palette (Ctrl+Shift+P), select Build and push IoT Edge Solution (this can take a while...especially to build numpy and pillow...) and select the deployment.test-amd64.template.json manifest file
   4.Deploy the solution to your device by right-clicking on the config/deployment.json file, select Create Deployment for Single device and choose your targeted device
3. verify module image-classifier-service and camera-capture are not running.
   create module image-classifier-service failed in docker.
   

docker logs camera-capture
Time to process frame externally: 6 ms
Time to display frame: 1 ms
Wait time between frames :16
Total time for one frame: 17 ms
Frame number: 106
Time to capture (+ straighten up) a frame: 6 ms
Time to pre-process a frame: 1 ms
Time to encode a frame for processing: 1 ms
__sendFrameForProcessing Excpetion -HTTPConnectionPool(host='image-classifier-service', port=80): Max retries exceeded with url: /image (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f6ef817f208>: Failed to establish a new connection: [Errno -2] Name or service not known',))

docker logs edgeHub
2019-05-09 02:52:13 : Starting Edge Hub
[05/09/2019 02:52:13.711 AM] Edge Hub Main()
[05/09/2019 02:52:15.436 AM] Found intermediate certificates: [CN=iotedged workload ca:07/07/2019 06:42:18],[CN=Test Edge Device CA:07/07/2019 06:42:18],[CN=Test Edge Owner CA:07/07/2019 06:42:18]
2019-05-09 02:52:17.176 +00:00 [INF] - Created persistent store at /tmp/edgeHub
2019-05-09 02:52:17.255 +00:00 [INF] - Starting Edge Hub
2019-05-09 02:52:17.256 +00:00 [INF] -
█████╗ ███████╗██╗ ██╗██████╗ ███████╗
██╔══██╗╚══███╔╝██║ ██║██╔══██╗██╔════╝
███████║ ███╔╝ ██║ ██║██████╔╝█████╗
██╔══██║ ███╔╝ ██║ ██║██╔══██╗██╔══╝
██║ ██║███████╗╚██████╔╝██║ ██║███████╗
╚═╝ ╚═╝╚══════╝ ╚═════╝ ╚═╝ ╚═╝╚══════╝

██╗ ██████╗ ████████╗ ███████╗██████╗ ██████╗ ███████╗
██║██╔═══██╗╚══██╔══╝ ██╔════╝██╔══██╗██╔════╝ ██╔════╝
██║██║ ██║ ██║ █████╗ ██║ ██║██║ ███╗█████╗
██║██║ ██║ ██║ ██╔══╝ ██║ ██║██║ ██║██╔══╝
██║╚██████╔╝ ██║ ███████╗██████╔╝╚██████╔╝███████╗
╚═╝ ╚═════╝ ╚═╝ ╚══════╝╚═════╝ ╚═════╝ ╚══════╝

2019-05-09 02:52:17.259 +00:00 [INF] - Version - 1.0.7.21905529 (f455ae2cd66db716c4bd8e7aaa7984ce092481c0)
2019-05-09 02:52:17.265 +00:00 [INF] - Loaded server certificate with expiration date of "2019-07-07T06:42:18.0000000+00:00"
2019-05-09 02:52:17.309 +00:00 [INF] - Created new message store
2019-05-09 02:52:17.311 +00:00 [INF] - Started task to cleanup processed and stale messages
2019-05-09 02:52:17.429 +00:00 [INF] - Created device scope identities cache
2019-05-09 02:52:17.447 +00:00 [INF] - Starting refresh of device scope identities cache
2019-05-09 02:52:17.586 +00:00 [INF] - Initialized twin manager v1.
2019-05-09 02:52:17.627 +00:00 [INF] - Initializing configuration
2019-05-09 02:52:17.680 +00:00 [INF] - New device connection for device customubuntuprod/$edgeHub
2019-05-09 02:52:17.806 +00:00 [INF] - Attempting to connect to IoT Hub for client customubuntuprod/$edgeHub via AMQP...
2019-05-09 02:52:21.771 +00:00 [INF] - Exiting disconnected state
2019-05-09 02:52:21.776 +00:00 [INF] - Device connected to cloud, processing subscriptions for connected clients.
2019-05-09 02:52:21.784 +00:00 [INF] - Processing subscriptions for client customubuntuprod/$edgeHub.
2019-05-09 02:52:21.797 +00:00 [INF] - Cloud connection for customubuntuprod/$edgeHub is True
2019-05-09 02:52:21.810 +00:00 [INF] - Connection status for customubuntuprod/$edgeHub changed to ConnectionEstablished
2019-05-09 02:52:21.817 +00:00 [INF] - Entering connected state
2019-05-09 02:52:21.823 +00:00 [INF] - Created cloud proxy for client customubuntuprod/$edgeHub via AMQP, with client operation timeout 20 seconds.
2019-05-09 02:52:21.839 +00:00 [INF] - Initialized cloud proxy 6d07fdd7-18f5-4337-b172-29c47923af4b for customubuntuprod/$edgeHub
2019-05-09 02:52:21.846 +00:00 [INF] - Created cloud connection for client customubuntuprod/$edgeHub
2019-05-09 02:52:24.826 +00:00 [INF] - Obtained edge hub config from module twin
2019-05-09 02:52:25.377 +00:00 [INF] - Set the following 1 route(s) in edge hub
2019-05-09 02:52:25.379 +00:00 [INF] - CameraCaptureToIoTHub: FROM /messages/modules/camera-capture/outputs/output1 INTO $upstream
2019-05-09 02:52:25.383 +00:00 [INF] - Updated message store TTL to 7200 seconds
2019-05-09 02:52:25.384 +00:00 [INF] - Updated the edge hub store and forward configuration
2019-05-09 02:52:25.388 +00:00 [INF] - Initialized edge hub configuration
2019-05-09 02:52:25.420 +00:00 [INF] - Starting timer to authenticate connections with a period of 300 seconds
2019-05-09 02:52:25.667 +00:00 [INF] - Scheduling server certificate renewal for "2019-07-07T06:39:48.0002760Z".
2019-05-09 02:52:25.671 +00:00 [INF] - Starting protocol heads - (MQTT, AMQP, HTTP)
2019-05-09 02:52:25.681 +00:00 [INF] - Starting MQTT head
2019-05-09 02:52:25.847 +00:00 [INF] - Initializing TLS endpoint on port 8883 for MQTT head.
2019-05-09 02:52:25.964 +00:00 [INF] - Starting AMQP head
2019-05-09 02:52:26.000 +00:00 [INF] - Started MQTT head
2019-05-09 02:52:26.156 +00:00 [INF] - Started AMQP head
2019-05-09 02:52:26.163 +00:00 [INF] - Starting HTTP head
2019-05-09 02:52:26.346 +00:00 [INF] - User profile is available. Using '"/home/edgehubuser/.aspnet/DataProtection-Keys"' as key repository; keys will not be encrypted at rest.
2019-05-09 02:52:26.417 +00:00 [INF] - Creating key {6bfd2c9b-fafe-45a0-9d1e-e518d6454428} with creation date 2019-05-09 02:52:26Z, activation date 2019-05-09 02:52:26Z, and expiration date 2019-08-07 02:52:26Z.
2019-05-09 02:52:26.447 +00:00 [WRN] - No XML encryptor configured. Key {6bfd2c9b-fafe-45a0-9d1e-e518d6454428} may be persisted to storage in unencrypted form.
2019-05-09 02:52:26.456 +00:00 [INF] - Writing data to file '"/home/edgehubuser/.aspnet/DataProtection-Keys/key-6bfd2c9b-fafe-45a0-9d1e-e518d6454428.xml"'.
2019-05-09 02:52:27.125 +00:00 [WRN] - Overriding address(es) '"http://+:80"'. Binding to endpoints defined in "UseKestrel()" instead.
2019-05-09 02:52:27.192 +00:00 [INF] - Started HTTP head
2019-05-09 02:57:25.435 +00:00 [INF] - Reauthenticating connected clients
2019-05-09 03:02:25.427 +00:00 [INF] - Reauthenticating connected clients
2019-05-09 03:07:25.425 +00:00 [INF] - Reauthenticating connected clients
2019-05-09 03:12:25.424 +00:00 [INF] - Reauthenticating connected clients
2019-05-09 03:17:25.425 +00:00 [INF] - Reauthenticating connected clients
2019-05-09 03:22:17.330 +00:00 [INF] - Started task to cleanup processed and stale messages for endpoint iothub
2019-05-09 03:22:17.351 +00:00 [INF] - Cleaned up 0 messages from queue for endpoint iothub and 0 messages from message store.
2019-05-09 03:22:25.422 +00:00 [INF] - Reauthenticating connected clients

docker logs edgeAgent

2019-05-09 03:17:56.786 +00:00 [INF] - Executing command: "Command Group: (
[Stop module image-classifier-service]
[Start module image-classifier-service]
[Saving image-classifier-service to store]
)"
2019-05-09 03:17:56.786 +00:00 [INF] - Executing command: "Stop module image-classifier-service"
2019-05-09 03:17:56.788 +00:00 [INF] - Executing command: "Start module image-classifier-service"
2019-05-09 03:17:58.266 +00:00 [INF] - Executing command: "Saving image-classifier-service to store"
2019-05-09 03:17:58.267 +00:00 [INF] - Plan execution ended for deployment 2
2019-05-09 03:18:03.282 +00:00 [INF] - Module 'image-classifier-service' scheduled to restart after 05m:00s (04m:55s left).
2019-05-09 03:18:03.712 +00:00 [INF] - Updated reported properties
2019-05-09 03:18:08.720 +00:00 [INF] - Module 'image-classifier-service' scheduled to restart after 05m:00s (04m:50s left).
2019-05-09 03:18:13.731 +00:00 [INF] - Module 'image-classifier-service' scheduled to restart after 05m:00s (04m:45s left).
2019-05-09 03:18:18.741 +00:00 [INF] - Module 'image-classifier-service' scheduled to restart after 05m:00s (04m:40s left).
2019-05-09 03:18:23.751 +00:00 [INF] - Module 'image-classifier-service' scheduled to restart after 05m:00s (04m:35s left).
2019-05-09 03:18:28.760 +00:00 [INF] - Module 'image-classifier-service' scheduled to restart after 05m:00s (04m:30s left).

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ X ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Follow the installation guide --> instructions to install Azure IoT Edge

Any log messages given by the failure

Sep 25 16:20:38 raspberrypi iotedged[4154]: 2018-09-25T14:20:38Z [INFO] - Checking edge runtime status
Sep 25 16:20:38 raspberrypi iotedged[4154]: 2018-09-25T14:20:38Z [INFO] - Edge runtime is running.
Sep 25 16:20:42 raspberrypi iotedged[4154]: 2018-09-25T14:20:42Z [ERR!] - Internal server error: Sign failed
Sep 25 16:20:42 raspberrypi iotedged[4154]:         caused by: A error occurred retrieving a key from the key store.
Sep 25 16:20:42 raspberrypi iotedged[4154]:         caused by: HSM failure
Sep 25 16:20:42 raspberrypi iotedged[4154]:         caused by: HSM API failure occurred: 364
Sep 25 16:20:42 raspberrypi iotedged[4154]: 2018-09-25T14:20:42Z [INFO] - [work] - - - [2018-09-25 14:20:42.378014093 UTC] "POST /modules/%24edgeAgent/genid/636734724559850094/encrypt?api-version=2018-06-28 HTTP/1.1" …3 "-" "-" pid(4361)
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:47Z [INFO] - [mgmt] - - - [2018-09-25 14:20:47.455864768 UTC] "GET /modules?api-version=2018-06-28 HTTP/1.1" 200 OK 962 "-" "-" pid(4361)
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:47Z [ERR!] - Internal server error: Sign failed
Sep 25 16:20:47 raspberrypi iotedged[4154]:         caused by: A error occurred retrieving a key from the key store.
Sep 25 16:20:47 raspberrypi iotedged[4154]:         caused by: HSM failure
Sep 25 16:20:47 raspberrypi iotedged[4154]:         caused by: HSM API failure occurred: 364
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:47Z [INFO] - [work] - - - [2018-09-25 14:20:47.459371101 UTC] "POST /modules/%24edgeAgent/genid/636734724559850094/encrypt?api-version=2018-06-28 HTTP/1.1" …3 "-" "-" pid(4361)
Sep 25 16:20:47 raspberrypi iotedged[4154]: t open file for reading /var/lib/iotedge/hsm/enc_keys/edgelet-masterWt5mT2xpO72EPKlt2Tt0Sq4uJCrMvfl2rzzKRB3pnyo_.enc.key. Errno 2 'No such file or directory'
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:25Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/edge_hsm_client_store.c:load_encryption_key_from_file:824) Could not read key from file. Key size 0
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:25Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/edge_hsm_client_store.c:edge_hsm_client_open_key:2145) HSM store could not load encryption key edgelet-master
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:25Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/edge_hsm_client_crypto.c:encrypt_data:363) Could not get encryption key by name 'edgelet-master'
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:25Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/hsm_utils.c:read_file_into_buffer_impl:166) Could not open file for reading /var/lib/iotedge/hsm/enc_keys/e… file or directory'
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:25Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/edge_hsm_client_store.c:load_encryption_key_from_file:824) Could not read key from file. Key size 0
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:25Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/edge_hsm_client_store.c:edge_hsm_client_open_key:2145) HSM store could not load encryption key edgelet-master
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:25Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/edge_hsm_client_crypto.c:encrypt_data:363) Could not get encryption key by name 'edgelet-master'
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:30Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/hsm_utils.c:read_file_into_buffer_impl:166) Could not open file for reading /var/lib/iotedge/hsm/enc_keys/e… file or directory'
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:30Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/edge_hsm_client_store.c:load_encryption_key_from_file:824) Could not read key from file. Key size 0
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:30Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/edge_hsm_client_store.c:edge_hsm_client_open_key:2145) HSM store could not load encryption key edgelet-master
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:30Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/edge_hsm_client_crypto.c:encrypt_data:363) Could not get encryption key by name 'edgelet-master'
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:42Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/hsm_utils.c:read_file_into_buffer_impl:166) Could not open file for reading /var/lib/iotedge/hsm/enc_keys/e… file or directory'
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:42Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/edge_hsm_client_store.c:load_encryption_key_from_file:824) Could not read key from file. Key size 0
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:42Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/edge_hsm_client_store.c:edge_hsm_client_open_key:2145) HSM store could not load encryption key edgelet-master
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:42Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/edge_hsm_client_crypto.c:encrypt_data:363) Could not get encryption key by name 'edgelet-master'
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:47Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/hsm_utils.c:read_file_into_buffer_impl:166) Could not open file for reading /var/lib/iotedge/hsm/enc_keys/e… file or directory'
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:47Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/edge_hsm_client_store.c:load_encryption_key_from_file:824) Could not read key from file. Key size 0
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:47Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/edge_hsm_client_store.c:edge_hsm_client_open_key:2145) HSM store could not load encryption key edgelet-master
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:47Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/edge_hsm_client_crypto.c:encrypt_data:363) Could not get encryption key by name 'edgelet-master'
Sep 25 16:20:47 raspberrypi iotedged[4154]: 2018-09-25T14:20:47Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/hsm_utils.c:read_file_into_buffer_impl:166) Could not open file for reading /var/lib/iotedge/hsm/enc_keys/e… error: Sign failed

Expected/desired behavior

Working IoTEdge daemon with no encryption errors, for some reason I'm missing some files

OS and Version?

Raspberry Pi 3

PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian
ID_LIKE=debian

Mention any other details that might be useful

Could be due to an installation error that the certificates are missing (timing issues maybe)
Is there a command that will refresh all the IoT Edge certificate files ?

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [X ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.