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

Access Engine Log, made to the VB-C500VD/VB-C500D

Page 271 highlights

Messages List Messages Camera Effective recording rate (% -> %) ERROR(http): socket type= (Image), cameraserver= (:) http_status=400 Failed to start the recording-mode stream for Camera . Cause The recording frame rate has been changed from y% to z% because the load of the recording engine continued to increase (decrease). An HTTP 400 error occurred when getting the image. Recording video stream requests were made to the VB-C500VD/VB-C500D/ VB-C60 from multiple Storage Servers. Action Even though there is no necessary action, you can reduce the system load using the following methods if you want to avoid frame rate decrease events. 1. Reduce the amount of data to record (For example, lower the resolution or frame rate). 2. Install an additional hard disk. 3. Implement an action such as upgrading the CPU, or increasing memory or existing hard disk space. It may be connected to SNC-P5, DF40N in the MPEG mode. Change it to the JPEG mode. For other causes, see the corresponding HTTP error code in "Error Codes in Log File" ( P. 9-31). Change the settings such that the recording video stream request is only made by one unit. Access Engine Log A list of messages shown in the Storage Server log file nvr_ae_log_.txt ( is either 0 or 1) is shown below. These messages are generated by the access engine (Win32 service) that runs as part of a Storage Server. Messages NVR Access Engine startup complete. Log level = NVR Access Engine has finished shutting down. Cause It indicates that startup of the access engine has been completed. The access engine has been stopped. Action No action is required. No action is required. Troubleshooting 9-29

  • 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-29
Messages List
Troubleshooting
Access Engine Log
A list of messages shown in the Storage Server log file
nvr_ae_log_<N>.txt
(<N> is either 0 or 1) is shown
below. These messages are generated by the access engine (Win32 service) that runs as part of a Storage
Server.
Camera <camera>
Effective recording
rate (<y>% ->
<z>%)
The recording frame rate has been
changed from y% to z% because the
load of the recording engine continued
to increase (decrease).
Even though there is no necessary
action, you can reduce the system load
using the following methods if you want
to avoid frame rate decrease events.
1.
Reduce the amount of data to record
(For example, lower the resolution or
frame rate).
2.
Install an additional hard disk.
3.
Implement an action such as
upgrading the CPU, or increasing
memory or existing hard disk space.
ERROR(http):
socket type=
(Image),
cameraserver=
(<host>:<port>)
http_status=400
An HTTP 400 error occurred when
getting the image.
It may be connected to SNC-P5, DF40N
in the MPEG mode. Change it to the
JPEG mode. For other causes, see the
corresponding HTTP error code in "Error
Codes in Log File" (
P. 9-31).
Failed to start the
recording-mode
stream for Camera
<IP address of
camera>.
Recording video stream requests were
made to the VB-C500VD/VB-C500D/
VB-C60 from multiple Storage Servers.
Change the settings such that the
recording video stream request is only
made by one unit.
Messages
Cause
Action
NVR Access Engine
startup complete.
Log level = <log
level>
It indicates that startup of the access
engine has been completed.
No action is required.
NVR Access Engine
has finished shutting
down.
The access engine has been stopped.
No action is required.
Messages
Cause
Action