Name resolver problem after upgrade from woody to sarge
Hi, (sorry if you receive this twice, I sent it a couple of days ago but the email has still not appeared in the archives, so I try again) I have just upgraded my machine at home from woody to sarge and now the name resolution doesn't work anymore. To be more precise, programs such as Mozilla or lynx don't manage to lookup any names, but i can use host or dig or nslookup (or even socket.gethostbyname(...) in Python) without problems. Also, once I have looked up a name using host, for example, then Mozilla can also find it, at least for some minutes of time. I have tried looking in different documents and HOWTO:s and Google but haven't found anything really related. Also, I don't know the inner workings of name resolution in Linux, so I may have missed something obvious. Some facts on my setup: - I use an ADSL connection with a combined ADSL modem/router configured as a DNS relay. - ifup seems to detect this setup correctly and writes nameserver 192.168.1.1 in /etc/resolv.conf - Since I only have 2 machines connected to the router, I haven't setup any DNS for my private network and have simply added a line 192.168.1.2 MatsPC in /etc/hosts At the moment, I don't really have any clue on where to search, so any hints are welcome. /Mats -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Name resolver problem after upgrade from woody to sarge
Hi, I have just upgraded my machine at home from woody to sarge and now the name resolution doesn't work anymore. To be more precise, programs such as Mozilla or lynx don't manage to lookup any names, but i can use host or dig or nslookup (or even socket.gethostbyname(...) in Python) without problems. Also, once I have looked up a name using host, for example, then Mozilla can also find it, at least for some minutes of time. I have tried looking in different documents and HOWTO:s and Google but haven't found anything really related. Also, I don't know the inner workings of name resolution in Linux, so I may have missed something obvious. Some facts on my setup: - I use an ADSL connection with a combined ADSL modem/router configured as a DNS relay. - ifup seems to detect this setup correctly and writes nameserver 192.168.1.1 in /etc/resolv.conf - Since I only have 2 machines connected to the router, I haven't setup any DNS for my private network and have simply added a line 192.168.1.2 MatsPC in /etc/hosts At the moment, I don't really have any clue on where to search, so any hints are welcome. /Mats -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Name resolver problem after upgrade from woody to sarge
[This message has also been posted to linux.debian.user.] In article [EMAIL PROTECTED], Mats Bengtsson wrote: Hi, I have just upgraded my machine at home from woody to sarge and now the name resolution doesn't work anymore. To be more precise, programs such as Mozilla or lynx don't manage to lookup any names, but i can use host or dig or nslookup (or even socket.gethostbyname(...) in Python) without My impression is Mozilla only reads /etc/resolv.conf once, when it's launched. If you change resolv.conf, you have to exit mozilla and start a new one. I haven't seen Lynx have that problem. problems. Also, once I have looked up a name using host, for example, then Mozilla can also find it, at least for some minutes of time. In that case, I would look for a problem with the forwarder (dns cache) that you're pointing at with resolv.conf. I have tried looking in different documents and HOWTO:s and Google but haven't found anything really related. Also, I don't know the inner workings of name resolution in Linux, so I may have missed something obvious. Some facts on my setup: - I use an ADSL connection with a combined ADSL modem/router configured as a DNS relay. - ifup seems to detect this setup correctly and writes nameserver 192.168.1.1 in /etc/resolv.conf Is there really a name server at 192.168.1.1? Does it work? Try host kernel.org 192.168.1.1 and see. - Since I only have 2 machines connected to the router, I haven't setup any DNS for my private network and have simply added a line 192.168.1.2 MatsPC in /etc/hosts At the moment, I don't really have any clue on where to search, so any hints are welcome. While you're working on your home network, routers, resolv.conf, ifup/down, etc, use a reliable name server on the public Internet. After everything else is working, *then* worry about a local forwarder. Maybe you don't need one. Don't assume the name server you're told about by DHCP actually works. There are still a lot of name servers around that answer all queries from everywhere. They'll die (or be secured) if somebody publishes software that uses them by default, but short of that the potential for abuse isn't too bad. Pick half a dozen of your favorite ISPs and look up their name servers in whois. Try all the listed name servers. Some will work, some won't. Chances are you'll find at least two that answer queries about unrelated domains as well. A certain large telco on the West coast of the US, that doesn't have any network tech support for its residential DSL customers, has one. Perhaps the last technical person forgot to shut it off when they laid her or him off. The largest cable TV operator in the US, who happens also to be #2 on the Spamhaus.org list, has another. And the #1 spam supporter worldwide (see spamhaus top 10) has two more. Cameron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
problem with upgrade from Woody to Sarge
hello, i got a problem during the upgrade from Woody to Sarge with apache (Version 1) and the module libapache-mod-php4. I get the error: Setting up libapache-mod-php4 (4.3.10-15) ... Error: mod_webapp.so does not have a corresponding .info file. what can i do to fix this? thanks a lots for some help. Pierre log file: Errors were encountered while processing: fetchmail libapache-mod-php4 php4 E: Sub-process /usr/bin/dpkg returned an error code (1) Ack! Something bad happened while installing packages. Trying to recover: Setting up fetchmail (6.2.5-12) ... Starting mail retrieval agent: fetchmail (failed). dpkg: error processing fetchmail (--configure): subprocess post-installation script returned error exit status 1 Setting up libapache-mod-php4 (4.3.10-15) ... Error: mod_webapp.so does not have a corresponding .info file. The above errors might cause apache to not work properly or start Please refer to the documentation on how to fix it or report it to Debian Apache Mailing List debian-apache@lists.debian.org if in doubt on how to proceed dpkg: error processing libapache-mod-php4 (--configure): subprocess post-installation script returned error exit status 128 dpkg: dependency problems prevent configuration of php4: php4 depends on libapache-mod-php4 (= 4:4.3.10-15) | libapache2-mod-php4 (= 4:4.3.10-15); however: Package libapache-mod-php4 is not configured yet. Package libapache2-mod-php4 is not installed. dpkg: error processing php4 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: fetchmail libapache-mod-php4 php4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ssh problem after upgrade from woody to sarge
I've upgraded two Debian Woody boxes to testing (sarge). I use putty from a windows 2000 PC to login to these linux boxes, but after the upgrade i can't login anymore. What happens is that after typing the username and password putty generates errors. Is there anything wrong with the new version of the ssh server or is there anything more i need to do to get ssh to work ? Any help appreciated. Thanks Pete = --- Thanks Pete __ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ssh problem after upgrade from woody to sarge
On Mon, Apr 19, 2004 at 03:15:44AM -0700, Pete RedHair wrote: I've upgraded two Debian Woody boxes to testing (sarge). Is there anything wrong with the new version of the ssh server or is there anything more i need to do to get ssh to work ? Did you find your problem in the BTS? The new ssh uses PAM, and there seems to be some problem with the config file updates from different versions. You should look at your /etc/ssh/sshd_config and verify the following settings: PasswordAuthentication no ChallengeResponseAuthentication yes UsePAM yes Shade and sweet water! Stephan -- | Stephan SeitzE-Mail: [EMAIL PROTECTED] | | WWW: http://fsing.rootsland.net/~stse/| | PGP Public Keys: http://fsing.rootsland.net/~stse/pgp.html | signature.asc Description: Digital signature
Re: ssh problem after upgrade from woody to sarge
I've tried that and now i can't login at all i get access denied. PasswordAuthentication no (was yes) ChallengeResponseAuthentication yes (was no) UsePAM yes (was yes) Could'nt find it on BTS, i'll check again. Thanks Pete --- Stephan Seitz [EMAIL PROTECTED] wrote: On Mon, Apr 19, 2004 at 03:15:44AM -0700, Pete RedHair wrote: I've upgraded two Debian Woody boxes to testing (sarge). Is there anything wrong with the new version of the ssh server or is there anything more i need to do to get ssh to work ? Did you find your problem in the BTS? The new ssh uses PAM, and there seems to be some problem with the config file updates from different versions. You should look at your /etc/ssh/sshd_config and verify the following settings: PasswordAuthentication no ChallengeResponseAuthentication yes UsePAM yes Shade and sweet water! Stephan -- | Stephan SeitzE-Mail: [EMAIL PROTECTED] | | WWW: http://fsing.rootsland.net/~stse/ | | PGP Public Keys: http://fsing.rootsland.net/~stse/pgp.html | ATTACHMENT part 2 application/pgp-signature name=signature.asc = --- Thanks Pete __ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ssh problem after upgrade from woody to sarge
On Mon, Apr 19, 2004 at 03:15:44AM -0700, Pete RedHair wrote: I've upgraded two Debian Woody boxes to testing (sarge). I use putty from a windows 2000 PC to login to these linux boxes, but after the upgrade i can't login anymore. What happens is that after typing the username and password putty generates errors. What errors? It's impossible to help without seeing those. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ssh problem after upgrade from woody to sarge
Sorry. What happens is that i get the usual window when an application crashes saying putty.exe generated errors and is being closed by windows, you need to restart the program (it's something like this i had to translate since my windows is not english. Also if i open an ssh connection to a woody server everything works ok, only to these two servers upgraded to sarge generate this error in putty. Windows doesn't log anything in the event log. The only thing i get is a 15.5Mb user.dmp. --- Colin Watson [EMAIL PROTECTED] wrote: On Mon, Apr 19, 2004 at 03:15:44AM -0700, Pete RedHair wrote: I've upgraded two Debian Woody boxes to testing (sarge). I use putty from a windows 2000 PC to login to these linux boxes, but after the upgrade i can't login anymore. What happens is that after typing the username and password putty generates errors. What errors? It's impossible to help without seeing those. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] = --- Thanks Pete __ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ssh problem after upgrade from woody to sarge
Thanks for your reply . I was forgetting putty since it worked fine with woody, however i did upgraded putty and now it works ok, even after the changes i made in sshd_config which didn't let me login. Guess i missed the problem tracking when i assumed everything was ok with my old version of putty (0.5.1), sorry. Thanks for your help Pete --- Colin Watson [EMAIL PROTECTED] wrote: On Mon, Apr 19, 2004 at 04:43:48AM -0700, Pete RedHair wrote: What happens is that i get the usual window when an application crashes saying putty.exe generated errors and is being closed by windows, you need to restart the program (it's something like this i had to translate since my windows is not english. Best report that to the PuTTY team, then. Whether or not a current OpenSSH server triggers it, it's still a bug in PuTTY and should be fixed there. Are you using a recent version? -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] = --- Thanks Pete __ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ssh problem after upgrade from woody to sarge
On Mon, Apr 19, 2004 at 06:11:07AM -0700, Pete RedHair wrote: Thanks for your reply . I was forgetting putty since it worked fine with woody, however i did upgraded putty and now it works ok, even after the changes i made in sshd_config which didn't let me login. Guess i missed the problem tracking when i assumed everything was ok with my old version of putty (0.5.1), sorry. Aha, right. http://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html indeed lists some crash bugs fixed after 0.51. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ssh problem after upgrade from woody to sarge
Yep, it's writen there, thanks for your help. It is now working without any problems. Stephan reported about some changes needed to do in the sshd_config, should i keep them, are they to be default in sarge ? Thanks again Colin, and Stephan Pete --- Colin Watson [EMAIL PROTECTED] wrote: On Mon, Apr 19, 2004 at 06:11:07AM -0700, Pete RedHair wrote: Thanks for your reply . I was forgetting putty since it worked fine with woody, however i did upgraded putty and now it works ok, even after the changes i made in sshd_config which didn't let me login. Guess i missed the problem tracking when i assumed everything was ok with my old version of putty (0.5.1), sorry. Aha, right. http://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html indeed lists some crash bugs fixed after 0.51. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] = --- Thanks Pete __ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ssh problem after upgrade from woody to sarge
On Mon, Apr 19, 2004 at 06:36:32AM -0700, Pete RedHair wrote: It is now working without any problems. Fine. Stephan reported about some changes needed to do in the sshd_config, should i keep them, are they to be You'll need them, if you don't have your passwords in /etc/shadow but in LDAP or Samba. At least, I needed them. default in sarge ? ChallengeResponseAuthentication is yes in new versions. I seemed to have an really old config file. The other options are, too, yes in new installations. Shade and sweet water! Stephan -- | Stephan SeitzE-Mail: [EMAIL PROTECTED] | | WWW: http://fsing.rootsland.net/~stse/| | PGP Public Keys: http://fsing.rootsland.net/~stse/pgp.html | signature.asc Description: Digital signature
Re: ssh problem after upgrade from woody to sarge
I'm using shadow so i guess i need the other config. Anyway it's working. Thanks Pete --- Stephan Seitz [EMAIL PROTECTED] wrote: On Mon, Apr 19, 2004 at 06:36:32AM -0700, Pete RedHair wrote: It is now working without any problems. Fine. Stephan reported about some changes needed to do in the sshd_config, should i keep them, are they to be You'll need them, if you don't have your passwords in /etc/shadow but in LDAP or Samba. At least, I needed them. default in sarge ? ChallengeResponseAuthentication is yes in new versions. I seemed to have an really old config file. The other options are, too, yes in new installations. Shade and sweet water! Stephan -- | Stephan SeitzE-Mail: [EMAIL PROTECTED] | | WWW: http://fsing.rootsland.net/~stse/ | | PGP Public Keys: http://fsing.rootsland.net/~stse/pgp.html | ATTACHMENT part 2 application/pgp-signature name=signature.asc = --- Thanks Pete __ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
