[support] dlandon - Zoneminder 1.36

[Kuleinc]

So, I have a spare disc in unraid that I would like to use to store recorded footage from the cameras with. Is this possible? I have a small 500GB cache drive and I think the zoneminder docker may be filling it as I have it set to purge older than 30 days, which is how long I'd like to keep the footage. I tried to move the default data path in the docker settings but im not sure this did what I want. I may need help fixing that too....

[Kuleinc]

On 9/25/2022 at 11:10 AM, Kuleinc said:

So, I have a spare disc in unraid that I would like to use to store recorded footage from the cameras with. Is this possible? I have a small 500GB cache drive and I think the zoneminder docker may be filling it as I have it set to purge older than 30 days, which is how long I'd like to keep the footage. I tried to move the default data path in the docker settings but im not sure this did what I want. I may need help fixing that too....

I decided to install a 3TB drive and just my appdata and domain folders on that. Problem solved.

[Phoenix26]

Any reason this hasn't been updated?

 

Its running 1.36.12 and 1.36.28 was just released.

 

 

 

[DaFr0n]

Does anyone know why event playbacks are coloured flickering on the bottom 3 quarters across all 3 of my cameras?

[Thomas_H]

Hello,

I get regularly hints like this "Docker critical image disk utilization:"

 

But when I'm checking my settings everything seems OK.

 

Any suggestion why Zoneminder.docker is using so much space?

 

Best regards

 

Thomas

 

[Phoenix26]

17 hours ago, Thomas_H said:

Hello,

I get regularly hints like this "Docker critical image disk utilization:"

 

But when I'm checking my settings everything seems OK.

 

Any suggestion why Zoneminder.docker is using so much space?

 

Best regards

 

Thomas

 

 

If you log into the container (select docker container and hit console) and run `du -sh` it will show you the size of the folders within the container, look for something big that you haven't mapped out to a share. Might take a while if you have a large number of events in zoneminder.

[Thomas_H]

@Phoenix26 thank you for the the hint.

 

The output is a little bit weird 

 

Quote

