Troubleshooting For Recording - Canon VB-C300 Administrator's Manual

Troubleshooting for Recording

When a recording trouble occurs when playing back recorded vide data (e.g., data is not found), you can
guess the cause by checking the Event Logs of the VK-64/VK-16 and Storage Server Log (re_log).
Log
Event
Connection to
<Camera Server's IP
address> error: Error
ERROR (connect) : socket type=
occurred (<Error No.>:
(IMAGE/EVENT/COMMAND),
<Description>)
cameraserver= (<host>:<port>)
Ex. Connection to
win32_error= (<Winsock Error
192.168.100.1 error:
Code>:<Error Message>)
Error occurred
(10060: Connection
time-out)
Camera <camera> Effective
Effective recording recording rate (y%->z%)
rate (<Recording rate If the following message is also
before change> recorded, a large amount of
<Recording rate after captured data may have been
change> %) discarded:
Ex. Effective recording Camera <camera>: <x>/<y>
rate (100 90.0%) frames discarded due to busy
frame queue in last 1 minutes.
Camera <camera>: <x>/<y>
N/A frames discarded due to busy
drive thread in last 1 minutes.
Camera <camera>: <x>/<y>
N/A frames discarded due to busy
frame queue in last 1 minutes.
Error writing frame for camera
<camera>: <error message>
If the following messages are also
recorded, a large amount of
captured data may have been
discarded:
N/A
Camera <camera>: <x>/<y>
frames discarded due to busy
frame queue in last 1 minutes.
Camera <camera>: <x>/<y>
frames discarded due to busy
drive thread in last 1 minutes.
Recording to E:\drive
is on standby due to
No Storage Server Log
shortage of free HDD
space.
Storage Server
Error No.
10050
10054
10060
10061
10064
The effective recording rate is too low
(below 50 %).
Load due to writing recorded video data
onto HDD may be too high.
CPU load of the Storage Server PC may
be too high.
Load due to writing recorded video data
onto HDD may be too high.
Cause
Description
Network may be out of
service.
A Camera Server's
network problem or
session disconnection due
to Camera Server's reboot
has occurred.
Sensor and motion detection events
occur too frequently, exceeding the
standard given by the guideline.
CPU load of the Storage Server PC
may be high.
The specified drive may be unable to
be written.
The time setting of the VK-64/VK-16
Storage Server PC may have been
changed to the past (in the NTP
operation environment).
Countermeasure
Check the network (HUB, cables, etc.)
for any problem and confirm that the
Camera Server is operating normally.
Adjust the recording schedule and
sensitivity of motion detection.
Check the CPU usage and terminate
any applications which are putting
heavy loads to the CPU.
Use the Windows' Performance
Monitor to check the writing status of
HDD. Review the recording schedule or
add servers as required.
Use the Task Manager to find out the
application causing the problem.
If the VK-64/VK-16 module
(AE.EXE) is causing the problem,
the event generation frequency may
be too high. Try the following:
- Shorten the Maximum retained
history setting for the recorded data
- Reduce the number of events to
generate
- Add servers to distribute the load.
Check the drive for recording video
data.
If you are using NTP to adjust time,
shorten the synchronization interval
with NTP (e.g., 7 days 1 day).
Shorten the Maximum retained history
or add HDD. Also, review the recording
schedule.
9-3