Master on Ubuntu 20.04

[DVB Hardware]

I am on a test machine and for a whim I upgraded Mint 19.4 > 20.04 to see what happens.
Seems ZM is broken however Apache & MSQL are running
I checked the wiki nothing for 20.04 yet , the latest is 19.10
Cannot find any guidance for 20.04 in the forum

Jimmy

[SteveGilvarry]

Might have missed it as it doesn't list a version. I did this recently just changed ppa to master.
https://wiki.zoneminder.com/Ubuntu_Serv ... der_1.34.x

[DVB Hardware]

Thanks Steve, it was hidden at the top of the wiki page
I did not have much luck with that script but I did find this one with some success

https://bkjaya.wordpress.com/2020/05/26 ... cal-fossa/
This one runs but no monitor to view (Not Green)
I know the camera works via vlc and web app and it was running ok master=1.35.5 on Linux mint 19.3
When I upgraded to 20.04 hence this problem using the same monitor configuration
I'm missing something

Attached jpg of errors, just keeps repeating


Thank You

Jimmy

[dougmccrary]

FWIW -
I did the same but on mysql, and it's working mostly fine.
I do one remote camera as in your http:; the rest are rstp:.
Looks like you have a buffer permissions problem.

[SteveGilvarry]

Maybe I will check Mint sometime but that script flies through on Ubuntu 20.04 and gives me a ready system. I do change ppa to zoneminder-master to get 1.35.

You got non h264 cameras I take it? I am not so good on them or the remote monitor side at all. But I think that is a mismatch in frame size what you have configured vs what camera is outputting. If that confirms OK turn on debug on _zmc_m1 level 9 and see what the debug file says.

[DVB Hardware]

Yes it is an older Panasonic BL-C131A that I use at home just for testing ZM
Funny part is it always worked flawlessly and on Mint 19.3 18.04 Bionic on ZM 1.35 before I changed to 20.04
I did wipe 1.35x and installed 1.34x only with the same problem

Gut feeling its a problem using 20.04 , possibly something missing, Mint based on Ubuntu kernal ??

I will check the log once I figure out to generate and find it...know some Linux not proficient

Jimmy

[DVB Hardware]

Still trying
Log (attached) seems the same as I posted if I have the correct one

Jimmy

[DVB Hardware]

GOT IT!!
Camera > Source > Path = "/nphMotionJpeg?Resolution=640x480&Quality=Standard
was imputing "nphMotionJpeg?Resolution=640x480&Quality=Standard"

I never backed up my monitors table since I only have one camera but I did have an older one that did not have "/" in the table. So I just exported the monitors table in 1.35 and it does have "/"

Jimmy

[SteveGilvarry]

Good to hear you found it.

[dougmccrary]

I guess I'm missing something or the latest three or so packages are broken somehow.

I've done a fresh install of 1.34.x , and it's functional.
"Upgrade" to master, and it's broken. mysql password problem.
apt remove zoneminder (master) and apt install zoneminder (1.34) and it works again.

Code: Select all

root@doug-System-zmx:/home/doug# zmupdate.pl

Initiating database upgrade to version 1.35.18 from version 1.34.23

Do you wish to take a backup of your database prior to upgrading?
This may result in a large file in /var/tmp/zm if you have a lot of events.
Press 'y' for a backup or 'n' to continue : n

Upgrading database to version 1.35.18
Loading config from DB 220 entries
Saving config to DB 220 entries
Upgrading DB to 1.35.0 from 1.34.23
mysql: [Warning] Using a password on the command line interface can be insecure.

Database successfully upgraded to version 1.35.0.
Upgrading DB to 1.35.1 from 1.34.23
mysql: [Warning] Using a password on the command line interface can be insecure.

Database successfully upgraded to version 1.35.1.
Upgrading DB to 1.35.2 from 1.34.23
mysql: [Warning] Using a password on the command line interface can be insecure.

