Crash Restart

Description

Adding certain cameras with the wrong plugin type causes the exacqVision Server to go into a crash loop.

Product

exacqVision Server

Steps to Reproduce

Add a camera using the wrong plugin type

Expected Results

Camera fails to connect

Actual Results

Camera fails to connect
The Server status alternates between “Connected” and “Address Found but Not an exacqVision Server” on the Client Systems page

Solution

Stop the exacqVision Server service
Import a saved export OR
Edit the associated plugin xml file, removing the section for the offending camera(s) OR
Delete the associated plugin xml file being mindful this could also remove cameras that are correctly using the plugin
Start the exacqVision Server service
Determine the correct plugin https://www.exacq.com/integration/ipcams/
Add the camera(s) using the correct plugin

NOTE: This has been specifically observed when Illustra cameras are added with Illustraflex instead of Illustra3 and Samsung cameras are added with Onvif instead of Samsung

<br>

Problem:

If the server crashes, exacqd will restart the server, but then exacqd exits. This causes the server to hang during initialization. If there is no watchdog timer, the server will remain in this state. The ‘core’ process should be killed. Introduced in server 9.5.25.

In addition, if someone was to accidentally kill the exacqd process, ‘core’ may enter a bad state with loss of functionality. On Windows, SCM will start exacqd again and this may lead to multiple instances of ‘core’. Now ‘core’ will detect the disappearance of exacqd and shutdown gracefully. On Windows, SCM will restart the server. On Linux, if the watchdog is present, it will reboot the system.