Syslog doesn't show monitor number

Forum for questions and support relating to the 1.29.x releases only.
Locked
dsdee
Posts: 29
Joined: Thu May 04, 2006 4:21 pm
Location: Denver, CO

Syslog doesn't show monitor number

Post by dsdee »

Previous installs of ZM have shown me a monitor number associated with a process, ie, zmc_m1, zma_m2.

Installation from ZMRepo on CentOS 7 is only showing the 'zma' or 'zmc' part. I'm not finding any logging parameters that seem like they relate to that...

Is this something in the compiled version in the ZMRepo or is it a config option that i'm not seeing in the logging dialog box ?
User avatar
knight-of-ni
Posts: 2406
Joined: Thu Oct 18, 2007 1:55 pm
Location: Shiloh, IL

Re: Syslog doesn't show monitor number

Post by knight-of-ni »

I'm running the same system and I see the monitor number just fine under the component column.
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/
dsdee
Posts: 29
Joined: Thu May 04, 2006 4:21 pm
Location: Denver, CO

Re: Syslog doesn't show monitor number

Post by dsdee »

I wish I was makin' this up, but:

Code: Select all

Mar 14 19:12:43 sec2 zma[19703]: INF [Front_Right_New: 045 - Opening new event 552, alarm start]
Mar 14 19:12:44 sec2 zma[19745]: INF [Front_Yard_2: 053 - Opening new event 553, alarm start]
Mar 14 19:12:45 sec2 zma[19726]: INF [Front_Yard_1: 024 - Opening new event 554, alarm start]
Mar 14 19:12:46 sec2 zma[19745]: INF [Front_Yard_2: 063 - Closing event 553, alarm end]
Mar 14 19:12:49 sec2 zma[19703]: INF [Front_Right_New: 089 - Closing event 552, alarm end]
Mar 14 19:12:49 sec2 zma[19726]: INF [Front_Yard_1: 033 - Closing event 554, alarm end]
User avatar
knight-of-ni
Posts: 2406
Joined: Thu Oct 18, 2007 1:55 pm
Location: Shiloh, IL

Re: Syslog doesn't show monitor number

Post by knight-of-ni »

Here is mine:

Code: Select all

03/14/16 20:07:08.676543 zmc_m15[13373].INF-zm_monitor.cpp/3131 [Airlink777W_Demo: 566000 - Capturing at 5.00 fps]
03/14/16 20:10:28.653033 zmc_m15[13373].INF-zm_monitor.cpp/3131 [Airlink777W_Demo: 567000 - Capturing at 5.00 fps]
03/14/16 20:13:48.679000 zmc_m15[13373].INF-zm_monitor.cpp/3131 [Airlink777W_Demo: 568000 - Capturing at 5.00 fps]
03/14/16 20:17:08.901332 zmc_m15[13373].INF-zm_monitor.cpp/3131 [Airlink777W_Demo: 569000 - Capturing at 5.00 fps]
03/14/16 20:20:29.045780 zmc_m15[13373].INF-zm_monitor.cpp/3131 [Airlink777W_Demo: 570000 - Capturing at 4.98 fps]
Look in your /var/log/zoneminder log folder, instead of /var/log/messages (after turning on log to component files)
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/
dsdee
Posts: 29
Joined: Thu May 04, 2006 4:21 pm
Location: Denver, CO

Re: Syslog doesn't show monitor number

Post by dsdee »

ok, so, turning up all the debugging options does show it logged that way in the zm_debug.log files and zm[ac]_m# files in the /var/log/zoneminder

but not in the syslog files... which is *so* helpful to have one combined, chronological log instead of the separate log files

From my old system, the syslog files showed it in syslog in the processname column... Has the syslogging changed since 1.25.0 ? old system example from syslog:

Code: Select all

% zgrep zmc_m /var/log/all.log.5.gz | tail -4
Mar  9 04:17:49 sec1 zmc_m2[3307]: WAR [Unable to capture image, retrying]
Mar  9 04:18:02 sec1 zmc_m2[3307]: WAR [Select timed out]
Mar  9 04:18:02 sec1 zmc_m2[3307]: ERR [Connection dropped by remote end]
Mar  9 04:18:02 sec1 zmc_m2[3307]: WAR [Unable to capture image, retrying]
Maybe its something only affecting the syslog side of things, and not the component logs? Knnniggett, what do you see in your /var/log/messages file? 'zmc' or 'zmc_m#' ?
User avatar
knight-of-ni
Posts: 2406
Joined: Thu Oct 18, 2007 1:55 pm
Location: Shiloh, IL

Re: Syslog doesn't show monitor number

Post by knight-of-ni »

Newer version of zoneminder can access the log right from the web console, simply by clicking logs. That is the easiest way to view your logs.
Alternatively, you can enable logging to component files and get your log information from that.

To answer your question, systemd happened to all major Linux distros, which affects system logging. Do a "systemctl -l status zoneminder" and you can see what I mean.

I don't log to /var/log/messages because that just makes reading the logs harder when events from the entire system are mashed together into a single log file. If you want one, chronological log with all zoneminder events, then clicking Log from the zoneminder web console is your best option.
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/
Locked