Zoneminder keeps going into "Stopped" state

Forum for questions and support relating to the 1.29.x releases only.
Post Reply
moorsey
Posts: 51
Joined: Sun Jan 03, 2010 8:56 am

Zoneminder keeps going into "Stopped" state

Post by moorsey » Wed Apr 13, 2016 11:18 am

Hi all,

Have a fresh Zoneminder 1.29.0 install on Mint 17.3 XFCE

Installed from PPAs (iconner master)

Have come across this about four times now, logging into Zoneminder web page and finding the status as "Stopped":

Image

After the last occurence, I turned on logging to disk, so I could post some data here

My current example, recording is still actually happening, two out of four cameras are still recording and have viewable events up to current. One of the cameras ("Rear") last recorded at 09:30 on the 10th April and the fourth camera last recorded at 10:10 today (10th April)

So bit of a jumble.

I have copied logs from around 09:30 on the 10th April from the rear camera. ZMC log still thinks it is capturing, but ZMA at 09:38 (which fits) ended with " Closing event 35584, shutting down" and nothing else after.

So I'm non the wiser as to what caused it to shut down, I'm thinking perhaps I need to up the logging level and wait for it to happen again as my next step? But any thoughts would be much appreciated. A little worried that something could happen while the system has randomly stopped!

Many thanks

Martin

zmc.m1.log.1

Code: Select all

04/10/16 08:20:25.913864 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1971000 - Capturing at 5.99 fps]
04/10/16 08:23:12.941658 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1972000 - Capturing at 5.99 fps]
04/10/16 08:25:59.880246 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1973000 - Capturing at 5.99 fps]
04/10/16 08:28:46.851831 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1974000 - Capturing at 5.99 fps]
04/10/16 08:31:33.878994 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1975000 - Capturing at 5.99 fps]
04/10/16 08:34:20.814689 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1976000 - Capturing at 5.99 fps]
04/10/16 08:37:07.784662 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1977000 - Capturing at 5.99 fps]
04/10/16 08:39:54.812984 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1978000 - Capturing at 5.99 fps]
04/10/16 08:42:41.759848 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1979000 - Capturing at 5.99 fps]
04/10/16 08:45:28.718174 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1980000 - Capturing at 5.99 fps]
04/10/16 08:48:15.745236 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1981000 - Capturing at 5.99 fps]
04/10/16 08:51:02.714442 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1982000 - Capturing at 5.99 fps]
04/10/16 08:53:49.665421 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1983000 - Capturing at 5.99 fps]
04/10/16 08:56:36.677737 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1984000 - Capturing at 5.99 fps]
04/10/16 08:59:23.629876 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1985000 - Capturing at 5.99 fps]
04/10/16 09:02:10.590425 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1986000 - Capturing at 5.99 fps]
04/10/16 09:04:57.615587 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1987000 - Capturing at 5.99 fps]
04/10/16 09:07:44.585530 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1988000 - Capturing at 5.99 fps]
04/10/16 09:10:31.538731 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1989000 - Capturing at 5.99 fps]
04/10/16 09:13:18.559065 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1990000 - Capturing at 5.99 fps]
04/10/16 09:16:05.519757 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1991000 - Capturing at 5.99 fps]
04/10/16 09:18:52.458694 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1992000 - Capturing at 5.99 fps]
04/10/16 09:21:39.489517 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1993000 - Capturing at 5.99 fps]
04/10/16 09:24:26.457101 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1994000 - Capturing at 5.99 fps]
04/10/16 09:27:13.393786 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1995000 - Capturing at 5.99 fps]
04/10/16 09:30:00.417952 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1996000 - Capturing at 5.99 fps]
04/10/16 09:32:47.351401 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1997000 - Capturing at 5.99 fps]
04/10/16 09:35:34.339249 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1998000 - Capturing at 5.99 fps]
04/10/16 09:38:12.477765 zmc_m1[420].WAR-zm_monitor.cpp/3100 [Buffer overrun at index 46, image 1998946, slow down capture, speed up analysis or increase ring buffer size]
04/10/16 09:38:21.356606 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 1999000 - Capturing at 5.99 fps]
04/10/16 09:41:08.327456 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 2000000 - Capturing at 5.99 fps]
04/10/16 09:43:55.288009 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 2001000 - Capturing at 5.99 fps]
04/10/16 09:46:42.299892 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 2002000 - Capturing at 5.99 fps]
04/10/16 09:49:29.221274 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 2003000 - Capturing at 5.99 fps]
04/10/16 09:52:16.209522 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 2004000 - Capturing at 5.99 fps]
04/10/16 09:55:03.233952 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 2005000 - Capturing at 5.99 fps]
04/10/16 09:57:50.164162 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 2006000 - Capturing at 5.99 fps]
04/10/16 10:00:37.164407 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 2007000 - Capturing at 5.99 fps]
04/10/16 10:03:24.167210 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 2008000 - Capturing at 5.99 fps]
04/10/16 10:06:11.102800 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 2009000 - Capturing at 5.99 fps]
04/10/16 10:08:58.110936 zmc_m1[420].INF-zm_monitor.cpp/3131 [Rear: 2010000 - Capturing at 5.99 fps]
zma_m1.log.1

