** Changed in: resolvconf (Ubuntu)
Status: Confirmed = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Title:
Symlink /etc/resolv.conf does not exist after installation or upgrade
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: resolvconf (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Title:
Added Release Notes since I believe this would be useful to list in the
release notes.
See bug #1355868 (marked duplicate of this bug) for my suggested wording
of the note. This problem is still current, since even though the bug
#1308378 was fixed, the problem affects for example people who have
On Thu, Apr 24, 2014 at 07:49:17AM -, Timo Jyrinki wrote in bug #1308378:
I think I know the actual reason (or one of those) it may be missing for
many people including me in 12.04 LTS:
https://help.ubuntu.com/community/LiveCDCustomization - as an example,
this in a modified form (just
Dear Sir,(Thomas Hood),
I am very heartily thankful to you for giving me good reply. Sir, As per your
given reply, I did on my Ubuntu Computer and got success. These following
things have been done on my computer ..
Fristly, Edited Network Interfaces using the following command.. on
Mullvad is another VPN client guilty of trashing /etc/resolv.conf.
http://askubuntu.com/questions/265376/major-problem-with-dns-in-
ubuntu-12-04-and-vpn/268077
Here's a new summary of the possible causes of the missing symlink and
the contributors possibly affected.
Images
Bad Linux
Dear Sir,
I have statically configured the IP Address in /etc/network/interfaces…
of ubuntu 12.04
auto eth0
iface eth0 inet static
address 10.10.80.180
netmask 255.255.0.0
network 10.10.80.0
broadcast 10.10.80.255
gateway 10.10.1.2
after that, I have configured /etc/resolv.conf file as well…
Basavaraj Chougala: The file /etc/network/interfaces is not dynamically
generated. The content of the file /etc/resolv.conf is dynamically
generated. To cause nameserver addresses accessible over eth0 to be
included in resolv.conf, add a dns-nameservers option line to
/etc/network/interfaces, as
@Cerin: Was your comment (#117) intended for this bug report?
(This report is about the /etc/resolv.conf symlink sometimes being
missing after installation of the resolvconf package, but your comment
was about a difficulty switching between Wi-Fi networks.)
--
You received this bug notification
Is there any temporary solution for this? In order to switch between
wifi networks, or switch to/from a wired/wireless connection, I have to
disable wifi with Network Manager and then unplug any wired connection,
and then re-enable the connection I want to use.
As you can imagine, this is
I also have this problem on my computer after a 11.10 - 12.04 upgrade
debconf-show resolvconf returns :
resolvconf/downup-interfaces:
resolvconf/linkify-resolvconf: false
resolvconf/link-tail-to-original: false
resolvconf/fixing-immutable:
resolvconf/reboot-recommended-after-removal:
--
resolvconf/linkify-resolvconf: false
This is always the case after installation because the Ubuntu resolvconf
postinst does the following.
db_set resolvconf/linkify-resolvconf false
This is done for a good reason: it is done in order to prevent the
postinst from attempting to linkify again
Another occurrence of this phenomenon:
http://ubuntuforums.org/showthread.php?t=2114266
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Title:
Symlink /etc/resolv.conf does not exist after
** Changed in: resolvconf (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Title:
Symlink /etc/resolv.conf does not exist after installation or
@a_paddy: Thanks. See comment #82 for the most recent summary of causes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Title:
Symlink /etc/resolv.conf does not exist after installation or
I can confirm that FortiClient is a cause of this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Title:
Symlink /etc/resolv.conf does not exist after installation or upgrade
of
Hi Thomas, will test all solutions you mentioned and report (have tried
dpkg-reconfigure, will try again). Positive feedback, our complete
server park upgraded to 12.04 without problems (one server crashed
during upgrade and ubuntu still recovered nicely).
--
You received this bug notification
I wrote in comment #107:
Can you please post the error message and
an exact description of the symptoms of the failure?
I now remember that you (Anders) already posted the error message in
comment #102.
Setting up resolvconf (1.63ubuntu16) ...
start: Job is already running: resolvconf
Anders, please do the following on the affected system when it is in the
state such that an attempt to configure resolvconf fails with the error
message quoted in comment #102.
Open a terminal and enter
sudo su
and your password. This gives you a shell with root privileges. Run the
One of the possible causes of this (bug #1000244) may have been
eliminated in the latest release -- resolvconf 1.69ubuntu1 -- which
fixes bug #1085862.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That it is not new installs but old ones that fail to upgrade properly
is intriguing. Let's get to the bottom of this!
Is there any way I can force apt or dpkg to install it
If you mean ... to install it (resolvconf) properly then the answer is
that you do dpkg-reconfigure resolvconf after
Sorry for the late reply.
I tested upgrading some other servers we use and the process went well.
The servers failing are our oldest in production. Meaning we have
updated them since version 9 (or perhaps even 8) to long term releases
of Ubuntu. I.e., gradually with apt-get (without problems to
Thanks for the support Thomas and Steve. The blog answered most
questions, the option to keep resolv.conf as a regular file is what I
probably need. The upgrade process seemed to use this option
automatically (no symlink was present after upgrade). Still, when
upgrading it fails as noted in post
Having a static file instead of a symlink at /etc/resolv.conf is
supported. It's recommended in that case to keep the resolvconf package
installed, since the presence of resolvconf prevents some other packages
from overwriting /etc/resolv.conf.
The bug is in the image. When we know what image you
Hi Anders. Please read Stéphane Graber's blog post about the
introduction of resolvconf and other changes to DNS in Ubuntu 12.04.
http://www.stgraber.org/2012/02/24/dns-in-ubuntu-12-04/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I agree that we should not mess with default settings. However, many
cloud images have changes reg. resolv.conf and backwards compatibility
is a good thing when doing upgrades.
Error message.
Unpacking replacement unattended-upgrades ...
Processing triggers for man-db ...
Processing triggers for
Hi Anders,
First, stock Ubuntu 12.04 and 12.10 don't malfunction like this. What
image are you using? Please give the exact version number. Where did you
get this image? Who built it?
Second, this isn't the same error as others have reported here (bug
#1000244) so we should move discussion of
Could you please add some quick clarifications for this Thomas? Might be
good for all users.
1) The message (as of today’s dist-upgrade) still shows critical error -
while I understand it is an warning. Many threads discuss this problem.
Is this correct, is dist-upgrade related problems in this
Anders, your follow-up message doesn't state what error message you're
seeing on upgrade. There's nothing I see linking your problem to this
bug report. There is certainly no generic critical error on upgrade
for users who are not manually modifying the state of /etc/resolv.conf
on their systems.
** Summary changed:
- /etc/resolv.conf symlink does not exist after initial installation of
resolvconf package
+ Symlink /etc/resolv.conf does not exist after installation or upgrade of
resolvconf -- various causes
--
You received this bug notification because you are a member of Ubuntu
Bugs,
30 matches
Mail list logo
