5 Deployment FAQ

Q1. The instruction set of the machine for deployment is too low in this version, or the instruction set does not contain the AVX instruction set. It is found that the log contains "SIGILL: illegal instruction” after executing tail -f tmp/worker.log.0 to check the returned log. What’s the solution to this problem?

First, check the instruction set contained in the current machine:

1. Execute this command: cat /proc/cpuinfo

2. Check flag

If it does not contain a mix of AVX & AVX2, indicating that the CPU instruction set does not support the Avx instruction set.

There are two solutions:

1) Replace it with a machine containing an AVX instruction set;

2) Force the machine to use an SSE instruction set. However, the service performance will degrade and processing speed will be halved;

Method to force the machine to use an SSE instruction set: open go-workers/. env,

Modify FORCE_SET_SSE=false to FORCE_SET_SSE=true.

Note: Save the exit after modifying, and restart the go-workers. The method to restart the service is as follows:

First execute ./stop/sh then execute ./start.sh

Q2. If the start command (./start.sh) is called repeatedly during deployment, or the port is used, for example, if you execute ./start.sh multiple times in go-workers, it is found that the following errors are reported after checking the log:

listen: listen tcp :50050: bind: address already in use

Note: Start "./start.sh "once respectively corresponding when starting Go-Workers or Ruby-Cloud-API.

1) Execute

ps aux | grep supervisord

2) Kill the corresponding process No. of ./tool/supervisord -c config/supervisor.conf -d:

kill -9 PID

Q3. A summary error type about the use of license:

The "private cloud package" which we provide does not contain licenses by default. For details of licenses, please refer to Chapter 3 License Activation.

1）error panic: bad license: -1

It means the license has broken（such as an empty licenes）,please replace the license file again.

2) error panic: open fixture/license/senseid_ocr/senseid_ocr.lic: no such file or directory

It means the license is not imported,please import the license file into the specified folder.

3）error panic: bad license: -16

It meas "udid mismatch", and the hardware fingerprint bound to the license is inconsistent with the current device’s hardware fingerprint.Please make sure the device's hardware information has not changed.

Maybe you use the wrong license or the device's udid is changed.

If you make sure that device's uuid has changed,please provide the new udid to the business person who can apply for the new license to you,and then remember to replace the new license.

Q4 error:-8 ？

It means the file format is incorrect, mainly related to the model file.

For example, using the decompression software under the windows system to decompress and upload the "private cloud package" to server may cause partial damage of the model file. It is recommended that customers re-upload the installation package(xxx.tar) to the server and use the command line(tax xf xxx.tar) to decompress it on the server