Code: Select all

04/10/16 08:20:00.348885 zma_m1[5742].INF-zm_monitor.cpp/1532 [Rear: 287348 - Opening new event 35557, section start]
04/10/16 08:21:49.265849 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 288000 - Analysing at 5.95 fps]
04/10/16 08:24:36.263190 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 289000 - Analysing at 5.99 fps]
04/10/16 08:27:23.542847 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 290000 - Analysing at 5.99 fps]
04/10/16 08:30:00.061319 zma_m1[5742].INF-zm_monitor.cpp/1512 [Rear: 290928 - Closing event 35557, section end]
04/10/16 08:30:00.352401 zma_m1[5742].INF-zm_monitor.cpp/1532 [Rear: 290928 - Opening new event 35561, section start]
04/10/16 08:30:12.015944 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 291000 - Analysing at 5.92 fps]
04/10/16 08:32:59.052546 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 292000 - Analysing at 5.99 fps]
04/10/16 08:35:45.975330 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 293000 - Analysing at 6.02 fps]
04/10/16 08:38:34.448681 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 294000 - Analysing at 5.92 fps]
04/10/16 08:40:00.127218 zma_m1[5742].INF-zm_monitor.cpp/1512 [Rear: 294511 - Closing event 35561, section end]
04/10/16 08:40:00.430733 zma_m1[5742].INF-zm_monitor.cpp/1532 [Rear: 294511 - Opening new event 35567, section start]
04/10/16 08:41:21.781792 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 295000 - Analysing at 5.99 fps]
04/10/16 08:44:08.781330 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 296000 - Analysing at 5.99 fps]
04/10/16 08:46:56.258088 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 297000 - Analysing at 5.95 fps]
04/10/16 08:49:45.398956 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 298000 - Analysing at 5.92 fps]
04/10/16 08:50:00.089746 zma_m1[5742].INF-zm_monitor.cpp/1512 [Rear: 298088 - Closing event 35567, section end]
04/10/16 08:50:00.353346 zma_m1[5742].INF-zm_monitor.cpp/1532 [Rear: 298088 - Opening new event 35569, section start]
04/10/16 08:52:32.559081 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 299000 - Analysing at 5.99 fps]
04/10/16 08:55:19.845855 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 300000 - Analysing at 5.99 fps]
04/10/16 08:58:07.334007 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 301000 - Analysing at 5.95 fps]
04/10/16 09:00:00.088379 zma_m1[5742].INF-zm_monitor.cpp/1512 [Rear: 301675 - Closing event 35569, section end]
04/10/16 09:00:00.390375 zma_m1[5742].INF-zm_monitor.cpp/1532 [Rear: 301675 - Opening new event 35572, section start]
04/10/16 09:00:54.297319 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 302000 - Analysing at 5.99 fps]
04/10/16 09:03:41.302547 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 303000 - Analysing at 5.99 fps]
04/10/16 09:06:28.458894 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 304000 - Analysing at 5.99 fps]
04/10/16 09:09:16.120365 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 305000 - Analysing at 5.95 fps]
04/10/16 09:10:00.208867 zma_m1[5742].INF-zm_monitor.cpp/1512 [Rear: 305263 - Closing event 35572, section end]
04/10/16 09:10:00.464359 zma_m1[5742].INF-zm_monitor.cpp/1532 [Rear: 305263 - Opening new event 35579, section start]
04/10/16 09:12:03.239099 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 306000 - Analysing at 5.99 fps]
04/10/16 09:14:51.035246 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 307000 - Analysing at 5.95 fps]
04/10/16 09:17:38.187996 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 308000 - Analysing at 5.99 fps]
04/10/16 09:20:00.152179 zma_m1[5742].INF-zm_monitor.cpp/1512 [Rear: 308849 - Closing event 35579, section end]
04/10/16 09:20:00.427758 zma_m1[5742].INF-zm_monitor.cpp/1532 [Rear: 308849 - Opening new event 35581, section start]
04/10/16 09:20:25.505747 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 309000 - Analysing at 5.99 fps]
04/10/16 09:23:12.509535 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 310000 - Analysing at 5.99 fps]
04/10/16 09:25:59.424715 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 311000 - Analysing at 5.99 fps]
04/10/16 09:28:47.571185 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 312000 - Analysing at 5.95 fps]
04/10/16 09:30:00.068302 zma_m1[5742].INF-zm_monitor.cpp/1512 [Rear: 312430 - Closing event 35581, section end]
04/10/16 09:30:00.363791 zma_m1[5742].INF-zm_monitor.cpp/1532 [Rear: 312430 - Opening new event 35584, section start]
04/10/16 09:31:35.277961 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 313000 - Analysing at 5.95 fps]
04/10/16 09:34:22.242038 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 314000 - Analysing at 5.99 fps]
04/10/16 09:37:10.389363 zma_m1[5742].INF-zm_monitor.cpp/1287 [Rear: 315000 - Analysing at 5.95 fps]
04/10/16 09:38:18.662049 zma_m1[5742].INF-zm_signal.cpp/40 [Got signal 15 (Terminated), exiting]
04/10/16 09:38:18.750918 zma_m1[5742].INF-zm_monitor.cpp/625 [Rear: 315311 - Closing event 35584, shutting down]

