Borbosch

Do the multiple classification-processes work for you? Object-, face- and style-classification all crash in my case and end with a "FATAL"-Log-Output. I used another Redis-Container an now it works. Before i used the one from A75G, that didn't work The two from "Bungy" and "jj9987" just work.

Okay, seems like a temporary problem. Today the installation and download just works. Yesterday i gave up after 6 tries. Thank you very much for your time.

Today i tried to reinstall the Plugin because i got some errors on Startup: modprobe: FATAL: Module nvidia not found in directory /lib/modules/5.10.28-Unraid During the reinstall the download of the driver fails. Anyone experiencing similar problems? plugin: installing: https://github.com/ich777/unraid-nvidia-driver/raw/master/nvidia-driver.plg plugin: downloading https://github.com/ich777/unraid-nvidia-driver/raw/master/nvidia-driver.plg plugin: downloading: https://github.com/ich777/unraid-nvidia-driver/raw/master/nvidia-driver.plg ... done plugin: downloading: https://github.com/ich777/unraid-nvidia-driver/raw/master/packages/nvidia-driver-2021.07.30.txz ... done +============================================================================== | Skipping package nvidia-driver-2021.07.30 (already installed) +============================================================================== +============================================================================== | WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING | | Don't close this window with the red 'X' in the top right corner until the 'DONE' button is displayed! | | WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING +============================================================================== -----------------Downloading Nvidia Driver Package v470.63.01------------------ ----------This could take some time, please don't close this window!------------ --------------Can't download Nvidia Driver Package v470.63.01----------------- plugin: run failed: /bin/bash retval: 1 Updating Support Links Finished Installing. If the DONE button did not appear, then you will need to click the red X in the top right corner

Hi there, had a problem with my km 200 Binding yesterday- The Problem was the limited crypto.policy for java. You can test the current policies yourself this way: https://www.jvmhost.com/articles/jce-unlimited-cipher-policy-different-jdk-versions/ cat > CipherTest.java<<EOF import javax.crypto.Cipher; class CipherTest { public static void main(String[] args) { try { int maxKeyLen = Cipher.getMaxAllowedKeyLength("AES"); System.out.println("Max AES key length = " + maxKeyLen); } catch (Exception e){ System.out.println("FAILED: No AES found!"); } } } EOF javac CipherTest.java java CipherTest Typical value for weak cipher policy is 128. Maximum value is 2147483647 and it confirms unlimited cipher strength policy. In the provided docker i had only 128 and did the following: I took the file /usr/lib/jvm/default-jvm/conf/security/java.security out of the Container as template and edited the java.security to "crypto.policy=unlimited". Put it to a known Location in my host filesystem and mounted in the Container: Host: /mnt/user/appdata/openhab2/java.security Mountpoint in the container: /usr/lib/jvm/default-jvm/conf/security/java.security After that i tested it again and the value was 2147483647 and the binding works.

Thank you so much. Similar problems occure while trying to authorize the spotify-player for the spotify-binding. This helped me alot!

Had the same problem today with the update and the idea of having a corrupted database. After some researching how to start the zoneminder-docker without automatically starting mysql and zoneminder (Create an environment variable: NO_START_ZM="1") i could connect to the console of the docker. There i could run mysqld in safe mode root@b02f8d0fc773:/# mysqld_safe That just helped me finding the error-log (mysqld_safe Logging to '/var/log/mysqld.log'.). In the error log i got the error "InnoDB: Upgrade after a crash is not supported." After some more searching i found this: https://discuss.erpnext.com/t/solved-mariadb-10-1-to-mariadb-10-2-upgrade-crash/35048 Then i just deleted the /var/lib/mysql/ib_logfile* and startet the Zoneminder-Docker without the NO_START_ZM="1" and everything works now.