Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

resolv gets wacked after reboots

0 views
Skip to first unread message

Curtis Vaughan

unread,
Jul 12, 2005, 3:00:16 PM7/12/05
to
On one Debian server (and only on one of several that we have - all
being sarge) after every reboot, the resolv.conf file is empty.

The only thing different about this computer compared to the rest is
that the /etc/resolv.conf is a link to /etc/resolvconf/run/
resolv.conf and I don't know why.
The IP on all servers is static (set in /etc/network/interfaces).
I have at times manually edited /etc/resolv.conf to have the set
nameservers I want it to have (removing the link). But when I reboot,
it is clear again. Same applies for manually editing /etc/resolvconf/
run/resolv.conf. Although I manually edit it, after rebooting it is
clear.

What is going on?

Thanks.

Curtis


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Curtis Vaughan

unread,
Jul 12, 2005, 3:20:08 PM7/12/05
to
In addition to what I've written already:
I noticed that in /etc/network/if-up.d there is a script
000resolvconf and in /etc/network/if-down.d there is a script
resolvconf. The latter looks like it clears the resolv.conf file,
while the former sets it up. I changed the mode on these from 755 to
644. Will this solve the problem? Unfortunately, I can't reboot or
do an ifup or ifdown right now to check that.

On 12 juil. 05, at 11:59, Curtis Vaughan wrote:

> On one Debian server (and only on one of several that we have - all
> being sarge) after every reboot, the resolv.conf file is empty.
>
> The only thing different about this computer compared to the rest
> is that the /etc/resolv.conf is a link to /etc/resolvconf/run/
> resolv.conf and I don't know why.
> The IP on all servers is static (set in /etc/network/interfaces).
> I have at times manually edited /etc/resolv.conf to have the set
> nameservers I want it to have (removing the link). But when I
> reboot, it is clear again. Same applies for manually editing /etc/

> resolvconf/run/resolv.conf. Although I manually edit it, after

> rebooting it is clear.
>
> What is going on?
>
> Thanks.
>
> Curtis
>
>
> --

> To UNSUBSCRIBE, email to debian-us...@lists.debian.orgwith a

John Hasler

unread,
Jul 12, 2005, 3:40:10 PM7/12/05
to
Curtis Vaughan writes:
> The only thing different about this computer compared to the rest is that
> the /etc/resolv.conf is a link to /etc/resolvconf/run/ resolv.conf and I
> don't know why.

Remove the resolvconf package and make sure the link is removed as well.
--
John Hasler

Thomas Hood

unread,
Jul 12, 2005, 3:50:08 PM7/12/05
to
On Tue, 12 Jul 2005 11:59:37 -0700, Curtis Vaughan wrote:
> What is going on?

You have the resolvconf package installed and haven't set it up.
Either remove the package or read /usr/share/doc/resolvconf/README.gz.
(You probably need "dns-nameservers" options in /etc/network/interfaces.)

--
Thomas Hood

Curtis Vaughan

unread,
Jul 12, 2005, 4:00:11 PM7/12/05
to

On 12 juil. 05, at 12:18, John Hasler wrote:

> Curtis Vaughan writes:
>
>> The only thing different about this computer compared to the rest
>> is that
>> the /etc/resolv.conf is a link to /etc/resolvconf/run/ resolv.conf
>> and I
>> don't know why.
>>
>
> Remove the resolvconf package and make sure the link is removed as
> well.
> --


Resolvconf is not installed. Maybe it was at one time though.

John Hasler

unread,
Jul 12, 2005, 5:40:13 PM7/12/05
to
Curtis Vaughan wrote:
> I noticed that in /etc/network/if-up.d there is a script 000resolvconf
> and in /etc/network/if-down.d there is a script resolvconf. The latter
> looks like it clears the resolv.conf file, while the former sets it up.

Those scripts are part of the resolvconf package. Remove it. If it is not
installed remove the scripts (and the link) and try figure out what went
wrong so that you can file a bug.
--
John Hasler

Bob Proulx

unread,
Jul 12, 2005, 6:10:09 PM7/12/05
to
Curtis Vaughan wrote:

> John Hasler wrote:
> >Remove the resolvconf package and make sure the link is removed as
> >well.
>
> Resolvconf is not installed. Maybe it was at one time though.

Perhaps it has left configuration files behind.

dpkg -l resolvconf

Does it say 'rc' as status?

dpkg --status resolvconf | grep Status:

If so then it needs to be purged to remove the configuration files.

dpkg --purge resolvconf

Bob

signature.asc

John Hasler

unread,
Jul 12, 2005, 6:50:08 PM7/12/05
to
Bob Proulx writes:
> If so then it needs to be purged to remove the configuration files.

However, if it left behind scripts that are being executed at boot it is
buggy.
--
John Hasler

Thomas Hood

unread,
Jul 13, 2005, 5:10:10 AM7/13/05
to
Package: resolvconf
Version: 1.29
Severity: important

Yes, there is a bug in resolvconf's removal logic. The problem
is that /etc/resolvconf/run/resolv.conf resides on a volatile
filesystem and is therefore empty after boot until something
writes to it. If the resolvconf package is removed then the
resolvconf program no longer updates the file. But the symlink
/etc/resolv.conf -> /etc/resolvconf/run/resolv.conf is only
deleted if the resolvconf package is _purged_.

Purging resolvconf should fix the user's problem.

The resolvconf package should be changed so that the symlink
is deleted on package removal.
--
Thomas Hood

0 new messages