bbunge
Posts: 2706
Joined: Mon Mar 26, 2012 11:40 am
Location: Pennsylvania

Re: Zoneminder keeps going into "Stopped" state

Post by bbunge » Wed Apr 13, 2016 12:16 pm

As you are running a desktop system the first thing I would look into is memory. A "df" will show you if you are running out of space in your tmpfs. You could be running out of space in your innodb_buffer_pool_size for MySQL.

moorsey
Posts: 51
Joined: Sun Jan 03, 2010 8:56 am

Re: Zoneminder keeps going into "Stopped" state

Post by moorsey » Wed Apr 13, 2016 1:03 pm

Thanks for the reply, df shows as follows:

Code: Select all

Filesystem      1K-blocks       Used Available Use% Mounted on
udev              3974484          4   3974480   1% /dev
tmpfs              804700       5024    799676   1% /run
/dev/sda1       232107000  195968700  24324824  89% /
none                    4          0         4   0% /sys/fs/cgroup
none                 5120          0      5120   0% /run/lock
none              4023492     865896   3157596  22% /run/shm
none               102400         20    102380   1% /run/user
/dev/sdb1      3845579580 3402889344 247322928  94% /media/zm
/dev/sdd1       961297736  259221888 653221628  29% /media/backup
/dev/sdc1       961297736   85958824 826484692  10% /media/storage
tmpfs showing as 1%, so assuming that's OK

THink I may have found some more info, from the combined versions of logs in syslog, which has all ZM items together in time order, which is more handy:

Code: Select all

