Tag: Server Crash

Categories
Knowledge Support Support exacqVision Server Categories Products

Server crashes on start-up when audit directory cannot be created

Affected Versions

exacqVision Server 7.6 and earlier

<br>

Description

The server will crash on start-up if the audit directory does not exist and the server cannot create a valid audit directory. An example of this is when ‘audit’ is a symlink with an invalid target or a file exists with the same name as the directory, in this case ‘audit’

<br>

Workaround

Remove the file or symlink that is prohibiting the server from creating the directory.

<br>

Resolution

Update to exacqVision Server 7.8.0 or higher

Categories
Knowledge Support Support exacqVision Server Categories Products

Onvif with incorrect profile parameter in host name would crash server

Description

Onvif plugin does allow additional parameters in the host name for added supports. Such as profile/tranport settings(#Profile=1 or #transport=udp). Profile expects a number but would crash the server if a string is entered.

<br>

Version Introduced

r38461

<br>

Platform

All

<br>

Steps to reproduce

connect onvif camera with host name and profile with string.

example: 10.16.1.1#profile=test

<br>

Expected result

string in profile is ignored and defaulted to the first profile.

server does not crash.

<br>

Actual result

server crashes with invalid string entry.

<br>

Work Around

remove profile entry or reconnect with valid profile number.

<br>

Version Fixed

r103382 dev build 8.1.8.103450

<br>

Keywords

Onvif

Categories
Knowledge Support Support exacqVision Server Categories Products

Server/SoundPI crashes on Linux

Symptom:

On some Linux systems, including 12.04, the exacqVision Server does not start. The exacqVision Client cannot connect. 

<br>

Problem:

Server 9.1.10 introduced issue causing ALSA audio mixer to fail. ‘gdb’ shows:

ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear

ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe

ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side

core: pcm_params.c:2249: snd1_pcm_hw_params_slave: Assertion `err >= 0' failed. Aborted (core dumped)

<br>

Solution:

Update exacqVision Server to version 9.2 or higher. 

Categories
Knowledge Support Support exacqVision Server Categories Products

Changing OS Language May Cause Server Crash

Symptom:

After changing OS language, user is unable to run exacqVision Server, crashes immediately after attempting to start. 

<br>

Problem:

This has been seen with some languages, notably Japanese, on Ubuntu 16.04 and 18.04 systems. 

Changes made after language configuration to ‘lshw’ cause the server service to crash. 

<br>

Solution:

Update exacqVision Server to 9.6 or later. 

Categories
Knowledge Support Support exacqVision Server Categories Products

Server Fails to Fully Restart After Crash if there is No Watchdog

Symptom:

The sever fails to fully restart after a crash. 

<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.

<br>

Solution:

Kill the ‘core’ process. Then update to exacqVision Server version 9.5.32 or higher.

Categories
Knowledge Support Support exacqVision Server Categories Products

Samsung SPE-100/400 Causes Server Crash

Symptom:

exacqVision Server crashes when connecting to a Samsung SPE-100/400 using the native Samsung plugin. 

<br>

Problem:

This encoder is only supported for use with the Onvif plugin (device type).

Additionally, the device firmware only supports HTTP version 1.0 but Live555 defaults to 1.1. 

<br>

Solution:

Connect to the device with the Onvif device type on the ‘Add IP Cameras’ page. 

Add the ‘#http=1.0’ override option to the ‘Hostname/IP Address’ field. 

If the device IP is 192.168.0.5, change it to read 192.168.0.5#http=1.0

<br>

Samsung-SPE-100-400-Causes-Server-Crash.pdf
Categories
Knowledge Support Support Categories Products exacqVision Integrations

Older Panasonic cameras cause Live555 server crash

There is a potential for discontinued cameras from Panasonic (i.e. WV-NS202A and WV-NW484) to cause the exacqVision server service to crash and thus reboot the system. This can be alleviated by:

  1. Disconnect the camera from the exacqVision Server through the exacqVision Client.
  2. Navigate to the camera’s webpage in Internet Explorer as Panasonic requires a pop-up window that works best in this browser.
  3. Navigate to Setup > Authentication Setup.
  4. Select the radial next to User Authentication to OFF. 
  5. Select SET.
  6. Connect the camera in exacq and make sure the system does not reboot once connected.

More information can be found on the DVR Trac under Panasonic Network Cameras. Since these cameras have been discontinued from Panasonic, there will most likely never be a firmware fix to address the authentication issue. 

Newer models with more recent firmware can use User Authentication, but this must be set to either “Digest” or “Basic” mode. 

<br>

Older-Panasonic-cameras-cause-Live555-server-crash.pdf
Categories
Knowledge Support Support exacqVision Server Categories Products

exacqServer Server Crash with Illustra3 Camera Plug-in

exacqVision Server versions earlier than 5.10.3 can crash if you select Apply Defaults on the Camera Settings page of an Illustra camera that does not have a motion mask configured. <br>

To avoid this issue, upgrade to exacqVision Server 5.10.3 or later. As a workaround on earlier versions, create a motion mask on the camera. <br>

Categories
Knowledge Support Support exacqVision Server Categories Products

Locating Server and Client Crash Dump Files

ExacqVision Server crash dumps can be found in the server log folder, typically C:\Program Files\exacqVision\Server\logs. The location of ExacqVision Client crash dump files varies based on the operating system. <br>

Windows Vista SP 1, Win 7, Win 8, Win 10, Win 11

  1. Click Start.
  2. Type %APPDATA%\edvrclient\logs and press Enter.
  3. Look for entries with a .DMP extension.

Windows XP

  1. Click Start and select Run.
  2. Type drwtsn32 and press Enter.
  3. Find the log file path (normally C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson).
  4. Copy and paste the path into the Run window and click OK (not shown)

MacOS

  1. Select the Go menu.
  2. Select Go To Folder.
  3. Type /Users/“Username”/Library/Logs/DiagnosticReports/. (In versions 10.4 and 10.5, replace DiagnosticReports with CrashReporter.)
  4. Click Go.