Installed zoneminder 1.30.4 (via one of the "Easy way" scripts on the wiki) onto Ubuntu 18.04. Set up 5 IP cams: 1280x1024, 8bit greyscale, cams set to 6fps. Have been running this for several days now & am getting good performance and quality. But, I had one nagging issue: I'd periodically see a ton of these zms signal 6 messages in the web gui log view:
.
.
.
2018-07-23 14:04:59.953325 zms 2937 ERR Got signal 6 (Aborted), crashing zm_signal.cpp 50
2018-07-23 14:04:59.938718 zms 2937 ERR Got signal 6 (Aborted), crashing zm_signal.cpp 50
2018-07-23 14:04:59.916859 zms 2937 ERR Got signal 6 (Aborted), crashing zm_signal.cpp 50
2018-07-23 14:04:59.895009 zms 2937 ERR Got signal 6 (Aborted), crashing zm_signal.cpp 50
2018-07-23 14:04:59.880569 zms 2937 ERR Got signal 6 (Aborted), crashing zm_signal.cpp 50
2018-07-23 14:04:59.873170 zms 2937 ERR Got signal 6 (Aborted), crashing zm_signal.cpp 50
2018-07-23 14:04:59.851254 zms 2937 ERR Got signal 6 (Aborted), crashing zm_signal.cpp 50
2018-07-23 14:04:59.829494 zms 2937 ERR Got signal 6 (Aborted), crashing zm_signal.cpp 50
2018-07-23 14:04:59.798618 zms 2937 INF Got signal 15 (Terminated), exiting zm_signal.cpp 40
There would be an initial normal "signal 15 (Terminated)" log entry, but immediately followed by dozens-to-hundreds of zms "Got signal 6 (Aborted)" messages - at the rate of several per second.
Oddly, while I had logging set to go to the database (log gui) AND the system logs, the zms signal 6 messages would only show in the log gui but they'd never make it to the system logs (all other zms messages appeared in the system logs).
What triggered this (for me): In the web gui, open an "Events view", click on an event to review the video, then click the "Video" link to get the small window for generating/saving a video. Then close all the windows in reverse order. About 70% of the time, doing this workflow triggered the zms signal 6 errors.
I set logging to debug (to the system logs only) to get more clues about this but, ironically, I could never reproduce the problem when debug logging was enabled. This led me to believe some weird latency/timing edge condition was tripping zms/zm_signal and putting it into a short lived race condition. So I made 3 changes to each of the High, Medium and Low B/W settings in Options:
Set WEB_M_VIDEO_MAXFPS to match my cams (6)
Turned off WEB_M_SHOW_PROGRESS
Set WEB_M_AJAX_TIMEOUT to 10000
After doing this I no longer trigger zms signal 6 logging storms when using the web gui.