Advice for deployment - a stable install of 1.36?

[texastexas]

I'm a ZM newbie. I'm passable with linux/unix.

I loved playing with it a few weeks ago when I tried my first download.

Now, I'm getting ready to deploy a version for real life use. So far, I haven't found anything that just works. I'm not adverse to fiddling, if I get something at the other end that is robust. I feel like every time I fiddle with ZM, something else is a breaks.

I just did a fresh install of 1.36.8 on Ubuntu sever focal. I followed exactly:

https://bkjaya.wordpress.com/2021/05/15 ... cal-fossa/

And there are memory problems and:

10/15/2021 13:14:20.053439 zmdc[1282].INF [ZMServer:411] ['zmc -m 1' starting at 21/10/15 13:14:20, pid = 3953]
10/15/2021 13:14:20.053449 zmdc[3953].INF [ZMServer:411] ['zmc -m 1' started at 21/10/15 13:14:20]
10/15/2021 13:15:03.844450 zmdc[1282].INF [ZMServer:706] ['zmc -m 1' crashed, signal 8]

Events fail after one second.

I tried to follow:

https://wiki.zoneminder.com/Ubuntu_Serv ... der_1.36.x

but the mods to the mysql conf were fatal in my case and I'm not good enough at mysql to run down the problems

Is there an install of a recent version of ZM (preferable 1.36) that's pretty bulletproof?

[Magic919]

Drop out the database tweaks and then work through any remaining problems. It’s might not be 100% plug and play, but it’s not bad.

[iconnor]

The instructions for 1.36 havn't changed since 1.34.

https://www.youtube.com/watch?v=RhBsW8HkOG4

Just type 1.36 instead of 1.34 wherever appropriate.

[bbunge]

Easy instructions: https://wiki.zoneminder.com/Ubuntu_Serv ... der_1.36.x

[junior466]

I am having the exact same problem and been pulling my hair out lately. Constant

Code: Select all

'zmc -m 1' crashed, signal 8

in the logs.

Any ideas?

[kitkat]

I tried to follow:

https://wiki.zoneminder.com/Ubuntu_Serv ... der_1.36.x

but the mods to the mysql conf were fatal in my case and I'm not good enough at mysql to run down the problems

There are errors in that guide which will very probably stop MySQL/Mariadb from starting: innodb_buffer_pool_ size shouldn't have a space in it, and innodb_log_file_size - 32M should be innodb_log_file_size = 32M (equals instead of minus)

Also, changing innodb_log_file_size can often prevent the service starting or the InnoDB handler/driver loading if you don't get rid of the old logs first.

Check the database log (/var/log/mariadb/mariadb.log) for errors along the lines of

Code: Select all

InnoDB: Error: log file ./ib_logfile0 is of different size 0 123456789  bytes
InnoDB: than specified in the .cnf file 0 987654321 bytes!

You can probably fix this (works for me) by:

Stopping the mariadb service (systemctl stop mariadb).
Deleting (or moving/renaming) the old log files (mv /var/lib/mysql/ib_logfile[01] /tmp/)
Starting mariadb (systemctl start mariadb)

Check the log again and you should see a warning that the log files are missing and that they're being recreated.