JustinChase 5 Posted September 12, 2014 Share Posted September 12, 2014 I just upgraded to beta9, and was having some issues, then I remembered that when I upgraded to beta8, unRAID reset my DNS settings. I just checked, and unRAID did it again. Please let me know what I can provide to help fix this really annoying bug. Thanks. syslog.zip Quote Link to post
eroz 0 Posted September 12, 2014 Share Posted September 12, 2014 I just upgraded to beta9, and was having some issues, then I remembered that when I upgraded to beta8, unRAID reset my DNS settings. I just checked, and unRAID did it again. Please let me know what I can provide to help fix this really annoying bug. Thanks. Justin, change the setting of Obtain IP Address Automatically to No. Then assign your server an IP address that you want that is not in use. I think since it is set to automatically obtain an ip address, everytime you reboot/upgrade you will have a chance of getting a new IP address. Quote Link to post
JustinChase 5 Posted September 12, 2014 Author Share Posted September 12, 2014 Justin, change the setting of Obtain IP Address Automatically to No. Then assign your server an IP address that you want that is not in use. I think since it is set to automatically obtain an ip address, everytime you reboot/upgrade you will have a chance of getting a new IP address. It's not the IP that gets changed, my router assigns it based on the server MAC address, that's fine. It's only the DNS addresses that get removed and replaced with one that I don't have on my system. I suspect this might actually be happening to others, but since 192.168.1.254 is a very common gateway/DNS address for many/most routers/modems, no one would notice. Quote Link to post
MyKroFt 7 Posted September 12, 2014 Share Posted September 12, 2014 If set to dhcp, the dns ips are coming from your router. Check your dhcp settings there. Quote Link to post
limetech 2284 Posted September 12, 2014 Share Posted September 12, 2014 Are you saying that even though "Obtain DNS Server Address Automatically" is set to NO, that it still changes that field? Quote Link to post
JustinChase 5 Posted September 12, 2014 Author Share Posted September 12, 2014 If set to dhcp, the dns ips are coming from your router. Check your dhcp settings there. see screenshot of my router settings, it's not coming from there. Are you saying that even though "Obtain DNS Server Address Automatically" is set to NO, that it still changes that field? Yes, that is what is happening. The screenshot in the first post is what I get after every install. I change the DNS IP addresses to match the screenshot of my router (3 different IP addresses), and everything works fine until I upgrade, then it goes back to having only one DNS address, like the first screenshot. Quote Link to post
JustinChase 5 Posted September 17, 2014 Author Share Posted September 17, 2014 So, last night, and most of today all file transfers have been really slow, and the GUI has been slow to respond. I rebooted this morning, thinking something was just 'gummed up', but it's not really gotten any better. I'm moving a lot of files around (not really a lot, it's just taking a long time). So, it dawned on me that it's acting like the DNS is jacked up, so I just checked, and sure enough, it's back to having only one IP in the list 192.168.1.254, which I don't have on my network. I don't know why this keeps happening, but I really, REALLY need it to stop reverting my DNS settings. I'm attaching a new syslog, but I'm not sure if the reversion happened before or after the reboot, so I'm not sure if there is any useful information in the syslog. Regardless, I'll do whatever you need me to do in order to find and fix this very annoying bug. syslog.zip Quote Link to post
JustinChase 5 Posted September 17, 2014 Author Share Posted September 17, 2014 I just tried updating the DNS IP's again, and when I hit apply, it tries to update, but instead of coming back with the page simply updated, it comes back all greyed out, with some sort of message in the footer, which is not possible to read, but I was able to mouse over it and copy the message. I'm not sure I got it all, but the message is below. If I navigate to another tab (the Explorer tab in this case), then back to the settings tab, then go back into network settings, it appears to have saved the IP addresses, but I suspect that it might not actually be saving my values to wherever they need to be saved, and that's why this isn't working. I'm going to attach another syslog after these attempts to save the DNS settings, which might tell us why this seems to not be working. The connection was reset The connection to the server was reset while the page was loading. The site could be temporarily unavailable or too busy. Try again in a few moments. If you are unable to load any pages, check your computer's network connection. If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web. syslog1.zip syslog2.zip Quote Link to post
limetech 2284 Posted September 20, 2014 Share Posted September 20, 2014 I can't duplicate this behavior. Next time it happens, please post contents of /etc/resolve.conf /boot/config/network.cfg Also I notice you are installing power-down plugin - might try removing that and see if issue related to that. Quote Link to post
JustinChase 5 Posted September 21, 2014 Author Share Posted September 21, 2014 Thanks for getting back to me about this Tom. /boot/config/network.cfg... # Generated settings: USE_DHCP="yes" IPADDR="192.168.20.150" NETMASK="255.255.255.0" GATEWAY="192.168.20.1" DHCP_KEEPRESOLV="yes" DNS_SERVER1="24.178.162.3" DNS_SERVER2="24.159.64.23" DNS_SERVER3="66.189.0.100" BONDING="yes" BONDING_MODE="0" BRIDGING="yes" BRNAME="br0" BRSTP="no" It all looks right, except the DHCP_KEEPRESOLV=YES it's the only line in there that doesn't match a line in the settings page, so I'm thinking it might be the setting for Obtain DNS Server Address Automatically, since that's the only other line in the settings that doesn't have a match in the cfg If so, this might be the error. I have the setting in the GUI set for No If you think this might be the problem, let me know if I should just change it to No in the cfg, then I'll reboot. I removed the powerdown and UPS plugin. Hopefully beta 10 has this built-in Quote Link to post
JustinChase 5 Posted September 21, 2014 Author Share Posted September 21, 2014 I started a parity check last night, and after running about 8 hours it was only 4% done. I'm not sure why, as it normally takes less than a day for the full thing. So, I stopped it, then rebooted the server. I started a new parity sync, and it seems like it's running at the 'right' speed now, but then remembered to check the DNS. It's reverted to 192.168.1.254 again. /etc/resolve.conf only shows "nameserver 192.168.1.254" whereas it showed all 3 correct IP's last night. I just checked /boot/config/network.cfg, and it has not changed, it still shows # Generated settings: USE_DHCP="yes" IPADDR="192.168.20.150" NETMASK="255.255.255.0" GATEWAY="192.168.20.1" DHCP_KEEPRESOLV="yes" DNS_SERVER1="24.178.162.3" DNS_SERVER2="24.159.64.23" DNS_SERVER3="66.189.0.100" BONDING="yes" BONDING_MODE="0" BRIDGING="yes" BRNAME="br0" BRSTP="no" So, how can I help figure out what's going on here? syslog.zip Quote Link to post
JustinChase 5 Posted September 21, 2014 Author Share Posted September 21, 2014 I tried changing Obtain DNS Server Address automatically to no, and when I hit apply, I got the same 'error' message I posted above, but it did seem to save, and now the DNS has changed to 192.168.20.1 on that screen, which is my router IP, and it should probably work. I checked the /etc/resolv.conf file, and it now says this... # Generated by dhcpcd from br0 # /etc/resolv.conf.head can replace this line nameserver 192.168.20.1 # /etc/resolv.conf.tail can replace this line I'm going to leave it and see if things work okay, but wanted to post the findings for completeness sake. Quote Link to post
limetech 2284 Posted September 21, 2014 Share Posted September 21, 2014 /etc/resolve.conf only shows "nameserver 192.168.1.254" whereas it showed all 3 correct IP's last night. Is that the exact contents of the file? I need to see the exact contents because what else might be in there is a clue to why it's like that. Quote Link to post
JustinChase 5 Posted September 21, 2014 Author Share Posted September 21, 2014 yes, that was the exact content, nothing more. After it changed, it had 3 more lines (like in my more recent post), all commented out, but before that, it only showed exactly that. Quote Link to post
limetech 2284 Posted September 22, 2014 Share Posted September 22, 2014 Are you sure it didn't look like this: # Generated entries: nameserver 192.168.1.254 Quote Link to post
JustinChase 5 Posted September 22, 2014 Author Share Posted September 22, 2014 I can't absolutely say for 100% certain, since it's been changed, and I didn't keep the screenshot. But, I'm 95% sure, since I thought it was odd that there was just the one line. Quote Link to post
limetech 2284 Posted September 24, 2014 Share Posted September 24, 2014 I found where /etc/resolv.conf can be written: avahi Does this file exist on your server? /etc/resolv.conf.avahi If not now, next time you see the DNS settings change, please check to see if that file exists then. Quote Link to post
JustinChase 5 Posted September 24, 2014 Author Share Posted September 24, 2014 I found where /etc/resolv.conf can be written: avahi Does this file exist on your server? /etc/resolv.conf.avahi If not now, next time you see the DNS settings change, please check to see if that file exists then. Sounds like progress! I don't see that file right now, but once I get my server fixed up, I'll change back to not get DNS automatically, and reboot and see if that comes back. I'll let you know once I test. thanks for taking the time to look at this unusual/uncommon bug!! Quote Link to post
jonp 559 Posted October 2, 2014 Share Posted October 2, 2014 Hey Justin, just thought I'd check to see if this issue has been ongoing for you since your last post or if you found a resolution. Let us know. Thanks! Quote Link to post
JustinChase 5 Posted October 2, 2014 Author Share Posted October 2, 2014 I changed it to get DNS automatically when I was testing and that worked (it didn't last time I tried it), so I've just left it alone since then. i finally got all my red-ball drive problems resolved, and got all the data moved around, and was going to test it, but then I got a new red-ball on disk5, so I have a new drive on order, and should be able to install it tomorrow. Once that's done, I'll try to test again (assuming nothing else goes wrong) thanks for following up. Quote Link to post
jonp 559 Posted October 3, 2014 Share Posted October 3, 2014 I changed it to get DNS automatically when I was testing and that worked (it didn't last time I tried it), so I've just left it alone since then. i finally got all my red-ball drive problems resolved, and got all the data moved around, and was going to test it, but then I got a new red-ball on disk5, so I have a new drive on order, and should be able to install it tomorrow. Once that's done, I'll try to test again (assuming nothing else goes wrong) thanks for following up. No problem. We'll leave this ticket open for now in case you have the issue reoccur or anyone else has it. Sorry to hear about your red balls (hmm, we should maybe find a better way to describe that ;-). Hopefully no more for a while... Quote Link to post
JustinChase 5 Posted October 8, 2014 Author Share Posted October 8, 2014 So, I've had lots of problems with failing or failed drives over the last few weeks, but today is the first day that everything is 'back to normal'. I installed a new cache drive (an old array drive), and am in the process of setting up my dockers again, and will try to install a new windows VM later today. But, as I'm doing this, the GUI is responding VERY slowly. I thought it might have to do with the cache drive being formatted, but then I tried to setup my SABnzbd docker, and it's telling me the server address is invalid. After checking it a couple of times, to make absolutely sure it's correct, I remembered this issue, and looked at the settings. It's still set to obtain the DNS automatically, but now it's grabbed the wrong DNS server. It's set to 192.168.1.254. I have no idea why this is, or when it happened, but the screenshot of the settings page and the syslog are attached. I'm available most of the day today to help troubleshoot/diagnose this, so if you need me to do anything, just let me know. syslog.zip Quote Link to post
limetech 2284 Posted October 10, 2014 Share Posted October 10, 2014 But now in this state, Does this file exist on your server? /etc/resolv.conf.avahi Quote Link to post
JustinChase 5 Posted October 10, 2014 Author Share Posted October 10, 2014 Nope. I have /etc/resolv.conf but not /etc/resolv.conf.avahi root@media:/etc# ls -l total 496 -rw-r--r-- 1 root root 4593 Feb 26 2013 DIR_COLORS drwxr-xr-x 2 root root 40 Feb 5 2001 X11/ drwxr-xr-x 3 root root 80 Oct 9 09:34 acpi/ drwxr-xr-x 2 root root 260 Oct 9 09:34 apcupsd/ -rw-r----- 1 root daemon 144 Jul 28 2010 at.deny drwxr-xr-x 3 root root 120 Sep 29 02:51 avahi/ drwxr-xr-x 2 root root 60 Sep 8 00:34 bash_completion.d/ drwxr-xr-x 3 root root 60 Sep 30 2013 ca-certificates/ -rw-r--r-- 1 root root 6990 Sep 30 2013 ca-certificates.conf -rw-r--r-- 1 root root 902 Mar 8 2011 cgconfig.conf -rw-r--r-- 1 root root 940 Feb 23 2013 cgred.conf -rw-r--r-- 1 root root 1705 Mar 8 2011 cgrules.conf -rw-r--r-- 1 root root 131 Mar 8 2011 cgsnapshot_blacklist.conf drwxr-xr-x 2 root root 60 Oct 9 09:39 cron.d/ drwxr-xr-x 2 root root 80 Sep 29 02:51 cron.daily/ drwxr-xr-x 2 root root 40 Sep 7 2012 cron.hourly/ drwxr-xr-x 2 root root 40 Sep 7 2012 cron.monthly/ drwxr-xr-x 2 root root 40 Sep 7 2012 cron.weekly/ -rw-r--r-- 1 root root 1614 Aug 2 2013 csh.login drwxr-xr-x 4 root root 120 Sep 24 13:27 dbus-1/ drwxr-xr-x 2 root root 240 Sep 29 02:52 default/ -rw-r--r-- 1 root root 1257 Sep 29 02:52 dhcpcd.conf -rw-r--r-- 1 root root 700 Oct 9 09:38 exports -rw-r--r-- 1 root root 154 Sep 29 02:52 exports- -rw-r--r-- 1 root root 22063 Sep 21 2008 fb.modes drwxr-xr-x 2 root root 60 May 21 2013 file/ -rw-r--r-- 1 root root 106 Sep 29 02:52 fstab -rw-r--r-- 1 root root 2006 Dec 13 2008 genpowerd.conf -rw-r--r-- 1 root root 4655 Oct 2 2013 gettydefs -rw-r--r-- 1 root root 671 Sep 29 02:52 group -rw-r----- 1 root shadow 0 Apr 7 2000 gshadow -rw-r--r-- 1 root root 122 Sep 29 02:52 hardwareclock -rw-r--r-- 1 root root 27 Jul 7 1994 host.conf -rw-r--r-- 1 root root 58 Oct 9 09:34 hosts -rw-r--r-- 1 root root 293 Nov 25 1993 hosts.allow -rw-r--r-- 1 root root 296 Nov 25 1993 hosts.deny -rw-r--r-- 1 root root 320 Feb 8 1998 hosts.equiv -rw-r--r-- 1 root root 4676 Sep 29 02:52 inetd.conf -rwxr-xr-x 1 root root 463 Sep 29 02:52 initscript* -rw-r--r-- 1 root root 2344 Oct 9 09:34 inittab -rw-r--r-- 1 root root 2354 Oct 28 2013 inittab.bak -rw-r--r-- 1 root root 690 May 30 2002 inputrc drwxr-xr-x 2 root root 180 Sep 29 02:51 iproute2/ -rw-r--r-- 1 root root 24 Sep 24 2000 issue -rw-r--r-- 1 root root 0 Sep 17 1999 issue.net -rw-r--r-- 1 root root 37504 Oct 9 09:34 ld.so.cache -rw-r--r-- 1 root root 69 Oct 2 2013 ld.so.conf drwxr-xr-x 2 root root 80 Sep 29 02:51 libnl/ drwxr-xr-x 4 root root 180 Sep 29 02:52 libvirt/ -rw-r--r-- 1 root root 3519 Oct 9 09:34 localtime lrwxrwxrwx 1 root root 36 Oct 9 09:34 localtime-copied-from -> /usr/share/zoneinfo/America/New_York -rw-r--r-- 1 root root 2060 Feb 14 2014 login.access -rw-r--r-- 1 root root 10877 Sep 29 02:52 login.defs -rw-r--r-- 1 root root 1546 Sep 29 02:52 logrotate.conf drwxr-xr-x 2 root root 200 Oct 9 09:34 logrotate.d/ drwxr-xr-x 3 root root 80 Sep 29 02:51 lvm/ drwxr-xr-x 2 root root 240 Oct 10 2013 mc/ -r--r--r-- 1 root root 11298 Aug 2 2013 mediaprm lrwxrwxrwx 1 root root 4 Sep 29 02:51 misc -> file/ -rw-r--r-- 1 root root 956 Aug 16 2013 mke2fs.conf drwxr-xr-x 2 root root 100 Sep 29 02:52 modprobe.d/ -rw-r--r-- 1 root root 21 Oct 9 09:34 motd -rw-r--r-- 1 root root 1012 Oct 9 09:38 mtab -rw-r--r-- 1 root root 1914 Aug 2 2013 mtools.conf -rw-r--r-- 1 root root 1911 Jul 4 2012 nail.rc -rw-r--r-- 1 root root 8897 Mar 22 2013 nanorc drwxr-xr-x 2 root root 120 Sep 29 02:52 netatalk/ -rw-r--r-- 1 root root 233 Apr 7 1998 networks -rw-r--r-- 1 root root 3388 May 21 2013 nfsmount.conf -rw-r--r-- 1 root root 24 Feb 8 1998 nntpserver -rw-r--r-- 1 root root 2387 Sep 15 2013 nscd.conf -rw-r--r-- 1 root root 1141 Sep 29 02:52 nsswitch.conf drwxr-xr-x 2 root root 100 Oct 10 09:34 ntp/ -rw-r--r-- 1 root root 1983 Oct 9 09:34 ntp.conf -rw-r--r-- 1 root root 1867 Sep 29 02:52 ntp.conf- drwxr-xr-x 2 root root 60 Sep 29 02:51 openldap/ -rw-r--r-- 1 root root 327 Oct 11 2013 os-release -rw-r--r-- 1 root root 930 Oct 9 09:34 passwd drwxr-xr-x 3 root root 80 Sep 29 02:52 php/ drwxr-xr-x 2 root root 80 Sep 29 02:51 php-fpm/ drwxr-xr-x 3 root root 80 May 18 2013 pkcs11/ -rw-r--r-- 1 root root 395 Aug 18 2003 printcap -rw-r--r-- 1 root root 2197 Sep 29 02:52 profile drwxr-xr-x 2 root root 240 Sep 29 02:52 profile.d/ -rw-r--r-- 1 root root 5748 Feb 10 2002 protocols drwxr-xr-x 2 root root 60 Aug 22 23:26 qemu/ -rw------- 1 root root 512 Oct 9 09:34 random-seed drwxr-xr-x 3 root root 880 Oct 9 09:34 rc.d/ -rw-r--r-- 1 root root 25 Oct 9 09:34 resolv.conf lrwxrwxrwx 1 root root 16 Sep 29 02:51 rmt -> /usr/libexec/rmt* -rw-r--r-- 1 root root 1615 Oct 14 2008 rpc -rw-r--r-- 1 root root 3362 Sep 29 02:52 rsyslog.conf drwxr-xr-x 3 root root 140 Oct 9 09:34 samba/ -rw-r--r-- 1 root root 410 Sep 29 02:52 securetty drwxr-xr-x 2 root root 40 Sep 27 2013 sensors.d/ -rw-r--r-- 1 root root 10191 Sep 27 2013 sensors3.conf -rw-r--r-- 1 root root 2948 Aug 7 2013 serial.conf -rw-r--r-- 1 root root 83348 Feb 5 2010 services -rw-r----- 1 root root 816 Oct 9 09:34 shadow -rw-r--r-- 1 root root 10 Sep 29 02:51 shells drwxr-xr-x 2 root root 40 Jul 24 2012 skel/ -rw-r--r-- 1 root root 15 Oct 11 2013 slackware-version -rw-r--r-- 1 root root 6739 Feb 27 2014 smartd.conf -rwxr-xr-x 1 root root 5753 Feb 27 2014 smartd_warning.sh* drwxr-xr-x 2 root root 300 Oct 9 09:34 ssh/ drwxr-xr-x 5 root root 120 Sep 29 02:51 ssl/ -r--r----- 1 root root 2849 May 16 2013 sudoers drwxr-x--- 2 root root 40 May 16 2013 sudoers.d/ -rw-r--r-- 1 root root 163 Sep 29 02:52 sysctl.conf drwxr-xr-x 2 root root 60 Sep 29 02:51 sysctl.d/ -rw-r--r-- 1 root root 8969 Feb 15 2004 termcap drwxr-xr-x 3 root root 80 Sep 26 2013 udev/ -rw-r--r-- 1 root root 22 Sep 29 02:52 unraid-version -rw-r--r-- 1 root root 513 Sep 29 02:52 vsftpd.conf -rw-r--r-- 1 root root 4499 May 19 2013 wgetrc drwxr-xr-x 4 root root 200 Sep 29 02:52 xen/ also, see screenshot of resolv.conf This is what I see when the DNS is set for 192.168.1.254 after a reboot. If I change the IP addresses, then hit apply, I get the third screenshot, and the following message... The connection was reset The connection to the server was reset while the page was loading. The site could be temporarily unavailable or too busy. Try again in a few moments. If you are unable to load any pages, check your computer's network connection. If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web. Even though it looks like it 'failed' to save, /etc/resolv.conf then changes to the last screenshot. Please let me know what more testing you need me to do. I'd very much like to help you squash this annoying bug. Quote Link to post
limetech 2284 Posted October 10, 2014 Share Posted October 10, 2014 Please try this. Edit your /boot/config/share.cfg file and change shareAvahiEnabled="yes" to shareAvahiEnabled="no" Then reboot server or Stop/Start array, and try and make it happen again (hopefully it won't). If you are using OSX the server will no longer show up under Finder but you can still use 'connect to server' and specify the IP address. Also, 'servername.local' will not work to bring up webGui but again, you can specify the IP address. This issue almost certainly is being caused avahi finding another mDNS server on your network announcing that DNS server. Making this change will confirm and then we can figure out what config changes have to be made on unRaid side. Quote Link to post
35 posts in this topic Last Reply
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.