Hi Community!
I am not a linux expert so will try to explain the best I can:
I have a 1.23 setup with 16CH capture card. Setup was running with no problems until (I guess) HD filled up to 90% which is where it is at running Purgewhenfull, I mention this but, dunno if this could have something to do with the problem.
About every 5 minutes (havent clocked it precisely) TOP shows mysqld-max using 20% processor time, load goes above 2, during which a whole bunch of Buffer overrun at index xxx in all dvideo0, dvideo1, dvideo2 and dvideo3 WAR nings spit up on the messages.log
Monitoring TOP, once mysqld-max "finishes" or goes "away", load drops back under 1 and ZM is logging as normal, responsive and "fine and dandy".
During the time mysqld-max pushes the load on the server, sometimes events show up with no images (or broken images) I think because of the buffer overrun and the mess this error creates on newly created events.
I have up to now, deleted events in the HD as to show a 71% full thinking it had to do with Purgewhenfull deleting events phisically from the database and making everything run behind, but even with Purgewhenfull not working (because HD is under the stipulated 90%) I still get WAR Buffer overrun errors.
The 16 cams are in modect and produce in all about 200 motion detection events per hour, something I do not belive to be overload on the server. The server is a Pentium 4 machine with 2GB or ram and did handle this load without problems for months before.
The loss of realtime events while this Buffer overrun thing is what worries me.
Any light on how to debug this problem?
Regards!
mysqld-max and Buffer overrun at index xxx
Hi
I am running a single IDE drive, these are the results:
With ZM running, 3 tests:
With ZM not running, 3 tests:
With ZM running and WAR Bufferoverrun at index xxx
Again when WAR Buffer overrun is on, mysqld-max TOPs with:
What does mysql-max do?
Can its priority perhaps be changed?
Regards!
I am running a single IDE drive, these are the results:
With ZM running, 3 tests:
Code: Select all
# hdparm -tT /dev/hda
/dev/hda:
Timing cached reads: 2344 MB in 2.00 seconds = 1172.35 MB/sec
Timing buffered disk reads: 72 MB in 3.20 seconds = 22.52 MB/sec
[root@sanl1v16 /]# hdparm -tT /dev/hda
/dev/hda:
Timing cached reads: 2388 MB in 2.00 seconds = 1193.39 MB/sec
Timing buffered disk reads: 96 MB in 3.01 seconds = 31.88 MB/sec
[root@sanl1v16 /]# hdparm -tT /dev/hda
/dev/hda:
Timing cached reads: 2328 MB in 2.00 seconds = 1164.33 MB/sec
Timing buffered disk reads: 108 MB in 3.00 seconds = 35.96 MB/secWith ZM not running, 3 tests:
Code: Select all
# hdparm -tT /dev/hda
/dev/hda:
Timing cached reads: 2592 MB in 2.00 seconds = 1296.81 MB/sec
Timing buffered disk reads: 138 MB in 3.09 seconds = 44.73 MB/sec
/dev/hda:
Timing cached reads: 2924 MB in 2.00 seconds = 1462.36 MB/sec
Timing buffered disk reads: 158 MB in 3.02 seconds = 52.25 MB/sec
/dev/hda:
Timing cached reads: 2856 MB in 2.00 seconds = 1427.15 MB/sec
Timing buffered disk reads: 158 MB in 3.03 seconds = 52.12 MB/secWith ZM running and WAR Bufferoverrun at index xxx
Code: Select all
# hdparm -tT /dev/hda
/dev/hda:
Timing cached reads: 2344 MB in 2.00 seconds = 1172.60 MB/sec
Timing buffered disk reads: 108 MB in 3.01 seconds = 35.92 MB/sec
[root@sanl1v16 /]# hdparm -tT /dev/hda
/dev/hda:
Timing cached reads: 2380 MB in 2.00 seconds = 1190.30 MB/sec
Timing buffered disk reads: 130 MB in 3.01 seconds = 43.13 MB/sec
[root@sanl1v16 /]# hdparm -tT /dev/hda
/dev/hda:
Timing cached reads: 2468 MB in 2.00 seconds = 1236.53 MB/sec
Timing buffered disk reads: 126 MB in 3.07 seconds = 41.01 MB/secCode: Select all
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2717 mysql 15 0 140m 38m 4832 S 19.3 3.8 123:43.57 mysqld-maxCan its priority perhaps be changed?
Regards!
ovesely thats wrong.