Occasionally zmc-d0 will be sent the TERM signal where it will die and then be re-spawned. Is this normal, and if so, what is the purpose of this? If not, what could be some causes?
Jan 12 22:23:15 localhost zmc-d0[29071]: INF [Got TERM signal, exiting]
Jan 12 22:23:15 localhost kernel: pwc Closing video device: 2608 frames received, dumped 1354 frames, 0 frames with errors.
Jan 12 22:23:15 localhost zmc-d0[29135]: INF [Debug Level = 0, Debug Log = ]
What process/script is responsible for sending the TERM sign
-
zoneminder
- Site Admin
- Posts: 5215
- Joined: Wed Jul 09, 2003 2:07 pm
- Location: Bristol, UK
- Contact:
Re: What process/script is responsible for sending the TERM
Hi Ian,
I _think_ that apart from restarts caused by direct user intervention that the only thing likely to do this would be the watchdog, zmwatch.pl. If you check the zmwatch.log you should see if it is that doing it and why. If not then check zmdc.log to see if the restart is going through that and we can try looking for other reasons.
Cheers,
Phil,
I _think_ that apart from restarts caused by direct user intervention that the only thing likely to do this would be the watchdog, zmwatch.pl. If you check the zmwatch.log you should see if it is that doing it and why. If not then check zmdc.log to see if the restart is going through that and we can try looking for other reasons.
Cheers,
Phil,
Re: What process/script is responsible for sending the TERM
Hmm.. okay.. Here's a cut from zmwatch.pl. I should note that this started happening more often after applying the patches I still need to e-mail you, but that it still happened less frequently before any modifications:
Restarting capture daemon ('/usr/local/bin/zmdc.pl restart zmc -d 0'), time since last capture 1 seconds (1074046975-1074046974)
'zmc -d 0' starting at 04/01/13 18:22:55, pid = 1412
'zmc -d 0' started at 04/01/13 18:22:55
Reading through zmwatch.pl it looks like the zmc is getting killed due to:
$max_image_delay = $monitor->{MaxFPS}>0?(10/$monitor->{MaxFPS}):ZM_WATCH_MAX_DELAY;
...
if ( $image_delay <= $max_image_delay )
Looking at the monitor settings, it looks like I've got MaxFPS set to "30.00" and looking at zmconfig.pl ZM_WATCH_MAX_DELAY is set to 15... I'll bet this is happening due to a decimal point.. I'm going to try to remove that and see what happens.
Restarting capture daemon ('/usr/local/bin/zmdc.pl restart zmc -d 0'), time since last capture 1 seconds (1074046975-1074046974)
'zmc -d 0' starting at 04/01/13 18:22:55, pid = 1412
'zmc -d 0' started at 04/01/13 18:22:55
Reading through zmwatch.pl it looks like the zmc is getting killed due to:
$max_image_delay = $monitor->{MaxFPS}>0?(10/$monitor->{MaxFPS}):ZM_WATCH_MAX_DELAY;
...
if ( $image_delay <= $max_image_delay )
Looking at the monitor settings, it looks like I've got MaxFPS set to "30.00" and looking at zmconfig.pl ZM_WATCH_MAX_DELAY is set to 15... I'll bet this is happening due to a decimal point.. I'm going to try to remove that and see what happens.
Re: What process/script is responsible for sending the TERM
The decimal point change didn't have any affect which is good really.. I believe my problem was due to my zone settings... Originally I set up the monitor at 640x480 and used pixel sizes for the zones... later I lowered the picture size to 320x240 without changing the zone settings and I believe that is when this started happening. After killing my old zones and creating new ones, this problem has stopped.