[Cooker] Network cannot resolve dns addresses again after last nights update

[Colin Guthrie-8]

Steve Morris wrote:
> I have checked /etc/resolv.conf and the nameserver statement is still
> there, and, /var/run/resolvconf/interface/eth0 still exists and contains
> the nameserver statement. Could this be an indication of where my dns
> failures are originating from?

Very odd. If the files are still there then this would seem to suggest
that your core name resolution still works.

Can you post your /etc/nsswitch.conf

Col

--

+--------------------------+
|      Colin Guthrie       |
+--------------------------+
| cguthrie(at)mandriva.org |
|  http://colin.guthr.ie/  |
+--------------------------+

[Steve Morris-5]

Colin Guthrie wrote:

> Steve Morris wrote:
>> I have checked /etc/resolv.conf and the nameserver statement is still
>> there, and, /var/run/resolvconf/interface/eth0 still exists and
>> contains the nameserver statement. Could this be an indication of
>> where my dns failures are originating from?
>
> Very odd. If the files are still there then this would seem to suggest
> that your core name resolution still works.
>
> Can you post your /etc/nsswitch.conf
>
> Col
>

Thanks Col, I have attached the file.

One other thing I have noticed is that I am getting the following
message at boot time:

Loop detected: network -> resolvconf: ignoring resolvconf

I have seen somebody else mention this as well, and that he fixed it by
changing the order of these to scripts. I could do the same thing by
renaming one of these in rc5.d, but that can lead to duplicate script
issues if the distribution doesn't make the same change. Hence this
issue should really be resolved by Mandriva.
Is is possible that this loop message is randomly having an impact and
causing resolv.conf to be wiped?

Also I am getting a host of these loop detected type messages at
shutdown, but ignored them because I figured that being at shutdown who
cares, but should I be ignoring them?

regards,
Steve



#
# /etc/nsswitch.conf
#
# An example Name Service Switch config file. This file should be
# sorted with the most-used services at the beginning.
#
# The entry '[NOTFOUND=return]' means that the search for an
# entry should stop if the search in the previous entry turned
# up nothing. Note that if the search failed due to some other reason
# (like no NIS server responding) then the search continues with the
# next entry.
#
# Legal entries are:
#
#       compat                  Use compatibility setup
#       nisplus or nis+         Use NIS+ (NIS version 3)
#       nis or yp               Use NIS (NIS version 2), also called YP
#       dns                     Use DNS (Domain Name Service)
#       files                   Use the local files
#       db                      Use the local database (.db) files
#       [NOTFOUND=return]       Stop searching if not found so far
#
# For more information, please read the nsswitch.conf.5 manual page.
#

# passwd: files nis
# shadow: files nis
# group:  files nis

passwd: files compat
shadow: files
group: files compat

hosts:   mdns4_minimal files nis dns
 mdns4 networks: files

services: files
protocols: files
rpc: files
ethers: files
netmasks: files
netgroup: files
publickey: files

bootparams: files
automount: files
aliases: files

[samorris.vcf]

---

begin:vcard
fn:Steve Morris
n:Morris;Steve
email;internet:samorris@...
x-mozilla-html:TRUE
version:2.1
end:vcard

---

[Colin Guthrie-8]

Steve Morris wrote:
> Colin Guthrie wrote:
>> Can you post your /etc/nsswitch.conf

> Thanks Col, I have attached the file.

There is a typo in that file.


See the line that starts with "hosts:", it has an extra carriage return
before the next line that it shouldn't have, but that next line is also
missing a carriage return!!

You have:
hosts:   mdns4_minimal files nis dns
  mdns4 networks: files


And you should have:
hosts: mdns4_minimal files nis dns mdns4
networks: files


And actually, I think you /should/ have:
hosts:          mdns4_minimal [NOTFOUND=return] files nis dns mdns4
networks:       files

This NOTFOUND=return is not strictly speaking needed but it does allow a
short circuit return when mdns4_minimal doesn't work for a specific
address TLD/IP range (i.e. addresses ending in .local or the zeroconf ip
address range which escapes me right now).

