since i started using it i have a camera that keeps going down (the one using it)
i guess not crash the camera itself, crash the zms (i think?) instance for the camera
asker
no I haven't seen it ever crash the camera, but trigger does crash itself every once in a while. I believe a patch was added to master to fix it but I never tried it
looks like all the core ZM folks are out on vacation - haven't seen Andy or Isaac this week
LiENUS
im trying switching over to the api, had too many issues with trigger anyway
was going to make the trigger access code more robust, have it retry connections and the like but f it
this'll tell me if its trigger or something else too
asker
if I recall correctly, you are trying to programmatically force an alarm. If so, then yes, just the API should be fine
LiENUS
yeah, i liked trigger because it seemed to be perfect, send an alarm for 20 seconds, if i get more motion within that time frame resend for another 20 seconds and it'll renew the old one and keep it going, api i have to track how long its been since the last motion and shut down the alarms manually
ic0n
we can certainly try to figure out why zm is crashing. Which procss is crashing zma or zmc?
and what is zm version?
LiENUS
happened with 1.30.4 i tried upgrading to 1.31
give me a sec t o see if i can figure out what process
i have
03/27/18 20:33:27.466986 zma_m2[3389].INF-zm_signal.cpp/40 [Got signal 15 (Terminated), exiting]
neoweb joined the channel
neoweb
can I still use frame rate limits on mjpeg streams?
LiENUS
i thought i had something similar in zmc_m2.log but i guess not
or zmc_m2.log has been overwritten
oh no wait found it in zmc_m2.log as well
03/27/18 20:33:02.373165 zmc_m2[19902].INF-zm_ffmpeg_camera.cpp/114 [Priming capture from rtsp://admin:admin@192.168.90.22/11]
03/27/18 20:33:08.673493 zmc_m2[19902].INF-zm_ffmpeg_camera.cpp/307 [Stream open rtsp://admin:admin@192.168.90.22/11]
03/27/18 20:34:07.674241 zmc_m2[19902].INF-zm_signal.cpp/40 [Got signal 15 (Terminated), exiting]
neoweb
wait, it is only for local...
hmm
LiENUS
and zmwatch.log says its restarting both capture and analysis daemons, my guess is one goes down and the other follows it
the_k_ has quit
ic0n
signal 15 isn't a crash. It was told to quit. Check your zmwatch logs
the_k joined the channel
right, zmwatch logs should say why it restarted them.
zoneminder is restarting my server all the time. I tested with zoneminder services down and he stays up. is that normal? if yes can i configure when to reboot?
the_k joined the channel
Haxxa joined the channel
the_k has quit
asdb has quit
the_k joined the channel
digdilem
zoneminder doesn't force any restarts, asdb
if the server is spontaneously restarting, i'm guessing a hardware issue that only occurs under load
the_k has quit
the_k joined the channel
imox has quit
the_k has quit
the_k joined the channel
the_k has quit
the_k joined the channel
the_k has quit
the_k joined the channel
the_k has quit
the_k joined the channel
the_k has quit
the_k joined the channel
the_k has quit
the_k joined the channel
the_k has quit
e-anima joined the channel
the_k joined the channel
the_k has quit
Robh__ joined the channel
ic0n
LiENUS: so zmc is not capturing for more than 6 seconds. (You can change this to a longer period in zm config). Why is it not capturing? does your zmtrigger use tell it to stop capturing? Can we get the zmc logs for the same time period?