All Activity

Again, the interface spam happened at 8am on Sunday. I've tried getting logs from docker via this script: #!/bin/bash cd /mnt/user/appdata timeout 2h docker compose logs -f -t --since=1s > /mnt/user/data/docker-compose.log However, this didn't record properly for the full duration: Script Starting Apr 28, 2024 07:00.01 Full logs for this script are available at /tmp/user.scripts/tmpScripts/Get Docker Compose Logs/log.txt error from daemon in stream: Error grabbing logs: unexpected EOF Script Finished Apr 28, 2024 07:01.21 Full logs for this script are available at /tmp/user.scripts/tmpScripts/Get Docker Compose Logs/log.txt I don't think it's a problem with the script, since it recorded over a minute. The last line from the logs doesn't seem to be the problem either: autobrr | 2024-04-28T05:01:21.043895040Z {"level":"debug","module":"filter","method":"CheckFilter","time":"2024-04-28T07:01:21+02:00","message":"(Cross-Seed) external filter check not matching what filter wanted"}

I've been having issues getting a successful backup. I tried excluding things and all changing the order of things.... but never had luck. Now, I decided to simply stop ALL dockers before running the backup, and it still failed. A number of files changed somehow? And some other strange errors. 7 total failures. I have quite a lot of images installed, but I figured with NOTHING running, it should complete successfully. Mover isn't running either, not that it should be moving appdata files anyway.. Any protips? Debug log: a5598295-47ea-4c73-b1c7-909c1dc1ea3a

Please update your container, already updated it.

They just released a new version... I already updated the container. (Maybe the found an issue which is with the new version fixed) I assume that's when you mount a share to the container where the share is meant to not stay on the cache drive or is this the case for all shares on the cache (which would not make much sense).

Following the most recent update of Parity Check Tuning (2024.04.27), I'm now receiving an "Unclean shutdown detected". Doesn't matter if I do a shut-down or a reboot - the msg shows up the next time I log in. Happening on both my unRAID servers. If it matters - my Parity Checks run monthly on the evening of the 1st of the month - so I have NOT run a parity check since the update. Also rcving msgs that SAYS it kicked in an "Non-Correcting Parity Check" (zero errors), but I have not seen it actually running whenever I've looked. My larger system Parity check usually takes a couple days (16TB), but this "Non-Correcting" check only took 2.5 hrs!? The smaller system parity check usually takes 16 hrs and that matches the time for that system's "Non-Correcting" check.