root@a43e6fd62ad8:/# du -sh
du: cannot read directory './proc/963/task/963/fdinfo': Permission denied
du: cannot read directory './proc/963/task/965/fdinfo': Permission denied
du: cannot read directory './proc/963/task/966/fdinfo': Permission denied
du: cannot read directory './proc/963/task/967/fdinfo': Permission denied
du: cannot read directory './proc/963/task/968/fdinfo': Permission denied
du: cannot read directory './proc/963/task/969/fdinfo': Permission denied
du: cannot read directory './proc/963/task/970/fdinfo': Permission denied
du: cannot read directory './proc/963/task/971/fdinfo': Permission denied
du: cannot read directory './proc/963/task/972/fdinfo': Permission denied
du: cannot read directory './proc/963/task/973/fdinfo': Permission denied
du: cannot read directory './proc/963/task/974/fdinfo': Permission denied
du: cannot read directory './proc/963/task/975/fdinfo': Permission denied
du: cannot read directory './proc/963/task/976/fdinfo': Permission denied
du: cannot read directory './proc/963/task/977/fdinfo': Permission denied
du: cannot read directory './proc/963/task/979/fdinfo': Permission denied
du: cannot read directory './proc/963/task/980/fdinfo': Permission denied
du: cannot read directory './proc/963/task/981/fdinfo': Permission denied
du: cannot read directory './proc/963/task/982/fdinfo': Permission denied
du: cannot read directory './proc/963/task/983/fdinfo': Permission denied
du: cannot read directory './proc/963/task/984/fdinfo': Permission denied
du: cannot read directory './proc/963/task/985/fdinfo': Permission denied
du: cannot read directory './proc/963/task/986/fdinfo': Permission denied
du: cannot read directory './proc/963/task/987/fdinfo': Permission denied
du: cannot read directory './proc/963/task/988/fdinfo': Permission denied
du: cannot read directory './proc/963/task/989/fdinfo': Permission denied
du: cannot read directory './proc/963/task/990/fdinfo': Permission denied
du: cannot read directory './proc/963/task/991/fdinfo': Permission denied
du: cannot read directory './proc/963/task/992/fdinfo': Permission denied
du: cannot read directory './proc/963/task/993/fdinfo': Permission denied
du: cannot read directory './proc/963/task/994/fdinfo': Permission denied
du: cannot read directory './proc/963/task/997/fdinfo': Permission denied
du: cannot read directory './proc/963/task/1142/fdinfo': Permission denied
du: cannot read directory './proc/963/task/1154/fdinfo': Permission denied
du: cannot read directory './proc/963/task/1177/fdinfo': Permission denied
du: cannot read directory './proc/963/task/1183/fdinfo': Permission denied
du: cannot read directory './proc/963/task/3684/fdinfo': Permission denied
du: cannot read directory './proc/963/task/7073/fdinfo': Permission denied
du: cannot read directory './proc/963/task/15415/fdinfo': Permission denied
du: cannot read directory './proc/963/task/16589/fdinfo': Permission denied
du: cannot read directory './proc/963/task/16618/fdinfo': Permission denied
du: cannot read directory './proc/963/map_files': Permission denied
du: cannot read directory './proc/963/fdinfo': Permission denied
du: cannot read directory './proc/1112/task/1112/fdinfo': Permission denied
du: cannot read directory './proc/1112/map_files': Permission denied
du: cannot read directory './proc/1112/fdinfo': Permission denied
du: cannot read directory './proc/1146/task/1146/fdinfo': Permission denied
du: cannot read directory './proc/1146/task/1153/fdinfo': Permission denied
du: cannot read directory './proc/1146/task/16630/fdinfo': Permission denied
du: cannot read directory './proc/1146/task/16631/fdinfo': Permission denied
du: cannot read directory './proc/1146/map_files': Permission denied
du: cannot read directory './proc/1146/fdinfo': Permission denied
du: cannot read directory './proc/1151/task/1151/fdinfo': Permission denied
du: cannot read directory './proc/1151/task/1160/fdinfo': Permission denied
du: cannot read directory './proc/1151/task/16628/fdinfo': Permission denied
du: cannot read directory './proc/1151/task/16629/fdinfo': Permission denied
du: cannot read directory './proc/1151/map_files': Permission denied
du: cannot read directory './proc/1151/fdinfo': Permission denied
du: cannot read directory './proc/1169/task/1169/fdinfo': Permission denied
du: cannot read directory './proc/1169/map_files': Permission denied
du: cannot read directory './proc/1169/fdinfo': Permission denied
du: cannot read directory './proc/1176/task/1176/fdinfo': Permission denied
du: cannot read directory './proc/1176/map_files': Permission denied
du: cannot read directory './proc/1176/fdinfo': Permission denied
du: cannot read directory './proc/1187/task/1187/fdinfo': Permission denied
du: cannot read directory './proc/1187/map_files': Permission denied
du: cannot read directory './proc/1187/fdinfo': Permission denied
du: cannot read directory './proc/6492/task/6492/fdinfo': Permission denied
du: cannot read directory './proc/6492/map_files': Permission denied
du: cannot read directory './proc/6492/fdinfo': Permission denied
du: cannot read directory './proc/6514/task/6514/fdinfo': Permission denied
du: cannot read directory './proc/6514/map_files': Permission denied
du: cannot read directory './proc/6514/fdinfo': Permission denied
du: cannot read directory './proc/7074/task/7074/fdinfo': Permission denied
du: cannot read directory './proc/7074/task/7075/fdinfo': Permission denied
du: cannot read directory './proc/7074/task/16632/fdinfo': Permission denied
du: cannot read directory './proc/7074/task/16633/fdinfo': Permission denied
du: cannot read directory './proc/7074/map_files': Permission denied
du: cannot read directory './proc/7074/fdinfo': Permission denied
du: cannot read directory './proc/7712/task/7712/fdinfo': Permission denied
du: cannot read directory './proc/7712/map_files': Permission denied
du: cannot read directory './proc/7712/fdinfo': Permission denied
du: cannot read directory './proc/7737/task/7737/fdinfo': Permission denied
du: cannot read directory './proc/7737/map_files': Permission denied
du: cannot read directory './proc/7737/fdinfo': Permission denied
du: cannot read directory './proc/7741/task/7741/fdinfo': Permission denied
du: cannot read directory './proc/7741/map_files': Permission denied
du: cannot read directory './proc/7741/fdinfo': Permission denied
du: cannot read directory './proc/10984/task/10984/fdinfo': Permission denied
du: cannot read directory './proc/10984/map_files': Permission denied
du: cannot read directory './proc/10984/fdinfo': Permission denied
du: cannot read directory './proc/11077/task/11077/fdinfo': Permission denied
du: cannot read directory './proc/11077/map_files': Permission denied
du: cannot read directory './proc/11077/fdinfo': Permission denied
du: cannot read directory './proc/11691/task/11691/fdinfo': Permission denied
du: cannot read directory './proc/11691/map_files': Permission denied
du: cannot read directory './proc/11691/fdinfo': Permission denied
du: cannot read directory './proc/11700/task/11700/fdinfo': Permission denied
du: cannot read directory './proc/11700/map_files': Permission denied
du: cannot read directory './proc/11700/fdinfo': Permission denied
du: cannot read directory './proc/11729/task/11729/fdinfo': Permission denied
du: cannot read directory './proc/11729/map_files': Permission denied
du: cannot read directory './proc/11729/fdinfo': Permission denied
du: cannot read directory './proc/16619/task/16619/fdinfo': Permission denied
du: cannot read directory './proc/16619/map_files': Permission denied
du: cannot read directory './proc/16619/fdinfo': Permission denied
du: cannot read directory './proc/16621/task/16621/fdinfo': Permission denied
du: cannot read directory './proc/16621/map_files': Permission denied
du: cannot read directory './proc/16621/fdinfo': Permission denied
du: cannot read directory './proc/16622/task/16622/fdinfo': Permission denied
du: cannot read directory './proc/16622/map_files': Permission denied
du: cannot read directory './proc/16622/fdinfo': Permission denied
du: cannot access './proc/16918/task/16918/fd/3': No such file or directory
du: cannot access './proc/16918/task/16918/fdinfo/3': No such file or directory
du: cannot access './proc/16918/fd/4': No such file or directory
du: cannot access './proc/16918/fdinfo/4': No such file or directory
du: ./sys/kernel/slab: Input/output error
57G     .
root@a43e6fd62ad8:/# 

 

