February 13, 20206 yr 51 minutes ago, dlandon said: I didn't take it as a demand. This docker has gotten to where it takes more time than I care to invest for virtually zero donations. I am a little frazzled. Do you have a link to buy beer/coffee? I imagine anyone using your docker would be more than happy to send some $$ :-) we appreciate your hard work and time you invest in this!
February 13, 20206 yr 4 hours ago, Jaburges said: Do you have a link to buy beer/coffee? I imagine anyone using your docker would be more than happy to send some $$ 🙂 we appreciate your hard work and time you invest in this! @Jaburges , you can donate to @dlandon here Donate to dlandon Edit:Hm link did not work Edit2: Now it should work Edited February 13, 20206 yr by Sic79
February 13, 20206 yr 40 minutes ago, Sic79 said: @Jaburges , you can donate to @dlandon here Donate to dlandon Edit:Hm link did not work Edit2: Now it should work Thanks - done 🙂
February 13, 20206 yr 5 hours ago, Jaburges said: Do you have a link to buy beer/coffee? If you enable signatures in your forum settings there is a link in his signature.
February 13, 20206 yr Author 14 hours ago, Sic79 said: Hi @dlandon , I saw that a new version of Zoneminder was released now, great work! Was about to check out the opencv GPU backend support for CUDA in the new ES 5.7 but did not find the new attribute to activate this in the "objectconfig.ini. So it seems you did not compile that, so my question is, do you plan to include that in your docker version? Thanks! Edit: It seems this is a feature in ES 5.7.4. It must have been released just after your version with ES 5.7. Turns out this is not as easy as just turning on a switch in the objectconfig.ini file. Opencv has to be compiled properly for gpu support, and nvidia support added to the docker. Not sure how to work it all out right now.
February 14, 20206 yr Turns out this is not as easy as just turning on a switch in the objectconfig.ini file. Opencv has to be compiled properly for gpu support, and nvidia support added to the docker. Not sure how to work it all out right now. Yeah, I saw that there are a couple of more things to do. And I actually began to test with compiling and testing with the new ES version yesterday. Think it is the Nvidia support that was the issue why I did not get it working. Talked a little with asker about that. And I also saw that you did that to, hope you can get it working when and if you get time to try some more. Have great Friday
February 16, 20206 yr Author The docker with cuda support is building now. You need to install the Nvidia plugin and set up the docker for cuda support. Read the first post for instructions on how to set up cuda.
February 16, 20206 yr Hey, i've just tried to add my old DCS-932LB into zoneminder on Unraid Version: 6.8.2. The configuration seems to be fine but as soon as i try to watch the stream the follwing message apears in the Log: "Socket /var/run/zm/zms-519522s.sock does not exist. This file is created by zms, and since it does not exist, either zms did not run, or zms exited early. Please check your zms logs and ensure that CGI is enabled in apache and check that the PATH_ZMS is set correctly. Make sure that ZM is actually recording. If you are trying to view a live stream and the capture process (zmc) is not running then zms will exit. Please go to http://zoneminder.readthedocs.io/en/latest/faq.html#why-can-t-i-see-streamed-images-when-i-can-see-stills-in-the-zone-window-etc for more information." As well as: "ZM_OPT_CAMBOZOLA is enabled, but the system cannot find /usr/share/zoneminder/www/cambozola.jar" What mostly confuses me is that the same configuration works on Unraid Version: 6.7.2 . Am i doing it wrong or did something change with the new Unraid version?! Thanks for the help !
February 16, 20206 yr Author 33 minutes ago, knusperkai said: "ZM_OPT_CAMBOZOLA is enabled, but the system cannot find /usr/share/zoneminder/www/cambozola.jar" Turn off OPT_CAMBOZOLA in options. It has been removed from the docker. It is no longer necessary. 33 minutes ago, knusperkai said: Am i doing it wrong or did something change with the new Unraid version?! Nothing changed in Unraid, Zoneminder changed. Edited February 16, 20206 yr by dlandon
February 16, 20206 yr 8 minutes ago, dlandon said: Turn off OPT_CAMBOZOLA in options. It has been removed from the docker. It is no longer necessary. Nothing changed in Unraid, Zoneminder changed. Okay. It’s off now but the first message is still in the log. is there a easy fix too?
February 16, 20206 yr 8 hours ago, dlandon said: Read the first post on changes to Zonemnder 1.34. can you be more specific on that?
February 16, 20206 yr Author 5 minutes ago, knusperkai said: can you be more specific on that? Version 1.34.x update release notes:
February 16, 20206 yr yeah, okay.....i actuall do not know what happened but its working now. tried to change the .conf file to add the PATH_ZMS: /zm/cgi-bin/nph-zms -> no acces to the Web-GUI -> reinstalled docker -> its working now. Even if the support wasnt helpfull as expected...thanks anyway PS: please keep in mind that not everyone is a developer regards
February 16, 20206 yr Author 9 minutes ago, knusperkai said: tried to change the .conf file to add the PATH_ZMS: /zm/cgi-bin/nph-zms -> no acces to the Web-GUI -> reinstalled docker -> its working now. Don't edit that file. Make the change in the Options of the UI.
February 19, 20206 yr Author There is a new docker building that supports Nvidia GPU support for ES hook processing. This is documented in the first post. You need to do some technical work to compile a custom opencv to support your Nvidia GPU. You will also need to install the Nvidia plugin and set it up for your GPU. NOTE: It takes a lot of docker image (at least 15GB free) and a LONG time to compile opencv. Another feature of the new docker is updates of ES will automatically be done when the docker is restarted. A new docker does not have to be built for a new release of ES. I do not have a Nvidia GPU and can offer no support except for the script to compile opencv. I will modify the compile opencv script as issues come up.
February 19, 20206 yr 3 minutes ago, dlandon said: NOTE: It takes a lot of docker image (at least 15GB free) and a LONG time to compile opencv. I recommend putting this in bold and possibly red at the top of the relevant section in the first thread post. Since trurl recommends 20GB docker image files, having 15GB free isn't likely by default. Any chance you can put a check in your script to abort if there isn't enough space in the image? Otherwise I suspect there will be some unhappy campers when their docker image gets corrupted.
February 19, 20206 yr Author 1 hour ago, jonathanm said: Any chance you can put a check in your script to abort if there isn't enough space in the image? Otherwise I suspect there will be some unhappy campers when their docker image gets corrupted. This whole process is pretty technical, I don't expect the average user would want to undertake this, but good suggestion. I have added a check on available space to the script.
February 29, 20206 yr Hi, any idea why won't zoneminder pick my cron file? I've put it inside the appdata/zoneminder folder like instructed but it won't be picked up, it's not problem to edit the crontab everytime by hand when i update/restart the container but its nice feature to have automatically get it inserted. ps. dlandon, donated $10, it's not much but maybe you'll get a premium cup of coffee with that?
February 29, 20206 yr Author I haven't looked at that in a while. I'll take a look. Many changes have been happening lately and it's possible that a new problem has occured. Thanks for the donation.
February 29, 20206 yr Author 3 hours ago, Jaska said: Hi, any idea why won't zoneminder pick my cron file? I've put it inside the appdata/zoneminder folder like instructed but it won't be picked up, it's not problem to edit the crontab everytime by hand when i update/restart the container but its nice feature to have automatically get it inserted. ps. dlandon, donated $10, it's not much but maybe you'll get a premium cup of coffee with that? Works for me. Be sure your cron file is in Linux format - line feed only.
March 1, 20206 yr 21 hours ago, dlandon said: Works for me. Be sure your cron file is in Linux format - line feed only. Yeah that was the problem, saved the cron file through smb share and it added some extra to the file that weren't visible until editing it inside the docker. Now it works great. Thanks!
March 1, 20206 yr Author Zoneminder supports hardware acceleration in the new version. I have been able to add the '-hwaccel auto' parameter to the ffmpeg options and I've not have any problems. When I try to add the vaapi hardware acceleration to the cameras Unraid locks up and has to be hard reset. When I use the 'ffmpeg -hwaccels' command in the docker, it says vaapi is available as a device to use for acceleration. I have an Intel GPU in my server so I believe qemu and libvirt are picking that up. For the time being, I would recommend caution with the hardware acceleration feature on the cameras. I have read that the vaapi driver has had issues with later Linux kernels, but those posts are a bit old. Just a heads up.
March 26, 20206 yr the last update for this container damage the container and it is no longer working. see logs below. *** Running /etc/my_init.d/20_apt_update.sh... Performing updates... Hit:1 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:2 http://ppa.launchpad.net/iconnor/zoneminder-1.34/ubuntu bionic InRelease Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:5 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease Hit:6 http://archive.ubuntu.com/ubuntu bionic-backports InRelease Reading package lists... E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. *** /etc/my_init.d/20_apt_update.sh failed with status 100 *** Killing all processes... Mar 26 18:08:22 0c1893660745 syslog-ng[16]: syslog-ng shutting down; version='3.13.2'
March 26, 20206 yr Author 48 minutes ago, Alan747 said: the last update for this container damage the container and it is no longer working. see logs below. *** Running /etc/my_init.d/20_apt_update.sh... Performing updates... Hit:1 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:2 http://ppa.launchpad.net/iconnor/zoneminder-1.34/ubuntu bionic InRelease Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:5 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease Hit:6 http://archive.ubuntu.com/ubuntu bionic-backports InRelease Reading package lists... E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. *** /etc/my_init.d/20_apt_update.sh failed with status 100 *** Killing all processes... Mar 26 18:08:22 0c1893660745 syslog-ng[16]: syslog-ng shutting down; version='3.13.2' Be sure you are using the latest docker. Remove the docker and then re-install.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.