Autchirion

Hey Guys, I'm using Unraid since quite a while now also the feature CPU pinning. Due to a change of my containers lately I wanted to update my CPU Pinning. However, as soon as I change the CPU pinning for at least one container and hit "apply" it will only show "Please wait..." with a spinning wheel in the UI which will never end. I tried it with Containers on and containers off and I checked the log for error messages while doing so. No error message commes up, it just seems like it's doing nothing. Since I'm not a super expert in debugging stuff like this I was hoping someone here could help me figure out what I need to do. I'm running an i5-12400. Have a great day Autchi

Hey Guys, I'm posting this here, since it feels like an issue of the engine, rather than the container. I've got 2 nextcloud containers, one is nextcloud_prod, the other is nextcloud_test. This was working fine until recently, I changed some stuff, but reverted it back and now it's not working any more. When I'm trying to start the container I get the message The command failed: docker run -d --name='nextcloud_test' --net='swag' --cpuset-cpus='2,4,6,8,10,3,5,7,9,11' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="server" -e HOST_CONTAINERNAME="nextcloud_test" -e 'PHP_MEMORY_LIMIT'='8192M' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://nextcloud.happyheppos.eu' -l net.unraid.docker.icon='https://decatec.de/wp-content/uploads/2017/08/nextcloud_logo.png' -p '3080:80/tcp' -v '/mnt/user/appdata/nextcloud_test/nextcloud':'/var/www/html':'rw' -v '/mnt/user/appdata/nextcloud_test/apps':'/var/www/html/custom_apps':'rw' -v '/mnt/user/appdata/nextcloud_test/config':'/var/www/html/config':'rw' -v '/mnt/user/nextcloud_data_prod':'/var/www/html/data':'rw' --user 99:100 --sysctl net.ipv4.ip_unprivileged_port_start=0 'nextcloud:production' && docker exec -u 0 nextcloud_test /bin/sh -c 'echo "umask 000" >> /etc/apache2/envvars' && docker exec -u 0 nextcloud_test /bin/bash -c "apt update && apt install -y libmagickcore-6.q16-6-extra ffmpeg imagemagick ghostscript" cab6b69a0570c5ce8417739b595a2a175f08e98ee01fca3a0fe37bceca09c7ad The command failed. Interestingly, this is basically only a copy/paste of the nextcloud_prod container which is working perfectly fine, the only thing I adapted is the container name for the Post arguments. Any ideas what might be going wrong here? EDIT: I tried removing the && docker exec -u 0 nextcloud_test /bin/bash -c "apt update && apt install -y libmagickcore-6.q16-6-extra ffmpeg imagemagick ghostscript" from the post arguments and out of the sudden it's starting just fine and just calling the command manually (after the container is started without it) is also working like a charm. Thank you in advance, Autchi

Can this plugin be extended to read activities as well (and probably limit it to only some disks of the array)? I've got some reads that prevent disks from spinning down, but I have no Idea where they are comming from.

Hey Guys, something is preventing my disc to spin down due to reads/writes every 30 seconds (created a video of it and double checked). The picture shows a read/write session directly after clearing all stats, so everything is only due to the 30 second r/w session. The picture shows also iotop as a reference, which unfortunately doesn't show anything. What I looked into: -No Docker Container/VM is active, they are all stoped. -I used the open Files Plugin and this shows no open files on /mnt/diskX or /mnt/user. -iotop doesn't show any process using it, however shows disk write. Interestingly, it does not write the same to cache and cache2, eventhough they are running in a mirrored setup. Also, it seems like there are only writes on the ZFS drives, but the XFS drives are only haveing reads. Does anyone have an idea what might go wrong here? Doesn't seem like a big issue, but I don't like the extra power consumed due to the drives not spinning down and I'm a bit scared that something might be wrong. Have a good day Autchi

Thank you, since you confirm my assumption, I'll go with this solution. 🙂

