[master] device-virtual fails at startup due to device creation failure about device-virtual-go

[tonyespy]

I just tried the latest (as of today's developer-scripts) docker-compose-nexus-redis compose file and device-virtual is failing even earlier than in the snap:

ERROR app=device-virtual source=init.go:112 msg="service dependency Data checking time out"
ERROR app=device-virtual source=init.go:112 msg="service dependency Metadata checking time out"
error: checking required dependencied services failed 
INFO app=device-virtual source=httpserver.go:106 msg="Web server shutting down"
INFO app=device-virtual source=httpserver.go:108 msg="Web server shut down"
INFO app=device-virtual source=httpserver.go:97 msg="Web server stopped"

[cloudxxx8]

may I know which compose file you are using? it looks like the core services did start up or can't be reached.

[chr1shung]

For now the latest docker-compose-nexus-redis-no-secty works well. the secty one, I still got the following error which is similar to edgexfoundry/edgex-go#2516

Couldn't register to metadata service: 500 - Could not dial Redis: ERR invalid password

level=ERROR ts=2020-04-27T15:55:12.0265664Z app=device-virtual source=service.go:86 msg="DeviceServicForName failed: 500 - Could not dial Redis: ERR invalid password\n"

[tonyespy]

may I know which compose file you are using? it looks like the core services did start up or can't be reached.

docker-compose-nexus-redis today...

[chr1shung]

I just tried the latest (as of today's developer-scripts) docker-compose-nexus-redis compose file and device-virtual is failing even earlier than in the snap:

ERROR app=device-virtual source=init.go:112 msg="service dependency Data checking time out"
ERROR app=device-virtual source=init.go:112 msg="service dependency Metadata checking time out"
error: checking required dependencied services failed 
INFO app=device-virtual source=httpserver.go:106 msg="Web server shutting down"
INFO app=device-virtual source=httpserver.go:108 msg="Web server shut down"
INFO app=device-virtual source=httpserver.go:97 msg="Web server stopped"

sometimes it took longer for the device service to do the health check on coredata and core-metadata (no matter via ping api or registry), and it usually because core services are also waiting for its dependency service, for example I got following logs in coredata:

level=INFO ts=2020-04-27T16:07:17.8910683Z app=edgex-core-data source=secret.go:67 msg="Reading secret store configuration and authentication token"
level=INFO ts=2020-04-27T16:07:17.8959305Z app=edgex-core-data source=secret.go:73 msg="Attempting to create secretclient"
level=WARN ts=2020-04-27T16:07:17.9440488Z app=edgex-core-data source=secret.go:82 msg="Retryable failure while creating SecretClient: HTTP response with status code 403, message: failed to lookup token"

and it retried like 6~7 times and finally succeed, during this period the device service exceed its connectionretries limit.

I think in this case we have no choice but to manually restart device-virtual..

[tonyespy]

For now the latest docker-compose-nexus-redis-no-secty works well. the secty one, I still got the following error which is similar to edgexfoundry/edgex-go#2516

Couldn't register to metadata service: 500 - Could not dial Redis: ERR invalid password

level=ERROR ts=2020-04-27T15:55:12.0265664Z app=device-virtual source=service.go:86 msg="DeviceServicForName failed: 500 - Could not dial Redis: ERR invalid password\n"

Looks like you may have some old images cached on your system. I'd recommend delete any cached images and start from a fresh developer-scripts. The error that your seeing indicates that you may not have all the update security bits required to use redis securely.

[tonyespy]

OK, my original problem is caused by the fact the binary device profile wasn't being copied to $SNAP_DATA.

[tonyespy]

Based on my previous comment, I'm closing this issue.