Hikvision and logcurfile.bin

[cariocap]

Hi all,

I'm using DS-2CD2032-I with firmware V5.2.0 build 140721 and setup it to use my Qnap TS-269L NAS using SMB/CIFS and everything is working ok.
I saw that the camera updates at each 10 minutes the file logcurfile.bin in the NAS.
I don't have any schedule set on the camera only Line Crossing Detection event.
Anyone know why the camera keep updating this file ? Is it something that I can turn off ?

Thanks,
Abel

 

[Zxel]

I found it mentioned in a forum post on a Hikvison form (http://www.hikvision.msk.ru/forum/4-300-1)- but it's in Russian, I used chrome to translate it.

 

[cariocap]

thanks for your answer, but as you said it only mentioned the name of the file

 

[Zxel]

You may want to ask @CBX, he's more familiar with Hikvision firmware than anyone else I know on the board - and he's online now.

 

[cariocap]

Hi Zxel,
Thanks for your suggestion. I contacted CBX and the answer to my question was:

"Yeah I wouldn't worry - it's just writing to it's event log which is stored on the NAS share.
It's not just videos and pictures - the event log is preserved also."

And this can't be turned off.
So, I can't activate the hard disk standby mode in my Qnap box. The hard disk will be always on.

 

[CBX]

If this was a normal linux server you could consider either a caching daemon, or even redirecting the logfile with a symlink to the file on a ram disk (it the file is expendable/you put in place a way to make it survive a server crash). I've no idea about this NAS product so can't provide advice there

 

[alastairstevenson]

Apart from the 3 or 4 watts per disc extra power consumption, I wouldn't worry about discs not spinning down in your NAS. With the correct model choices in use (both Seagate and WDC have NAS-specific products) they are rated for high MTBF at 24/7 operation, unlike desktop-grade (eg 'Green')discs which have high failure rates in a NAS (especially RAID) environment.
Additionally - spin up / spin down is a stressful activity for a HDD, some discs don't have a high rating for LCC (load cycle count) and high values in use are another cause of early failure.

 

[cariocap]

nice idea CBX, I will try to find in Qnap forum how to redirect the file to the ram disk and to survive a server restart, thanks

 

[cariocap]

Hi alastairstevenson,
Thanks for your feedback.
The power consumption is low but in case of a power outage this could save a few minutes from the UPS.
I'm using a desktop-grade discs, but for me the most important thing is to spin down the disks to keep lower temperatures. I live in Rio de Janeiro / Brazil and we have high temperatures here (today we have had 36ºC / 96.8ºF).
My Qnap TS-269L temperatures now (10:30PM) are:
CPU: 52ºC / 125ºF
System: 48ºC / 118ºF
HDD1: 41ºC / 105ºF
HDD2: 39ºC / 102ºF

Thanks,
Abel

 

[alastairstevenson]

Wow that's hot! Well that's a good enough reason for a spin down.

So - I did a little experiment. I have no idea if this would achieve your aim of disc spin down when alarm recording to the NAS - but it looks like you can set up a symbolic link from the file logCurFile.bin in the NAS folder the camera creates to the NAS /tmp mount point which is in RAM. But depending on your NAS model, and firmware, this can be a bit light on free space. Mine isn't too bad at 64MB, some have 32MB.
And the camera seemed quite happy to use it, recording on alarm events and still being able to retrieve the log file entries on the camera web admin.

And here is a shortened transcript of command-line activities on the QNAP NAS, which hopefully you can make some sense of.
I created a folder called /tmp/cam to hold the logCurFile.bin which I copied in before deleting it from its original location and creating the symbolic link.
Then I activated an event-based recording schedule and wandered around outside for a bit.
It seemed to work OK. But be aware - the file contents won't survive a reboot, and I don't know if the camera will simply recreate the file, or treat the NAS share as 'uninitialised' after reboot.

[/share/CACHEDEV2_DATA/cctv1/datadir0] # rm logCurFile.bin
<ir0] # ln -s /tmp/cam/logCurFile.bin logCurFile.bin
[/share/CACHEDEV2_DATA/cctv1/datadir0] # ll
drwxrwxrwx 2 IPcam everyone 12.0k Feb 11 11:44 ./
drwxrwxrwx 5 admin administ 4.0k Feb 11 11:38 ../
-rw-rw-rw- 1 IPcam everyone 512 Feb 11 11:39 HIKWS
-rw-rw-rw- 1 IPcam everyone 7.8k Feb 11 11:37 backupinfo00.bin
-rw-rw-rw- 1 IPcam everyone 7.8k Feb 11 11:37 backupinfo01.bin
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00000.mp4
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00000.pic
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00001.mp4
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00001.pic
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00002.mp4
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00002.pic

[snip]