Dunno how this could have been messed up automatically as most automatic
changes are done line-by-line, not multi-line which makes me suspect
this could have been a hand edit?

Col

--

+--------------------------+
|      Colin Guthrie       |
+--------------------------+
| cguthrie(at)mandriva.org |
|  http://colin.guthr.ie/  |
+--------------------------+

[Steve Morris-5]

Colin Guthrie wrote:

> Steve Morris wrote:
>> Colin Guthrie wrote:
>>> Can you post your /etc/nsswitch.conf
>
>> Thanks Col, I have attached the file.
>
> There is a typo in that file.
>
>
> See the line that starts with "hosts:", it has an extra carriage
> return before the next line that it shouldn't have, but that next line
> is also missing a carriage return!!
>
> You have:
> hosts:       mdns4_minimal files nis dns
>  mdns4 networks:    files
>
>
> And you should have:
> hosts:        mdns4_minimal files nis dns mdns4
> networks:    files
>
>
> And actually, I think you /should/ have:
> hosts:          mdns4_minimal [NOTFOUND=return] files nis dns mdns4
> networks:       files
>
> This NOTFOUND=return is not strictly speaking needed but it does allow
> a short circuit return when mdns4_minimal doesn't work for a specific
> address TLD/IP range (i.e. addresses ending in .local or the zeroconf
> ip address range which escapes me right now).
>
> Dunno how this could have been messed up automatically as most
> automatic changes are done line-by-line, not multi-line which makes me
> suspect this could have been a hand edit?
>
> Col
>

Thanks Col, I have made the changes you suggested. I don't believe I

have manually updated this file as the mdns entries don't mean anything
to me at the moment.

regards,
Steve


[samorris.vcf]

---

begin:vcard
fn:Steve Morris
n:Morris;Steve
email;internet:samorris@...
x-mozilla-html:TRUE
version:2.1
end:vcard

---

[Colin Guthrie-8]

Steve Morris wrote:
> Thanks Col, I have made the changes you suggested. I don't believe I
> have manually updated this file as the mdns entries don't mean anything
> to me at the moment.

the mdns entries will have been added by nss_mdns package (rpm -q
--scripts nss_mdns), but these automated replacements use perl's line
based regexp stuff so I'd say it's almost impossible that they were
responsible for this (it's actually quite hard to work with newlines in
such a way) and hence why I suspect a hand edit typo is at fault.

mdns is the Bonjour/Avahi/ZeroConf/[insert next name here] way of
creating an ad-hoc network complete with name resolution without
requiring a master/controlling server. It's all rather nice if you use
it well (e.g. the pulse stuff kicks ass!)

Col

--

+--------------------------+
|      Colin Guthrie       |
+--------------------------+
| cguthrie(at)mandriva.org |
|  http://colin.guthr.ie/  |
+--------------------------+

[Jan Ciger]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Colin Guthrie wrote:
> mdns is the Bonjour/Avahi/ZeroConf/[insert next name here] way of
> creating an ad-hoc network complete with name resolution without
> requiring a master/controlling server. It's all rather nice if you use
> it well (e.g. the pulse stuff kicks ass!)

Assuming that Shorewall is not blocking it - which it is by default ever
since Zeroconf was introduced to Mandriva in 2006 (!!!).

See bug (including workaround/fix):
https://qa.mandriva.com/show_bug.cgi?id=24969

Regards,

Jan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org

iD8DBQFIOuMzn11XseNj94gRAhvIAKDEOz7pR5VdDChYxIaUq7aKoLqirwCgllOz
QneVPF4Ks9fQdaA1IwCH36M=
=GnQ2
-----END PGP SIGNATURE-----

[Colin Guthrie-8]

Jan Ciger wrote:

