Troubleshooting neural network modules of video analytics🔗

List of neural network modules🔗

Neural network modules of video analytics:

Verifying conditions and configuration🔗

Before proceeding with troubleshooting, review the documentation for the video analytics module and ensure that:

the module is enabled and configured according to the documentation;
the conditions for using the module meet the requirements and recommendations.

Possible issues🔗

Paging file is disabled or incorrectly configured on the server🔗

Symptoms🔗

Video analytics modules do not start or do not operate correctly.
If video analytics modules are enabled, the server restarts continuously.

Recommendations🔗

It is not recommended to place paging files on physical disks that are used for recording video archives.

Solution for Windows server🔗

Stage 1 — Checking the size of the paging file in Windows settings
- Step 1 — Open the System Properties window:
  
  Press the Win + R key combination, type sysdm.cpl, and press Enter.
- Step 2 — Go to the Performance section:
  
  In the System Properties window, go to the Advanced tab and click the Settings button in the Performance section.
- Step 3 — Check the size of the paging file:
  
  In the Performance Options window, go to the Advanced tab.
  
  The Virtual Memory section will display the total size of the paging file on all drives.
Ensure that the paging file size is at least half of the total RAM.

For example, if the server has 16 GB (16384 MB) of RAM, the paging file size should be at least 8 GB (8192 MB).

Configure the paging file if necessary.
Stage 2 — Configuring the paging file
- Step 4 — Stop the Eocortex server.
- Step 5 — Open the paging file settings:
  
  Click the Change button in the Virtual Memory section of the Performance Options window.
  
  The Virtual Memory window will open.
- Step 6 — Enable manual paging file settings:
  
  Disable the Automatically manage paging file size for all drives option.
- Step 7 — Configure the paging file settings for the drive:
  
  Select the drive, enable Custom size, and set the Initial size so that it is at least half the size of the server's RAM.
  
  For example, if the server has 16 GB (16384 MB) of RAM, the Initial size should be at least 8192 MB.
  
  Set the Maximum size as well. There are no specific recommendations for this parameter, but it is required and must not be less than the initial size.
- Step 8 — Apply the paging file settings:
  
  Click the Set button in the Virtual Memory window, then close all settings windows using the OK buttons.
- Step 9 — Restart the computer.

Tip

If the problem persists, please contact technical support.

Solution for GNU/Linux server🔗

Stage 1 — Checking for a swap file
- Step 1
  
  Run the following command in the terminal:
```
$ sudo swapon -s
```
  As a result, information about all swap files used on the server will be displayed. The TYPE column will indicate the type of swap file — partition or file, and the SIZE column will indicate its size.
  
  Example of a response:
```
NAME        TYPE        SIZE   USED     PRIO
/dev/sda5   partition   16384M 507.4M   -1
/swapfile   file        8192M  0        -2
```
Ensure that the swap file size is equal to or slightly larger than the server's RAM (for systems with low RAM, it is recommended to set the swap file size to twice the amount of RAM).

For example, if the server has 16 GB (16,777,216 KB) of RAM, the swap file size should also be at least 16,777,216 KB.

Configure the swap file if necessary.
Stage 2 — Configuring the swap file

Note

The following examples show how to create a 16 GB swap file named swapfile in the / directory.
- Step 2
  
  Ensure that there is sufficient free space on the drive to create the swap file or increase its size:
```
$ df -h /
```
- Step 3
  
  Create a swap file:
```
$ sudo fallocate -l 16G /swapfile
```
  Tip
  
  If the fallocate command is not supported, please use another command:
  $ sudo dd if=/dev/zero of=/swapfile bs=1G count=16
- Step 4
  
  Set access rights to the swap file:
```
$ sudo chmod 600 /swapfile
```
- Step 5
  
  Initialize the created file as swap and activate it:
```
$ sudo mkswap /swapfile

$ sudo swapon /swapfile
```
- Step 6
  
  Ensure that the created swap file is active:
```
$ sudo swapon -s
```
- Step 7
  
  To ensure that the swap file is active every time the system starts, add the following line to the /etc/fstab file:
```
/swapfile none swap sw 0 0
```

Tip

If the problem persists, please contact technical support.