Bob1215

Background: I have reached the limit of SATA connections and am close to running out of space. I remove a 4TB (disk7) and replace it with a 14TB. Then, I accidentally hit the 'parity check' button, or it automatically started from schedule. Disk 10 shows 2 billions errors. I format new disk7, but am unsure how to rebuild disk7. Is it possible? I still have old disk7 unattached.

@binhex have you seen this issue before? I'm a bit perplexed by it, and there has been no download/upload activity for about a week. Assuming this was a VPN provider issue, as there does not seem to have been any updates to this container or unRAID OS recently, and everything is working again

I've been using this container for a few years, but starting on 2022-03-30, I've had an issue where torrent can be added, but will not download or upload. INFO: I can access both the webUI and thin client just fine. The bottom status bar in deluge show `N/A` for the IP. Torguard's test torrent is showing the correct TorGuard VPN IP address (matches the address in the torguard wireguard config `wg0.conf`) Adding a torrent via magnet populates the info about size, peers and seeders For example, recently added `ubuntu-20.04.4-desktop-amd64.iso` is showing as 3.1GB with 1214 seeds I have not touched unRaid in the last few weeks, so no changes have been made to the OS (uptime 40+ days) Containers are set to auto-update, but I'm unsure if binhex has released a new container since 2022-03-29 My privoxy works perfectly fine Nothing out of the ordinary in the logs (but I may have missed something). See below

I removed the port forwarding from the router. I also requested a new port from torguard (one that is not in use by any other container) and updated the wireguard conf file "ListeningPort" parameter to this new value. I needed to make one other correction, however. Instead of using this port in the deluge network settings "Listening Port", I used the port from the torguard "manage ports" page in the column named " VPN IP" instead of the new port listed in the "Port" column of that page. I am now connectable. Thanks for the guidance, @strike.

I'm hoping for some assistance setting up with custom VPN (torguard). I'll outline the steps I have taken. I followed the guide here (archived link) to request a port from torguard I requested port 58846 on the Chicago server (45.128.36.154). See image in spoiler below I added the conf file generated in the guide to `/config/wireguard` directory. I updated the listening port to 58846. See image in spoiler below I made sure that the container was running in privileged mode per FAQ A21. See image in spoiler below I changed `VPN_PROV` to "custom" and entered new torguard credentials. See image in spoiler below I added a new key/value for `VPN_CLIENT` per FAQ A21. See image in spoiler below I forwarded port 58846 on my router configuration page. IP 192.168.1.2 is the IP of the server running unRAID. See image in spoiler below I set the incoming port to 58846 in deluge. See image in spoiler below running `netstat -p` inside the container shows "58846" showing up once in the local address and once in the foreign address: It can be seen the in the deluge settings screenshot that, even though I input "58846" as the "incoming port", it shows the active port as "58847". I am also see that I am considered "unconnectable" on my favorite sites. These sites show me as connecting from "45.128.36.154:58847" Any assistance is greatly appreciated.

About a week ago sonarr was no longer able to connect to any indexers or any download clients. Test would fail, occasionally there would be an entry in the logs referring to privoxy. I disabled the proxy in the sonarr settings and am now able to connect with both my indexers and download clients. I will open an issue on github, but this message is for anyone looking for a temporary solution.

- I tried both Host and Bridge, and they both worked for me. - causes the container to succeed in creation, but fails to start (and no logs) - worked perfectly - I copied a different container and put `http://[IP]:[PORT:631]/`, which works! I have an HP printer connected by USB (with Parallel Port to USB cable) that I cannot get CUPS to see. Some basic info: root@Tower:~# lsusb Bus 002 Device 003: ID 0781:5575 SanDisk Corp. Cruzer Glide Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 003: ID 067b:2305 Prolific Technology, Inc. PL2305 Parallel Port Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub root@Tower:~# ls -l /dev/bus/usb/006/ total 0 crw-rw-r-- 1 root root 189, 640 Feb 18 23:43 001 crw-rw-r-- 1 root lp 189, 642 Feb 19 00:50 003 Any advice is welcome.

I'm using a subdomain like "subdomain_name.duckdns.org". I originally attempted to update by connecting remotely via a VPN connection to my server and applying the update through the webui. Not sure if that contributed to the 504s. I'll keep a closer eye on the update process and report back if I have any useful information for troubleshooting/debugging.

