Camera loses IoT Hub connection about vision-ai-developer-kit HOT 8 CLOSED

please include the output from running: iotedge check

from vision-ai-developer-kit.

@juniem Can you please provide output from iotcheck check? thanks.

from vision-ai-developer-kit.

Configuration checks

�[0m�[32m√ config.yaml is well-formed
�[0m�[0m�[32m√ config.yaml has well-formed connection string
�[0m�[0m�[32m√ container engine is installed and functional
�[0m�[0m�[32m√ config.yaml has correct hostname
�[0m�[0m�[31m× config.yaml has correct URIs for daemon mgmt endpoint
Unable to find image 'mcr.microsoft.com/azureiotedge-diagnostics:1.0.7' locally
docker: Error response from daemon: Get https://mcr.microsoft.com/v2/: tls: failed to parse certificate from server: asn1: syntax error: invalid boolean.
See 'docker run --help'.
�[0m�[0m�[33m‼ latest security daemon
Error while fetching latest versions of edge components: could not send HTTP request

from vision-ai-developer-kit.

same issue here. rebooting for confirmation

from vision-ai-developer-kit.

edgeAgent and edgeHub are of version: 1.0.8.3

[IoTHubMonitor] [12:00:11 AM] Message received from [xx/AIVisionDevKitGetStartedModule]:
{
"position_x": 824.832,
"confidence": 70,
"position_y": 78.948,
"id": 1,
"height": 989.928,
"label": "person",
"width": 952.896
}

<6> 2019-11-21 22:48:42.966 +00:00 [INF] - Closed HTTP head
<4> 2019-11-21 22:48:43.635 +00:00 [WRN] - Closing connection for device: xx/AIVisionDevKitGetStartedModule, Microsoft.Azure.Devices.ProtocolGateway.ProtocolGatewayException: Channel closed.,
<6> 2019-11-21 22:48:43.639 +00:00 [INF] - Disposing MessagingServiceClient for device Id xx/AIVisionDevKitGetStartedModule because of exception - Microsoft.Azure.Devices.ProtocolGateway.ProtocolGatewayException: Channel closed.
<6> 2019-11-21 22:48:43.646 +00:00 [INF] - Setting device proxy inactive for device Id xx/AIVisionDevKitGetStartedModule

from vision-ai-developer-kit.

Hi @Devinwong were you able to repro this issue?

from vision-ai-developer-kit.

I appear to be having the same kind of issue. I'm new to IoT Edge so may need some direction but I've run "iotedge check" which produced the following output ...

Configuration checks

√ config.yaml is well-formed - OK
√ config.yaml has well-formed connection string - OK
√ container engine is installed and functional - OK
√ config.yaml has correct hostname - OK
× config.yaml has correct URIs for daemon mgmt endpoint - Error
Unable to find image 'mcr.microsoft.com/azureiotedge-diagnostics:1.0.8.3' locally
docker: Error response from daemon: manifest for mcr.microsoft.com/azureiotedge-diagnostics:1.0.8.3 not found: manifest unknown: manifest unknown.
See 'docker run --help'.
caused by: docker returned exit code: 125, stderr = Unable to find image 'mcr.microsoft.com/azureiotedge-diagnostics:1.0.8.3' locally
docker: Error response from daemon: manifest for mcr.microsoft.com/azureiotedge-diagnostics:1.0.8.3 not found: manifest unknown: manifest unknown.
See 'docker run --help'.
‼ latest security daemon - Warning
Installed IoT Edge daemon has version 1.0.8.3 but 1.0.8 is the latest stable version available.
Please see https://aka.ms/iotedge-update-runtime for update instructions.
√ host time is close to real time - OK
× container time is close to host time - Error
Could not query local time inside container
caused by: docker returned exit code: 125, stderr = Unable to find image 'mcr.microsoft.com/azureiotedge-diagnostics:1.0.8.3' locally
docker: Error response from daemon: manifest for mcr.microsoft.com/azureiotedge-diagnostics:1.0.8.3 not found: manifest unknown: manifest unknown.
See 'docker run --help'.
‼ DNS server - Warning
Container engine is not configured with DNS server setting, which may impact connectivity to IoT Hub.
Please see https://aka.ms/iotedge-prod-checklist-dns for best practices.
You can ignore this warning if you are setting DNS server per module in the Edge deployment.
‼ production readiness: certificates - Warning
Device is using self-signed, automatically generated certs.
Please see https://aka.ms/iotedge-prod-checklist-certs for best practices.
√ production readiness: certificates expiry - OK
√ production readiness: container engine - OK
√ production readiness: logs policy - OK

Connectivity checks

× host can connect to and perform TLS handshake with IoT Hub AMQP port - Error
Could not connect to mmgs1iothubpoc.azure-devices.net:5671
caused by: Connection refused (os error 111)
√ host can connect to and perform TLS handshake with IoT Hub HTTPS / WebSockets port - OK
× host can connect to and perform TLS handshake with IoT Hub MQTT port - Error
Could not connect to mmgs1iothubpoc.azure-devices.net:8883
caused by: Connection refused (os error 111)
× container on the default network can connect to IoT Hub AMQP port - Error
Container on the default network could not connect to mmgs1iothubpoc.azure-devices.net:5671
caused by: docker returned exit code: 125, stderr = Unable to find image 'mcr.microsoft.com/azureiotedge-diagnostics:1.0.8.3' locally
docker: Error response from daemon: manifest for mcr.microsoft.com/azureiotedge-diagnostics:1.0.8.3 not found: manifest unknown: manifest unknown.
See 'docker run --help'.
× container on the default network can connect to IoT Hub HTTPS / WebSockets port - Error
Container on the default network could not connect to mmgs1iothubpoc.azure-devices.net:443
caused by: docker returned exit code: 125, stderr = Unable to find image 'mcr.microsoft.com/azureiotedge-diagnostics:1.0.8.3' locally
docker: Error response from daemon: manifest for mcr.microsoft.com/azureiotedge-diagnostics:1.0.8.3 not found: manifest unknown: manifest unknown.
See 'docker run --help'.
× container on the default network can connect to IoT Hub MQTT port - Error
Container on the default network could not connect to mmgs1iothubpoc.azure-devices.net:8883
caused by: docker returned exit code: 125, stderr = Unable to find image 'mcr.microsoft.com/azureiotedge-diagnostics:1.0.8.3' locally
docker: Error response from daemon: manifest for mcr.microsoft.com/azureiotedge-diagnostics:1.0.8.3 not found: manifest unknown: manifest unknown.
See 'docker run --help'.
× container on the IoT Edge module network can connect to IoT Hub AMQP port - Error
Container on the azure-iot-edge network could not connect to mmgs1iothubpoc.azure-devices.net:5671
caused by: docker returned exit code: 125, stderr = Unable to find image 'mcr.microsoft.com/azureiotedge-diagnostics:1.0.8.3' locally
docker: Error response from daemon: manifest for mcr.microsoft.com/azureiotedge-diagnostics:1.0.8.3 not found: manifest unknown: manifest unknown.
See 'docker run --help'.
× container on the IoT Edge module network can connect to IoT Hub HTTPS / WebSockets port - Error
Container on the azure-iot-edge network could not connect to mmgs1iothubpoc.azure-devices.net:443
caused by: docker returned exit code: 125, stderr = Unable to find image 'mcr.microsoft.com/azureiotedge-diagnostics:1.0.8.3' locally
docker: Error response from daemon: manifest for mcr.microsoft.com/azureiotedge-diagnostics:1.0.8.3 not found: manifest unknown: manifest unknown.
See 'docker run --help'.
× container on the IoT Edge module network can connect to IoT Hub MQTT port - Error
Container on the azure-iot-edge network could not connect to mmgs1iothubpoc.azure-devices.net:8883
caused by: docker returned exit code: 125, stderr = Unable to find image 'mcr.microsoft.com/azureiotedge-diagnostics:1.0.8.3' locally
docker: Error response from daemon: manifest for mcr.microsoft.com/azureiotedge-diagnostics:1.0.8.3 not found: manifest unknown: manifest unknown.
See 'docker run --help'.
√ Edge Hub can bind to ports on host - OK

10 check(s) succeeded.
3 check(s) raised warnings.
10 check(s) raised errors.

... from what I can see, it connected successfully over web sockets but yet, no messages coming through.

I was originally getting message but now nothing and it's only running the default delivered get started and web streaming module.

Would love some advice.

from vision-ai-developer-kit.

Closing issue - please re-open if still and issue.

from vision-ai-developer-kit.