zmdc crash

Forum for questions and support relating to the 1.32.x releases only.
Post Reply
kovaga
Posts: 7
Joined: Wed Nov 27, 2019 6:55 pm

zmdc crash

Post by kovaga »

Hi list,
following a pretty standard apt dist-upgrade, my zoneminder is not operational anymore.

zmc and zma processes crash
with the following in the zmdc.log

11/27/2019 19:49:52.460812 zmdc[3185].INF [ZMServer:692] ['zma -m 2' crashed, signal 134]
11/27/2019 19:49:52.470776 zmdc[3185].INF [ZMServer:692] ['zmc -m 2' crashed, signal 134]
no memkey in zmMemInvalidate
no memkey in zmMemInvalidate
no memkey in zmMemInvalidate
no memkey in zmMemInvalidate

if I start the processes manually, i get the
# ⚡ root@homenas  /var/log/zm  zma -m 2
double free or corruption (out)
[1] 2965 abort (core dumped) zma -m 2

⚡ root@homenas  /var/log/zm  zmc -m 2
double free or corruption (out)
[1] 3047 abort (core dumped) zmc -m 2

Amongst the packages that were upgraded is
mysql-server-5.7:amd64 (5.7.27-0ubuntu0.18.04.1, 5.7.28-0ubuntu0.18.04.4)

Any ideas on where to dig?
kovaga
Posts: 7
Joined: Wed Nov 27, 2019 6:55 pm

Re: zmdc crash

Post by kovaga »

Solved by upgrading to 1.33.14.
tcg
Posts: 46
Joined: Fri Jan 13, 2012 3:41 pm

Re: zmdc crash

Post by tcg »

Just wanted to post that I ran into this same problem over the weekend and spent way too many hours trying to find the cause. Like you, I saw that mysql had been updated and immediately assumed that was my problem. Manually running zmc gave me the same "double free" crash you mentioned. I "fixed" it by restoring my system from a level 0 dump that I made before the updates were applied. I wasn't ready to take the jump to 1.33 just yet. I have a number of ZM 1.32 servers running on Ubuntu 18.04 and this is going to make me reluctant to apply updates. Hopefully someone can provide some additional info on this problem.
Chris
Post Reply