mraneri

Well, that folder is empty. If I go to reinstall the container from community apps and just hit save it makes a new template. Still not sure what caused it though, and I'll need to check those corruption warnings. Thanks

Haven't touched the flash drive or run memtest lately. Scrub shows no file errors.

If I try to create a container all of the user templates are gone except for the recently installed grav container.

It's actually all of the project links as well. Everything was running perfectly fine. I rebooted the system via the button on the Main screen and when it came back all of my containers looked like the Emby screenshot. I tried rebooting again and the same thing. Emby has an update available, but trying to apply it gives me this "Configuration not found. Was this container created using this plugin?". I can still access all containers by IP:Port manually. I tried installing a container that I have never used before (grav) and WebUI, edit, all project links are there and working. Does anyone have any idea what happened, or how to fix this? Thanks tower-diagnostics-20220716-1925.zip

Setting > Display, very last option

Favorite: How easy it is to use and get started for 2020: maybe some way for the VM GUI to not reset custom xml. I don't know if having a separate area for custom entries that could be merged to the GUI generated xml on VM boot could work?

Do you remember what specifically you did for iMessage/Facetime? The Appstore and iCloud work fine for me, but not the other two. edit: This vm has two EFI mountable partitions, the top one has the CLOVER directory in it, the bottom one looks similar to the partitions mentioned in every tutorial but only has an APPLE folder. I'm a little lost.

16GB DDR3, works fine for a home NAS/media server. I am planning on upgrading next year to be able to run a couple VMs and reduce the number of computers I have running 24/7.

So for this to work you would need a router that supports vLANs as well? It doesn't look like the stock ASUS firmware has that functionality.

That works. I can use my router as the client DNS just fine, that doesn't solve the problem of not being able to access Dockers with custom IPs.

You most certainly need to be able to access it to use it. What are you talking about? You haven't added anything to this thread except say that it works for you and you don't know why.

Unraid is 10.0.2.6 The pi-hole container is on br0 with a custom ip of 10.0.2.3. If I connect through wireguard I can't see 10.0.2.3 to use it as a DNS.

I cannot figure out how to get my phone to see the pi-hole docker container on 10.0.2.3. I have the DNS configured on the client side. Setting NAT doesn't seem to change anything either. I can see other physical nodes on the network, just not the docker assigned a custom IP.

I just installed the docker and the only settings I changed were setting network type to custom and the time zone to America/New_York. When I go into the admin UI I can't change anything because of this. Does anyone have any insight? Edit: It looks like running chmod 0777 -R /mnt/user/appdata/pihole/pihole/ from the terminal fixed it. After hitting save I changed it back to 0755 and everything seems to be working normally. What would cause the permission issue in the first place?

Pinging 10.0.2.3 I get this:

Does it go on the server side of the peer config or the client side? I tried both and nothing changed. I can access other IPs on the network, just not custom IPs from Unraid.

10.0.2.1 is my router 10.0.2.6 is my Unraid server 10.20.0.2 and 10.20.0.3 are peers I can connect to 10.0.2.6 and 10.0.2.1 from both peers, but I can't figure out the routing to be able to get to a docker with its own IP (10.0.2.3). I'm not currently running any VMs.

That is with a write corrections checked. I just learned about making checksums for files doing research for this and installed the file integrity plugin. Is there anything else I can do from here?

A little over 24h of memtest came back with zero errors. I re-ran the parity check and came back with the same results. Aside from the sync errors everything looks and functions normally. tower-diagnostics-20191012-1120.zip

Almost seven hours, four passes, zero errors.

Not ECC memory. I'm running Memtest now and will report back. Thank you both.

Update: After the parity rebuild the old parity drive failed. After replacing and rebuilding the second drive there are 0 errors. I have a small server with 3x3TB data drives, 1x3TB parity, and 2x240GB SSD cache. It has run fine for the past couple years, but last week one of the data drives failed. It showed SMART failures, UnRaid kicked it out of the array and started emulating it. The only spare I had was a 4TB drive so I had to replace the parity drive. It cleared preclear so I set it as parity and moved the old parity to the array and let UnRaid start copying the parity and rebuilding the data drive. Everything went smooth, parity check after the rebuild returned 0 errors. This morning I get a notification that a parity check has started, it wasn't scheduled and I don't know what triggered it. I let it run its course and it finished with 183141001 errors. This is the first time in the two years the server has been running that I have had a parity check with any errors and I am at a loss for what happened - or what I should do next. As of right now everything on the server seems to be working normally. Thank you for any insight or advice. tower-diagnostics-20191009-2213.zip

I am assuming it's an issue with permissions? I just don't know how to remedy that with the docker install.

Removed the Docker, deleted everything related to Zoneminder, fresh install with everything set to defaults. Same issue with MariaDB and Apache failing. tower-diagnostics-20190815-1624.zip log.txt

I was wondering if anyone could shed some light on my issue. I have tried installing this docker many times, but it always fails setting up the database and apache server. You should consider upgrading via the 'pip install --upgrade pip' command. Traceback (most recent call last): File "/usr/bin/setup.py", line 22, in <module> with open(os.path.join(here, 'README.md'), encoding='utf-8') as f: FileNotFoundError: [Errno 2] No such file or directory: '/usr/bin/README.md' Hook processing installed Starting services... * Starting MariaDB database server mysqld Successfully installed Click-7.0 Pillow-6.1.0 dlib-19.17.0 face-recognition-1.2.3 face-recognition-models-0.3.0 You are using pip version 8.1.1, however version 19.2.2 is available. You should consider upgrading via the 'pip install --upgrade pip' command. Traceback (most recent call last): File "/usr/bin/setup.py", line 22, in <module> with open(os.path.join(here, 'README.md'), encoding='utf-8') as f: FileNotFoundError: [Errno 2] No such file or directory: '/usr/bin/README.md' Hook processing installed Starting services... * Starting MariaDB database server mysqld ...fail! DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Config.pm line 117. Can't connect to db at /usr/share/perl5/ZoneMinder/Config.pm line 166. BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder/Config.pm line 166. Compilation failed in require at /usr/bin/zmupdate.pl line 71. BEGIN failed--compilation aborted at /usr/bin/zmupdate.pl line 71. DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Config.pm line 117. Can't connect to db at /usr/share/perl5/ZoneMinder/Config.pm line 166. BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder/Config.pm line 166. Compilation failed in require at /usr/bin/zmupdate.pl line 71. BEGIN failed--compilation aborted at /usr/bin/zmupdate.pl line 71. * Starting Apache httpd web server apache2 * Starting ZoneMinder: DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Config.pm line 117. Can't connect to db at /usr/share/perl5/ZoneMinder/Config.pm line 166. BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder/Config.pm line 166. Compilation failed in require at /usr/share/perl5/ZoneMinder.pm line 33. BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder.pm line 33. Compilation failed in require at /usr/bin/zmpkg.pl line 34. BEGIN failed--compilation aborted at /usr/bin/zmpkg.pl line 34. ZoneMinder failed to start *** /etc/my_init.d/40_firstrun.sh failed with status 255 *** Killing all processes... Aug 15 10:46:46 5aa53986dce0 syslog-ng[32]: syslog-ng shutting down; version='3.5.6'