Hello Folks, I converted my cache and one drive to zfs. One of the main reasons was, that I want to use zfs snapshots to reduce downtime of my containers. But here comes nextcloud, I set my nextcloud to store data on the cache first and then move it to the disk at night. So, I'd need to create a backup of the cache and the zfs disk. let's assume ran the following command: zfs snapshot cache/zfs_test@test & zfs snapshot disk2/zfs_test@test Can I safely access /mnt/user/zfs_test/.zfs/snapshot/test and get the data from out of there and get all elements from both snapshots? I'd say yes, but since it's critical data I want to make sure. Also, if someone has a better suggestion on how to handle this type of scenario, let me know! Thank you for your help, Autchi

same (or simmilar) issue here if you are using the app (which I assume because of error 413). I can upload massive files (>20GB) via my chrome webbrowser on my PC but not via App. Do I assume correctly you are refering to the App? Also, did you try to upload via browser? And finaly, don't forget if you are using cloudflare and use the proxy settings to hide your IP, max filesize is 100MB you will have to activate uploading large files as chungs in the app. You can do this when going into the settings of the app and there should be an option like "advance" (sorry, not using the english translation of the app) you can set the chunk sitze for the file in the app. This issue seems new to me, because I'm quite sure I downloaded massive files from the app before. So, what I'm wondering is, did somethin go wrong in the app since a last update or so. Update: -I completely deleted my account from my phone -logged in again (didn't use an app login, but normal login) -set the chung size to 90MB -activated the auto upload and voila, was able to upload my 2GB video File

wie hast du das Token hinzugefügt? Das ist mir etwas unklar, ansonnsten sieht es relativ einfach aus 🙂

danke für die Info, habe nochmal gelesen und festgestellt, dass ich was falsch verstanden hatte! Netzwerk läuft jetzt. VNC läuft auch wieder, interessanterweiße habe ich nichts verändert, keine Ahnung was das für ein Schluckauf war.

Ich habe es gerade mit Windows 10 und 11 versucht, klappt leider beides nicht, scheitert am Netzwerk. Bei Windows 10 konnte ich das überspringen und wollte dann den Treiber über den Gerätemanager nachinstallieren. Es wird mir der Ethernet Controller angezeigt, Treiber aktualisieren, CD Laufwerk etc...er findet den Treiber und hängt ewig bei Treiber installieren. Wenn er dann mal irgendwann fertig kommt diese Meldung: Mehfrach neu installiert, Machine Q35-7.1 mit virtio 0.1.229-1. Zusätzliches Problem, mit dem VNC tool von Unraid komme ich nicht drauf (failed to connect to server), mit tightVNC auf einem anderen PC klappt es dann wunderbar zu verbinden. Irgend welche Ideen? Ich komme nicht weiter, hatte Win 10 vorher drauf, da hat es perfekt funktioniert, jetzt alles neu gemacht und plötzlich geht es nicht mehr.

uh, that's not happy news, since with the version 3.4.4 I'm getting an error with Borg Backup. Now, it seems like borg backup requires the file libffi.so.7 but libffi 3.4.4 doesn't have this file any more. Any known workarounds (except installing it manually via go file, which I don't like)? Traceback (most recent call last): File "/usr/lib64/python3.9/site-packages/borg/archiver.py", line 41, in <module> from .archive import Archive, ArchiveChecker, ArchiveRecreater, Statistics, is_special File "/usr/lib64/python3.9/site-packages/borg/archive.py", line 20, in <module> from . import xattr File "/usr/lib64/python3.9/site-packages/borg/xattr.py", line 9, in <module> from ctypes import CDLL, create_string_buffer, c_ssize_t, c_size_t, c_char_p, c_int, c_uint32, get_errno File "/usr/lib64/python3.9/ctypes/__init__.py", line 8, in <module> from _ctypes import Union, Structure, Array ImportError: libffi.so.7: cannot open shared object file: No such file or directory

Hello all, I need libffi to be able to run borg backup. For this I did these two steps, after running the last command I was able to run borg backup. # Download libffi from slackware.uk to /boot/extra: wget -P /boot/extra/ https://slackware.uk/slackware/slackware64-15.0/slackware64/l/libffi-3.3-x86_64-3.txz # Install the package: installpkg /boot/extra/libffi-3.3-x86_64-3.txz What I understand, if a package ist stored in /boot/extra/ it will be automatically installed. However, as soon as I reboot it won't be auto installed. My other packets are beeing installed, except for this one. Any clues why that is? Thank you in advance Autchi

solved it for me, thank you

I already tried the "vpn tunneled access for Docker" option, same behavior. The other options all require "Peer allowed IPs:" which I don't exactly know what is supposed to be put in. I delete the wq-quick.log and then activated the tunnel set for Docker (btw. had to reboot the server first, before that wg-quick.log wasn't beeing created): server:~# cat /var/log/wg-quick.log wg-quick up wg0 (autostart) [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 192.168.2.11 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] wg set wg0 fwmark 51820 [#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820 [#] ip -4 rule add not fwmark 51820 table 51820 [#] ip -4 rule add table main suppress_prefixlength 0 [#] sysctl -q net.ipv4.conf.all.src_valid_mark=1 [#] iptables-restore -n [#] logger -t wireguard 'Tunnel WireGuard-wg0 started' [#] ip -4 route flush table 200 [#] ip -4 route add default via 192.168.2.11 dev wg0 table 200 [#] ip -4 route add 192.168.1.0/24 via 192.168.1.1 dev table 200 Error: either "to" is duplicate, or "200" is a garbage. [#] iptables-restore -n [#] ip -4 rule delete table 51820 [#] ip -4 rule delete table main suppress_prefixlength 0 [#] ip link delete dev wg0

Hello Guys, I just got my second server and set it up. I want to use my old server as an off-site backup (off site) solution in case of a disaster and my new server will be at home. Both Servers are running unraid 6.11.1. I've got wireguard running on my router to handle incomming VPN connections to my home. For all my other devices I'm using a simmilar config structure, however if I import this config and select "VPN tunneld access for System" it doesn't seem to work. Workflow (what I do on the server=> server response): Import the config (see code) => config shows up in interface select "VPN tunneld access for System" click Apply => config is stored reboot (just in case) set switch from inactive to inactive => switch directly jumps back to inactive and syslog output: "Oct 19 13:28:14 servername wireguard: Tunnel WireGuard-wg0 started" (no more output) check on my router => there was an initial handshake, but the connection got closed immediately after that Config: [Interface] PrivateKey = OffsitePrivateKey Address = 192.168.2.11/32 DNS = 8.8.8.8 [Peer] PublicKey = HomePublicKey AllowedIPs = 0.0.0.0/0 Endpoint = domain:port PersistentKeepalive = 25 I don't know what I'm doing wrong here, since this is working for all other devices I'm using. If anyone can point me into the right direction I would be greatfull. Thank you in advance Autchi

Damn, this isn’t an option for me, 6.11.0 doesn’t work for me, it won’t start my array on startup.

did you find a solution for this yet?

Thank you for this, unfortunately this came relevant again after this script doesn't work any more. I took the liberty of posting your script on github. apk update apk add --upgrade -X http://dl-cdn.alpinelinux.org/alpine/edge/testing php7-pdlib apk add bzip2-dev

Hey Guys, I'm using File History on my two Windows 10 Machines. I created an extra share for this which is read/write for a specific unraid user. The logindata for this user ist stored in windows and I can use it to connect to said folder (I even can see the contend of the file history). However, it's keeping the data forever, eventhough it's set to 1 month. Also when trying to do a manual erase I get an error message which says (see screenshot) translation: Cleaning up of File History Filie History data couldn't be cleaned up. Element not found. Could this be something with unraid? It's weird to me, that this happenes to both my PCs, even after completely resetting the file history on one PC. Which for me suggests something unraid related. Thank you in advance Autchi

thank you! This was actually easier than expected.

Hello all, I'm running the linuxserver.io nextcloud container. Currently I want to add functionalities, but don't dare to touch my actuall production nextcloud instance for this stuff. Is it possible to run the same container twice and somehoe completely disconnect all data (including appdata and containers itself) from the other instance? That way I don't break my families data if make a mistake. Thank you in advance Autchi

