Documentation for Intellect 4.11.0-4.11.3. Documentation for other versions of Intellect is available too.

Previous page Typical tasks concerning system extended settings  Extended setup of the distributed architecture Next page


On the page:


Debug mode is a special operation mode when the Debug window is open, and is designed for analyzing the progress of Intellect software operation and for prompt debugging in case errors occur. Log files are created in this mode—they are stored on the disk for a specific time period. 

Enabling debug mode

By default, debug mode is disabled. To enable debug mode, do the following:

  1. Shut down Intellect.
  2. Start the Tweaki.exe utility (see the Starting and shutting-down the Tweaki.exe utility).
  3. Select the Intellect node in the tree on the left side of the utility dialog box.
  4. Change the parameter Debug Mode from None to Debug 1, Debug 2, Debug 3 or Debug 4 (see description of modes in The Settings panel of the Windows section).
  5. Click the OK button.
  6. Start Intellect.
    The Debug window item will appear in the Intellect main control menu.
  7. Select Debug window in the main control menu to open the Debug window. The selected item will be marked with a tick.

To hide the Debug window, select the Debug window item in the menu once more.

Note

The debug mode slows the system down and uses a lot of system resources. We strongly recommend to enable debug mode for debugging purposes only and to disable it when all the settings are completed.

Note

Find details in the The Debug window section of The Script object. Programming using the JScript language.

Configuring log file parameters

You can set log keeping parameters both on the Intellect setting panel in the Tweaki.exe utility (see The Settings panel of the Intellect section) and using some registry keys:

  1. The Time of log keeping (hours) parameter means the same as DebugTime registry key. It specifies the number of hours for keeping log files. 48 hours by default.
  2. The Maximum size (MB) parameter means the same as DebugSize registry key. It specifies the number of megabytes provided for log. 100 MB by default.
  3. The DebugZipDays registry key enables the logs archiving in the .gz format and specifies the time period for their keeping. 2 days by default.

Log files are rewritten when the maximum of one of the parameters is reached.

When the Debug 4 debug mode is enabled, the video.run log file displays the most detailed information about the file system and memory usage of each camera every 10 seconds. To reduce the number of info lines,, displayed every 10 seconds, to 6 (this will reduce the size of the log file), it is necessary to add the StatusInfo=0 key.

An example of the displayed information if StatusInfo=1 or no key:

Uptime: 00:00:12, memory: 423.0 MB
[FS]Health ok.
[FS]Ring cycles count: 0
[FS]Total index in memory size: 62.7 KB
[FS]Total recorders: 4, MemFile: -1, memFile total size: 16.0 MB, last frame skipped time: none, WritingQueueSize: 1500, avg speed: 18.99 MB/sec.
[FS]Total readers: 0 (cached frames: 0)
[FS]Total cameras: 4, internal VMDA detectors: 0, external VMDA detectors: 0. zone detectors: 0.
[FS]Camera 1. Writing queue: 1 frames(0% of 1500), size: 0.00 MB(0 ms). Streams(1): 1, total VMDA detectors 0 (int: 0, ext: 0), zone: 0. Grabber_IP_CAM queue size: 0.
[FS]Camera 2. Writing queue: 0 frames(0% of 1500), size: 0.00 MB(0 ms). Streams(1): 2, total VMDA detectors 0 (int: 0, ext: 0), zone: 0. Grabber_IP_CAM queue size: 0.
[FS]Camera 3. Writing queue: 0 frames(0% of 1500), size: 0.00 MB(0 ms). Streams(1): 3, total VMDA detectors 0 (int: 0, ext: 0), zone: 0. Grabber_IP_CAM queue size: 0.
[FS]Camera 4. Writing queue: 0 frames(0% of 1500), size: 0.00 MB(0 ms). Streams(1): 4, total VMDA detectors 0 (int: 0, ext: 0), zone: 0. Grabber_IP_CAM queue size: 0.
Total registered senders: 1
Objects:
VideoFrame: 38(max: 77 at '09-09-22 14:40:13.014')
AudioFrame: 0(max: 5 at '09-09-22 14:40:08.816')
Msg: 73(max: 130 at '09-09-22 14:40:06.733')
Active[1]
SendVideoFrame(local=1,compressed=1) to 'TAG-5509.1': value: 0 (max 0), delay = 46 ms, 09-09-22 14:40:15.548
Inactive[0](no new data for more than 15 seconds)

An example of the displayed information if StatusInfo=0:

Uptime: 00:00:12, memory: 427.0 MB
[FS]Health ok.
[FS]Ring cycles count: 0
[FS]Total index in memory size: 52.9 KB
[FS]Total recorders: 4, MemFile: -1, memFile total size: 16.0 MB, last frame skipped time: none, WritingQueueSize: 1500, avg speed: 7.42 MB/sec.
[FS]Total readers: 0 (cached frames: 0).

Find more about registry keys in Registry keys reference guide.

Example.

The Time of log keeping (hours) is 720 hours (1 month) and the Maximum size (MB) is 100 MB.  

One week later the size of log file is 100 MB. It starts being rewritten though the log is kept less than it was specified. 

And if DebugZipDays has the value equal to the time period in days to keep logs, then logs are not rewritten − they are archived in the *.gz format and are kept for so long as it was specified in DebugZipDays parameter.

  • No labels