Apr 10 09:37:57 SERVER2 zmaudit[491]: INF [Filesystem event '3/28672' does not exist in database]
Apr 10 09:37:57 SERVER2 zmaudit[491]: INF [deleting]
Apr 10 09:37:57 SERVER2 zmaudit[491]: INF [Filesystem event '3/28706' does not exist in database]
Apr 10 09:37:57 SERVER2 zmaudit[491]: INF [deleting]
Apr 10 09:37:58 SERVER2 zmaudit[491]: INF [Filesystem event '3/28524' does not exist in database]
Apr 10 09:37:58 SERVER2 zmaudit[491]: INF [deleting]
Apr 10 09:38:00 SERVER2 zmaudit[491]: INF [Filesystem event '3/28606' does not exist in database]
Apr 10 09:38:00 SERVER2 zmaudit[491]: INF [deleting]
Apr 10 09:38:00 SERVER2 zmaudit[491]: INF [Filesystem event '3/28496' does not exist in database]
Apr 10 09:38:00 SERVER2 zmaudit[491]: INF [deleting]
Apr 10 09:38:01 SERVER2 zmaudit[491]: INF [Filesystem event '3/28734' does not exist in database]
Apr 10 09:38:01 SERVER2 zmaudit[491]: INF [deleting]
Apr 10 09:38:01 SERVER2 zmaudit[491]: INF [Filesystem event '3/28618' does not exist in database]
Apr 10 09:38:01 SERVER2 zmaudit[491]: INF [deleting]
Apr 10 09:38:02 SERVER2 zmaudit[491]: INF [Filesystem event '3/28741' does not exist in database]
Apr 10 09:38:02 SERVER2 zmaudit[491]: INF [deleting]
Apr 10 09:38:02 SERVER2 zmaudit[491]: INF [Filesystem event '3/28728' does not exist in database]
Apr 10 09:38:02 SERVER2 zmaudit[491]: INF [deleting]
Apr 10 09:38:03 SERVER2 zmaudit[491]: INF [Filesystem event '3/28703' does not exist in database]
Apr 10 09:38:03 SERVER2 zmaudit[491]: INF [deleting]
Apr 10 09:38:11 SERVER2 zmc[8840]: INF [Living_Room: 25000 - Capturing at 4.74 fps]
Apr 10 09:38:12 SERVER2 zmwatch[498]: INF [Analysis daemon for  Rear needs restarting, time since last analysis 7 seconds (1460277491-1460277484)]
Apr 10 09:38:12 SERVER2 zmwatch[498]: INF [Restarting analysis daemon for  Rear]
Apr 10 09:38:12 SERVER2 zmc[420]: WAR [Buffer overrun at index 46, image 1998946, slow down capture, speed up analysis or increase ring buffer size]
Apr 10 09:38:12 SERVER2 zmc[435]: WAR [Buffer overrun at index 31, image 1998981, slow down capture, speed up analysis or increase ring buffer size]
Apr 10 09:38:12 SERVER2 zmc[453]: WAR [Buffer overrun at index 4, image 2002204, slow down capture, speed up analysis or increase ring buffer size]
Apr 10 09:38:12 SERVER2 zmdc[391]: INF ['zma -m 1' sending stop to pid 5742 at 16/04/10 09:38:12]
Apr 10 09:38:14 SERVER2 zmc[8840]: WAR [Buffer overrun at index 15, image 25015, slow down capture, speed up analysis or increase ring buffer size]
Apr 10 09:38:15 SERVER2 zmc[435]: INF [Front: 1999000 - Capturing at 5.99 fps]
Apr 10 09:38:18 SERVER2 zma[5742]: INF [Got signal 15 (Terminated), exiting]
Apr 10 09:38:18 SERVER2 zma[5742]: INF [Rear: 315311 - Closing event 35584, shutting down]
Apr 10 09:38:18 SERVER2 zmdc[391]: WAR ['zma -m 1' has not stopped at 16/04/10 09:38:18. Sending KILL to pid 5742]
Apr 10 09:38:18 SERVER2 zmdc[391]: INF ['zma -m 1' exited normally]
Apr 10 09:38:19 SERVER2 n't kill a non-numeric process ID at /usr/bin/zmdc.pl line 551, <CLIENT> line 1.
Apr 10 09:38:21 SERVER2 zmc[420]: INF [Rear: 1999000 - Capturing at 5.99 fps]
Apr 10 09:38:26 SERVER2 zmaudit[491]: INF [Filesystem event '3/28732' does not exist in database]
Apr 10 09:38:26 SERVER2 zmaudit[491]: INF [deleting]
Apr 10 09:38:27 SERVER2 zmc[8840]: WAR [Buffer overrun at index 24, image 25074, slow down capture, speed up analysis or increase ring buffer size]
Apr 10 09:38:28 SERVER2 zmaudit[491]: INF [Filesystem event '3/28686' does not exist in database]
Apr 10 09:38:28 SERVER2 zmaudit[491]: INF [deleting]
Apr 10 09:38:29 SERVER2 zmwatch[498]: ERR [Error getting last capture time for  Rear]
Apr 10 09:38:29 SERVER2 zmwatch[498]: INF [Restarting analysis daemon for  Rear]
Apr 10 09:38:29 SERVER2 zmwatch[498]: ERR [Unable to run "/usr/bin/zmdc.pl restart zma -m 1", output is "Unable to connect to server"]
Apr 10 09:38:29 SERVER2 zmaudit[491]: INF [Filesystem event '3/28507' does not exist in database]
Apr 10 09:38:29 SERVER2 zmaudit[491]: INF [deleting]
Apr 10 09:38:30 SERVER2 zmaudit[491]: INF [Filesystem event '3/28699' does not exist in database]
Apr 10 09:38:30 SERVER2 zmaudit[491]: INF [deleting]
Apr 10 09:38:31 SERVER2 zmaudit[491]: INF [Filesystem event '3/28461' does not exist in database]
Apr 10 09:38:31 SERVER2 zmaudit[491]: INF [deleting]
Apr 10 09:38:31 SERVER2 zmaudit[491]: INF [Filesystem event '3/28473' does not exist in database]
Apr 10 09:38:31 SERVER2 zmaudit[491]: INF [deleting]
Apr 10 09:38:32 SERVER2 zmaudit[491]: INF [Filesystem event '3/28534' does not exist in database]
Apr 10 09:38:32 SERVER2 zmaudit[491]: INF [deleting]
Apr 10 09:38:32 SERVER2 zmaudit[491]: INF [Filesystem event '3/28579' does not exist in database]
Apr 10 09:38:32 SERVER2 zmaudit[491]: INF [deleting]
Apr 10 09:38:34 SERVER2 zmaudit[491]: INF [Filesystem event '3/28493' does not exist in database]
Apr 10 09:38:34 SERVER2 zmaudit[491]: INF [deleting]
Apr 10 09:38:35 SERVER2 zmaudit[491]: INF [Filesystem event '3/28536' does not exist in database]
Apr 10 09:38:35 SERVER2 zmaudit[491]: INF [deleting]
Apr 10 09:38:35 SERVER2 zmaudit[491]: INF [Filesystem event '3/28596' does not exist in database]
Apr 10 09:38:35 SERVER2 zmaudit[491]: INF [deleting]
Apr 10 09:38:36 SERVER2 zmaudit[491]: INF [Filesystem event '3/28477' does not exist in database]
Apr 10 09:38:36 SERVER2 zmaudit[491]: INF [deleting]
So following that through, it has a buffer over-run, which I need to fix, the process doesn't stop, so ZM tries to kill it, then it restarts, but can't connect to server?

