Two ZMC processes running on the same monitor?

Forum for questions and support relating to the 1.30.x releases only.
Locked
duke1swd
Posts: 8
Joined: Tue Oct 10, 2017 2:04 am

Two ZMC processes running on the same monitor?

Post by duke1swd »

Background: I am a newcomer to zoneminder. I set up zoneminder on a clean Debian install last October. Got things up and running on a single camera. A couple of weeks ago I finally got the camera installed on my front porch and I'm ready to go into "production" with my one camera system.

I recently changed both the image orientation and the name of my monitor. I've also defined 2 zones. I've set up filters to remove events should my disk fill up and to remove events that are more than 30 days old.

I'm hoping to eventually get all of the various faults and errors recorded in my logs either fixed or understood. The first one I am working on is that I appear to have 2 zmc processes running against my camera. I don't believe that is correct behavior. How do I debug and/or fix this?
2018-03-17 11:19:13.227893 zma_m3[702].INF-zm_monitor.cpp/1296 [FrontPorch: 2000 - Analysing at 4.55 fps]
2018-03-17 11:19:11.272460 zmc_m3[699].INF-zm_monitor.cpp/3125 [FrontPorch: 2000 - Capturing at 4.55 fps]
Second problem: I see this error in my log. Is this related to the first problem? How do I debug or fix this?
2018-03-17 11:11:49.771879 zma_m3[675].ERR-zm_monitor.cpp/442 [Shared data not initialised by capture daemon for monitor FrontPorch]
Here is an excerpt of my log, starting with a complete server reboot.