Database successfully upgraded to version 1.35.2.
Upgrading DB to 1.35.3 from 1.34.23
mysql: [Warning] Using a password on the command line interface can be insecure.

Database successfully upgraded to version 1.35.3.
Upgrading DB to 1.35.4 from 1.34.23
mysql: [Warning] Using a password on the command line interface can be insecure.

Database successfully upgraded to version 1.35.4.
Upgrading DB to 1.35.5 from 1.34.23
mysql: [Warning] Using a password on the command line interface can be insecure.

Database successfully upgraded to version 1.35.5.
Upgrading DB to 1.35.6 from 1.34.23
mysql: [Warning] Using a password on the command line interface can be insecure.

Database successfully upgraded to version 1.35.6.
Upgrading DB to 1.35.7 from 1.34.23
mysql: [Warning] Using a password on the command line interface can be insecure.

Database successfully upgraded to version 1.35.7.
Upgrading DB to 1.35.8 from 1.34.23
mysql: [Warning] Using a password on the command line interface can be insecure.

Database successfully upgraded to version 1.35.8.
Upgrading DB to 1.35.9 from 1.34.23
mysql: [Warning] Using a password on the command line interface can be insecure.

Database successfully upgraded to version 1.35.9.
Upgrading DB to 1.35.10 from 1.34.23
mysql: [Warning] Using a password on the command line interface can be insecure.

Database successfully upgraded to version 1.35.10.
Upgrading DB to 1.35.11 from 1.34.23
mysql: [Warning] Using a password on the command line interface can be insecure.

Database successfully upgraded to version 1.35.11.
Upgrading DB to 1.35.12 from 1.34.23
mysql: [Warning] Using a password on the command line interface can be insecure.

Database successfully upgraded to version 1.35.12.
Upgrading DB to 1.35.13 from 1.34.23
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 1419 (HY000) at line 83: You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)
Output: Column StartDateTime already exists in Events
Column StartDateTime already exists in Events
Column EndDateTime already exists in Events
Column EndDateTime already exists in Events
Column StartDateTime already exists in Events_Hour
Column StartDateTime already exists in Events_Hour
Column StartDateTime already exists in Events_Day
Column StartDateTime already exists in Events_Day
Column StartDateTime already exists in Events_Week
Column StartDateTime already exists in Events_Week
Column StartDateTime already exists in Events_Month
Column StartDateTime already exists in Events_Month
Command 'mysql -hlocalhost -uzmuser -p'zmpass' zm < /usr/share/zoneminder/db/zm_update-1.35.13.sql' exited with status: 1

[Magic919]

Sometimes it's worth running the update command as a user with greater DB privileges.

Stay on 1.34 is the option if you prefer not to have to fiddle about.

[dougmccrary]

Sometimes it's worth running the update command as a user with greater DB privileges.

Stay on 1.34 is the option if you prefer not to have to fiddle about.

Thanks.
I don't know how to run "update command as a user with greater DB privileges."
That's a sudo su command line, and that

ERROR 1419 (HY000) at line 83: You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)

also happened during the install from the script at https://wiki.zoneminder.com/Ubuntu_Serv ... der_1.34.x, I believe.
I thought it should work given the note about mysql 8 on eoan - ubuntu 19.10.

BTW, I run two machines - one release on bionic w/1.34 and the one on focal w/1.35 I call zmx...You might say the one on 1.34 is backup.
I mostly use 1.35 when it works, cuz it's cool(er).

[Magic919]

Ok. Maybe I needed to make that clearer.

This bit from your earlier post

Code: Select all

root@doug-System-zmx:/home/doug# zmupdate.pl

Run that command, but pass it details of a MySQL superuser.

Code: Select all

--user=<dbuser> - Alternate DB user with privileges to alter DB
    -p<dbpass>, --pass=<dbpass> - Password of alternate DB user with
    privileges to alter DB

[dougmccrary]

OK. Better.
Thanks.