Re: [Cooker] DNS Resolution failed again, but in a strange fashion, after last cooker update

[Steve Morris]

Frank Griffin wrote:
> Steve Morris wrote:
> > Why did it work under tty but not under X?
> The better question is why it stopped working when you rebooted.  I 
> assume you verified that other usage of DNS (besides Thunderbird) was 
> affected, and checked all the stuff mentioned in your other thread ?
Frank, I have just lost the network again after a cold boot and I think 
I know what caused it. I booted into a tty session from kdm and issued 
startx. This tried to start kde4 which failed as the kde4 migration 
hasn't worked as yet, but this attemped start of kde4 produced the 
following message:

Expected keysim, got XF86Info: line 959 of inet.

I then booted into kde3 and nothing could get dns resolution, as 
/etc/resolv.conf was empty, /var/run/resolvconf/interface/eth0 does not 
exist and route -n produced the following output:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use 
Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     5      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     5      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         192.168.1.1     0.0.0.0         UG    5      0        0 eth0

As ifconfig seems to also have been removed (do you know what package 
provides ifconfig as the command rpm -q --whatprovides ifconfig said no 
package provides ifconfig), I issued the command dhclient eth0 which 
went through a number of dhcpdiscover processes and eventually gave me 
my normal ip address.
The route -n command then produced the following messages:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use 
Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     5      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         192.168.1.1     0.0.0.0         UG    5      0        0 eth0

Using Network Manager to disconnect/connect from/to eth0 put the name 
server entry back into /etc/resolv.conf and created 
/var/run/resolvconf/interface/eth0 with the same nameserver entry.

So it looks to me like the issues I have been having with losing dns 
resolution has been inet not working properly. Also the message 
mentioned above from inet when startx attempted to start kde4 is the 
only message I have been able to get potentially indicating why kde4 
refuses to start at any time. I had been looking in syslog for kde 
messages of which there were none at all.

How do I resolve the inet issue? I have checked syslog and there are no 
messages relating to inet in there whatsoever, the only messages 
matching inet are ones from xinetd which all look to be normal.

regards,
Steve

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