Update 1.35.17~20210126.33-buster broke my system

[fiberman]

Today's update 1.35.17~20210126.33-buster broke my Zoneminder installation.
Update showed the following course/error:
-------------------------------------------
detected systemd
Detected db service is mariadb.service
Checking for db
Db exists.
Updating permissions for user zmuser@localhost

Initiating database upgrade to version 1.35.17 from version 1.35.16

Upgrading database to version 1.35.17
Loading config from DB 219 entries
Saving config to DB 220 entries
Upgrading DB to 1.35.17 from 1.35.16
ERROR 1054 (42S22) at line 1: Unknown column 'Encoder' in 'Monitors'
Output:
Command 'mysql -hlocalhost -uzmuser -p'zmpass' zm < /usr/share/zoneminder/db/zm_update-1.35.17.sql' exited with status: 1

Freshening configuration in database
Migratings passwords, if any...
Loading config from DB 220 entries
Saving config to DB 220 entries
Done Updating
Job for zoneminder.service failed because the control process exited with error code.
See "systemctl status zoneminder.service" and "journalctl -xe" for details.
Job for zoneminder.service failed because the control process exited with error code.
See "systemctl status zoneminder.service" and "journalctl -xe" for details.
invoke-rc.d: initscript zoneminder, action "start" failed.
● zoneminder.service - ZoneMinder CCTV recording and surveillance system
Loaded: loaded (]8;;file://server-tieckow/lib/systemd/system/zoneminder.service/lib/systemd/system/zoneminder.service]8;;; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2021-01-27 08:15:01 CET; 5ms ago
Process: 20861 ExecStart=/usr/bin/zmpkg.pl start (code=exited, status=255/EXCEPTION)
dpkg: Fehler beim Bearbeiten des Paketes zoneminder (--configure):
»installiertes zoneminder-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück
Trigger für man-db (2.8.5-2) werden verarbeitet ...
Trigger für systemd (241-7~deb10u5) werden verarbeitet ...
Fehler traten auf beim Bearbeiten von:
zoneminder
E: Sub-process /usr/bin/dpkg returned an error code (1)
-------------------------------------------

Zoneminder did not start after update because of error "...zmpkg[5670]: FAT [Version mismatch, system is version 1.35.17, database is 1.35.16, please run zmupdate.pl to update.]..."

In the file zm_update-1.35.17.sql ist the command "ALTER TABLE `Monitors` MODIFY `Encoder` enum('auto','h264','libx264', 'h264_omx', 'h264_vaapi', 'mjpeg','mpeg1','mpeg2');".
But in database Monitors table there is no column "Encoder".

I did a grep for "Encoder" in all sql-files in the /usr/share/zoneminder/db directory.
In zm_update-1.31.40.sql I found "ALTER TABLE `Monitors` ADD `Encoder` enum('auto','h264','h264_omx','mjpeg','mpeg1','mpeg2') AFTER `OutputCodec`"

So I connected to database and did a "ALTER TABLE `Monitors` ADD `Encoder` enum('auto','h264','h264_omx','mjpeg','mpeg1','mpeg2') AFTER `OutputCodec`" manually.
After that I did a "mysql -hlocalhost -uzmuser -p'zmpass' zm < /usr/share/zoneminder/db/zm_update-1.35.17.sql" manually.

Now I could finish the Debian update successful and Zoneminder could be started.

