acoop133

Same thing happened to me now. array is stuck at starting. My gui worked fine on 80 and 443 for many years. and suddenly now get nginx :80 already used error. booting into safe mode with UI, and changing ui port to 81 and 444 then start the array has temporary fixed it. However once booting into normal mode, conflict happens again but on 81 and 444. Something fucky is going on, when array starts, thats when the error happens. so something is during array startup procedure is trying to bind to the same port UI is configured to bind to. None of my docker containers are configured to bind to 80 or 81

Ive just now getting this issue and none of the mentions above helped me either.

+100000.

Ok i think i found the culprit. i looked in mover tuner. and i saw a setting that was only move if drive is above 95%. which. changed it to 5% and mover is working

Also what is the plugin name, i only see CA Mover Tuning

How do i reinstall mover after removing it?

Hi, ive had this issue since updating to beta 2 from non beta. im on beta 4 now which problem still persists. When i run the mover, it just immediately stops, not drives get spin up or anything. There are definitely files to move from cache to array and configuration is correct. Kinda annoying have to manually move files. Nov 22 17:29:23 Megavault nginx: 2024/11/22 17:29:23 [error] 3057690#3057690: *5343975 connect() to unix:/var/tmp/binhex-plex.log.sock failed (111: Connection refused) while connecting to upstream, client: 100.73.92.125, server: , request: "GET /logterminal/binhex-plex.log/ HTTP/2.0", upstream: "http://unix:/var/tmp/binhex-plex.log.sock:/", host: "megavault.local", referrer: "https://megavault.local/Docker" Nov 22 17:29:38 Megavault emhttpd: online: Linux_File-Stor_Gadget_0123456789ABCDEF-0:0 (sdl) 512 44505088 Nov 22 17:29:38 Megavault emhttpd: read SMART /dev/sdl Nov 22 17:29:41 Megavault emhttpd: shcmd (8018186): /usr/local/sbin/mover start &> /dev/null & Nov 22 17:29:41 Megavault root: Starting Mover Nov 22 17:29:41 Megavault root: ionice -c 2 -n 0 nice -n 5 /usr/local/sbin/mover.old megavault-diagnostics-20241122-1743.zip

Please +1

me impatiently waiting 😶

so i disabled transmission container and yeah, it seems to stopped the issue. shouldnt that mean the cable is fine and its transmission being sucky?

