Bullseye - Zoneminder Privacy page - re appearing each time console opens <Solved>

[dcung]

I also posted this in zoneminder forum.
https://forums.zoneminder.com/viewtopic.php?p=130618

I have used Zoneminder with BusterDog (Debian 10 distro).

I followed these guides/docs to install fresh zoneminder 1.36.x with Bullseye DDog (Debian 11 distro).
https://wiki.zoneminder.com/Debian_11_B ... der_1.36.x
https://zoneminder.readthedocs.io/en/la ... 1-bullseye

It works. But each time I open the console, it presented the Privacy Page again, regardless of whether I accept or decline. Sort of similar to this post, but I was not 'stuck'. I can proceed using zoneminder afterward.
https://forums.zoneminder.com/viewtopic.php?t=28398

I tried what was suggested here, but same result, it didn't work - i.e. redo fresh install with edited /usr/share/zoneminder/db/zm_create.sql
https://forums.zoneminder.com/viewtopic ... 58#p119558

I was going to try this suggestion (ie, edit the value in DB), but don't know how. Not enough DB skill.
https://forums.zoneminder.com/viewtopic ... 51#p111151

Would like to solve this. Any ideas/suggestions please?
Thanks.

[fredx181]

I cannot help but I know @rockedge knows a lot about zoneminder.

[rockedge]

@dcung,
I have directly asked the lead developer of Zoneminder for advice on the Slack dev channel for ZM.

I have a user on the Puppy Linux forum that is running a DebianDog Bullseye and has installed ZM which is working but the Privacy page keeps appearing regardless if accepted or declined. He posted on the ZM forum https://forums.zoneminder.com/viewtopic ... b5#p130618
1:39
I have not run into this problem is a long time but was asked for any advice
New
1:39 PM
I suspect it isn't saving the chosen response, for whatever reason. Perhaps a manual d update will get him through
1:43 PM
okay thanks I will relay the info. Where and how is the response stored?
1:44 PM
The value of the dropdown updates the config table as folllows:
1:44
UPDATE Config SET Value = '0' WHERE Name = 'ZM_TELEMETRY_DATA'
1:45
where value=1 or 0 depending on what is selected.
1:45 PM
Debian has always given me some wobbly behavior running ZM. Little things not seen on the Ubuntu or Void Linux OS
1:45 PM
Then it updates the config setting UPDATE Config SET Value = '0' WHERE Name = 'ZM_SHOW_PRIVACY'

[dcung]

Thank you @rockedge , @fredx181

I have updated the thread at Zoneminder forum and will do so as it progresses.

[dcung]

I have both Firefox and Chrome installed (in my Bullseye ISO mklive build).
I was using Firefox.
I just discovered that if I use Chrome, the privacy page does not appear (???).

I think Chrome is using run_as_user (i.e. puppy instead of root?).
Could it be the issue root vs user? Well, I'll use Chrome then for the time being.
Edit: I ran Chrome as root too - no privacy page appeared.

Still have not solved that I have to start zoneminder manually for each reboot (I checked that /etc/rc.x dirs have zoneminder to auto start).
In BusterDog it starts automatically.

Code: Select all

service zoneminder start

And this messages during boot time.

boot-err2.jpg (130.94 KiB) Viewed 341 times

[dcung]

I marked the thread <Solved> - at least for me.

I found out that if I use Bullseye with systemd, the errors during boot time disappeared.
EDIT - Not sure whether my BusterDog zoneminder use systemd (?) Will check later.

I still haven't resolved the Privacy Page issue. But since it only appears when using Firefox and not in Chrome, and I am indifferent with using either. No real problem for me.

[rockedge]

@dcung Looking at the screenshot it looks like the MySQL server is not running or the zm database is not set up. So Zoneminder is failing because there is no connection to the very important database.

Investigate whether or not the MySQL database server is running. Insure that the Zoneminder database is inilized and the user "zmuser" with the password "zmpass" or whatever user you have chosen is created on the MySQL server and that Zoneminder can access it.

Looking at the screenshot the errors clearly indicate probelms connecting to a Zoneminder database. If so ZM will not work correctly or at all.

[dcung]

@rockedge
The screenshot was from a non-systemd. Everything was setup already.

I think it's a matter of timing/sequence of when things get started, etc - for non systemd environment. My guess is that MySQL server is not ready at the time zoneminder service started.

The reason I say this is that I only need to start zoneminder service manually after booting finished and all works - despite all those errors. This would not be possible if zmuser/zmpass/DB is not already setup - at least that's my thinking. And also, I have verified that I can access ZM database manually (as either zmuser or root), showing values, setting values, etc (eg. ZM_TELEMETRY_DATA, ZM_SHOW_PRIVACY).

Yes, the screenshot tells that problem is connection to the database at boot time only.

Need someone with deeper knowledge of systemd vs non-systemd to fix that.
For me - I just use a 'workaround' -i.e. use a systemd built.

Edit: before I deleted the no-systemd Bullseye test setup, I removed zoneminder from autostart, so no errors during boot.
And put this in startup dir

Code: Select all

#!/bin/bash
service zoneminder start

I let it run for few hours - all works, can't see any difference in function. As far as I can tell, it 'appears' the 'same' as systemd Bullseye.
As what 'real' difference between the two install, I have no idea.
For my own personal need, I will use the Bullseye with systemd and decommission my BusterDog zoneminder.

2023-05-28-082059_904x542_scrot.png (74.73 KiB) Viewed 214 times