-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00245.mp4
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00246.mp4
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00247.mp4
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00248.mp4
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00249.mp4
-rw-rw-rw- 1 IPcam everyone 4.9M Feb 11 11:37 index00.bin
-rw-rw-rw- 1 IPcam everyone 4.1M Feb 11 11:37 index00p.bin
-rw-rw-rw- 1 IPcam everyone 4.9M Feb 11 11:37 index01.bin
-rw-rw-rw- 1 IPcam everyone 4.1M Feb 11 11:37 index01p.bin
lrwxrwxrwx 1 admin administ 23 Feb 11 11:44 logCurFile.bin -> /tmp/cam/logCurFile.bin
-rw-rw-rw- 1 IPcam everyone 30.5M Feb 11 11:38 logMainFile.bin

# Activate a recording schedule.

[/share/CACHEDEV2_DATA/cctv1/datadir0] # ll
drwxrwxrwx 2 IPcam everyone 12.0k Feb 11 11:44 ./
drwxrwxrwx 5 admin administ 4.0k Feb 11 11:38 ../
-rw-rw-rw- 1 IPcam everyone 512 Feb 11 11:39 HIKWS
-rw-rw-rw- 1 IPcam everyone 7.8k Feb 11 11:37 backupinfo00.bin
-rw-rw-rw- 1 IPcam everyone 7.8k Feb 11 11:37 backupinfo01.bin
-rw-rw-rw- 1 IPcam everyone 256.0M Feb 11 11:51 hiv00000.mp4
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00000.pic
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00001.mp4
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00001.pic
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00002.mp4
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00002.pic
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00003.mp4

[snip]

-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00243.mp4
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00244.mp4
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00245.mp4
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00246.mp4
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00247.mp4
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00248.mp4
-rw-rw-rw- 1 IPcam everyone 0 Feb 11 11:37 hiv00249.mp4
-rw-rw-rw- 1 IPcam everyone 4.9M Feb 11 11:51 index00.bin
-rw-rw-rw- 1 IPcam everyone 4.1M Feb 11 11:37 index00p.bin
-rw-rw-rw- 1 IPcam everyone 4.9M Feb 11 11:51 index01.bin
-rw-rw-rw- 1 IPcam everyone 4.1M Feb 11 11:37 index01p.bin
lrwxrwxrwx 1 admin administ 23 Feb 11 11:44 logCurFile.bin -> /tmp/cam/logCurFile.bin
-rw-rw-rw- 1 IPcam everyone 30.5M Feb 11 11:38 logMainFile.bin
[/share/CACHEDEV2_DATA/cctv1/datadir0] # ll /tmp/cam
drwxr-xr-x 2 admin administ 60 Feb 11 11:42 ./
drwxrwxrwx 14 admin administ 2.3k Feb 11 11:54 ../
-rw-r--r-- 1 admin administ 15.3M Feb 11 11:42 logCurFile.bin
[/share/CACHEDEV2_DATA/cctv1/datadir0] #
[/share/CACHEDEV2_DATA/cctv1/datadir0] #
[/share/CACHEDEV2_DATA/cctv1/datadir0] # df
Filesystem Size Used Available Use% Mounted on
devtmpfs 496.8M 4.0k 496.8M 0% /dev
tmpfs 64.0M 17.9M 46.1M 28% /tmp
tmpfs 502.0M 28.0k 501.9M 0% /dev/shm
/dev/md9 515.5M 136.9M 378.6M 27% /mnt/HDA_ROOT
/dev/mapper/cachedev1 1.9T 1.7T 277.5G 86% /share/CACHEDEV1_DATA
/dev/mapper/cachedev2 199.1G 414.9M 198.2G 0% /share/CACHEDEV2_DATA
/dev/md13 371.0M 207.7M 163.3M 56% /mnt/ext
tmpfs 32.0M 0 32.0M 0% /.eaccelerator.tmp
[/share/CACHEDEV2_DATA/cctv1/datadir0] #

 

[DaveP]

but for me the most important thing is to spin down the disks to keep lower temperatures

Or ......

Stick an extra fan in somewhere and get the temperature closer to ambient air temperature ...

Sure it may cost you a minute on the UPS, but if your really struggling for UPS time then driving your self crazy to save a watt or three isn't the remedy.

 

[hereu]

Alistair, stop hiding from the Mrs in the blind spot when it's your turn to dry the dishes

Or ......

Stick an extra fan in somewhere and get the temperature closer to ambient air temperature ...

Sure it may cost you a minute on the UPS, but if your really struggling for UPS time then driving your self crazy to save a watt or three isn't the remedy.

That's what I like about the turbo (TVI). There is no fan in the smaller one and it still produces a good 1080p picture.

 

[alastairstevenson]

It didn't work - I had to do the dishes later, as usual ...