|
Bugzilla – Full Text Bug Listing |
| Summary: | resolv.conf is empty therefore no dns | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | Forgotten User bSWU20Bh6O <forgotten_bSWU20Bh6O> |
| Component: | Network | Assignee: | Marius Tomaschewski <mt> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | david.maillists, forgotten_Xh41Ao4q6j, forgotten_zhFaldehF_, gp, greenpagan13, kailed, kairo, lnozot, nedux, willkeinspam |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
/var/log/messages
/var/log/NetworkManager |
||
|
Description
Forgotten User bSWU20Bh6O
2009-10-12 16:11:40 UTC
Created attachment 322099 [details]
/var/log/messages
Created attachment 322100 [details]
/var/log/NetworkManager
Confirmed. It's a post M8 bug for me. *** Bug 546546 has been marked as a duplicate of this bug. *** If resolv.conf was not touched since M8, then it still has wrong md5sum, and netconfig has no reason to update it. While NetworkManager is now using netconfig: From NetworkManager log: Oct 12 08:34:59 bensteinm08 NetworkManager: <debug> [1255358099.021905] run_netconfig(): Spawning '/sbin/netconfig modify --service NetworkManager' the update still fails From messages: Oct 12 08:34:59 bensteinm08 dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... After copy of resolv.conf.netconfig to resolv.conf: From messages: Oct 12 08:37:27 bensteinm08 sudo: bensteinm : TTY=pts/2 ; PWD=/home/bensteinm ; USER=root ; COMMAND=/bin/cp /etc/resolv.conf.netconfig /etc/resolv.conf which brought copy with correct md5sum, netconfig will update resolv.conf. The same effect would be achieved by removing resolv.conf. Have any of you hand-edited resolv.conf? *** Bug 546700 has been marked as a duplicate of this bug. *** I never hand-edited resolv.conf Coming over from #546700, once I discovered the empty DNS was the reason for the internet access suddenly not working, I added the relevant lines from my regular computer. It works now through two reboots. I can confirm this after updating to RC1 This starts happening with RC1 (M8 was still fine). M8 has NetworkManager-0.7.1_git20090811-2.2 while RC1 comes with NetworkManager-0.7.1_git20090811-3.2. Changelog diff is: * Mon Oct 05 2009 tambet@novell.com - Never fall back to manually updating resolv.conf, even if netconfig fails (bnc #537907, #544195). The change mentioned in comment #11 fixed the NetworkManager to do the right thing - to never update resolv.conf on it's own and to always use only netconfig. This has always been our policy, but things unfortunately broke in RC7. Now that the bug has been fixed, there's a side effect - if you have used NetworkManager from RC7, you have resolv.conf written by NetworkManager, which netconfig refuses to change. You can fix that by running 'sudo /sbin/netconfig update -f'. This problem will not affect anyone who hasn't run RC7, so I suggest we just close this bug. i confirm this bug too. after last update (15-10-2009) of 11.2 M8 i lost contact to outside world. Empty resolv.conf was the reason. Adding DNS IPs and restarting network service does the trick. But this is not the first time i come across of this problem. Once i remember someone with opensuse 10.3 had similar problem. That is not relevant now, but that makes me think that this bug has deeper roots then one might think. As I mentioned in #546700 (now duped to this), M8 was fine until an update on 2009-10-12. I have been trying out these betas, and I always do a full, wipe the hard drive, new install on each one. This problem only appeared for me after that M8 update. Previous to that, it was fine. I am now installing RC1 on that machine, using the same clean and install I was doing before. I will know if this problem has been fixed for RC1 or not (regardless of M7). I will post that result here. Okay, it installed (I just upgraded the CD drive to a DVDR/CDR drive so that I could use the DVD install (first time I tried that). It installed the fastest of either of the other two options I was using before. The only problem I encountered was the first time I tried to log in, all I got was a blank screen with a movable mouse cursor. I killed the X server (ctrl-alt-backspace) and tried again. It logged me properly this time. I tested the internet access and it works. Looking at resolv.conf, I see the first line: ### /etc/resolv.conf file autogenerated by netconfig! The only other issue I see is when I create a new icon for Konqueror file browser in the Desktop folder, I cannot edit the title in the General tab of properties. It cannot be changed from "Link to Application." However, the title I insert in the Name box of the Application tab comes up in the Desktop folder as the title of the icon. I did complete updates, both the test updates from the updater applet and from Yast. The only problem I got was an exit with error 5 from the Yast app. When I went back to see if there were any packages that were missed, it showed no updates for anything installed on the computer. This is RC1 I just installed. Sorry about any confusion. *** Bug 547916 has been marked as a duplicate of this bug. *** I've always found that if I did: sudo mv /etc/resolv.conf /tmp then sudo /sbin/service network restart NetworkManager will then start writing resolv.conf again.. this is something similar I reported and was fixed for openSUSE 11.1.. There's no need to invent new workarounds or guess why it might fail, please read comment #12. This bug does not affect anyone who hasn't been helping out with testing - if you do a fresh install of 11.2 or upgrade from 11.1, everything works fine. I don't think we can or should support upgrades from every broken testing build, so I'm going to close this bug. Once again, if you do experience this issue, run: sudo /sbin/netconfig update -f *** Bug 551741 has been marked as a duplicate of this bug. *** |