> Colin Guthrie wrote:
>> mdns is the Bonjour/Avahi/ZeroConf/[insert next name here] way of
>> creating an ad-hoc network complete with name resolution without
>> requiring a master/controlling server. It's all rather nice if you use
>> it well (e.g. the pulse stuff kicks ass!)
>
> Assuming that Shorewall is not blocking it - which it is by default ever
> since Zeroconf was introduced to Mandriva in 2006 (!!!).
>
> See bug (including workaround/fix):
> https://qa.mandriva.com/show_bug.cgi?id=24969

Indeed. I need to look at this and see if we can kickstart the
discussion again :)

Col
--

+--------------------------+
|      Colin Guthrie       |
+--------------------------+
| cguthrie(at)mandriva.org |
|  http://colin.guthr.ie/  |
+--------------------------+

[Steve Morris-5]

Colin Guthrie wrote:

> Steve Morris wrote:
>> Thanks Col, I have made the changes you suggested. I don't believe I
>> have manually updated this file as the mdns entries don't mean
>> anything to me at the moment.
>
> the mdns entries will have been added by nss_mdns package (rpm -q
> --scripts nss_mdns), but these automated replacements use perl's line
> based regexp stuff so I'd say it's almost impossible that they were
> responsible for this (it's actually quite hard to work with newlines
> in such a way) and hence why I suspect a hand edit typo is at fault.
>
> mdns is the Bonjour/Avahi/ZeroConf/[insert next name here] way of
> creating an ad-hoc network complete with name resolution without
> requiring a master/controlling server. It's all rather nice if you use
> it well (e.g. the pulse stuff kicks ass!)
>
> Col
>

Thanks Col, why I said they don't mean anything to me at the moment is

that I don't remember ever seeing them with a suffix of 4. I guess it is
possible that I manually updated this file and forgot about it, the last
time the file was updated was 27/12/2007, but if the structure of that
file was an issue, it should have caused my problem every boot, not just
after a cooker update. Also it doesn't explain why over the last 2-3
weeks the frequency of the problem had increased.
I have also bitten the bullet and done what Mandriva should have done, I
have renamed the rc5.d resolvconf script so that it get started before
the network script. This has removed the loop warning and has made the
resolvconf started message more obvious (although it could be more
obvious because now I tend to look for it at boot).

regards,
Steve


[samorris.vcf]

---

begin:vcard
fn:Steve Morris
n:Morris;Steve
email;internet:samorris@...
x-mozilla-html:TRUE
version:2.1
end:vcard

---

[Steve Morris-5]

Jan Ciger wrote:

> Colin Guthrie wrote:
> > mdns is the Bonjour/Avahi/ZeroConf/[insert next name here] way of
> > creating an ad-hoc network complete with name resolution without
> > requiring a master/controlling server. It's all rather nice if you use
> > it well (e.g. the pulse stuff kicks ass!)
>
> Assuming that Shorewall is not blocking it - which it is by default ever
> since Zeroconf was introduced to Mandriva in 2006 (!!!).
>
> See bug (including workaround/fix):
> https://qa.mandriva.com/show_bug.cgi?id=24969
>
> Regards,
>
> Jan

Thanks Jan, as far as I can tell from looking at the services in

drakconf I don't have Shorewall installed. I am using Firestarter as my
firewall with iptables and ip6tables disabled in all run levels.

regards,
Steve


[samorris.vcf]

---

begin:vcard
fn:Steve Morris
n:Morris;Steve
email;internet:samorris@...
x-mozilla-html:TRUE
version:2.1
end:vcard

---

[Laurent Suchet]

Hi,

this morning I used XFdrake to change some settings . Testing the new
configuration was ok, but when restarting Xserver, I have:

xauth: error in locking authority file /home/laurent/.Xauthority
(repeted several time)
execve failed for /etc/X11/X (errno 2)


What could be the issue? Is it a .rpmnew conf file problem? (during update in
CLI no .rpmnew was signaled..)

Thanks

LS

[Moreno]

Hi

On Sat, May 31, 2008 at 10:41 AM,  <laurent.s3@...> wrote:

