Troubleshoot reasons for service startup failure of EasyCVR, a video networking cloud platform, in Linux systems

EasyCVR is a video cloud gateway platform developed by the Qingxi team, and has been actually used in some projects. For EasyCVR, we are testing and using it at the same time, so most of the problems are problems encountered during the testing process of our R&D.

We tried to start EasyCVR in the Linux system today. At this time, we found that when EasyCVR is started as a service, it will fail (./start.sh), and running directly is normal.

1211.png

The above picture can clearly see that our service was indeed successfully installed, but failed to run. So we started to investigate the cause of the problem.

First, we will check the linux system services and status

1212.png

From the above picture, you can see Systemctl status EasyCVR_Service, which shows that the service status is running failure, and the error code is 127.

Among them, ExecStart=..., is the absolute path of program execution. Run the path in ExecStart directly in the console to see.

1213.png

It can be analyzed that libhpr.so was not added to the system/lib64, which caused the service to fail to start, so we only need to copy libhpr.so to /lib64 to run the program normally.

EasyCVR interface display:

EasyCVR.png

Guess you like

Origin blog.csdn.net/EasyNVS/article/details/107834489