Contents

• Contents

  • Troubleshooting

    • Issue 1: “host” network_mode is incompatible with port_bindings during docker compose up

    • Issue 2: The eii_libs_installer.sh Script Failing During the Bare-metal Execution

    • Issue 3: Build Issues

    • Issue 4: Provisioning Failure when changing from Prod to Dev Mode

Troubleshooting

The troubleshooting guide here talks about the useful tips to address some of the EII configuration and installation issues.

Note

In this document, you will find labels of ‘Edge Insights for Industrial (EII)’ for file names, paths, code snippets, and so on.

Issue 1: “host” network_mode is incompatible with port_bindings during docker compose up

Problem Description:

Issue in starting the InfluxDBConnector, Kapacitor, and Grafana Services like InfluxDBConnector, Kapacitor, Grafana whose ports are exposed to start the service might fail to start during docker compose up.

Error Description:

• Error for ia_kapacitor: “host” network_mode is incompatible with port_bindings

• ERROR for ia_grafana:  “host” network_mode is incompatible with port_bindings

• ERROR for ia_influxdbconnector: “host” network_mode is incompatible with port_bindings

• docker.errors.InvalidArgument: “host” network_mode is incompatible with port_bindings

Issue 2: The eii_libs_installer.sh Script Failing During the Bare-metal Execution

Problem Description:

You may run into issue of $GOPATH not being set appropriately, which results in the EII libraries installation failure, when run on bare-metal.

Error Description:

CMake Error at CMakeLists.txt:63 (message): – $GOPATH environmental variable is not set

– Configuring incomplete, errors occurred!

See also “/home/eisval-desk6/FOG/EIIv2.4_RC6/IEdgeInsights/common/libs/ConfigMgr/build/CMakeFiles/CMakeOutput.log”. See also “/home/eisval-desk6/FOG/EIIv2.4_RC6/IEdgeInsights/common/libs/ConfigMgr/build/CMakeFiles/CMakeError.log”. running install running build running build_py running build_ext building ‘cfgmgr.app_config’ extension x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/inclupython3.8 -c ./build/cython/./cfgmgr/app_config.c -o build/temp.linux-x86_64-3.6/./build/cython/./cfgmgr/app_config.o ./build/cython/./cfgmgr/app_config.c:626:10: fatal error: eii/config_manager/cfgmgr.h: No such file or directory

include “eii/config_manager/cfgmgr.h”

^~~~~~~~~~ compilation terminated. error: command ‘x86_64-linux-gnu-gcc’ failed with exit status 1

Possible Cause:

If “GO” is already installed in the system, eii_libs_installer script skips the installation of it.

In this case, where GO is already installed, GOPATH needs to be set in the system. If not, then this error occurs.

Solution:

Installing GO through eii_libs_installer script will install GO and set the required env variables like GOPATH. If not, then one need to set GOPATH environment variable with appropriate path.

export GOPATH=<path_to_where_GO_is_installed>

You can run into docker build issues, if there is any change in the location of the third party package being referenced. Additionally, there could be issues related to the Python requirements.txt, golang go.mod and so on. You can fix it in the appropriate service Docker file or code and re-build it.

If the docker image of the service is already available on the Docker Hub (https://hub.docker.com/u/edgeinsights), we strongly suggest using it to avoid seeing build failures.

Problem Description:

Issue while Config Manager Agent doing provisioning when env is changed from Prod to Dev.

Error Description:

ia_configmgr_agent | 2022-12-09 05:11:30.830948 I | embed: ready to serve client requests

ia_configmgr_agent | 2022-12-09 05:11:30.831505 I | etcdserver: published {Name:leader ClientURLs:[http://0.0.0.0:2379]} to cluster eb504ef19b552264

ia_configmgr_agent | 2022-12-09 05:11:30.833111 N | embed: serving insecure client requests on [::]:2379, this is strongly discouraged!

ia_configmgr_agent | 2022-12-09 05:11:31.117162 W | etcdserver: read-only range request “key:"health" “ with result “error:auth: user name is empty” took too long (267.143626ms) to execute

Possible Cause:

This might have caused due to improper clean-up on startup of config manager agent.

Solution:

Manually clean-up/removal of the Certificate and EII_INSTALL_PATH would solve this issue.

docker compose down -v
sudo rm -r /opt/intel/eii
sudo rm -r Certificates

Bring up the EII stack by referring the section Run EII Service