search

edgexfoundry / device-coap-c

EdgeX device service for CoAP-based REST protocol
Apache License 2.0
3 stars 18 forks source link

device-coap failing with "Error processing file ./res/devices/devices.json" #46

Closed bnevis-i closed 1 year ago

bnevis-i commented 1 year ago

🐞 Bug Report

Affected Services [REQUIRED]

device-coap

Is this a regression?

Unknown

Description and Minimal Reproduction [REQUIRED]

device-coap fails with "Error processing file ./res/devices/devices.json" when started in docker with no-secty option

make run ds-coap no-secty

🔥 Exception or Error


level=INFO ts=2023-04-18T20:59:30Z app=device-coap msg="iot_threadpool_alloc (threads: 8 max_jobs: 0 default_priority: -1 affinity: -1)"
level=INFO ts=2023-04-18T20:59:30Z app=device-coap msg="iot_scheduler_alloc (priority: -1 affinity: -1)"
level=INFO ts=2023-04-18T20:59:30Z app=device-coap msg="Override config Service/Host = edgex-device-coap"
level=INFO ts=2023-04-18T20:59:30Z app=device-coap msg="Found registry service at consul.http://edgex-core-consul:8500"
level=INFO ts=2023-04-18T20:59:35Z app=device-coap msg="Unable to get configuration from registry."
level=INFO ts=2023-04-18T20:59:35Z app=device-coap msg="Will load from file."
level=INFO ts=2023-04-18T20:59:35Z app=device-coap msg="Uploading configuration to registry."
level=ERROR ts=2023-04-18T20:59:35Z app=device-coap msg="consul: no service named core-metadata"
level=ERROR ts=2023-04-18T20:59:36Z app=device-coap msg="consul: no service named core-metadata"
level=INFO ts=2023-04-18T20:59:37Z app=device-coap msg="Starting device-coap device service, version 2.3.0"
level=INFO ts=2023-04-18T20:59:37Z app=device-coap msg="EdgeX device SDK for C, version 2.3.0"
level=INFO ts=2023-04-18T20:59:37Z app=device-coap msg="iot_threadpool_alloc (threads: 1 max_jobs: 0 default_priority: -1 affinity: -1)"
level=INFO ts=2023-04-18T20:59:37Z app=device-coap msg="Found core-data service at edgex-core-data:59880"
level=INFO ts=2023-04-18T20:59:37Z app=device-coap msg="Event data will be posted to core-data at http://edgex-core-data:59880/api/v2/event///"
level=INFO ts=2023-04-18T20:59:37Z app=device-coap msg="Found core-metadata service at edgex-core-metadata:59881"
level=INFO ts=2023-04-18T20:59:37Z app=device-coap msg="Processing Device Profiles from ./res/profiles"
level=INFO ts=2023-04-18T20:59:37Z app=device-coap msg="Device profile example-datatype created"
level=INFO ts=2023-04-18T20:59:37Z app=device-coap msg="Starting HTTP server on interface edgex-device-coap, port 59988"
level=INFO ts=2023-04-18T20:59:37Z app=device-coap msg="Processing Devices from ./res/devices"
level=INFO ts=2023-04-18T20:59:40Z app=device-coap msg="Reconfiguring"
level=INFO ts=2023-04-18T20:59:42Z app=device-coap msg="Device d1 create failed: HTTP request failed: HTTP request timeout"
level=INFO ts=2023-04-18T20:59:47Z app=device-coap msg="Device d2 create failed: HTTP request failed: HTTP request timeout"
level=INFO ts=2023-04-18T20:59:52Z app=device-coap msg="Device d3 create failed: HTTP request failed: HTTP request timeout"
level=INFO ts=2023-04-18T20:59:57Z app=device-coap msg="Device d4 create failed: HTTP request failed: HTTP request timeout"
level=ERROR ts=2023-04-18T20:59:57Z app=device-coap msg="Error processing file ./res/devices/devices.json"
Error: 21: HTTP request failed

🌍 Your Environment

Deployment Environment: docker

EdgeX Version [REQUIRED]: minnesota-dev

Anything else relevant?

bnevis-i commented 1 year ago

No longer fails in 3.0