Final error being:
Apr 10 09:38:29 SERVER2 zmwatch[498]: ERR [Unable to run "/usr/bin/zmdc.pl restart zma -m 1", output is "Unable to connect to server"]
I'll do some searching now on the buffer over-run stuff, seem to remember there was a calculator somewhere to figure out what to set this as, long time ago I read that though. Will check and post back

Cheers

User avatar
knight-of-ni
Posts: 2332
Joined: Thu Oct 18, 2007 1:55 pm
Location: Shiloh, IL

Re: Zoneminder keeps going into "Stopped" state

Post by knight-of-ni » Wed Apr 13, 2016 1:04 pm

You are aware of the web log, which can be viewed directly from the web console, yes? It will provide a bigger picture of the entire system, all in one log, rather than individual component files.

Code: Select all

04/10/16 09:38:12.477765 zmc_m1[420].WAR-zm_monitor.cpp/3100 [Buffer overrun at index 46, image 1998946, slow down capture, speed up analysis or increase ring buffer size]
This means you have hit the limits of your system as it is currently configured. You are trying to drive your system too hard. Since this message only happens occasionally, and not over and over, that means you are right on the brink of an overload. Only when a perfect storm of system events happens at once, do things start to break. When it gets bad enough ZoneMinder can stop, or parts of it can stop.

