[solved] Fail to start after ugprade from 1.32

Forum for questions and support relating to 1.33.x development only.
Post Reply
lbm
Posts: 43
Joined: Mon Mar 26, 2018 7:44 pm

[solved] Fail to start after ugprade from 1.32

Post by lbm » Thu Jan 16, 2020 3:35 pm

Hi,

I've upgraded from 1.32 to 1.33 from the master repo.
Then ran . zmupdate.pl to update schema changes, etc..

No other changes was done.

But im now unable to start zoneminder.
If I just trie with the binary, I get.:

Code: Select all

zmpkg.pl start
01/16/2020 16:29:56.314070 zmpkg[9087].INF [main:310] [Sanity checking States table...]
01/16/2020 16:29:56.315263 zmpkg[9087].INF [main:95] [Command: start]
01/16/2020 16:29:56.395417 zmsystemctl[9093].INF [main:71] [Redirecting command through systemctl]
Job for zoneminder.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status zoneminder.service" and "journalctl -xe" for details.
And in the log...

Code: Select all

Jan 16 16:32:43 zoneminder systemd[1]: session-c427.scope: Succeeded.
Jan 16 16:32:43 zoneminder systemd[1]: zoneminder.service: New main PID 10310 does not belong to service, and PID file is not owned by root. Refusing.
Jan 16 16:32:43 zoneminder systemd[1]: zoneminder.service: New main PID 10310 does not belong to service, and PID file is not owned by root. Refusing.
Jan 16 16:32:43 zoneminder systemd[1]: zoneminder.service: Failed with result 'protocol'.
Jan 16 16:32:43 zoneminder systemd[1]: Failed to start ZoneMinder CCTV recording and surveillance system.
Jan 16 16:32:45 zoneminder systemd[1]: Stopped ZoneMinder CCTV recording and surveillance system.
Last edited by lbm on Thu Jan 16, 2020 8:35 pm, edited 1 time in total.

lbm
Posts: 43
Joined: Mon Mar 26, 2018 7:44 pm

Re: Fail to start after ugprade from 1.32

Post by lbm » Thu Jan 16, 2020 3:45 pm

Ok. So the "/lib/systemd/system/zoneminder.service" had

#User=www-data

Changed it to:
User=www-data

Can now, start but now it keeps crashing..

Code: Select all

Jan 16 16:45:08 zoneminder zmdc[11048]: INF [Starting pending process, zmc -m 5]
Jan 16 16:45:08 zoneminder zmdc[11145]: INF ['zmc -m 5' started at 20/01/16 16:45:08]
Jan 16 16:45:08 zoneminder zmdc[11048]: INF ['zmc -m 5' starting at 20/01/16 16:45:08, pid = 11145]
Jan 16 16:45:08 zoneminder zmdc[11048]: INF ['zmc -m 18' crashed, signal 6]
Jan 16 16:45:08 zoneminder zmc_m5[11145]: INF [zmc_m5] [Not enabling ffmpeg logs, as LOG_FFMPEG and/or LOG_DEBUG is disabled in options, or this monitor not part of your debug targets]
Jan 16 16:45:09 zoneminder zmdc[11048]: INF ['zmc -m 5' crashed, signal 6]

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

Re: Fail to start after ugprade from 1.32

Post by bbunge » Thu Jan 16, 2020 7:42 pm

Linux distro and version?

lbm
Posts: 43
Joined: Mon Mar 26, 2018 7:44 pm

Re: Fail to start after ugprade from 1.32

Post by lbm » Thu Jan 16, 2020 7:53 pm

Sorry.

Its Debian 10 buster, with zm: 1.33.16~20191225.23-buster
In the zm web interface, I've got the following errors:

Code: Select all

Date/Time
Component	Server	PID	Level	Message	File	Line
2020-01-16 20:53:11	zma_m18		1834	ERR	Shared data not initialised by capture daemon for monitor Backyard_Modetect	zm_monitor.cpp	498
2020-01-16 20:53:11	zmdc		1219	ERR	'zma -m 18' exited abnormally, exit status 255	zmdc.pl	
2020-01-16 20:53:11	zmdc		1219	ERR	'zma -m 18' exited abnormally, exit status 255	zmdc.pl	
2020-01-16 20:53:11	zma_m18		1833	ERR	Shared data not initialised by capture daemon for monitor Backyard_Modetect	zm_monitor.cpp	498
2020-01-16 20:53:10	zmdc		1219	ERR	'zma -m 5' exited abnormally, exit status 255	zmdc.pl	
2020-01-16 20:53:10	zma_m5		1827	ERR	Shared data not initialised by capture daemon for monitor Entrance_Modect	zm_monitor.cpp	498

lbm
Posts: 43
Joined: Mon Mar 26, 2018 7:44 pm

Re: Fail to start after ugprade from 1.32

Post by lbm » Thu Jan 16, 2020 8:32 pm

I've fixed it..

I've got these errors, at some point, and increased it to 1024:

Code: Select all

ImageBufferCount 550 is too small. Needs to be at least 553. Either increase it or decrease time between keyframes	
Tried to lower it, to 550, and now it works, but with the above error.

Increased it to 560, now error seems to be gone.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest