dnLL

Members
  • Posts

    216
  • Joined

  • Last visited

Everything posted by dnLL

  1. My stress levels are so high while reading this thread. I really hope all will go well.
  2. Not really the end of the world but unRAID keeps saying there is a new update for this Plex docker even if I just updated it. Sorry if this has been discussed previously (didn't find it).
  3. Not sure why I didn't read about this before but I've just set it up (takes 30 seconds to do) and tested it and it works perfectly. Transcoding a 1080p movie to 480p on a poor connection with the server's IGP (some Intel HD something integrated into my Xeon E3-1245 V6) and it took about ~30MB of space on the FS... which translated to +30MB of RAM used too. As soon as I stopped the playback, the files were deleted. I'll test it for a while and as long as Plex keeps deleting its transcoding cache, this should be fine. CPU is usually around ~120% when transcoding with the GPU (or like 12% in the webUI, it's a 4c8t CPU). Without GPU transcoding it would usually gobble all 8 threads immediately until it throttled a little bit. I added another extra parameter to the docker to make sure it never takes more than 75% of my CPU: --cpus=6.
  4. Thanks for the quick reply and fixing the support thread for your docker. Since I don't see any reason to use a docker only to run a ~40ish lines script, I won't use it, but for people less at ease with programming, I can see the ease of use of just clicking buttons in the UI being helpful for them.
  5. I don't have access to this sadly: https://access.redhat.com/solutions/3249121 unRAID uses logrotate as shown here: root@server:~# cat /etc/logrotate.d/docker /var/log/docker.log { rotate 5 notifempty missingok size=5M compress delaycompress } Another suggestion coming from the Redhat community: https://bugzilla.redhat.com/show_bug.cgi?id=1477486 Maybe I should report this as a bug for unRAID. Multiple events must happen for this bug to even exist: 1) dockerd not properly closing handles on rotated logs 2) the log rotation must move files rather than copy them 3) having limited /var/log space 4) dockerd must not be restarted for a long time Workaround: using copytruncate option with logrotate. http://man7.org/linux/man-pages/man8/logrotate.8.html I added copytruncate to the config file shown above and tested before/after with logrotate -f and lsof and I can see this fixes the issue completely. I'm gonna add a user script to modify the docker logrotate config file on boot.
  6. I'm thinking docker.log is empty solely because the process is writing in the moved (but deleted) file. Since the file is still opened by dockers, despite not having a pointer on the filesystem is can still be read (and shown in the GUI) as long as you go through the dockerd process. unRAID does have logrotate not only for dockerd. I will take a look at the config and see what I can do but I'm thinking everyone has the same problem here.
  7. Traditionally when rotating a log manually you make a copy of it and empty the original, this way the process keeps writing in the original file and there is no handle on the copy. This is weird.
  8. The issue here is that we move files that are being used by the process (dockerd) so the handles stays there. Deleting it just remove the pointer to the file but the space isn't freed until the handle is fully closed. There is a workaround described here: https://unix.stackexchange.com/questions/68523/find-and-remove-large-files-that-are-open-but-have-been-deleted Now, why is docker.log rotated? To prevent it from taking too much space... but we don't prevent anything by rotating it, and since we delete the old file rather than archiving it, wouldn't it be better to just empty the file rather than move it and delete it? Not sure if this is a dockerd issue or unRAID issue, really. Who handles the log rotation?
  9. I stopped the docker engine through the webUI... here are the results: root@server:~# df -h /var/log Filesystem Size Used Avail Use% Mounted on tmpfs 256M 2.9M 254M 2% /var/log root@server:~# lsof | grep deleted ipmitail 5272 root 0r REG 0,2 1598 2925 /var/spool/atjobs/a00001018cd2c1 (deleted) tail 5279 root 0r REG 0,2 1598 2925 /var/spool/atjobs/a00001018cd2c1 (deleted) What this shows is... the problem is indeed caused by dockerd. The handles on deleted files are gone, so it was most likely the deleted files. Maybe one of the docker.log actually had stuff in it, I will never know? I still think it's a problem that deleted files take space on /var/log, I will try to find a creative solution to avoid having to stop dockerd while still getting rid of the handles.
  10. The file is actually empty. root@server:~# ls -lh /var/log/docker.log -rw-rw-rw- 1 root root 0 Sep 13 04:40 /var/log/docker.log Something else is taking space... I have no idea how? root@server:~# du -sm /var/log/* 1 /var/log/apcupsd.events 1 /var/log/apcupsd.events.1 1 /var/log/apcupsd.events.2 1 /var/log/apcupsd.events.3 1 /var/log/apcupsd.events.4 0 /var/log/btmp 1 /var/log/btmp.1 0 /var/log/cron 0 /var/log/debug 1 /var/log/dmesg 0 /var/log/docker.log 0 /var/log/faillog 1 /var/log/lastlog 1 /var/log/libvirt 1 /var/log/maillog 0 /var/log/messages 0 /var/log/nfsd 1 /var/log/nginx 0 /var/log/packages 1 /var/log/pkgtools 0 /var/log/plugins 0 /var/log/removed_packages 0 /var/log/removed_scripts 0 /var/log/samba 0 /var/log/scripts 0 /var/log/secure 0 /var/log/setup 0 /var/log/spooler 0 /var/log/swtpm 1 /var/log/syslog 2 /var/log/syslog.1 2 /var/log/syslog.2 1 /var/log/wtmp That doesn't make sense at all, df says I have 168MB used.
  11. As shown in my original post I have 256MB for mine which is already double the size. Expanding it further only buys time and doesn't solve the issue. I will take a look tonight at what's in the docker logs but 200MB in 7 months ain't that bad overall considering how we use Plex alone.
  12. That won't prevent it from happening again. Of course I could do a script to do this every once in a while but I can't have Plex randomly reboot when busy, so most likely I'd need to keep doing it manually. I can't be the only one with this problem.
  13. Not sure if normal but this is where I get redirected when clicking the support thread for the godaddy ddns docker. I was wondering if you were doing anything special since I've modified some script I found on the web and run it with cron and it gets the job done. #!/bin/bash keys=(key1 key2) secrets=(secret1 secret2) domains=(domain1 domain2) Type=A Name=@ TTL=600 CachedIP=/tmp/current_ip CheckURL=http://api.ipify.org echo -n "$(date +%Y%m%d%H%M%S) Checking current 'Public IP' from '${CheckURL}': " PublicIP=$(curl -kLs ${CheckURL}) if [ $? -eq 0 ] && [[ "${PublicIP}" =~ [0-9]{1,3}\.[0-9]{1,3} ]]; then echo "${PublicIP}." else sleep 120 PublicIP=$(curl -kLs ${CheckURL}) if [ $? -eq 0 ] && [[ "${PublicIP}" =~ [0-9]{1,3}\.[0-9]{1,3} ]]; then echo "[retry] ${PublicIP}." else echo "[retry] Fail! ${PublicIP}" exit 1 fi fi if [ "$(cat ${CachedIP} 2>/dev/null)" != "${PublicIP}" ]; then for ((i = 0; i < ${#domains[@]}; ++i)); do echo -n "$(date +%Y%m%d%H%M%S) Checking '${domains[$i]}' IP records from 'GoDaddy': " Check=$(curl -kLsH"Authorization: sso-key ${keys[$i]}:${secrets[$i]}" -H"Content-type: application/json" https://api.godaddy.com/v1/domains/${domains[$i]}/records/${Type}/${Name} 2>/dev/null|jq -r '.[0].data')>/dev/null if [ $? -eq 0 ] && [ "${Check}" = "${PublicIP}" ]; then echo -e "unchanged.\n$(date +%Y%m%d%H%M%S) Current 'Public IP' matches 'GoDaddy' records. No update required." else echo -e "changed.\n$(date +%Y%m%d%H%M%S) Updating '${domains[$i]}' from '${Check}' to '${PublicIP}'." Update=$(curl -kLsXPUT -H"Authorization: sso-key ${keys[$i]}:${secrets[$i]}" -H "Content-type: application/json" https://api.godaddy.com/v1/domains/${domains[$i]}/records/${Type}/${Name} -d "[{\"data\":\"${PublicIP}\",\"ttl\":${TTL}}]" 2>/dev/null) if [ $? -eq 0 ] && [ "${Update}" = "" ]; then echo "$(date +%Y%m%d%H%M%S) Success." else echo "$(date +%Y%m%d%H%M%S) Fail. ${Update}" exit 1 fi fi done echo ${PublicIP}>${CachedIP} else echo -en "$(date +%Y%m%d%H%M%S) Current 'Public IP' matches 'Cached IP' recorded. No update required.\n" fi exit $? I'm trying to understand in what use case scenario would a docker be a better solution than a simple 40ish lines script (could probably be optimized to < 30 lines).
  14. Old thread but I'm also looking to get a persistent private key across reboots/updates and this doesn't seem to work anymore, it says mkpkg isn't installed.
  15. Here: root@server:~# df -h /var/log Filesystem Size Used Avail Use% Mounted on tmpfs 256M 167M 90M 65% /var/log root@server:~# du -sm /var/log 3 /var/log du doesn't find much and there is no mountmoint under /var/log/* either. I looked it up on the web and people mentionned it usually happens if there are deleted files/handles locked by a process such as: root@server:~# lsof | grep "/var/log/" | grep deleted dockerd 6282 root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 2047 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 2047 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6286 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6286 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6287 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6287 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6288 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6288 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6290 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6290 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6291 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6291 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6295 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6295 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6296 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6296 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6297 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6297 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6298 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6298 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6299 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6299 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6317 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6317 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6318 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6318 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6319 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6319 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6320 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6320 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6321 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6321 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6322 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6322 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6323 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6323 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6324 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6324 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6325 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6325 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6578 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6578 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6579 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 6579 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 8090 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 8090 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 10337 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 10337 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 12624 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 12624 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 17100 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 17100 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 17643 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 17643 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 19395 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 19395 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 20294 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 20294 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 25049 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 25049 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 28520 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 28520 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 31502 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 31502 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 32693 dockerd root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) dockerd 6282 32693 dockerd root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 1082 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 1082 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 3031 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 3031 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6301 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6301 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6302 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6302 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6303 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6303 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6304 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6304 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6305 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6305 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6306 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6306 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6307 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6307 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6308 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6308 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6309 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6309 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6310 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6310 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6311 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6311 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6312 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6312 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6314 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6314 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6315 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6315 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6316 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6316 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6976 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6976 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6977 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6977 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6978 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 6978 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 7304 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 7304 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 8412 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 8412 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 9110 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 9110 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 9111 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 9111 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 10407 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 10407 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 11343 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 11343 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 13038 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 13038 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 13371 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 13371 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 15705 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 15705 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 16646 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 16646 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 20586 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 20586 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 32149 container root 1w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) container 6300 32149 container root 2w REG 0,28 171606437 25553 /var/log/docker.log.1 (deleted) Right... so the log rotation works I guess... but the deleted files apparently still take space on /var/log (at least that's what I'm thinking)? I didn't try (yet) to kill/restart the dockerd engine (which would remove the locked handles shown above) since I'd like to find a better way. My server has 200+ days of uptime so yes, rebooting once in a while would obviously prevent the issue but that's not an actual fix, so I'm looking for a better solution.
  16. That's probably out of topic a little bit but I use Check_MK to keep stats on all my dockers/VMs/servers so I do need the API if I want a nice chart over 400 days of active tunnels and activity. With the wg command I can easily make a local check in shell or bash. Edit: Just realized I need 6.8 to get this working, I'm still under 6.7 with over 200 days of uptime. I will wait a little bit but will definitely try it.
  17. Seems like there is extra setup required to be able to properly connect to dockers from the VPN with Wireguard, which just shows how clueless I am about networking in general since I don't understand how different it is exactly from my current setup. You are right though, I should give it a try. I assume there is an API that comes with Wireguard to monitor who is connected or the number of connections? I will give it a look.
  18. For this to work you do have to forward one port from your router directly to your unRAID server. It's been established in the past that it's better not to forward any port to your unRAID server because unRAID was never really built around security. Did I misunderstand something or did something change? Aside from performances (and assuming this is not an issue), what are the advantages of using Wireguard instead of a dedicated docker/VM with OpenVPN/Softether where you can get better isolation from your unRAID server? Also I'm no network expert but I have a Softether server installed in a Windows VM and never had to add any rule to my router besides forwarding 1 port to that VM and my dockers are perfectly accessible from the VPN. My router is still the DHCP server within that VPN tunnel so the peripheral jsut behaves like anything else on the local network (which is, from my perspective, what people usually try to achieve with VPN).
  19. What I like the most about unRAID is its versatility. One feature I wish in the future is the ability to make a cluster of 2 unRAID servers for redundancy.
  20. Has anyone been able to make this board work out of the box with an Oculink cable (such as this one: https://store.supermicro.com/supermicro-50cm-oculink-to-4-sata-cable-cbl-sast-0933.html)? Was there anything extra needed (jumpers on the board, software issues, etc) or was it just plug and play? Looking to build an array with at least 8 drives (maybe even 10 with the cache drives). Otherwise, any suggestion for an add-on card to hook up more drives (something like up to 16 ideally)? Maybe from LSI? Something that will work well with Unraid obviously.
  21. Personally I just use NFS to mount them on my guest machines. I only mount the shares that I need. Not sure what are the best practices however so I'm curious to hear about what others have to say. I've never used the built-in option in the template to use a share. Sent from my Pixel 3 using Tapatalk
  22. Has anyone updated to 6.7.1 or 6.7.2 and can confirm that this still works properly for the new zombieland vulnerability? I assume everything is fine looking at cybrnook's post.
  23. Honestly, getting 2 or 3% on average is already a lot in my book and enough to bother. People overclock and sometimes stress their components a lot for barely more than that. Getting more than that in some specific scenarios is just a nice bonus.
  24. So what advantage does the plugin provide over a simple parity check overall other than performance-related issues? Does bitrot still happen in modern system or is it something that should be disregarded altogether? The reason I started worrying about it is my friend lost some JPG files recently due to this, had to recover from a backup and he's been using unRAID for a while. He does have a lot of old hard drives however and old hardware in general so that may be an issue that I'm not really facing as much.
  25. I'm no expert (so no, I'm not sure about this) but from my understanding, since you have at least 1 parity disk which has each bit set to the sum of the corresponding bits on all the other disks, if one disk is corrupted, some bits won't add up anymore, thus creating parity check issues. I thought it would be easy to repair then. But I'm probably wrong, I just need someone with better knowledge about this to explain it. With RAID5 it's different, the parity is stripped across all disks. So if you lose a disk, you definitely lose some data and some parity, but you can recover with your stripped parity and data from the other disks.