Re: starting X hangs on network timeout (hosts file ignored)
On Wed, Jul 14, 2004 at 12:08:39AM +0100, Steven Satelle wrote: On Tue, 13 Jul 2004 20:28:56 +0300, Micha Feigin wrote: Same behavior (I am using wdm and no xdmcp and the no listen on tcp switch). It seems like /usr/X11R6/bin/X is whats causing the trouble, running tcpdump when X startx shows the name lookup BTW: you know, I think we're barking up the wrong tree, in fact I dont even think we are in the woods at all ;-) It might well be a bug. but a bug in what? Try without any x sessions running run 'X' as root and see how long does it take to start, that way you can see if it is xfree or (I assume your using it) gnome. Running just X also hangs in the same way, so its X that's giving the problems. I am not running gnome btw, I'm running FVWM (gnome is too slow,heavy and not configurable enough). Also running wdm gives the same problem and its not starting .xsession or gnome-session so thats not the problem. Assuming it starts quickly, next you want to type: $ export DISPLAY=localhost:0.0 $ gnome-session (or enter the name of your wm's main app) If what I think the problem is is right this should be slow to launch, so exit it (not X just the wm) and this time on another console run 'netstat -c' This will show all network connections and refresh them every few seconds. then relaunch your wm and see does any new datagrams or streams open up in netstat, esp ones that sit in a state of 'SYN_SENT' You are going to get a few going no further than /tmp/.orbit-root, I'm fairly sure they will be streams, they are what gives gnome its network transparency, even local only connections open up sockets. Thats what I think the problem is, gnome is trying to open up a network socket to somewhere. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] +++ This Mail Was Scanned By Mail-seCure System at the Tel-Aviv University CC. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
On Tue, Jul 13, 2004 at 01:49:29AM +0100, Steven Satelle wrote: On Mon, 12 Jul 2004 17:58:40 +0300, Micha Feigin wrote: BTW I got the following reply after I tried reporting a bug on netbase on this: [...] this is how it's supposed to work. host(1) is an interface to the resolver library, which does not use /etc/hosts by design. The problem is that it seems that a few other things seem to be ignoring the /etc/hosts file also. what package are you getting host from, I dont have it on my system. whats /usr/bin/host in your /etc/resolv.conf, mine has search personal.ie nameserver 192.168.1.1 domain luna.local nameserver 192.168.0.1 I think you should have nameserver 127.0.0.1 in there before any remote binds, I dont, but then, I dont have a problem ;-) I think If you have 127.0.0.1 in there as the first nameserver it will check the local one first (/etc/hosts) Doesn't work. apart from that what happens if you run startx without gdm running? Same behavior (I am using wdm and no xdmcp and the no listen on tcp switch). It seems like /usr/X11R6/bin/X is whats causing the trouble, running tcpdump when X startx shows the name lookup BTW: 20:25:55.791908 IP litshi.luna.local.32784 rice.luna.local.domain: 6405+ A? -.luna.local. (30) 20:25:55.792612 IP litshi.luna.local.32785 rice.luna.local.domain: 7688+ PTR? 1.0.168.192.in-addr.arpa. (42) 20:25:55.793239 IP rice.luna.local.domain litshi.luna.local.32784: 6405 NXDomain* 0/1/0 (80) 20:25:55.793411 IP litshi.luna.local.32786 rice.luna.local.domain: 6406+ A? -. (19) 20:25:55.793894 IP rice.luna.local.domain litshi.luna.local.32785: 7688* 1/1/0 PTR[|domain] 20:25:55.794140 IP litshi.luna.local.32787 rice.luna.local.domain: 7689+ PTR? 3.0.168.192.in-addr.arpa. (42) 20:25:55.794252 IP rice.luna.local.domain litshi.luna.local.32786: 6406 NXDomain 0/1/0 (94) 20:25:55.794411 IP litshi.luna.local.32788 rice.luna.local.domain: 6407+ A? -.luna.local. (30) 20:25:55.795182 IP rice.luna.local.domain litshi.luna.local.32787: 7689* 1/1/0 PTR[|domain] 20:25:55.795591 IP rice.luna.local.domain litshi.luna.local.32788: 6407 NXDomain* 0/1/0 (80) 20:25:55.795645 IP litshi.luna.local.32788 rice.luna.local.domain: 6408+ A? -. (19) 20:25:55.796280 IP rice.luna.local.domain litshi.luna.local.32788: 6408 NXDomain 0/1/0 (94) 20:25:55.796419 IP litshi.luna.local.32788 rice.luna.local.domain: 6409+ A? local:root.luna.local. (39) 20:25:55.797114 IP rice.luna.local.domain litshi.luna.local.32788: 6409 NXDomain* 0/1/0 (89) 20:25:55.797158 IP litshi.luna.local.32788 rice.luna.local.domain: 6410+ A? local:root. (28) 20:25:55.797800 IP rice.luna.local.domain litshi.luna.local.32788: 6410 NXDomain 0/1/0 (103) 20:26:00.790557 arp who-has litshi.luna.local tell rice.luna.local 20:26:00.790591 arp reply litshi.luna.local is-at 08:00:46:5b:70:62 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] +++ This Mail Was Scanned By Mail-seCure System at the Tel-Aviv University CC. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
On Tue, 13 Jul 2004 20:28:56 +0300, Micha Feigin wrote: Same behavior (I am using wdm and no xdmcp and the no listen on tcp switch). It seems like /usr/X11R6/bin/X is whats causing the trouble, running tcpdump when X startx shows the name lookup BTW: you know, I think we're barking up the wrong tree, in fact I dont even think we are in the woods at all ;-) It might well be a bug. but a bug in what? Try without any x sessions running run 'X' as root and see how long does it take to start, that way you can see if it is xfree or (I assume your using it) gnome. Assuming it starts quickly, next you want to type: $ export DISPLAY=localhost:0.0 $ gnome-session (or enter the name of your wm's main app) If what I think the problem is is right this should be slow to launch, so exit it (not X just the wm) and this time on another console run 'netstat -c' This will show all network connections and refresh them every few seconds. then relaunch your wm and see does any new datagrams or streams open up in netstat, esp ones that sit in a state of 'SYN_SENT' You are going to get a few going no further than /tmp/.orbit-root, I'm fairly sure they will be streams, they are what gives gnome its network transparency, even local only connections open up sockets. Thats what I think the problem is, gnome is trying to open up a network socket to somewhere. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
On Mon, Jul 12, 2004 at 12:06:41AM +0100, Steven Satelle wrote: Ping uses the hosts file but host seems to ignore it. So if the nameserver is not reachable then ping hostname works but host hostname returns 192.168.0.1 connect: Network is unreachable Nameserver not reachable litshi.luna.local A record not found, try again my /etc/hosts has the following lines: 127.0.0.1 localhost 127.0.0.1 litshi.luna.local litshi (I know pointing hostname to 127.0.0.1 is not advised, but its a laptop and has several possible IPs). Any ideas? right you are getting me puzzled now :-) I suppose a bit of fishing is in order what's in /etc/host.conf, it should say 'order hosts,bind' order hosts,bind multi on that file tells the sys how to resolve hosts in the network, you want it to check the local hosts file before going to bind also whats in /etc/hostname? It should, at least on my sys, have the litshi hostname of the sys, not the fqdn, just the hostid.If It doesnt use 'hostname litshi' to set it, ignore the fqdn for now, just try with that. If that doesnt work, have you looked at m$ windows recently ;-) If even that doesnt work you could try (dont tell anyone I said this) a reboot, after setting the hostname and entering it into /etc/hosts, the files may just need to be re-read hostname returns litshi now I tried pulling the cable and testing again: ping litshi PING litshi.luna.local (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.112 ms 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.082 ms 64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.082 ms host litshi Nameserver not responding litshi.luna.local A record not found, try again (after reconnecting cable) host litshi litshi.luna.local A 192.168.0.3 /etc/hosts file: cat /etc/hosts 127.0.0.1 localhost 127.0.0.1 litshi.luna.local litshi Tried everything as root and checked read permissions for all the files ll /etc/ | grep -v .r..r..r total 1620 -rw---1 root root 144 2002-01-18 10:13 at.deny -rw---1 root root 549 2004-04-27 04:07 group- -rw-r-1 root shadow467 2004-05-08 16:54 gshadow -rw---1 root root 457 2004-04-27 04:07 gshadow- -rw---1 root root 998 2004-05-08 16:55 passwd- -rw-r-1 root shadow745 2004-05-08 16:55 shadow -rw---1 root root 685 2004-04-01 15:52 shadow- -r--r-1 root root 302 2004-04-01 06:14 sudoers Anything else that could cause the problem? BTW I got the following reply after I tried reporting a bug on netbase on this: [...] this is how it's supposed to work. host(1) is an interface to the resolver library, which does not use /etc/hosts by design. The problem is that it seems that a few other things seem to be ignoring the /etc/hosts file also. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] +++ This Mail Was Scanned By Mail-seCure System at the Tel-Aviv University CC. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
On Mon, 12 Jul 2004 17:58:40 +0300, Micha Feigin wrote: BTW I got the following reply after I tried reporting a bug on netbase on this: [...] this is how it's supposed to work. host(1) is an interface to the resolver library, which does not use /etc/hosts by design. The problem is that it seems that a few other things seem to be ignoring the /etc/hosts file also. what package are you getting host from, I dont have it on my system. whats in your /etc/resolv.conf, mine has search personal.ie nameserver 192.168.1.1 I think you should have nameserver 127.0.0.1 in there before any remote binds, I dont, but then, I dont have a problem ;-) I think If you have 127.0.0.1 in there as the first nameserver it will check the local one first (/etc/hosts) apart from that what happens if you run startx without gdm running? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
Incoming from Steven Satelle: On Mon, 12 Jul 2004 17:58:40 +0300, Micha Feigin wrote: [...] this is how it's supposed to work. host(1) is an interface to the resolver library, which does not use /etc/hosts by design. The problem is that it seems that a few other things seem to be ignoring the /etc/hosts file also. what package are you getting host from, I dont have it on my system. whats in your /etc/resolv.conf, mine has search personal.ie nameserver 192.168.1.1 If you want to augment that, it may be dependent on the package/transport you use to set up your network. I use pppd and I see there's a /etc/ppp/resolv/provider that lists nameserver xxx.xxx.xxx.xxx records to be used to create resolv.conf -- Any technology distinguishable from magic is insufficiently advanced. (*) http://www.spots.ab.ca/~keeling - - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
On Sun, Jul 11, 2004 at 08:33:15PM +0100, Steven Satelle wrote: On Sun, 11 Jul 2004 20:18:19 +0100, Thomas Adam wrote: --- Micha Feigin [EMAIL PROTECTED] wrote: I'm not sure yet on what package to report this bug, but was wondering if anyone else experiences it too. Have a look at the bugpage for 'xserver-xfree86'. If it isn't listed there, then maybe consider filing one. no, its caused by the machine trying to resolve its name over eth0 AFAIR. If the network is up. If you've configured the network, you've set a hostname, so it is trying to resolvethat. add the hostname to /etc/hosts and you shouldnt have any further problems. at least AFAIR Ping uses the hosts file but host seems to ignore it. So if the nameserver is not reachable then ping hostname works but host hostname returns 192.168.0.1 connect: Network is unreachable Nameserver not reachable litshi.luna.local A record not found, try again my /etc/hosts has the following lines: 127.0.0.1 localhost 127.0.0.1 litshi.luna.local litshi (I know pointing hostname to 127.0.0.1 is not advised, but its a laptop and has several possible IPs). Any ideas? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] +++ This Mail Was Scanned By Mail-seCure System at the Tel-Aviv University CC. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
Ping uses the hosts file but host seems to ignore it. So if the nameserver is not reachable then ping hostname works but host hostname returns 192.168.0.1 connect: Network is unreachable Nameserver not reachable litshi.luna.local A record not found, try again my /etc/hosts has the following lines: 127.0.0.1 localhost 127.0.0.1 litshi.luna.local litshi (I know pointing hostname to 127.0.0.1 is not advised, but its a laptop and has several possible IPs). Any ideas? right you are getting me puzzled now :-) I suppose a bit of fishing is in order what's in /etc/host.conf, it should say 'order hosts,bind' that file tells the sys how to resolve hosts in the network, you want it to check the local hosts file before going to bind also whats in /etc/hostname? It should, at least on my sys, have the hostname of the sys, not the fqdn, just the hostid.If It doesnt use 'hostname litshi' to set it, ignore the fqdn for now, just try with that. If that doesnt work, have you looked at m$ windows recently ;-) If even that doesnt work you could try (dont tell anyone I said this) a reboot, after setting the hostname and entering it into /etc/hosts, the files may just need to be re-read -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
