Hello everyone!
I am still fighting with trouble from this post: viewtopic.php?f=40&t=29547. I finally came to stage to enable and study debug logs. However it seems that zm switches logging only after restart. But in my situation the trouble I am trying to catch appears only after many hours of operations and disappears with zm restart. Being enabled (even limited to only two linked monitors out of ten) logs files consume about 100MBytes per minute, so I can't just leave them enabled for a day or two...
Is there any way to switch zoneminder logging without restarting it entirely?
Triggering debug logging without restart
-
- Posts: 23
- Joined: Fri Mar 22, 2019 1:21 pm
Re: Triggering debug logging without restart
kill -SIGUSR1 <pid of process>
So if debugging capture on monitor 1, do
sudo kill -SIGUSR1 <pid of zmc -m 1>
each signal sent increases logging level by 1. So you may have to do this several times to get enough. SIGUSR2 decreases the log level.
So if debugging capture on monitor 1, do
sudo kill -SIGUSR1 <pid of zmc -m 1>
each signal sent increases logging level by 1. So you may have to do this several times to get enough. SIGUSR2 decreases the log level.
-
- Posts: 23
- Joined: Fri Mar 22, 2019 1:21 pm
Re: Triggering debug logging without restart
Thank you Isaac!
I believe this information worth mentioning in zoneminder docs chapter "Options -> Logging" (https://zoneminder.readthedocs.io/en/st ... gging.html).