The problem could be memory, bandwidth, disk i/o, or cpu. It could be any piece of hardware that makes up your system. It could be the database can't keep up if it has not be configured properly.

The only data you've given us which might indicate the source of the problem is your system load. Your system load shows 1.83. If you only have two (real) cpu cores then this load is too high to run reliably.

UPDATE: The errors shown in your second post are a result of the system running out of resources.
Visit my blog for ZoneMinder related projects using the Raspberry Pi, Orange Pi, Odroid, and the ESP8266
All of these can be found at https://zoneminder.blogspot.com/

hsagostini
Posts: 1
Joined: Thu Apr 14, 2016 5:03 am

Re: Zoneminder keeps going into "Stopped" state

Post by hsagostini » Thu Apr 14, 2016 5:21 am

I have this exact problem here!

In my case i have Zoneminder 1.29.0 install on Ubuntu Server 14.04.4

Code: Select all

2016-04-13 23:19:20.869763	zmc_m1		22913	ERR	Unable to get response, disconnecting	zm_remote_camera_http.cpp	1141
2016-04-13 23:19:20.538354	zmc_m1		22913	ERR	Unable to read header	zm_remote_camera_http.cpp	628
2016-04-13 23:19:20.219435	zmc_m1		22913	ERR	Select error: Interrupted system call	zm_remote_camera_http.cpp	175
2016-04-13 23:19:19.060960	zmwatch		9136	ERR	Unable to run "/usr/bin/zmdc.pl restart zma -m 1", output is "Unable to connect to server"	zmwatch.pl	
2016-04-13 23:19:16.833920	zmwatch		9136	ERR	Error getting last capture time for Monitor-1	zmwatch.pl	
2016-04-13 23:18:54.016570	zmc_m12		11120	ERR	Unable to read packet from stream 0: error -541478725 "End of file".	zm_ffmpeg_camera.cpp	167
2016-04-13 23:16:21.285300	zmwatch		9136	ERR	Error getting last capture time for Monitor-1	zmwatch.pl	
2016-04-13 23:15:46.526110	zmwatch		9136	ERR	Error getting last capture time for Monitor-1	zmwatch.pl	
2016-04-13 23:14:55.690050	zmdc			8894	ERR	'zmc -m 5' exited abnormally, exit status 255	zmdc.pl	

eprohaska
Posts: 2
Joined: Tue Feb 23, 2016 8:41 pm

Re: Zoneminder keeps going into "Stopped" state

Post by eprohaska » Thu Apr 14, 2016 10:59 pm

This is exactly what happens when the system runs out of resources. We used an older machine we had laying around that had a core i5 and 16gb of ram and it could not handle our camera load. Our cameras have to be ran at a higher resolution for identity purposes and thus the load was causing Zoneminder to stop. We ended up virtualizing the server and using 8 cores for the machine and we dropped our load from 12 to 3 just by doing that and have had no issues since.

moorsey
Posts: 51
Joined: Sun Jan 03, 2010 8:56 am

Re: Zoneminder keeps going into "Stopped" state

Post by moorsey » Fri Apr 22, 2016 12:11 pm

Thanks for the replies, CPU was at the high end when all cameras running, turned one off for the past week and everything ran OK.

Now moved the drives into my old gaming machine, 8 core i7 etc, so should be able to handle what I have now and future plans for more cameras.

Thanks all for the help

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests