Known Issues
Services | Description | Solution |
---|---|---|
xpert-manager |
Edge Xpert Manager has been tested with Google Chrome only | |
consul core-data core-metadata |
When a Device Service runs in a Docker container and uses nsenter, the Device Service may be unable to resolve the hostnames for the Core Data and Core Metadata | To resolve this issue, you can do either of the following:
|
xpert-manager core-metadata |
When using Xpert Manager and nsenter, there are issues connecting to Core Metadata and adding devices Core Metadata logs show that the connection was refused or could not be found |
Update your Device Service environment variables to use the IP address of the machine running the Device Service. For example:
|
Device Services | Device Service will return Error: 5:Failed to start HTTP server when running the container with both the --privileged and -p flags |
Use only the --privileged command.In the docker-compose.yml file, ensure that the privileged parameter is set to true: device-opc-ua: |
Device Services | If the names of deviceResource or deviceCommand are duplicated in any profile, an error or warning message occursThis does not prevent the device profile from being uploaded or used in Edge Xpert |
To avoid the error or warning messages, ensure that unique names are used across all profiles |
Redis | Tokens for retrieving a password from Vault cannot be obtained if you wish to directly access the Redis database | Modify docker-compose-security.yml to add EDGEXPERT_PASSWORD_FILE environment variable with 'true' in the secretstore-setup microservice and restart Edge Xpert. Use the password, located at /tmp/edgex/secrets/redis-password and the default username redis5 for database authentication |
Docker Toolbox | If using Docker Toolbox, you may encounter issues when running Edge Xpert in the secure mode To identify any issues, open a terminal and enter the docker logs vault-worker command. Check the end of the log for the following: ...If you do not see Waiting for termination signal , there is likely a X509: certificate signed by unknown authority issue |
Clean all services, remove the security folder and restart Edge Xpert |
--secret --api-gateway |
On resource-constrained machines, services may sometimes fail to start when running Edge Xpert in the secure mode This is due to service times timing out during the bootstrap process |
Start the services For example, to start the Virtual Device Service and run Edge Xpert in the secure mode, enter the following commands: edgexpert up --no-core --secret edgexpert up --no-core --api-gateway edgexpert up device-virtual |
OPC-UA Device Service | Some device resources are unreadable if they point to empty values. This affects variable-type nodes that are not required to have a value | A fix is in the works for this issue. In the meantime, this can be avoided either by not sending commands to these resources or by manually marking these resources with the attribute isHidden=false in the device profile |