Somehow it seems this is not working for me, I don't get any trafic, even after a couple days waiting. Does someone have an idea what could go wrong? I'm stopping the container every day at night for one hour or so, since this is backup time. https://bridges.torproject.org/status?id=[MyID] is reporting: * obfs4: dysfunctional Error: timed out waiting for bridge descriptor Last tested: 2022-03-22 03:15:07.691628216 +0000 UTC (7h19m51.151949657s ago) Using NICKNAME=DockerObfs4Bridge, OR_PORT=9393, PT_PORT=9292, and [email protected]. Additional properties from 'OBFS4V_' environment variables processing enabled Overriding 'AddressDisableIPv6' with value '1' Starting tor. Mar 22 02:08:33.162 [notice] Tor 0.4.6.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1k, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.31 as libc. Mar 22 02:08:33.162 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/ Mar 22 02:08:33.162 [notice] Read configuration file "/etc/tor/torrc". Mar 22 02:08:33.163 [notice] Based on detected system memory, MaxMemInQueues is set to 6374 MB. You can override this by setting MaxMemInQueues by hand. Mar 22 02:08:33.164 [notice] Opening OR listener on 0.0.0.0:9393 Mar 22 02:08:33.164 [notice] Opened OR listener connection (ready) on 0.0.0.0:9393 Mar 22 02:08:33.165 [notice] Opening OR listener on [::]:9393 Mar 22 02:08:33.165 [notice] Opened OR listener connection (ready) on [::]:9393 Mar 22 02:08:33.165 [notice] Opening Extended OR listener on 127.0.0.1:0 Mar 22 02:08:33.165 [notice] Extended OR listener listening on port 46133. Mar 22 02:08:33.165 [notice] Opened Extended OR listener connection (ready) on 127.0.0.1:46133 Mar 22 02:08:34.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip. Mar 22 02:08:34.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6. Mar 22 02:08:34.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now. Mar 22 02:08:34.000 [notice] Your Tor server's identity key fingerprint is 'DockerObfs4Bridge ID' Mar 22 02:08:34.000 [notice] Your Tor bridge's hashed identity key fingerprint is 'DockerObfs4Bridge MyID' Mar 22 02:08:34.000 [notice] Your Tor server's identity key ed25519 fingerprint is 'DockerObfs4Bridge AnotherID Mar 22 02:08:34.000 [notice] You can check the status of your bridge relay at https://bridges.torproject.org/status?id=MyID Mar 22 02:08:34.000 [notice] Bootstrapped 0% (starting): Starting Mar 22 02:08:51.000 [notice] Starting with guard context "default" Mar 22 02:08:51.000 [notice] Registered server transport 'obfs4' at '[::]:9292' Mar 22 02:08:52.000 [notice] Bootstrapped 5% (conn): Connecting to a relay Mar 22 02:08:52.000 [notice] Unable to find IPv4 address for ORPort 9393. You might want to specify IPv6Only to it or set an explicit address or set Address. Mar 22 02:08:52.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay Mar 22 02:08:52.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay Mar 22 02:08:52.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done Mar 22 02:08:52.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits Mar 22 02:08:52.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits Mar 22 02:08:52.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit Mar 22 02:08:52.000 [notice] External address seen and suggested by a directory authority: my.private.ip Mar 22 02:08:52.000 [notice] Bootstrapped 100% (done): Done Mar 22 02:09:52.000 [notice] Now checking whether IPv4 ORPort my.private.ip:9393 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) Mar 22 02:09:52.000 [notice] Self-testing indicates your ORPort my.private.ip:9393 is reachable from the outside. Excellent. Publishing server descriptor. Mar 22 02:21:52.000 [notice] Performing bandwidth self-test...done. Using NICKNAME=DockerObfs4Bridge, OR_PORT=9393, PT_PORT=9292, and [email protected]. Additional properties from 'OBFS4V_' environment variables processing enabled Overriding 'AddressDisableIPv6' with value '1' Starting tor. Mar 22 04:45:01.774 [notice] Tor 0.4.6.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1k, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.31 as libc. Mar 22 04:45:01.774 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/ Mar 22 04:45:01.774 [notice] Read configuration file "/etc/tor/torrc". Mar 22 04:45:01.775 [notice] Based on detected system memory, MaxMemInQueues is set to 6374 MB. You can override this by setting MaxMemInQueues by hand. Mar 22 04:45:01.776 [notice] Opening OR listener on 0.0.0.0:9393 Mar 22 04:45:01.776 [notice] Opened OR listener connection (ready) on 0.0.0.0:9393 Mar 22 04:45:01.776 [notice] Opening OR listener on [::]:9393 Mar 22 04:45:01.776 [notice] Opened OR listener connection (ready) on [::]:9393 Mar 22 04:45:01.776 [notice] Opening Extended OR listener on 127.0.0.1:0 Mar 22 04:45:01.776 [notice] Extended OR listener listening on port 33923. Mar 22 04:45:01.776 [notice] Opened Extended OR listener connection (ready) on 127.0.0.1:33923 Mar 22 04:45:03.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip. Mar 22 04:45:03.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6. Mar 22 04:45:03.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now. Mar 22 04:45:03.000 [notice] Your Tor server's identity key fingerprint is 'DockerObfs4Bridge ID' Mar 22 04:45:03.000 [notice] Your Tor bridge's hashed identity key fingerprint is 'DockerObfs4Bridge MyID' Mar 22 04:45:03.000 [notice] Your Tor server's identity key ed25519 fingerprint is 'DockerObfs4Bridge AnotherID Mar 22 04:45:03.000 [notice] You can check the status of your bridge relay at https://bridges.torproject.org/status?id=MyID Mar 22 04:45:03.000 [notice] Bootstrapped 0% (starting): Starting Mar 22 04:45:13.000 [notice] Starting with guard context "default" Mar 22 04:45:13.000 [notice] Registered server transport 'obfs4' at '[::]:9292' Mar 22 04:45:14.000 [notice] Bootstrapped 5% (conn): Connecting to a relay Mar 22 04:45:14.000 [notice] Unable to find IPv4 address for ORPort 9393. You might want to specify IPv6Only to it or set an explicit address or set Address. Mar 22 04:45:14.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay Mar 22 04:45:14.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay Mar 22 04:45:14.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done Mar 22 04:45:14.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits Mar 22 04:45:14.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits Mar 22 04:45:14.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit Mar 22 04:45:14.000 [notice] External address seen and suggested by a directory authority: my.private.ip Mar 22 04:45:14.000 [notice] Bootstrapped 100% (done): Done Mar 22 04:46:14.000 [notice] Now checking whether IPv4 ORPort my.private.ip:9393 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) Mar 22 04:46:14.000 [notice] Self-testing indicates your ORPort my.private.ip:9393 is reachable from the outside. Excellent. Publishing server descriptor. Mar 22 04:53:14.000 [notice] Performing bandwidth self-test...done. Mar 22 10:45:14.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, with 0 circuits open. I've sent 2.26 MB and received 6.20 MB. I've received 28 connections on IPv4 and 0 on IPv6. I've made 23 connections with IPv4 and 0 with IPv6. Mar 22 10:45:14.000 [notice] While bootstrapping, fetched this many bytes: 48465 (consensus network-status fetch); 897 (microdescriptor fetch) Mar 22 10:45:14.000 [notice] While not bootstrapping, fetched this many bytes: 3889100 (server descriptor fetch); 359 (server descriptor upload); 339753 (consensus network-status fetch); 31346 (microdescriptor fetch) Mar 22 10:45:14.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. My Config:

Dude, you are fast. Let me know if you still need something! Sorry, had to take care is other matters.

Wed Mar 9 12:47:11 2022 daemon.warn dnsmasq[3219]: possible DNS-rebind attack detected: rebindtest.unraid.net Wed Mar 9 12:47:42 2022 daemon.warn dnsmasq[3219]: possible DNS-rebind attack detected: rebindtest.unraid.net Wed Mar 9 12:48:12 2022 daemon.warn dnsmasq[3219]: possible DNS-rebind attack detected: rebindtest.unraid.net Wed Mar 9 12:48:42 2022 daemon.warn dnsmasq[3219]: possible DNS-rebind attack detected: rebindtest.unraid.net Could you let me know which part of the diagnostics you want? I'd want to remove some of the information, ideally only provide what you want to look at, but of course I'll gladly help. Btw, after removing the plugin the "issue" is gone. If you want me to reinstall it before getting the diagnostics let me know as well!