Ive had this issue for a while now where my eth0 keeps going offline. theres no set time it does it, sometimes its after a few minutes, sometimes its after a day, sometimes its after a week. Unplugging and replugging cable kicks it back online sometimes, and sometimes doing so doesnt help. The system eventually goes into full deadlock where it isn't even possible to log into via terminal so I could dump the diagnostics... See pictures and following log (luckily i have syslog written to drive).20240109_095526.heic20240109_095432.heic20240109_095413.heic20240109_095328.heic syslog-192.168.200.8(5).log The only fool proof fix is to restart the entire system. My system unraid 6.12.6 cpu: 3900x mem: 64GB 3200 corsair vengence mb: gigabyte x570 master eth0: ConnectX-3 10GBE SFP eth2: 2.5ghz onboard Ethernet (backup line so i can access unraid in event eth0 goes down.) Jan 8 00:03:15 Megavault rc.inet1: ip link add name br0 type bridge stp_state 0 forward_delay 0 Jan 8 00:03:15 Megavault rc.inet1: ip link set br0 up Jan 8 00:03:15 Megavault rc.inet1: ip link set eth0 master br0 up Jan 8 00:03:15 Megavault kernel: br0: port 1(eth0) entered blocking state Jan 8 00:03:15 Megavault kernel: br0: port 1(eth0) entered disabled state Jan 8 00:03:15 Megavault kernel: br0: port 1(eth0) entered blocking state Jan 8 00:03:15 Megavault kernel: br0: port 1(eth0) entered forwarding state Jan 8 00:03:16 Megavault rc.inet1: polling up to 60 sec for DHCP server on interface br0 Jan 8 00:03:16 Megavault rc.inet1: timeout 60 dhcpcd -w -q -n -p -t 10 -h Megavault -4 br0 Jan 8 00:03:16 Megavault dhcpcd[1808]: br0: soliciting a DHCP lease Jan 8 00:03:16 Megavault dhcpcd[1808]: br0: offered 192.168.200.8 from 192.168.200.1 Jan 8 00:03:16 Megavault dhcpcd[1808]: br0: probing address 192.168.200.8/24 Jan 8 00:03:21 Megavault dhcpcd[1808]: br0: leased 192.168.200.8 for 7200 seconds Jan 8 00:03:21 Megavault dhcpcd[1808]: br0: adding route to 192.168.200.0/24 Jan 8 00:03:21 Megavault dhcpcd[1808]: br0: adding default route via 192.168.200.1 Jan 8 00:03:21 Megavault network: hook services: interface=br0, reason=BOUND, protocol=dhcp Jan 8 00:03:21 Megavault rc.inet1: ip link set br0 up Jan 8 00:04:53 Megavault root: Interface "br0" added with 10000 Mbit bandwidth limit. Jan 8 00:04:53 Megavault vnstatd[5329]: Monitoring (7): tunl0 (no limit) eth2 (2500 Mbit) eth1 (no limit) eth0 (10000 Mbit) br2 (2500 Mbit) br1 (no limit) br0 (10000 Mbit) Jan 8 00:05:10 Megavault avahi-daemon[9981]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.200.8. Jan 8 00:05:10 Megavault avahi-daemon[9981]: New relevant interface br0.IPv4 for mDNS. Jan 8 00:05:10 Megavault avahi-daemon[9981]: Registering new address record for 192.168.200.8 on br0.IPv4. Jan 8 00:05:32 Megavault avahi-daemon[16671]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.200.8. Jan 8 00:05:32 Megavault avahi-daemon[16671]: New relevant interface br0.IPv4 for mDNS. Jan 8 00:05:32 Megavault avahi-daemon[16671]: Registering new address record for 192.168.200.8 on br0.IPv4. Jan 8 00:05:42 Megavault root: Error response from daemon: network with name br0 already exists Jan 8 00:05:42 Megavault rc.docker: connecting pihole to network br0 Jan 8 00:05:42 Megavault rc.docker: connecting NginxProxyManager to network br0 Jan 8 00:05:42 Megavault rc.docker: connecting Nextcloud to network br0 Jan 8 00:05:42 Megavault rc.docker: connecting RustDeskServer-AiO to network br0 Jan 8 00:05:43 Megavault dnsmasq-dhcp[19788]: DHCP, sockets bound exclusively to interface virbr0 Jan 8 00:05:44 Megavault kernel: br0: port 2(vnet0) entered blocking state Jan 8 00:05:44 Megavault kernel: br0: port 2(vnet0) entered disabled state Jan 8 00:05:44 Megavault kernel: br0: port 2(vnet0) entered blocking state Jan 8 00:05:44 Megavault kernel: br0: port 2(vnet0) entered forwarding state Jan 8 00:06:19 Megavault kernel: br0: port 1(eth0) entered disabled state Jan 8 00:10:00 Megavault vnstatd[5329]: Detected bandwidth limit for "br0" changed from 10000 Mbit to 10 Mbit. Jan 8 01:48:21 Megavault dhcpcd[1808]: br0: failed to renew DHCP, rebinding Jan 8 02:03:21 Megavault dhcpcd[1808]: br0: DHCP lease expired Jan 8 02:03:21 Megavault dhcpcd[1808]: br0: deleting route to 192.168.200.0/24 Jan 8 02:03:21 Megavault dhcpcd[1808]: br0: deleting default route via 192.168.200.1 Jan 8 02:03:21 Megavault dhcpcd[1808]: br0: soliciting a DHCP lease Jan 8 02:03:26 Megavault dhcpcd[1808]: br0: probing for an IPv4LL address Jan 8 02:03:32 Megavault dhcpcd[1808]: br0: using IPv4LL address 169.254.208.156 Jan 8 02:03:32 Megavault dhcpcd[1808]: br0: adding route to 169.XXX.XXX.0/16 Jan 8 02:03:32 Megavault dhcpcd[1808]: br0: adding default route Jan 8 02:03:32 Megavault network: hook services: interface=br0, reason=IPV4LL, protocol=ipv4ll Jan 9 06:28:15 Megavault kernel: br0: port 1(eth0) entered blocking state Jan 9 06:28:15 Megavault kernel: br0: port 1(eth0) entered forwarding state Jan 9 06:28:32 Megavault dhcpcd[1808]: br0: offered 192.168.200.8 from 192.168.200.1 Jan 9 06:28:32 Megavault dhcpcd[1808]: br0: probing address 192.168.200.8/24 Jan 9 06:28:37 Megavault dhcpcd[1808]: br0: leased 192.168.200.8 for 7200 seconds Jan 9 06:28:37 Megavault dhcpcd[1808]: br0: adding route to 192.168.200.0/24 Jan 9 06:28:37 Megavault dhcpcd[1808]: br0: changing default route via 192.168.200.1 Jan 9 06:28:37 Megavault network: hook services: interface=br0, reason=BOUND, protocol=dhcp Jan 9 06:28:37 Megavault dhcpcd[1808]: br0: deleting route to 169.XXX.XXX.0/16 Jan 9 06:28:37 Megavault network: hook services: interface=br0, reason=IPV4LL, protocol=ipv4ll Jan 9 06:30:30 Megavault vnstatd[5329]: Detected bandwidth limit for "br0" changed from 10 Mbit to 10000 Mbit. megavault-diagnostics-20240109-0644.zip

i dont understand how native kubernetes support would benefit unraid market. Why dont you spin up a vm and setup kubernetes in there? Im doing that right now and it works great.

Hey guys, my docker instance is online and bound to a port. its worked for a month and since last week i havent been able connect to it at all. i even tried spinning up fresh instances in new folders, and cant connect to that either. Any ideas? fyi i can access other hosted containers fine. only found this in the logs AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.3. Set the 'ServerName' directive globally to suppress this message AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.3. Set the 'ServerName' directive globally to suppress this message [Wed Nov 11 15:59:47.193870 2020] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.38 (Debian) PHP/7.4.12 configured -- resuming normal operations [Wed Nov 11 15:59:47.193891 2020] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND'

im using smb and gave myself read/write access to unssigned drives. On windows 10, i can try delete a file from said mounted drives, it will start and finish the deletion menu. but the target that i wanted to delete wasnt deleted. also if i were to map the drive as a network, i dont get the deletion option at all. Readonly is off. Looking into security tab in properties of file, the assigned user with read and write access isnt listed. This leads me to think the smb function in this plugin isnt working.