> Hi,
>
> this morning I used XFdrake to change some settings . Testing the new
> configuration was ok, but when restarting Xserver, I have:
>
> xauth: error in locking authority file /home/laurent/.Xauthority
> (repeted several time)
> execve failed for /etc/X11/X (errno 2)
>
>
> What could be the issue? Is it a .rpmnew conf file problem? (during update in
> CLI no .rpmnew was signaled..)
>
> Thanks
>
> LS
>

This is a well know Bug without a possible solution (for the moment),
this problm come each time you change the X configuration.

To solve

1) Remove the demaged link X in /etc/X11
2) Create the link of /usr/bin/Xorg in /etc/X11/X


Bye Bye, Moreno

[Paulo César Pereira de Andrade]

Quoting Moreno <moreno.mg@...>:

> Hi
>
> On Sat, May 31, 2008 at 10:41 AM,  <laurent.s3@...> wrote:
>> Hi,
>>
>> this morning I used XFdrake to change some settings . Testing the new
>> configuration was ok, but when restarting Xserver, I have:
>>
>> xauth: error in locking authority file /home/laurent/.Xauthority
>> (repeted several time)
>> execve failed for /etc/X11/X (errno 2)
>>
>>
>> What could be the issue? Is it a .rpmnew conf file problem? (during
>> update in
>> CLI no .rpmnew was signaled..)
>>
>> Thanks
>>
>> LS
>>
>
> This is a well know Bug without a possible solution (for the moment),
> this problm come each time you change the X configuration.
>
> To solve
>
> 1) Remove the demaged link X in /etc/X11
> 2) Create the link of /usr/bin/Xorg in /etc/X11/X
>
>
> Bye Bye, Moreno

  There is an bug report about it at
https://qa.mandriva.com/show_bug.cgi?id=41021
that was marked a duplicate of a related one I opened
https://qa.mandriva.com/show_bug.cgi?id=40970

  I believe this is caused by some old code in drakx-kdb-mouse-x11,
from when there were alternate X Servers, as the link is properly
created when installing x11-server-xorg.

  You can fix it by running something like:

$ sudo ln -sf ../../../usr/bin/Xorg /usr/share/X11/X


Paulo

[Laurent Suchet]

pcpa@... a écrit :

> Quoting Moreno <moreno.mg@...>:
>
>> Hi
>>
>> On Sat, May 31, 2008 at 10:41 AM,  <laurent.s3@...> wrote:
>>> Hi,
>>>
>>> this morning I used XFdrake to change some settings . Testing the new
>>> configuration was ok, but when restarting Xserver, I have:
>>>
>>> xauth: error in locking authority file /home/laurent/.Xauthority
>>> (repeted several time)
>>> execve failed for /etc/X11/X (errno 2)
>>>
>>>
>>> What could be the issue? Is it a .rpmnew conf file problem? (during
>>> update in
>>> CLI no .rpmnew was signaled..)
>>>
>>> Thanks
>>>
>>> LS
>>>
>>
>> This is a well know Bug without a possible solution (for the moment),
>> this problm come each time you change the X configuration.
>>
>> To solve
>>
>> 1) Remove the demaged link X in /etc/X11
>> 2) Create the link of /usr/bin/Xorg in /etc/X11/X
>>
>>
>> Bye Bye, Moreno
>
>  There is an bug report about it at
> https://qa.mandriva.com/show_bug.cgi?id=41021
> that was marked a duplicate of a related one I opened
> https://qa.mandriva.com/show_bug.cgi?id=40970
>
>  I believe this is caused by some old code in drakx-kdb-mouse-x11,
> from when there were alternate X Servers, as the link is properly
> created when installing x11-server-xorg.
>
>  You can fix it by running something like:
>
> $ sudo ln -sf ../../../usr/bin/Xorg /usr/share/X11/X
>
>
> Paulo
>
>
>

Hi,

Moreno's trick worked well, recreating simply the symbolic link
/etc/X11/X --> /usr/bin/Xorg solved the issue.

Thanks Moreno and Paulo

Laurent