%1 Network error 102 in the metadata stream using scheme http
Description
Indicates a libcurl error where the status is OutOfRequest. Requires a packet capture for further investigation.%BR%%BR%
%1 – Device IP Address %BR%
Category: GenericCameraPI
%1 Network error 101 in the metadata stream using scheme http
Description
Indicates a libcurl error where the status is AlreadySending. Requires a packet capture for further investigation.%BR%%BR%
%1 – Device IP Address %BR%
%1 Network error 56 in the metadata stream using scheme http
Description
Indicates a failure receiving network data. This could be due to a network issue or a plugin issue. Requires a packet capture for further investigation.%BR%%BR%
%1 – Device IP Address %BR%
%1: Context %2. Media open but data timed out. Close and retry
Description
The video stream is still open, but we haven’t received video for 10 seconds. %BR%%BR%
%1 – Device IP Address %BR%
%2 – Device name
Notes
Will usually be noted just prior to a stream closing due to some sort of loss of communication. Possibly caused by extended packet loss or network disruption between the NVR and the device.
The processing loop has taken too long *** times. The longest time was ***ms for *** passes.
Description
A calculation is made by each camera plugin to determine if network operations ever took longer than 32ms. Once a minute, this data is logged. If it logs that it has “taken too long” this may indicate that the CPU is not able to keep up with the load.
Notes
A plugin that is not connected to any cameras will log this message once a minute and is not concerning.%BR%
Antivirus software may cause a delay in processing data.
The processing loop may take too long during heavy use, such as lots of reconnects to cameras, or many CGI commands (PTZ) and could be a sign that the system (CPU) is not powerful enough to process the current amount of camera data.
The processing loop performed *** passes and took ***ms to process the data.
Description
A calculation is made by each camera plugin to determine if network operations ever took longer than 32ms. Once a minute, this data is logged. If it logs that it has “taken too long” this may indicate that the CPU is not able to keep up with the load.
Notes
Antivirus software may cause a delay in processing data.
The processing loop may take too long during heavy use, such as lots of reconnects to cameras, or many CGI commands (PTZ) and could be a sign that the system (CPU) is not powerful enough to process the current amount of camera data.
EBADRESP – 110
Description
Invalid ping response.
Notes
This error occurs during xn_ping if an invalid response to a ping request is received. An invalid response is detected if the sequence number or the source IP address in the response is incorrect.
Input (%1) : Opening RTSP stream – %2.
Description
%1 = the camera name or ip address. %BR% %2 = the URI stream requested from the device. This indicates that the video/audio stream has been requested from the device.
Notes
This is a normal message.
*** Got response ***
Description
Configuration data requested from an IP device returned with the information listed.
Notes
This is a normal message.
%1 disconnected.
Description
%1 = The IP address of camera/device name. %BR% The camera/device has been disabled.
Notes
This is a normal message.