EdgeX cannot communicate with Device Service #113
Replies: 2 comments 2 replies
-
For some reason the service is registering its listening host as |
Beta Was this translation helpful? Give feedback.
-
@sounak-1989 , you must set the Service.Host in your configuration to the IP address of your system. This is the only way the services running in the Docker network can find your service running outside docker network. You will need to do a clean restart of EdgeX stack so that the DB volume has been removed. |
Beta Was this translation helpful? Give feedback.
-
Hi guys,
I am using EdgeX Kamakura. I am running EdgeX from EdgeX compose using Docker. I am running the device service natively from source. So it is a hybrid development environment.
The device service is able to register devices, profiles and provision watchers to core-metadata. But when I am sending a command or querying a resource using core-data or core-command, I am unable to access it. I am getting the following error.
level=ERROR ts=2023-05-23T22:44:02.038901461Z app=core-command source=http.go:47 X-Correlation-ID=3e2d68a2-35d2-4704-9cf3-dcd3c5f40d20 msg="failed to send a http request -> Get \"http://0.0.0.0:59991/api/v2/device/name/IOCard2031666/VInP1\": dial tcp 0.0.0.0:59991: connect: connection refused"
Although when I query the same endpoint using Postman I am able to get a response. There has been some kind of communication issue between the microservices running inside docker and the device service running natively. Any idea what can cause this issue?
Thanks,
Sounak
Beta Was this translation helpful? Give feedback.
All reactions