lightsout

For sure I appreciate the effort. I'll definitely come back here if it happens again. And helpful for anyone who runs into the same issue.

Honestly I have no idea but that's helpful if it happens again. I did what was recommended. Can't remember exactly but partially started over. Didn't touch the array but got rid of all plugins and turned off all dockers. The problem went away and I slowly started adding things back to see if it acted up again. Haven't had any issues since.

edit - seems to be resolved.

I got it working with tailscale.

All good thanks man.

To sent you a pm if you don't mind to hide ip's.

I keep trying to figure out what that is but nothing works.

I am using the wireguard app on my phone and connecting it to my routers vpn. I can access all the others arrs with my home local ip (192.168.1.x) but qbitorrent never works.

Any idea what one would add to be able to access from mobile data?

Thanks I am not looking to open up unraid remotely. Basically I have a wireguard vpn in my router that I want to be able to connect to to interact with qbit throughh nzb360. I can do it with every arr app except qbit. I will do more testing.

No it's intentionally not. It's 192.168.0.0/24 I added that to the wg config and qbit wouldn't load. Any help on how to do that. Also how would I know what ip range to add for my phone on Mobile data.

I am running qbitorrentvpn with airvpn and wireguard. All works great. I also have a wireguard vpn on my asus router that I can turn on to access my home lan remotely. When I do this I can access all my other arr stack dockers remotely. (through nzb360 or web browser, such as sab, radarr, sonarr, etc.) But I cannot access qbit remotely, I believe this is related to the vpn in this docker. My home lan is simple, 192.168.1.0/24 everything on that same network, no vlans or docker networks. I have entered the home lan address (192.168.1.0/24) in the config for this docker. Is there something I need to do in my wireguard config file inside the docker container so that I can access qbit like all my other arrs from outside the network. Hopefully the way I have explained it makes sense.

Ok thanks. I have to imagine it is something to do with the custom VPN setup of this version. But idk. I'll go ask over there.

Anyone help a guy out here? I have a bunch of well seeded torrents that add in the "stalled" condition. The tracker is having no issue, I am connectable, port is forwarded in air on, VPN server is up and good. It's not every torrent even from one site. Really at a loss been dealing with it on and on.

