Canon Vb-C60 Network Video Recorder VK-64/VK-16 Administrator's Manual - Page 245

Troubleshooting for Recording

Page 245 highlights

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). Event Log Storage Server Cause Countermeasure Connection to

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288

9-3
Troubleshooting
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
Cause
Countermeasure
Event
Storage Server
Connection to
<Camera Server's IP
address> error: Error
occurred (<Error No.>:
<Description>)
Ex. Connection to
192.168.100.1 error:
Error occurred
(10060: Connection
time-out)
ERROR (connect) : socket type=
(IMAGE/EVENT/COMMAND),
cameraserver= (<host>:<port>)
win32_error= (<Winsock Error
Code>:<Error Message>)
Error No.
Description
Check the network (HUB, cables, etc.)
for any problem and confirm that the
Camera Server is operating normally.
10050
Network may be out of
service.
10054
A Camera Server's
network problem or
session disconnection due
to Camera Server's reboot
has occurred.
10060
10061
10064
Effective recording
rate (<Recording rate
before change>
<Recording rate after
change> %)
Ex. Effective recording
rate (100
90.0%)
Camera <camera> Effective
recording rate (y%->z%)
If the following message is also
recorded, a large amount of
captured data may have been
discarded:
Camera <camera>: <x>/<y>
frames discarded due to busy
frame queue in last 1 minutes.
The effective recording rate is too low
(below 50 %).
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.
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.
N/A
Camera <camera>: <x>/<y>
frames discarded due to busy
drive thread in last 1 minutes.
Load due to writing recorded video data
onto HDD may be too high.
Use the Windows' Performance
Monitor to check the writing status of
HDD. Review the recording schedule or
add servers as required.
N/A
Camera <camera>: <x>/<y>
frames discarded due to busy
frame queue in last 1 minutes.
CPU load of the Storage Server PC may
be too high.
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.
N/A
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:
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.
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).
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).
Recording to E:\drive
is on standby due to
shortage of free HDD
space.
No Storage Server Log
Load due to writing recorded video data
onto HDD may be too high.
Shorten the Maximum retained history
or add HDD. Also, review the recording
schedule.