BigChris

After the update today I get the following error message when calling zoneminder: Unable to connect to ZM db.SQLSTATE[HY000] [2002] No such file or directory The container is automatically terminated. What can I do? Update I fix it wirth this: Because of the change in how shared memory is set up, you will need to use the new Zoneminder template:;, Do this procedure: - Remove the docker image. All your data and settings will be kept. - Click on add a container and delete the Zoneminder template. - Go to he apps and get the new

is it possible to deactivate ssl? With everything that came to mind, the web frontend is no longer accessible afterwards.

Thank you! Works great. Now i check the playback today.

The title was difficult to describe. I have the following problem: System: Dell T20 Unraid, with Emby as Docker, from emby. Client: Nvidia Shield If I now watch a movie from the array, then I get the message in Kodi sometime: Source too slow for smooth playback. The film stops for a short time and then runs normally until the end. If I watch Emby directly (via the app) the film starts to stutter. Audio continues to run normally. Then I have to stop and restart the playback. Does anyone else have this problem? Then I read in the unraid forum that if there are problems

Hello. I have two hard drives in my array that I'm a little worried about. Hard disk 1 shows the following under Attributes: 199 UDMA CRC error count 0x0032 200 092 000 Old age Always Never 514 Hard disk 3 this: 187 Reported uncorrect 0x0032 099 099 000 Old age Always Never 1 Both hard disks show SMART extendes self-test: Completed with no errors Do I have to worry about the two hard disks, respectively should I change them soon?

Thank you !

Hello, I wanted to change my parity disc and thought it would be good if I always had a valid parity during the whole process. To do this, I set up a larger hard disk in parity 2 and after sync i removed the first parity disk. Now I have an array, with 3 data disks and a ParityDisk2. This looks strange, but is it also a problem? Could I assign Parity2 to Slot Parity? (as a cosmetic measure) Or are the slots not interchangeable? Translated with www.DeepL.com/Translator

By quasi idle I mean that only my dockers are running and I don't make data access from outside. Following dockers run at my place: - Zoneminder video surveillance with four H.264 full HD cameras - 2 x mariasql - ubiquiti unifi - piwigo photo management - Nginx ProxyManager - emby server I'm guessing that Zoneminder creates the load.

My Unraid is a Dell T20 server with 32GB RAM and an Intel Xeon E3-1225 v3 CPU. In addition there is a parity hard disk and 2 data hard disks as well as a cachepool with 2 ssd hard disks. The overall load is at times 62%. (in quasi idle operation on, only docker, no access to shares) Beside severall shares I have 8 docker containers in which among other things my video surveillance Zoneminder runs with 4 cameras. (I plan to upgrade two to 3 cameras). In addition there are two virtual machines with ubuntu server installations. Does it make sense to upgrade with this load? Which CPU /

I try this, and edit the /etc/nfsmount.conf to this: # Protocol Version [2,3,4] # This defines the default protocol version which will # be used to start the negotiation with the server. Defaultvers=3 # # Setting this option makes it mandatory the server supports the # given version. The mount will fail if the given version is # not support by the server. Nfsvers=4 But if i try to mount sudo mount -t nfs -o nfsvers=4 10.10.11.200:/mnt/user/ftp_holz /mnt/nfsv4-test/ I got this: mount.nfs: Protocol not supported What am I doing wro

Since the last update I can't reach the webinterface anymore. I tried different configurations. (Bridge/Host...) I make the call from the Docker, or manually. https://10.10.11.4:8443/zm I can ping the IP successfully A status query in the console results in the following: # service zoneminder status 12/18/18 10:39:44.556974 zmpkg[889].INF [main:57] [Command: status] 12/18/18 10:39:44.562528 zmpkg[889].INF [main:305] [Sanity checking States table...] 12/18/18 10:39:44.566693 zmpkg[889].INF [main:97] [Command: status] ZoneMinder is running

Back to 6.4.1, no issues. Don't think it is an hardware problem.

I installed PIWIGO as docker on the cache. However, I would like to put the location of the images on a share in the array so that I can keep the docker container small. How can I do that?

I had the problem twice since the update to version 6.5 that I had no connection to the internet from my unraid. From the LAN the unraid was accessible. In addition, two interfaces were no longer connected according to the GUI. A reboot via the GUI was not possible, I had to shut down the server hard. After the reboot everything was ok. Anybody else have the problem? tower-diagnostics-20180320-1859.zip

For this rebuild i try another one.