Closed abishai closed 7 years ago
@abishai Please take all troubleshooting sessions to the user forum. If, during the discussion, someone can identify a specific component of the zoneminder source code misbehaving, which is not due to how zoneminder was packaged, then we can certainly file a bug report here. This is done intentionally to keep keep all discussions requests for help out of our github forum.
Previous problem reports with these same symptoms involved restarting zoneminder (usually through the web console) in a way that bypasses systemd. This is caused by a misconfiguration of the init scripts, which are created during the build/packaging process. If I recall you may be one of our FreeBSD users (always tell us what distro you are using when creating a report), in which case this probably does not apply. However, it would be worth checking if your init system agrees or differs with the start/stopped status shown on the web console. Please include that in your user forum post.
Running revision a7979eb (20161003) of video-storage-h264, 12 monitors are in h.264 passthrough. From time to time, ZM web interface indicating that instance is stopped, however all main functions works - video is written, motion is detected, ZMNinja fully works.
I enable debug output for zmdc, however I found nothing obvious. http://pastebin.com/WsGjLAqh
I can't figure out what is stopped ? All process seems to be here.