If you still needed to complete the update: Click the link to the update guide in the first post, skip step 2 (putting nextcloud into maintenance mode with occ), complete the steps to update manually and close maintenance mode. Otherwise just do the last steps in that guide to close maintenance mode. Sent from my SM-N950U using Tapatalk

Has anyone experienced this and were able to solve it?

I kept getting 504 codes at different points in the web updater sequence, and at another time some message about not being able to unzip/zip. But I did just skip that second step regarding turning maintenance mode on (like you said, it was already stuck on). I completed the steps in the guide and it's back up and running. Thanks for taking the time to help out [emoji4]

I attempted to follow the guide linked in the first post, but it my `occ` is missing root@Tower:~# docker exec -it nextcloud bash root@7010b1d5296c:/# sudo -u abc php7 /config/www/nextcloud/occ maintenance:mode --on Could not open input file: /config/www/nextcloud/occ root@7010b1d5296c:/# ls -l /config/www/nextcloud/ total 16 drwxrwxr-x 1 abc abc 0 Jan 10 17:17 apps drwxrwxr-x 1 abc abc 38 Jan 10 17:17 config -rw-rw-r-- 1 abc abc 57 Jan 10 17:16 index.php -rw-rw-r-- 1 abc abc 57 Jan 10 17:16 public.php -rw-rw-r-- 1 abc abc 57 Jan 10 17:16 remote.php -rw-rw-r-- 1 abc abc 57 Jan 10 17:16 status.php drwxrwxr-x 1 abc abc 42 Jan 10 17:17 themes drwxrwxr-x 1 abc abc 42 Jul 23 2018 updater root@7010b1d5296c:/# find . -type f -iname "occ" find: ./sys/kernel/slab/unraid/md: No such file or directory ./data/updater-ocahy6bwi45i/backups/nextcloud-16.0.5.1/occ ./data/updater-ocahy6bwi45i/backups/nextcloud-17.0.1.1/occ ./data/updater-ocahy6bwi45i/backups/nextcloud-16.0.4.1/occ ./data/updater-ocahy6bwi45i/backups/nextcloud-16.0.3.0/occ ./data/updater-ocahy6bwi45i/downloads/nextcloud/occ root@7010b1d5296c:/# Any advice on how to move forward?

I kept getting a 504 code when attempting to update form the webUI. Now I can't access nextcloud at all. I posted and issue here Expected Behavior When navigating to the NextCloud instance through the web browser, the application should be shown. Current Behavior The following message is shown "Update in process." and has persisted for multiple hours, including after reboot and using multiple browsers (FireFox ESR and Brave Browser) Steps to Reproduce 1. Open web browser 2. Type in NextCloud URL 3. See message Environment OS: unRAID 6.8.0 CPU architecture: x86_64 Docker logs [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 1000 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 40-config: executing... [cont-init.d] 40-config: exited 0. [cont-init.d] 50-install: executing... [cont-init.d] 50-install: exited 0. [cont-init.d] 60-memcache: executing... [cont-init.d] 60-memcache: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Could not open input file: /config/www/nextcloud/cron.php Could not open input file: /config/www/nextcloud/cron.php .... .... .... Could not open input file: /config/www/nextcloud/cron.php Could not open input file: /config/www/nextcloud/cron.php [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... usermod: no changes ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 1000 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 40-config: executing... [cont-init.d] 40-config: exited 0. [cont-init.d] 50-install: executing... [cont-init.d] 50-install: exited 0. [cont-init.d] 60-memcache: executing... [cont-init.d] 60-memcache: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Could not open input file: /config/www/nextcloud/cron.php Could not open input file: /config/www/nextcloud/cron.php Could not open input file: /config/www/nextcloud/cron.php Could not open input file: /config/www/nextcloud/cron.php

I can't speak to your other questions, but I've read quite a bit on this forum and other forums about the number of torrents that are able to be seeded. It seems like most torrent clients start to have issues after 3,000 or so (some as few as a couple hundred). Many people mentioned that in order to get the 35k+ torrents work, you'd be using rTorrent in a terminal, as even ruTorrent seems to max out around 4-5,000. Others can correct me if I have misunderstood this, though.

I'm having the same issue, and same log output: "[warn] Wait for rTorrent process to start aborted, too many retries"