ZoneMinder Forums

ok, so, turning up all the debugging options does show it logged that way in the zm_debug.log files and zm[ac]_m# files in the /var/log/zoneminder but not in the syslog files... which is *so* helpful to have one combined, chronological log instead of the separate log files From my old system, the ...

I wish I was makin' this up, but: Mar 14 19:12:43 sec2 zma[19703]: INF [Front_Right_New: 045 - Opening new event 552, alarm start] Mar 14 19:12:44 sec2 zma[19745]: INF [Front_Yard_2: 053 - Opening new event 553, alarm start] Mar 14 19:12:45 sec2 zma[19726]: INF [Front_Yard_1: 024 - Opening new event ...

Previous installs of ZM have shown me a monitor number associated with a process, ie, zmc_m1, zma_m2. Installation from ZMRepo on CentOS 7 is only showing the 'zma' or 'zmc' part. I'm not finding any logging parameters that seem like they relate to that... Is this something in the compiled version ...

That's the only change major change I've seen.

I'm going to do another rebuild from the ground up in the next day or so just to eliminate my having done something funky during the installation from the whole equation. Will see how it looks after that.

Interesting. Never had to click on that gray bar before... Wondering why it changed between 1.25 and 1.29 . Thanks!

Instead of upgrading my old system, I built out a new CentOS7 machine, and used the ZMRepo yum repository to install Zoneminder. For the most part, it is working with no problems, captures events that I can view the stream, view live events... But I just can't view via the "Stills" link on the ...

actaually, the references to zmtriggershowtext in zmtrigger.pl also only contain one parameter, the text, and it really needs to have the monitor # and the text...

zmtrigger.pl references "zmTriggerShowText" function

actual function name as defined in SharedMem.pm is "zmTriggerShowtext"

(note case of 't' in 'text')


--d2

It may or may not be related, but make sure your setting for "Limit Continuous Motion JPEG" is set to "Unlimited" on the "Setup" Tab / Advanced / "Image Display" if it's not set to unlimited, you should be able to correlate the times of the failures with the duration set for the time-limit. --d2

ok, when a signal is lost, and then reacquired, an event is made in the DB as: 05/11/06 18:03:57.938458 zmfilter[7516].DBG [Checking event 11898] 05/11/06 18:03:57.938831 zmfilter[7516].INF [Deleting event 11898 vvv] 05/11/06 18:03:57.940280 zmfilter[7516].DBG [$VAR1 = { 'Time' => '0', 'AvgScore ...

ok, I think I've narrowed down the culprit. I can't say why the frames are coming up as part of the event in question, but the answer is that some of the events are not there, so (probably) fstat returns a 0 or -1, which diff'ed with the 'end time' of the event (or beginning time if it's the ending ...

Thanks Phil; I've turned up debug, and I've turned the cam timeout back down to hopefully cause a failure to happen sooner than later, so that I can capture the info for you. In the past 90 mins it's been running like that, it of course has had the ZMC failures we talked about yesterday, but the ...

Thanks! Works great!

Phil;

any chance we can get the patch for this???

Thanks!

Bingo. That pointed me directly to it, after looking at the other logs I had captured earlier today... So the Panasonic Network Cameras evidently have a setting that says "after XXX minutes of continuous motion viewing, change the display to refresh the image YYY seconds" I had my cam1 set to 30 ...