I'd be grateful for any assistance. Thanks much.
2018-03-17 11:19:13.227893 zma_m3[702].INF-zm_monitor.cpp/1296 [FrontPorch: 2000 - Analysing at 4.55 fps]
2018-03-17 11:19:11.272460 zmc_m3[699].INF-zm_monitor.cpp/3125 [FrontPorch: 2000 - Capturing at 4.55 fps]
2018-03-17 11:15:33.534772 zma_m3[702].INF-zm_monitor.cpp/1296 [FrontPorch: 1000 - Analysing at 4.59 fps]
2018-03-17 11:15:31.716607 zmc_m3[699].INF-zm_monitor.cpp/3125 [FrontPorch: 1000 - Capturing at 4.55 fps]
2018-03-17 11:11:55.384099 zma_m3[702].INF-zma.cpp/142 [In mode 3/1, warming up]
2018-03-17 11:11:55.093850 zmdc[702].INF-zmdc.pl ['zma -m 3' started at 18/03/17 11:11:55]
2018-03-17 11:11:55.093840 zmdc[644].INF-zmdc.pl ['zma -m 3' starting at 18/03/17 11:11:55, pid = 702]
2018-03-17 11:11:55.055990 zmdc[644].INF-zmdc.pl [Starting pending process, zma -m 3]
2018-03-17 11:11:51.193064 zmc_m3[699].INF-zmc.cpp/247 [Starting Capture version 1.30.4]
2018-03-17 11:11:50.808190 zmdc[644].ERR-zmdc.pl ['zma -m 3' exited abnormally, exit status 255]
2018-03-17 11:11:50.754785 zma_m3[700].ERR-zm_monitor.cpp/442 [Shared data not initialised by capture daemon for monitor FrontPorch]
2018-03-17 11:11:50.475480 zmdc[700].INF-zmdc.pl ['zma -m 3' started at 18/03/17 11:11:50]
2018-03-17 11:11:50.474520 zmdc[644].INF-zmdc.pl ['zma -m 3' starting at 18/03/17 11:11:50, pid = 700]
2018-03-17 11:11:50.429700 zmdc[644].INF-zmdc.pl [Starting pending process, zma -m 3]
2018-03-17 11:11:50.340150 zmdc[644].INF-zmdc.pl ['zmc -m 3' starting at 18/03/17 11:11:50, pid = 699]
2018-03-17 11:11:50.340150 zmdc[699].INF-zmdc.pl ['zmc -m 3' started at 18/03/17 11:11:50]
2018-03-17 11:11:50.295910 zmdc[644].INF-zmdc.pl [Starting pending process, zmc -m 3]
2018-03-17 11:11:50.254050 zmdc[644].ERR-zmdc.pl ['zma -m 3' exited abnormally, exit status 255]
2018-03-17 11:11:50.224480 zmdc[644].ERR-zmdc.pl ['zmc -m 3' exited abnormally, exit status 255]
2018-03-17 11:11:49.771879 zma_m3[675].ERR-zm_monitor.cpp/442 [Shared data not initialised by capture daemon for monitor FrontPorch]
2018-03-17 11:11:48.793510 zmfilter[679].INF-zmfilter.pl [Scanning for events]
2018-03-17 11:11:47.553470 zmwatch[687].INF-zmwatch.pl [Watchdog pausing for 30 seconds]
2018-03-17 11:11:47.352680 zmwatch[687].INF-zmwatch.pl [Watchdog starting]
2018-03-17 11:11:46.893750 zmdc[687].INF-zmdc.pl ['zmwatch.pl' started at 18/03/17 11:11:46]
2018-03-17 11:11:46.893750 zmdc[644].INF-zmdc.pl ['zmwatch.pl' starting at 18/03/17 11:11:46, pid = 687]
2018-03-17 11:11:46.567380 zmdc[644].INF-zmdc.pl ['zmaudit.pl -c' starting at 18/03/17 11:11:46, pid = 683]
2018-03-17 11:11:46.567380 zmdc[683].INF-zmdc.pl ['zmaudit.pl -c' started at 18/03/17 11:11:46]
2018-03-17 11:11:46.235270 zmdc[679].INF-zmdc.pl ['zmfilter.pl' started at 18/03/17 11:11:46]
2018-03-17 11:11:46.235270 zmdc[644].INF-zmdc.pl ['zmfilter.pl' starting at 18/03/17 11:11:46, pid = 679]
2018-03-17 11:11:45.873890 zmdc[644].INF-zmdc.pl ['zma -m 3' starting at 18/03/17 11:11:45, pid = 675]
2018-03-17 11:11:45.873890 zmdc[675].INF-zmdc.pl ['zma -m 3' started at 18/03/17 11:11:45]
2018-03-17 11:11:45.579090 zmdc[671].INF-zmdc.pl ['zmc -m 3' started at 18/03/17 11:11:45]
2018-03-17 11:11:45.579090 zmdc[644].INF-zmdc.pl ['zmc -m 3' starting at 18/03/17 11:11:45, pid = 671]
2018-03-17 11:11:45.307360 zmpkg[599].INF-zmpkg.pl [Single server configuration detected. Starting up services.]
2018-03-17 11:11:42.299990 zmdc[644].INF-zmdc.pl [Server starting at 18/03/17 11:11:42]
2018-03-17 11:11:41.488020 zmpkg[599].INF-zmpkg.pl [Command: start]
2018-03-17 11:11:41.315560 zmpkg[599].INF-zmpkg.pl [Sanity checking States table...]
alabamatoy
Posts: 349
Joined: Sun Jun 05, 2016 2:53 pm

Re: Two ZMC processes running on the same monitor?

Post by alabamatoy »

duke1swd wrote: Sat Mar 17, 2018 5:42 pm How do I debug and/or fix this?
2018-03-17 11:19:13.227893 zma_m3[702].INF-zm_monitor.cpp/1296 [FrontPorch: 2000 - Analysing at 4.55 fps]
2018-03-17 11:19:11.272460 zmc_m3[699].INF-zm_monitor.cpp/3125 [FrontPorch: 2000 - Capturing at 4.55 fps]
I believe this is audit and control, and is normal behavior. Both of mine seem to be similar.

I cannot help with the other issue....
Locked