monitor gone berserk

[gnuorder]

I have several remote monitors that are set up to record with a section length of 900 and they work fine. I have a local monitor set up the same way and it often goes berserk. It will start off saving in 900 sec chucks but then it switches to 14 second chunks or even less. Now it even starts off using small sections. This uses up disk space rapidly and is hard to delete all those events. This is a bt878 type TV card using the composite input and nothing else. I see nothing out of the ordinary in the logs.

[zoneminder]

Can you post a listing of some sample event details so I can see if there's anything that stands out as to why this might be happening.

Phil

[gnuorder]

Well I had some saved up for you but I purged them all. I ended up deleting the events from console because web was too slow. I had 27000 or more events. I ended up screwing up the database doing that but I have it fixed now. Next time it screws up, I will save it.

[gnuorder]

Here is an example of it going haywire. It was exactly 50 events after starting it up but that isn't always the case. I thought I found the problem with some perl X10 stuff missing from the install. I dont use x10 so I disabled it but that monitor seems to have X10 triggering always on even if I uncheck it. I will make another monitor to monitor the same source and see if that one does the same thing.

Id Name Monitor Cause Time Duration Frames Alarm
Frames Total Score Avg. Score Max. Score Mark
280591 Event-280591 GE-wireless Continuous 06/14 12:51:31 8.04 12 0 0 0 0
280590 Event-280590 GE-wireless Continuous 06/14 12:51:29 8.01 12 0 0 0 0
280589 Event-280589 GE-wireless Continuous 06/14 12:51:25 10.02 13 0 0 0 0
280588 Event-280588 GE-wireless Continuous 06/14 12:51:24 7.62 12 0 0 0 0
280584 Event-280584 GE-wireless Continuous 06/14 12:45:00 387.29 200 0 0 0 0
280581 Event-280581 GE-wireless Continuous 06/14 12:30:01 899.68 459 0 0 0 0
280579 Event-280579 GE-wireless Continuous 06/14 12:15:01 899.61 459 0 0 0 0
280572 Event-280572 GE-wireless Continuous 06/14 12:00:01 899.88 459 0 0 0 0
280569 Event-280569 GE-wireless Continuous 06/14 11:45:01 899.85 459 0 0 0 0
280565 Event-280565 GE-wireless Continuous 06/14 11:30:00 901.83 460 0 0 0 0
280562 Event-280562 GE-wireless Continuous 06/14 11:15:00 899.73 459 0 0 0 0
280559 Event-280559 GE-wireless Continuous 06/14 11:00:00 899.60 459 0 0 0 0

[zoneminder]

Events will be closed if a capture daemon crashes. Do you know if this is happening on your system?

Phil

[gnuorder]

Yes there are. I originally didn't see them because I was grepping for "zmc -m 7" by mistake.

'zma -m 7' starting at 05/06/14 23:15:21, pid = 27508
'zma -m 7' crashed at 05/06/14 23:15:26, exit status 255
'zma -m 7' started at 05/06/14 23:25:26
'zma -m 7' starting at 05/06/14 23:25:26, pid = 27577
'zma -m 7' crashed at 05/06/14 23:25:31, exit status 255
'zma -m 7' started at 05/06/14 23:35:31
'zma -m 7' starting at 05/06/14 23:35:31, pid = 27689
'zma -m 7' crashed at 05/06/14 23:35:36, exit status 255

What does this error mean and why does it start randomly? It worked for maybe a week before this.

Oh, and the new monitor I made does the same thing so it's unrelated to why the x10 trigger stays set.

[zoneminder]

You should find something in /var/log/messages that corresponds to the crashes. If you grep for ERR then you should find it fairly quickly.

Phil