I am getting these errors in the log.
2016-04-13 10:05:12.268177 zms 15838 INF addr2line -e /usr/lib/zoneminder/cgi-bin/nph-zms 0x7f956b35b512 0x7f956a1bd340 0x7f956b304166 0x7f956b304ddb 0x7f956b2c3041 0x7f9567770ec5 0x7f956b2c3d47 zm_signal.cpp 113
2016-04-13 10:05:12.263458 zms 15838 INF Backtrace complete, please execute the following command for more information zm_signal.cpp 112
2016-04-13 10:05:12.262723 zms 15838 ERR Backtrace 6: /usr/lib/zoneminder/cgi-bin/nph-zms(+0x1fd47) [0x7f956b2c3d47] zm_signal.cpp 105
2016-04-13 10:05:12.261919 zms 15838 ERR Backtrace 5: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f9567770ec5] zm_signal.cpp 105
2016-04-13 10:05:12.260900 zms 15838 ERR Backtrace 4: /usr/lib/zoneminder/cgi-bin/nph-zms(main+0x991) [0x7f956b2c3041] zm_signal.cpp 105
2016-04-13 10:05:12.259559 zms 15838 ERR Backtrace 3: /usr/lib/zoneminder/cgi-bin/nph-zms(_ZN13MonitorStream9runStreamEv+0xb4b) [0x7f956b304ddb] zm_signal.cpp 105
2016-04-13 10:05:12.258900 zms 15838 ERR Backtrace 2: /usr/lib/zoneminder/cgi-bin/nph-zms(_ZN7Monitor11SingleImageEi+0x46) [0x7f956b304166] zm_signal.cpp 105
2016-04-13 10:05:12.258171 zms 15838 ERR Backtrace 1: /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7f956a1bd340] zm_signal.cpp 105
2016-04-13 10:05:12.255716 zms 15838 ERR Backtrace 0: /usr/lib/zoneminder/cgi-bin/nph-zms(_Z14zm_die_handleriP9siginfo_tPv+0x72) [0x7f956b35b512] zm_signal.cpp 105
2016-04-13 10:05:12.254595 zms 15838 ERR Signal address is 0x34, from 0x7f956b304166 zm_signal.cpp 84
2016-04-13 10:05:12.253916 zms 15838 ERR Got signal 11 (Segmentation fault), crashing zm_signal.cpp 54
2016-04-13 10:05:12.252460 zms 15838 ERR Got empty memory map file size 0, is the zmc process for this monitor running? zm_monitor.cpp 533
Everything seems to run fine. I was hing issues with the time being out of sync but I fix that by installing vmware tools. The only issue I have been having is with the VM just turning off but it only happens maybe once a week. The syslog does not show anything about it shutting down. Just looks like someone yanked the power to it.
I dont know if the shutdown is related to theses errors I'm getting but I would still like to fix this error if I can.