This manual describes how to install the JCV face recognition service "Sense ID." To successfully deploy the service, please read this manual carefully before starting.

This manual is intended for customers who belong to the IT department and have experience using and operating Linux, Kubernetes, Docker, and cloud.

The installation process described in this manual is described in detail in the following figure.

3.1 What is license

A license file is required to use the Go-Workers service of SenseID. The activation of the license is associating with the UDID. License files may differ depending on the services you are using. One SenseID server can correspond to one to three license files. You must rename the license file and place it in the specified directory before you can deploy the service.

The JCV product window provides the SenseID license file. Refer to the following parts for activation details.

3.2 Change license file names

• Change the SENSEID_FACE_xxx.lic file to senseid_face.lic.

• Change the SENSEID_KESTREL_xxx.lic file to senseid_kestrel.lic.

• Change the SENSEID_LIVENESS_xxx.lic

3.3 Replace license files

3.3.1 Unzip the installation package

Package name: 1v1-private-cloud-v1.8.tgz

3.3.2 Place the license files

Change the directory to the license folder where you unzipped the SenseID installation package.

You can confirm that the following three folders are displayed by executing the following command.

Copy the license files to the specified directories and overwrite the original files.

2.1 What is UDID

The UDID is a server identification code calculated from the server hardware information. SenseID activation is associating with the UDID. Download the UDID acquisition tool and follow the instructions to acquire the UDID before applying for a SenseID license.

2.2 UDID acquisition tool

The UDID acquisition tool is used to get the UDID of the deployment target server.

The file name of the UDID acquisition tool isSenseIDPrivateCloud-UDIDGetter-V4.1.0.zip.

2.3 Get UDID

Place and unzip the UDID acquisition tool on the server.

Change the directory to the unzipped folder and execute theUDIDGetter.sh.

Please sent the outputUDID.txtfile, together with your contract number to the JCV product window .

1.1 System

Ubuntu Server 18.04 LTS is recommended for the Sense ID usage environment. We recommend a quad-core or higher CPU, 8GM or higher RAM, and 100GB or higher disk capacity on the hardware side. Note that AVX is required for the CPU instruction set.

1.2 Services

• Ruby-Cloud-API

  • The HTTP services, including the main interface for client API calls.

  • Service port: 3000

This chapter describes how to deploy and activate the SenseID service, primarily installing, configuring, launching critical services and potential issues and solutions.

4.1 Confirm the installation package

The installation package should have been unzipped to place the license files. See Section for more details.

Change the directory to the root folder where you unzipped the SenseID installation package.

The structure is as follows:

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:

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

1) Execute

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

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 .

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