The main question is why? You usually create to a TS3 server via your hostname and port like host.com PORT You have to forward all ports since one is the query port, then there is one for the voice channel and one for data transfer. As said above you have to forward all ports because this is not a web server that proxies http/https traffic... Sure you could use streaming ports but the benefit from this is non existent and you are overcomplicating your setup. It is fine to forward the ports in your Firewall like it is for a game server (game servers are also not using http/https). You can read a bit more here where I write and rant about it a bit more (it's another application but it applies here too) :

No, this is just a display thing and because I don't expose any ports in the Dockerfile but that won't prevent the container from working. You will get the same on other container too where they don't expose ports, I'm also not a huge fan of exposing ports because it will always show a wrong port if you change the port in the game config and use eth0 or br0. Yes, because this is a game server and this is nothing like Plex (this was already discussed multiple times in this thread). Reason behind this is that such port check sites will only check for http/https and can't check if a port for a game server is open because game servers use their own proprietary protocol <- not http/https and game servers won't answer to such sites. Please forget about that, that doesn't matter at all, the container is running and is exposing the ports just fine. Are you sure that your NAT Reflection is working properly? Have you yet tried to connect from outside your LAN, I had many users where NAT Reflection was not working properly and they simply couldn't see their server from their own network.

How do you try to connect, which port have you set? This is a really game specific question and I think you have to look that up or at least ask on the SvenCoop Forums over here or here. This should not be related to the container itself.

ei ei ei ... wo willst du denn die Dokumente haben ? hast du dir ein Share erstellt für Dokumente ? hast du dir in einem vorhandenen Share einen Ordner erstellt für deine Dokumente ? ... und dorthin mountest du dann Beispiel, ich nutze einen Share Dokumente und einen separaten import Pfad ... export gar nicht da ich eh sichere ... jetzt hast du beide Beispiele vereint, eigener Share, Ordner in einem vorhandenen Share ... wenn du dein o.g. Beispiel nutzt, liegen die Daten später im appdata Ordner, wenn das ok ist kannst du das auch so machen ... aber nicht wenn was nicht passt aus Versehen den ganzen appdata/paper... löschen, dann sind auch deine Dokumente weg.

Thanks for the hint. This should be the right cable and mode then? https://www.ebay.de/itm/193629242797?itmmeta=01HWHKWCS6ZCJF1D96G5S2ZBQH&hash=item2d1533c5ad:g:iokAAOSwv9pfO~0C&itmprp=enc%3AAQAJAAAA4Fe9XOqzobqx%2FwX9OH7iF6N0Rr5aUMJlaGBKwDIWTsg9gKUQ2fWmm1%2BmF9S59M8hCgbMv%2BR%2FsBcdBNKiZQ9Jo487Tqyg6bWd9HtrcBg8C9G44X2MzDusiOEgNZ8HVfZiz%2FFcv4s4jNfFgZ86V430SC%2FzzIKTchTwqr8QAWnUUFXpAYAT2mYXB%2BHX61%2B%2FPTWORepAcurlbZPpRMIkA658hVH%2F7wk4ATSeSuEf9i%2Fz--1RzPScLh3%2FZ%2FDJdcEojS1axHWdlukROMLEwqUispmVEEaXptn2CYjQ%2F8kAsldCsFjv|tkp%3ABk9SR9rM8bPkYw

vpn tunneling may be best for secure connection for 1 to 1 ... but why nfs and not smb? I would recommend using unassigned for smb share. Take control of your smb and make a manual smb config:

the cables are wrong. Those cables are for 7 pin fiber jbod external. also you want to use unraids software raid not the hba hardware raid you need to make sure it is in IT mode. you will need a mini sas connector for the HBA card see EU links:

In etwa so ? /mnt/user/appdata/paperless-ngx/data /mnt/user/appdata/paperless-ngx/consume /mnt/user/appdata/paperless-ngx/export /mnt/user/appdata/paperless-ngx/media

Where you find this Information?

I don't have time too,,,, I would love to learn to make a docker image. But this is a lot of editing to make. But possible to run similar to test and use a database to collect data. More of a issue to maintain/ keep its parts updated. all in all the git and scripts are not bad and properly setup. Thanks for sharing. Sorry, used post as a hijacked rock wall for notes. Not sure what you did to "have mess of docker tab"?

/mnt/user is a unified view of all the shares. Every share exists within there, along with /mnt/diskX (or /mnt/cache)

Because appdata also exists on disk3. Set the secondary storage to be array with mover action of array --> cache, stop the docker service in Settings -> docker and run mover.

And on a reboot the patch shows as not being installed in the plugins tab (don't worry about the install errors one)

da liegt dein Fehler, pass die mal ordentlich an und dann sollte das auch gehen ... /mnt/usr/src/.... ist sicher nicht dein Share auf Unraid ...

Long standing issue (fixed I believe in 6.13). It also has the net result of whenever you go to the VMs tab it's a given that all/most of your drives will spin up

docker run docker run -d --name='paperless-ngx' --net='bridge' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="paperless-ngx" -e 'PAPERLESS_REDIS'='redis://192.168.178.108:6379' -e 'PAPERLESS_OCR_LANGUAGE'='deu' -e 'PAPERLESS_OCR_LANGUAGES'='deu' -e 'PAPERLESS_FILENAME_FORMAT'='{created}-{correspondent}-{title}' -e 'PAPERLESS_TIME_ZONE'='Europe/Berlin' -e 'PAPERLESS_IGNORE_DATES'='' -e 'PAPERLESS_CONSUMER_POLLING'='5' -e 'PAPERLESS_SECRET_KEY'='e11fl1oa-*ytql8p)(06fbj4ukrlo+n7k&q5+$1md7i+mge=ee' -e 'USERMAP_UID'='99' -e 'USERMAP_GID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8000]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/selfhosters/unRAID-CA-templates/master/templates/img/paperless.png' -p '8000:8000/tcp' -v '/mnt/user/appdata/paperless-ngx/data':'/usr/src/paperless/data':'rw' -v '/mnt/user/src/paperless-ngx/media/':'/usr/src/paperless/media':'rw' -v '/mnt/user/src/paperless-ngx/consume/':'/mnt/user/src/paperless/consume':'rw' -v '/mnt/user/src/paperless-ngx/export/':'/usr/src/paperless/export':'rw' 'ghcr.io/paperless-ngx/paperless-ngx' 3441d5de26019c4936b72c688e62bf14eb1f60ca8a6b278294abb9377efdb19a

I would say B for future upgradability, maybe? Also, dedicated gpu for plex is overkill in my opinion. igpu works great. Downsides, no ECC...maybe?

I really can't. Just changed stuff around until it worked and that was what I changed. Edit: I moved it from "Game Parameters:" with "?Port=7779" to "Extra Game Parameters:" with "-Port=7779" and everything started working and both servers were running separately. Keeping it in Game Parameters with the "?" showed the server with the correct name, but any attempts to connect would just connect to the original server at 7777.

Just thought I would post my setup that currently runs great for Plex. Intel i7 13700k - Overkill for plex - just make sure yours has igpu for transcoding. ASUS PRIME Z690-A 128gb DDR5 Synology NAS - 20 terabytes - with 10gigabit over fiber. Stores all TV/Movie media The Synology and Unraid server are in different locations (house/detached garage) and serve as duplication for most data and backups. If you will only be running plex you don't need latest CPU, mb, etc. Hope it helps.