Xceed

Members
  • Posts

    9
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Xceed's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Thank you however i dont believe this to be linked to a specific version of the sonarr app from the CA apps store as i have now reproduced this issue with the hotio and linuxserver versions of sonarr from the CA app store.
  2. Ok everyone i've been trying to fix this for a day now, so i had the linuxserver:sonarr docker installed set up since early last year no issues. now 4 days ago i had installed a new 8tb drive after the drive install sonarr was still working fine until yesterday i restarted the server and i noticed all dockers returned to their working state except sonarr it's status showed "stopped" on the docker tab, so i tried to start the docker myself and i got the following error "Execution error - server error" so i then went into the docker config page to check for any obvious errors and when i "saved" the config and the docker attempted to start again i got this line "/usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint sonarr (0b5714eaaf96005aa8c3f0704895841bdbc08a61e91ab561654b01865dedad3a): Error starting userland proxy: listen tcp 0.0.0.0:8989: bind: address already in use." now i tried to navigate to mylocalip:8989 and got this so now i knew something was using the port.. but i thought ill just "stop all containers" and see what happens, now once i stopped all dockers i checked to make sure infact the error message i got when going to mylocalip:8989 is now gone. so i thought ok great! i tried to start ONLY the sonarr service and it worked. so i stopped it again and tried "start all" and again it started with no issues. so now this issues seems to start during start up. now ive looked through log files and cant find anything that sticks out to me. and have no idea how to fix this, anyhelp would be appreciated. diagnostics-20200716-0915.zip
  3. hello everyone I'm looking at building a 3900x server to upgrade my old dual xeon, I've seen writing's about iommu group issues with x570 boards. I was wondering if anyone has any suggestions for motherboards for this build? Minimum 8hdd and 2 ssd cache drives posibly gfx card pass-through to vm.
  4. but why only 1 core maxed out?
  5. Here it is. tower-diagnostics-20190714-1937.zip
  6. ok is there something specific i should be looking for or should i upload it here?
  7. my unraid diagnostic files?
  8. Hello all i have a strange issue of unraid maxing out 1 cpu core i can't figure out why. any ideas?
  9. hello i am having a issue accessing the web ui from LAN using default settings/port this is the logs: 2019-03-05 15:53:19.151069 [info] VPN_ENABLED defined as 'yes' 2019-03-05 15:53:19.194490 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/gw3.ewr1.slickvpn.com.ovpn dos2unix: converting file /config/openvpn/gw3.ewr1.slickvpn.com.ovpn to Unix format... 2019-03-05 15:53:19.226323 [info] VPN remote line defined as 'gw3.ewr1.slickvpn.com 443 udp' 2019-03-05 15:53:19.253372 [info] VPN_REMOTE defined as 'gw3.ewr1.slickvpn.com' 2019-03-05 15:53:19.281987 [info] VPN_PORT defined as '443' 2019-03-05 15:53:19.321838 [info] VPN_PROTOCOL defined as 'udp' 2019-03-05 15:53:19.349631 [info] VPN_DEVICE_TYPE defined as 'tun0' 2019-03-05 15:53:19.376320 [info] LAN_NETWORK defined as '192.168.0.0/24' 2019-03-05 15:53:19.402173 [info] NAME_SERVERS defined as '8.8.8.8,8.8.4.4' 2019-03-05 15:53:19.428185 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS) 2019-03-05 15:53:19.455175 [info] Adding 8.8.8.8 to resolv.conf 2019-03-05 15:53:19.483401 [info] Adding 8.8.4.4 to resolv.conf 2019-03-05 15:53:19.507962 [info] Starting OpenVPN... Tue Mar 5 15:53:19 2019 WARNING: file 'credentials.conf' is group or others accessible Tue Mar 5 15:53:19 2019 OpenVPN 2.4.4 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 5 2018 Tue Mar 5 15:53:19 2019 library versions: OpenSSL 1.1.0g 2 Nov 2017, LZO 2.08 Tue Mar 5 15:53:19 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]50.116.54.120:443 Tue Mar 5 15:53:19 2019 UDP link local: (not bound) Tue Mar 5 15:53:19 2019 UDP link remote: [AF_INET]50.116.54.120:443 Tue Mar 5 15:53:19 2019 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this Tue Mar 5 15:53:20 2019 [VPN] Peer Connection Initiated with [AF_INET]50.116.54.120:443 Tue Mar 5 15:53:21 2019 TUN/TAP device tun0 opened Tue Mar 5 15:53:21 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0 Tue Mar 5 15:53:21 2019 /sbin/ip link set dev tun0 up mtu 1500 Tue Mar 5 15:53:21 2019 /sbin/ip addr add dev tun0 local 10.10.8.10 peer 10.10.8.9 Tue Mar 5 15:53:21 2019 Initialization Sequence Completed 2019-03-05 15:53:24.542961 [info] WebUI port defined as 8080 2019-03-05 15:53:24.570092 [info] LAN Network defined as 192.168.0.0/24 2019-03-05 15:53:24.597878 [info] Default gateway defined as 10.10.8.9 Error: Nexthop has invalid gateway. 2019-03-05 15:53:24.624012 [info] ip route defined as follows... -------------------- default via 10.10.8.9 dev tun0 10.10.8.1 via 10.10.8.9 dev tun0 10.10.8.9 dev tun0 proto kernel scope link src 10.10.8.10 50.116.54.120 via 192.168.0.254 dev eth0 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1 -------------------- iptable_mangle 16384 1 ip_tables 24576 3 iptable_filter,iptable_nat,iptable_mangle 2019-03-05 15:53:24.653135 [info] iptable_mangle support detected, adding fwmark for tables 2019-03-05 15:53:24.706753 [info] Docker network defined as 192.168.0.0/24 2019-03-05 15:53:24.764238 [info] Incoming connections port defined as 8999 2019-03-05 15:53:24.793615 [info] iptables defined as follows... -------------------- -P INPUT DROP -P FORWARD ACCEPT -P OUTPUT DROP -A INPUT -i tun0 -j ACCEPT -A INPUT -s 192.168.0.0/24 -d 192.168.0.0/24 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --sport 443 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 8080 -j ACCEPT -A INPUT -s 192.168.0.0/24 -i eth0 -p tcp -m tcp --dport 8999 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i lo -j ACCEPT -A OUTPUT -o tun0 -j ACCEPT -A OUTPUT -s 192.168.0.0/24 -d 192.168.0.0/24 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --dport 443 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 8080 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT -A OUTPUT -d 192.168.0.0/24 -o eth0 -p tcp -m tcp --sport 8999 -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT -------------------- Adding 100 group groupadd: GID '100' already exists Adding 99 user useradd: UID 99 is not unique 2019-03-05 15:53:24.835057 [info] UMASK defined as '002' 2019-03-05 15:53:24.869162 [info] Starting qBittorrent daemon... Logging to /config/qBittorrent/data/logs/qbittorrent-daemon.log. 2019-03-05 15:53:25.899837 [info] qBittorrent PID: 189 2019-03-05 15:53:25.903727 [info] Started qBittorrent daemon successfully... any ideas as to what might be going on?