[Phoenix26]

4 hours ago, Thomas_H said:

@Phoenix26 thank you for the the hint.

 

The output is a little bit weird 

 

 

Apologies I missed a bit, command to run is..
 

du -sh *

 

This will break it down per folder, the previous cmd just gives the total size. 57GB in your case.

You can ignore the permission errors.

[Thomas_H]

Hi,

thank you very much.

I found out that the folder "/var/cache/zoneminder" is mapped correctly.

But the folder "/var/log" is unusual big.

Before mapping "/var/log" outside of the Docker.image may I ask if this size/behavior is normal for Zoneminder?

 

 

Quote

root@a43e6fd62ad8:/var/log# du -sh /var/log/*
24K     /var/log/alternatives.log
1.4M    /var/log/apache2
336K    /var/log/apt
28K     /var/log/auth.log
112K    /var/log/auth.log.1
8.0K    /var/log/auth.log.2.gz
8.0K    /var/log/auth.log.3.gz
60K     /var/log/bootstrap.log
0       /var/log/btmp
20K     /var/log/cron.log
68K     /var/log/cron.log.1
8.0K    /var/log/cron.log.2.gz
4.0K    /var/log/cron.log.3.gz
0       /var/log/daemon.log
4.0K    /var/log/daemon.log.1
4.0K    /var/log/daemon.log.2.gz
4.0K    /var/log/daemon.log.3.gz
0       /var/log/debug
28K     /var/log/debug.1
608K    /var/log/dpkg.log
92K     /var/log/error
4.0K    /var/log/faillog
4.0K    /var/log/fontconfig.log
0       /var/log/journal
32K     /var/log/lastlog
0       /var/log/mail.log
4.0K    /var/log/mail.log.1
4.0K    /var/log/mail.log.2.gz
4.0K    /var/log/mail.log.3.gz
922M    /var/log/messages
3.8G    /var/log/messages.1
232M    /var/log/messages.2.gz
151M    /var/log/messages.3.gz
3.1M    /var/log/mysql
0       /var/log/private
340M    /var/log/syslog
584M    /var/log/syslog.1
34M     /var/log/syslog.2.gz
33M     /var/log/syslog.3.gz
34M     /var/log/syslog.4.gz
33M     /var/log/syslog.5.gz
34M     /var/log/syslog.6.gz
34M     /var/log/syslog.7.gz
0       /var/log/user.log
4.0K    /var/log/user.log.1
4.0K    /var/log/user.log.2.gz
4.0K    /var/log/user.log.3.gz
0       /var/log/wtmp
1.2G    /var/log/zm

 

