February 4, 201214 yr Im sick to the back teeth with all the issues i am having, for something that was working fine and then everything just completley goes to pot, it seems very much like something is stopping anything on unraid accessing WAN, even SABnzb will not grab nzbs from correctly setup newzbin/nzbmatrix accounts, anything that involves an outside connection is not working, i dont feel i am going to get an answer for it...can i start from scratch with the usb stick ? i want to format it, and put a fresh install of beta14 on and then put back what i had to start with, all i want is shares, SAB and SB...i dont need more than that..what will happen to the drives if i do this ?? i am not stupid but this is not what i envisaged with UNraid
February 4, 201214 yr Sounds more like a network issue rather than an unraid one. Does unraid get network info from a dhcp server? What is the output of ifconfig and "route -n" commands from the console? Sent from my SGH-I727R using Tapatalk
February 4, 201214 yr Author I had it set to static ip, it has been fine but i have since tried with DHCP... ifconfig... eth0 Link encap:Ethernet HWaddr 44:1e:a1:3b:7b:a3 inet addr:192.168.0.222 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10501 errors:0 dropped:11 overruns:0 frame:0 TX packets:9315 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2231040 (2.1 MiB) TX bytes:4178500 (3.9 MiB) Interrupt:18 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:430 errors:0 dropped:0 overruns:0 frame:0 TX packets:430 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:58653 (57.2 KiB) TX bytes:58653 (57.2 KiB) route -n.... root@warptower:/# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.0.1 0.0.0.0 UG 1 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
February 4, 201214 yr Looks ok. Leave in dhcp. Can you ping 192.168.0.1 ok? Try to 'ping google.com' If that doesn't work check the contents of /etc/resolve.conf Sent from my SGH-I727R using Tapatalk
February 4, 201214 yr Author ping result of google.com from cmd prompt in windows on same network.. C:\Users\kevin>ping google.com Pinging google.com [209.85.147.103] with 32 bytes of data: Reply from 209.85.147.103: bytes=32 time=28ms TTL=51 Reply from 209.85.147.103: bytes=32 time=23ms TTL=50 Reply from 209.85.147.103: bytes=32 time=44ms TTL=51 Reply from 209.85.147.103: bytes=32 time=26ms TTL=51 Ping statistics for 209.85.147.103: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 23ms, Maximum = 44ms, Average = 30ms ping result for google.com from telnet session from tower... PING google.com (209.85.147.103) 56(84) bytes of data. 64 bytes from bru01m01-in-f103.1e100.net (209.85.147.103): icmp_req=1 ttl=51 time=26.7 ms 64 bytes from bru01m01-in-f103.1e100.net (209.85.147.103): icmp_req=2 ttl=51 time=67.0 ms 64 bytes from bru01m01-in-f103.1e100.net (209.85.147.103): icmp_req=3 ttl=51 time=46.6 ms 64 bytes from bru01m01-in-f103.1e100.net (209.85.147.103): icmp_req=4 ttl=51 time=44.0 ms 64 bytes from bru01m01-in-f103.1e100.net (209.85.147.103): icmp_req=5 ttl=51 time=50.7 ms 64 bytes from bru01m01-in-f103.1e100.net (209.85.147.103): icmp_req=6 ttl=50 time=21.8 ms 64 bytes from bru01m01-in-f103.1e100.net (209.85.147.103): icmp_req=7 ttl=51 time=37.8 ms 64 bytes from bru01m01-in-f103.1e100.net (209.85.147.103): icmp_req=8 ttl=51 time=54.7 ms 64 bytes from bru01m01-in-f103.1e100.net (209.85.147.103): icmp_req=9 ttl=51 time=39.2 ms 64 bytes from bru01m01-in-f103.1e100.net (209.85.147.103): icmp_req=10 ttl=51 time=47.3 ms 64 bytes from bru01m01-in-f103.1e100.net (209.85.147.103): icmp_req=11 ttl=51 time=27.9 ms just keeps scrolling onwards, dont know how to stop it but i would say thats pinging ok ?? ping results of 192.168.0.1 from telnet session from tower... warptower login: root Linux 3.1.1-unRAID. root@warptower:~# ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. 64 bytes from 192.168.0.1: icmp_req=1 ttl=64 time=0.658 ms 64 bytes from 192.168.0.1: icmp_req=2 ttl=64 time=0.569 ms 64 bytes from 192.168.0.1: icmp_req=3 ttl=64 time=0.595 ms 64 bytes from 192.168.0.1: icmp_req=4 ttl=64 time=0.604 ms 64 bytes from 192.168.0.1: icmp_req=5 ttl=64 time=0.601 ms 64 bytes from 192.168.0.1: icmp_req=6 ttl=64 time=0.611 ms 64 bytes from 192.168.0.1: icmp_req=7 ttl=64 time=0.607 ms 64 bytes from 192.168.0.1: icmp_req=8 ttl=64 time=0.594 ms 64 bytes from 192.168.0.1: icmp_req=9 ttl=64 time=0.586 ms 64 bytes from 192.168.0.1: icmp_req=10 ttl=64 time=0.563 ms 64 bytes from 192.168.0.1: icmp_req=11 ttl=64 time=0.539 ms 64 bytes from 192.168.0.1: icmp_req=12 ttl=64 time=0.556 ms 64 bytes from 192.168.0.1: icmp_req=13 ttl=64 time=0.566 ms 64 bytes from 192.168.0.1: icmp_req=14 ttl=64 time=0.577 ms 64 bytes from 192.168.0.1: icmp_req=15 ttl=64 time=0.504 ms and same again from cmd prompt on windows machine on same network... C:\Users\kevin>ping 192.168.0.1 Pinging 192.168.0.1 with 32 bytes of data: Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.0.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
February 4, 201214 yr Well, it appears that your UnRAID is accessing the WAN just fine now. Have you tried the SABnzbd again? May need to re-install SABnzbd (or try a reboot if you haven't yet). btw: hit CTRL-C to stop a ping test in linux.
February 5, 201214 yr btw: hit CTRL-C to stop a ping test in linux. or type ping -c 5 google.com to have it stop after 5 pings.
February 5, 201214 yr Author thanks guys, thats contstuctive advice for me, i also did a 'man ping' to find that out. I am still unwise as to what caused this sudden strange behaviour, i also noticed that i was getting a hang on the prompt appearing when i opened a telnet session (8 seconds) which has now gone back to normal, i had a static ip set but that was all fine and dandy..i am really wondering if it was the two lines of code i added to the go script, i was reading a thread about shares being slow to show in windows and added the two lines, cant remember exactly what they were but they went something like echo_res tower// >> ip address, since i removed them or went to static ip it seems to be working again, it was definatley a UNraid/WAN issue as the pre clear couldnt access my gmail either. I will set a static ip again and see if that was the issue.....would of running pre clear at the the time have any impact ??. I will install SABnzb again, what is the best way to do this, there seems to be different methods, i have installed SB using the .conf into packages and next time i tried it by pasting code into a .plg file and creating a plugins folder in /config and i have a nice button on the unraid page, i like this but the SAB one i did is missing the button...are the .plg methods outdated ??
February 5, 201214 yr i like this but the SAB one i did is missing the button...are the .plg methods outdated ?? Just the opposite. The .plg files are new as of the later 5.0beta unRAID series and can have a more impressive web-interface. they are frequently based on the older equivalent .conf files used by unMENU. .plg files have nothing to do with unMENU. In some cases, the .plg files are not as mature as their .conf file equivalents. Joe L.
Archived
This topic is now archived and is closed to further replies.