But not everythng works.
Remote monitors that fetch the image from the camera via http no longer work.
In syslog I see error messages - for example:
Jan 27 14:42:08 server-tieckow zmc_m2[2752]: ERR [zmc_m2] [Could not set 'crf' for output codec h264_vaapi.]
Jan 27 14:42:08 server-tieckow zmc_m2[2752]: ERR [zmc_m2] [Could not set 'crf' for output codec h264_omx.]
Jan 27 14:42:52 server-tieckow zmc_m10[27903]: ERR [zmc_m10] [Can't open video codec!]

Videos can no longer be played in the Event Viewer.

I get errors:
an 27 14:49:07 server-tieckow zms_e638985[32731]: ERR [zms_e638985] [Got signal 11 (Segmentation fault), crashing]
Jan 27 14:49:07 server-tieckow zms_e638985[32731]: ERR [zms_e638985] [Signal address is (nil), from 0x5573f83a9b73]
Jan 27 14:49:07 server-tieckow zms_e638985[32731]: ERR [zms_e638985] [Backtrace 0: /usr/lib/zoneminder/cgi-bin/nph-zms(_Z14zm_die_handleriP9siginfo_tPv+0x7a) [0x5573f83a494a]]
Jan 27 14:49:07 server-tieckow zms_e638985[32731]: ERR [zms_e638985] [Backtrace 1: /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730) [0x7fd58d26d730]]
Jan 27 14:49:07 server-tieckow zms_e638985[32731]: ERR [zms_e638985] [Backtrace 2: /usr/lib/zoneminder/cgi-bin/nph-zms(_ZN10StreamBase16checkInitialisedEv+0x43) [0x5573f83a9b73]]
Jan 27 14:49:07 server-tieckow zms_e638985[32731]: ERR [zms_e638985] [Backtrace 3: /usr/lib/zoneminder/cgi-bin/nph-zms(_ZN11EventStream9runStreamEv+0x35) [0x5573f8324a45]]
Jan 27 14:49:07 server-tieckow zms_e638985[32731]: ERR [zms_e638985] [Backtrace 4: /usr/lib/zoneminder/cgi-bin/nph-zms(main+0xeeb) [0x5573f830c41b]]
Jan 27 14:49:07 server-tieckow zms_e638985[32731]: ERR [zms_e638985] [Backtrace 5: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7fd58b00509b]]
Jan 27 14:49:07 server-tieckow zms_e638985[32731]: ERR [zms_e638985] [Backtrace 6: /usr/lib/zoneminder/cgi-bin/nph-zms(_start+0x2a) [0x5573f830e35a]]
Jan 27 14:49:08 server-tieckow web_php[11236]: 01/27/21 14:49:08.542438 web_php[11236].ERR [77.87.224.14] [socket_sendto( /run/zm/zms-729971s.sock ) failed: Connection refused] at /usr/share/zoneminder/www/includes/functions.php line 1921
Jan 27 14:49:08 server-tieckow web_php[11236]: 01/27/21 14:49:08.577478 web_js[11236].ERR [77.87.224.14] [getCmdResponse%20stream%20error%3A%20socket_sendto(%20%2Frun%2Fzm%2Fzms-729971s.sock%20)%20failed%3A%20Connection%20refused%20-%20checkStreamForErrors()] at ?view=event&eid=638985&fid=1117&filter%5BQuery%5D%5Bterms%5D%5B0%5D%5Battr%5D=MonitorId&filter%5BQuery%5D%5Bterms%5D%5B0%5D%5Bop%5D=%3D&filter%5BQuery%5D%5Bterms%5D%5B0%5D%5Bval%5D=1&filter%5BQuery%5D%5Bterms%5D%5B1%5D%5Bcnj%5D=and&filter%5BQuery%5D%5Bterms%5D%5B1%5D%5Battr%5D=StartDateTime&filter%5BQuery%5D%5Bterms%5D%5B1%5D%5Bop%5D=%3E%3D&filter%5BQuery%5D%5Bterms%5D%5B1%5D%5Bval%5D=2021-01-27+13%3A53%3A55&filter%5BQuery%5D%5Bterms%5D%5B2%5D%5Bcnj%5D=and&filter%5BQuery%5D%5Bterms%5D%5B2%5D%5Battr%5D=StartDateTime&filter%5BQuery%5D%5Bterms%5D%5B2%5D%5Bop%5D=%3C%3D&filter%5BQuery%5D%5Bterms%5D%5B2%5D%5Bval%5D=2021-01-27+14%3A48%3A54 line
Jan 27 14:49:09 server-tieckow zmwatch[2835]: ERR [Memory map file '/dev/shm/zm.mmap.10' does not exist in zmMemAttach. zmc might not be running.]

What happened with the Zoneminder Debian update?

regards
Daniel

[Magic919]

What did you think when you read the warning?

There are likely to be problems. Stay at 1.35.16 if you aren't adventurous!

[fiberman]

What did you think when you read the warning?

There are likely to be problems. Stay at 1.35.16 if you aren't adventurous!

Oh, unfortunately I haven't read that at all.
Where is this warning?
I always update my system on the command line via "aptitude update + aptitude upgrade".
Then I should have pinned Zoneminder beforehand?
That went stupid!
However, I'm a bit surprised that such a faulty package made it into the relevant repository.
Can a functioning update be expected soon?

many Greetings
Daniel

[coyote386]

Same here. Upgraded my system via apt upgrade.
Can't update DB to 1.35.17
Is there a way to downgrade to 1.35.16?


EDIT: Update and Upgrade again, now it works

[Magic919]

You are running the unstable version.

My method is that I keep ZM on hold and then run a script to unhold, update ZM then place it back on hold. I'm not aleays ready to dela with the fallout.

Read this thread viewtopic.php?f=42&t=29949

Have a browse of the 1.35.x to get the lie of the land. Look before you leap.