[Phoenix26]

No, that is much larger than usual, my /var/log dir is 200mb. Check your logging settings, you've probably got something set to debug.
 

5 minutes ago, Thomas_H said:

Hi,

thank you very much.

I found out that the folder "/var/cache/zoneminder" is mapped correctly.

But the folder "/var/log" is unusual big.

Before mapping "/var/log" outside of the Docker.image may I ask if this size/behavior is normal for Zoneminder?

 

 

 

[Thomas_H]

12 hours ago, Phoenix26 said:

No, that is much larger than usual, my /var/log dir is 200mb. Check your logging settings, you've probably got something set to debug.
 

 

Hi,

 

thank you again.

I changed this setting (see screenshot) and will look if this has an effect.

I can't remember that I made changes in this section.

 

[Steviewunda]

Hi - I am setting up ZM on unRaid 6.11.1. Everything works fine (no cameras yet, but that shouldn't matter) if I accept the default storage paths at installation - no errors in the log. But when I assign a USB 3.0 drive in Unassigned Devices and configure the ZM container settings and the Zoneminder/Options/Storage settings to use the USB drive for camera footage,etc - I get 'Path does not exist" errors in the ZM log. Here are screenshots of the default working settings in the ZM container settings, followed by Unassigned Devices settings, and ZM container and web GUI settings. Any assistance would be appreciated.

 

[Steviewunda]

I seem to have sorted this - I was changing both the container and the Web GUI Storage settings to /mnt/disks/cctv - it seems I should have only been changing the container variable, and leaving the Storage setting as is. Consider this solved (for now 😉)

[dlandon]

On 10/9/2022 at 4:56 AM, Phoenix26 said:

Any reason this hasn't been updated?

 

Its running 1.36.12 and 1.36.28 was just released.

I was finally able to build an updated container.  Seems there were some changes along the way that prevented updating Zoneminder past 1.36.12.  Should be working now.

[Phoenix26]

On 11/27/2022 at 4:34 AM, dlandon said:

I was finally able to build an updated container.  Seems there were some changes along the way that prevented updating Zoneminder past 1.36.12.  Should be working now.

Thank you, all updated and seems to be working fine. 👍

[Steviewunda]

Update went fine for me too ☝️

[Kuleinc]

Had a power outage, and now I get this database error:

 

Dec  3 18:06:02 142dc1b8c1a9 zmupdate[1154]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
Dec  3 18:06:02 142dc1b8c1a9 zmupdate[1154]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
Dec  3 18:06:02 142dc1b8c1a9 zmupdate[1156]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
Dec  3 18:06:02 142dc1b8c1a9 zmupdate[1156]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
Starting ZoneMinder:
Dec  3 18:06:12 142dc1b8c1a9 zmpkg[1167]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]
Dec  3 18:06:12 142dc1b8c1a9 zmpkg[1167]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:]

 

Is this something I can easily fix or do I need to reinstall ZM docker and start over?

[tvd1]

On 1/1/2021 at 12:05 PM, ThreeFN said:

Yes.  Not sure if this is best practice, but here's what I have configured and working:

1. You need to own your own domain so you can assign zoneminder.YOURDOMAIN.ETC