I don't think its permissions because restarting the container sometimes gets it to work. It comes and goes. Not sure if this is the correct log 2024-08-19 09:47:07,535 DEBG 'start-script' stdout output: [info] Attempting to bring WireGuard interface 'up'... 2024-08-19 09:47:07,540 DEBG 'start-script' stderr output: Warning: `/config/wireguard/wg0.conf' is world accessible 2024-08-19 09:47:07,543 DEBG 'start-script' stderr output: [#] ip link add wg0 type wireguard 2024-08-19 09:47:07,544 DEBG 'start-script' stderr output: [#] wg setconf wg0 /dev/fd/63 2024-08-19 09:47:07,545 DEBG 'start-script' stderr output: [#] ip -4 address add .... dev wg0 2024-08-19 09:47:07,545 DEBG 'start-script' stderr output: [#] ip link set mtu 1320 up dev wg0 2024-08-19 09:47:07,547 DEBG 'start-script' stderr output: [#] resolvconf -a wg0 -m 0 -x 2024-08-19 09:47:07,555 DEBG 'start-script' stderr output: [#] wg set wg0 fwmark 51820 2024-08-19 09:47:07,555 DEBG 'start-script' stderr output: [#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820 2024-08-19 09:47:07,556 DEBG 'start-script' stderr output: [#] ip -4 rule add not fwmark 51820 table 51820 2024-08-19 09:47:07,556 DEBG 'start-script' stderr output: [#] ip -4 rule add table main suppress_prefixlength 0 2024-08-19 09:47:07,558 DEBG 'start-script' stderr output: [#] sysctl -q net.ipv4.conf.all.src_valid_mark=1 2024-08-19 09:47:07,559 DEBG 'start-script' stderr output: [#] iptables-restore -n 2024-08-19 09:47:07,560 DEBG 'start-script' stderr output: [#] '/root/wireguardup.sh' 2024-08-19 09:47:08,629 DEBG 'start-script' stdout output: [info] Attempting to get external IP using 'http://checkip.amazonaws.com'... 2024-08-19 09:47:16,950 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address .... 2024-08-19 09:47:16,950 DEBG 'start-script' stdout output: [info] WireGuard interface 'up' 2024-08-19 09:47:16,951 DEBG 'start-script' stdout output: [info] VPN provider 'airvpn' not supported for automatic port forwarding, skipping incoming port assignment 2024-08-19 09:47:17,030 DEBG 'watchdog-script' stdout output: [info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP .... different, marking for reconfigure 2024-08-19 09:47:17,032 DEBG 'watchdog-script' stdout output: [info] qBittorrent not running 2024-08-19 09:47:17,032 DEBG 'watchdog-script' stdout output: [info] Removing session lock file (if it exists)... 2024-08-19 09:47:17,040 DEBG 'watchdog-script' stdout output: [info] Attempting to start qBittorrent... 2024-08-19 09:47:17,098 DEBG 'watchdog-script' stdout output: [info] qBittorrent process started [info] Waiting for qBittorrent process to start listening on port 8181... 2024-08-19 09:47:18,854 DEBG 'watchdog-script' stdout output: [info] qBittorrent process listening on port 8181

For some reason all of my downloads are stuck at "stalled". I haven't changed any config. I am using airvpn, went to their site and confirmed the server I am using is up, and port is open. Qbit says I am connectable. Not sure what to do. I have tried 3 or 4 trackers same issue.

Great thanks.

So I have been up for 24 hours. No longer in safe mode. I have reinstalled a few plugins, mainly just what was need to use Intel quicksync with Emby. I also have my main dockers up, which is the arr stack, and media servers like plex and emby. So far I see some smb panics and no issues with the webui or drives falling off. Pretty happy about that. Going to forgo dockers that I wasn't really needing, and slowly re-add the plugins that I need. A question on restoring the flash drive. Can I copy and past things into the config folder of the flash drive, like plugins, and then reboot and have them show up. Or do I need to shut down and pull the drive and add stuff that way? Thanks for all your help @JorgeB!

I am having the same issue. 10 days and all added media has not shown up. Other media apps like Emby and Navidrome see it fine. I have scanned libraries, deleted and re-added folders. Stuck at this point. EDIT### DB repair fixed me up. Thanks for that helpful tool.

I'm curious since this happened while in safe mode, is safe mode necessary? Does that rule out a plugin issue?

Would you recommend a different approach?

Uptime 3 hours nothing yet. I believe it has went longer before acting up. What would be the next move? Enable docker and start turning stuff on one by one?

Ok I've done that. So far it's not there but it is also not having any weird activity. I'll leave i t alone for a bit and see if it does it. Docker is totally disabled. On another note: I was also greeted with this when I first booted up (not in safe mode) "503 Service Temporarily Unavailable nginx" syslog(8).txt

I have another thread going here but found these SMB errors and thought maybe I should post here too. After about an hour up the webui becomes unstable. I can watch the drives dissapear, it will flash from 12 drives to 6 to 0. Even cache (nvme) and flash driver will show gone. There is a video in the other thread. I am seeing the same error over and over and it seems to be SMB related, but this is beyond me. Jun 18 13:56:23 Unraid smbd[5048]: [2024/06/18 13:56:23.730972, 0] ../../lib/util/fault.c:184(smb_panic_log) Jun 18 13:56:23 Unraid smbd[5048]: PANIC (pid 5048): reinit_after_fork() failed in 4.17.12 Jun 18 13:56:23 Unraid smbd[5048]: [2024/06/18 13:56:23.731373, 0] ../../lib/util/fault.c:292(log_stack_trace) Jun 18 13:56:23 Unraid smbd[5048]: BACKTRACE: 13 stack frames: Jun 18 13:56:23 Unraid smbd[5048]: #0 /usr/lib64/libgenrand-samba4.so(log_stack_trace+0x2e) [0x14b32450b64e] Jun 18 13:56:23 Unraid smbd[5048]: #1 /usr/lib64/libgenrand-samba4.so(smb_panic+0x9) [0x14b32450b8a9] Jun 18 13:56:23 Unraid smbd[5048]: #2 /usr/sbin/smbd(+0xb13b) [0x5646a80e013b] Jun 18 13:56:23 Unraid smbd[5048]: #3 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x14b3244cd8c1] Jun 18 13:56:23 Unraid smbd[5048]: #4 /usr/lib64/libtevent.so.0(+0xee07) [0x14b3244d3e07] Jun 18 13:56:23 Unraid smbd[5048]: #5 /usr/lib64/libtevent.so.0(+0xcef7) [0x14b3244d1ef7] Jun 18 13:56:23 Unraid smbd[5048]: #6 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x14b3244ccba1] Jun 18 13:56:23 Unraid smbd[5048]: #7 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x14b3244cce7b] Jun 18 13:56:23 Unraid smbd[5048]: #8 /usr/lib64/libtevent.so.0(+0xce97) [0x14b3244d1e97] Jun 18 13:56:23 Unraid smbd[5048]: #9 /usr/sbin/smbd(main+0x1489) [0x5646a80dd259] Jun 18 13:56:23 Unraid smbd[5048]: #10 /lib64/libc.so.6(+0x236b7) [0x14b3242d56b7] Jun 18 13:56:23 Unraid smbd[5048]: #11 /lib64/libc.so.6(__libc_start_main+0x85) [0x14b3242d5775] Jun 18 13:56:23 Unraid smbd[5048]: #12 /usr/sbin/smbd(_start+0x21) [0x5646a80ddb31] Jun 18 13:56:23 Unraid smbd[5048]: [2024/06/18 13:56:23.731414, 0] ../../source3/lib/dumpcore.c:315(dump_core) Jun 18 13:56:23 Unraid smbd[5048]: dumping core in /var/log/samba/cores/smbd Jun 18 13:56:23 Unraid smbd[5048]: Jun 18 13:56:34 Unraid smbd[9365]: [2024/06/18 13:56:34.003054, 0] ../../source3/lib/util.c:491(reinit_after_fork) Jun 18 13:56:34 Unraid smbd[9365]: messaging_reinit() failed: NT_STATUS_DISK_FULL Jun 18 13:56:34 Unraid smbd[9365]: [2024/06/18 13:56:34.003114, 0] ../../source3/smbd/server.c:1033(smbd_accept_connection) Jun 18 13:56:34 Unraid smbd[9365]: reinit_after_fork() failed Jun 18 13:56:34 Unraid smbd[9365]: [2024/06/18 13:56:34.003121, 0] ../../lib/util/fault.c:173(smb_panic_log) Jun 18 13:56:34 Unraid smbd[9365]: =============================================================== Jun 18 13:56:34 Unraid smbd[9365]: [2024/06/18 13:56:34.003125, 0] ../../lib/util/fault.c:174(smb_panic_log) Jun 18 13:56:34 Unraid smbd[9365]: INTERNAL ERROR: reinit_after_fork() failed in pid 9365 (4.17.12) Jun 18 13:56:34 Unraid smbd[9365]: [2024/06/18 13:56:34.003128, 0] ../../lib/util/fault.c:178(smb_panic_log) Jun 18 13:56:34 Unraid smbd[9365]: If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting Jun 18 13:56:34 Unraid smbd[9365]: [2024/06/18 13:56:34.003133, 0] ../../lib/util/fault.c:183(smb_panic_log) Help is greatly appreciated. syslog.txt

Jun 18 13:56:23 Unraid smbd[5048]: [2024/06/18 13:56:23.730972, 0] ../../lib/util/fault.c:184(smb_panic_log) Jun 18 13:56:23 Unraid smbd[5048]: PANIC (pid 5048): reinit_after_fork() failed in 4.17.12 Jun 18 13:56:23 Unraid smbd[5048]: [2024/06/18 13:56:23.731373, 0] ../../lib/util/fault.c:292(log_stack_trace) Jun 18 13:56:23 Unraid smbd[5048]: BACKTRACE: 13 stack frames: Jun 18 13:56:23 Unraid smbd[5048]: #0 /usr/lib64/libgenrand-samba4.so(log_stack_trace+0x2e) [0x14b32450b64e] Jun 18 13:56:23 Unraid smbd[5048]: #1 /usr/lib64/libgenrand-samba4.so(smb_panic+0x9) [0x14b32450b8a9] Jun 18 13:56:23 Unraid smbd[5048]: #2 /usr/sbin/smbd(+0xb13b) [0x5646a80e013b] Jun 18 13:56:23 Unraid smbd[5048]: #3 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x14b3244cd8c1] Jun 18 13:56:23 Unraid smbd[5048]: #4 /usr/lib64/libtevent.so.0(+0xee07) [0x14b3244d3e07] Jun 18 13:56:23 Unraid smbd[5048]: #5 /usr/lib64/libtevent.so.0(+0xcef7) [0x14b3244d1ef7] Jun 18 13:56:23 Unraid smbd[5048]: #6 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x14b3244ccba1] Jun 18 13:56:23 Unraid smbd[5048]: #7 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x14b3244cce7b] Jun 18 13:56:23 Unraid smbd[5048]: #8 /usr/lib64/libtevent.so.0(+0xce97) [0x14b3244d1e97] Jun 18 13:56:23 Unraid smbd[5048]: #9 /usr/sbin/smbd(main+0x1489) [0x5646a80dd259] Jun 18 13:56:23 Unraid smbd[5048]: #10 /lib64/libc.so.6(+0x236b7) [0x14b3242d56b7] Jun 18 13:56:23 Unraid smbd[5048]: #11 /lib64/libc.so.6(__libc_start_main+0x85) [0x14b3242d5775] Jun 18 13:56:23 Unraid smbd[5048]: #12 /usr/sbin/smbd(_start+0x21) [0x5646a80ddb31] Jun 18 13:56:23 Unraid smbd[5048]: [2024/06/18 13:56:23.731414, 0] ../../source3/lib/dumpcore.c:315(dump_core) Jun 18 13:56:23 Unraid smbd[5048]: dumping core in /var/log/samba/cores/smbd Jun 18 13:56:23 Unraid smbd[5048]: Jun 18 13:56:34 Unraid smbd[9365]: [2024/06/18 13:56:34.003054, 0] ../../source3/lib/util.c:491(reinit_after_fork) Jun 18 13:56:34 Unraid smbd[9365]: messaging_reinit() failed: NT_STATUS_DISK_FULL Jun 18 13:56:34 Unraid smbd[9365]: [2024/06/18 13:56:34.003114, 0] ../../source3/smbd/server.c:1033(smbd_accept_connection) Jun 18 13:56:34 Unraid smbd[9365]: reinit_after_fork() failed Jun 18 13:56:34 Unraid smbd[9365]: [2024/06/18 13:56:34.003121, 0] ../../lib/util/fault.c:173(smb_panic_log) Jun 18 13:56:34 Unraid smbd[9365]: =============================================================== Jun 18 13:56:34 Unraid smbd[9365]: [2024/06/18 13:56:34.003125, 0] ../../lib/util/fault.c:174(smb_panic_log) Jun 18 13:56:34 Unraid smbd[9365]: INTERNAL ERROR: reinit_after_fork() failed in pid 9365 (4.17.12) Jun 18 13:56:34 Unraid smbd[9365]: [2024/06/18 13:56:34.003128, 0] ../../lib/util/fault.c:178(smb_panic_log) Jun 18 13:56:34 Unraid smbd[9365]: If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting Jun 18 13:56:34 Unraid smbd[9365]: [2024/06/18 13:56:34.003133, 0] ../../lib/util/fault.c:183(smb_panic_log) Seeing this over and over.