2. Also I have both SWAG and ZM on a separate bridged network per spaceinvanderone's video(s) (along with other stuff).

3. Assign a wildcard cert to yourself so you don't need more than one cert.

4. Point zoneminder's cert folder contents to your swag certs as below:

5. Make sure you setup as read only on both, just in case

 

So far this works fine for me and doesn't seem to have any serious security faux pas.

 

I'm pretty sure if your using a duckdns style setup that this will work with your subdomain only cert setup because ZM uses a subfolder, but I haven't used/setup that sort of config.  Obviously this only covers ZM getting the cert and not swag rev proxy, for that I used the following for my subdomain config, which is basically the default subdomain config:

 

zoneminder.subdomain.conf : 

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name zoneminder.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    # enable for ldap auth, fill in ldap details in ldap.conf
    # include /config/nginx/ldap.conf;

    # enable for Authelia
    # include /config/nginx/authelia-server.conf;

    location / {
        # enable the next two lines for http auth
        #auth_basic "Restricted";
        #auth_basic_user_file /config/nginx/.htpasswd;

        # enable the next two lines for ldap auth
        #auth_request /auth;
        #error_page 401 =200 /ldaplogin;

        # enable for Authelia
        # include /config/nginx/authelia-location.conf;

        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_app zoneminder;
        set $upstream_port 443;
        set $upstream_proto https;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

        # REMOVE THIS LINE BEFORE SUBMITTING: Additional proxy settings such as headers go below this line, leave the blank line above.
    }
}

 

Where are you setting those configs (#4 + #5)?  I'm not seeing that as options in Zoneminder or Swag. I already have Nextcloud working fine w/ swag, so i'm not sure if im missing something or its work i've already done to get NC working.

[tvd1]

Okay i got swag working off my domain, so far, so good.   But now im running into issues with "AUTH HASH LOGINS".  If i have this option enabled, i have to authenticate when using my FQDN on each and every page within ZM.  It gets super annoying. If i leave "AUTH HASH LOGINS" off, the zmNinja app yells with this message constantly..

 

 

I know the zmNinja app is technically no longer supported, but i think this is more of an issue with the ZM docker, than the app.  Maybe something with swag i set up incorrectly, but my other sites work fine.

[dlandon]

1 hour ago, tvd1 said:

I know the zmNinja app is technically no longer supported, but i think this is more of an issue with the ZM docker, than the app.  Maybe something with swag i set up incorrectly, but my other sites work fine.

Working fine for me, but I don't use swag.  Be careful with the auth hash.  There is an option to include the IP address in the hash and that might be your issue.

 

BTW, the ZmNinja app is suooprted.  It's the event server that is no longer supported.  That being said, it does work and I'm using it with ZmNinja.

[tvd1]

On 12/12/2022 at 1:03 PM, dlandon said:

Working fine for me, but I don't use swag.  Be careful with the auth hash.  There is an option to include the IP address in the hash and that might be your issue.

 

BTW, the ZmNinja app is suooprted.  It's the event server that is no longer supported.  That being said, it does work and I'm using it with ZmNinja.

 

Thanks for that info!  I've tried enabling and disabling both AUTH HASH LOGINS and AUTH HASH IPS (in varying combos).  And all produce the same result if AUTH HASH LOGINS is enabled: Constant prompting of logins at every menu item/screen.  So i'm just going to live with the warning message in the ZmNinja app for now.  

 

Right now though, i still have AUTH HASH IPS enabled (it was by default).  Whats the risk in leaving that checked?

[dlandon]

1 minute ago, tvd1 said:

Right now though, i still have AUTH HASH IPS enabled (it was by default).  Whats the risk in leaving that checked?

There's no risk.   It's additional security by including the IP address.

[tucansam]

Fresh install, unable to open the GUI.

[dlandon]

2 hours ago, tucansam said:

Fresh install, unable to open the GUI.

How are you trying to access the GUI?

[tucansam]

Docker -> ZM Icon -> "WebGUI"

 

Also tried directly inputting the URL and port, both http and https

 

No change, does not work.  Same error.