From: Jonas M. <jo...@fr...> - 2004-11-24 13:44:11
|
hello, some services actually make problems with running in my kernel 2.6.9-bb2 uml (debian/testing). In detail ssh starts, but rejects any login attempts from localhost and other hosts: # ssh localhost Connection closed by 127.0.0.1 as another example, Zope starts as well, but if i try to access it's indexpage (http://localhost:9673), i get an empty page, without content. any suggestions? i read that there might be problems with kernel 2.6.9 and nodevfs. Currently i use this setup, and i'll try with udev now. bye jonas |
From: Brian M. <mcg...@gm...> - 2004-11-24 18:42:27
|
On Wed, 24 Nov 2004 14:43:59 +0100, Jonas Meurer <jo...@fr...> wrote: > hello, > > some services actually make problems with running in my kernel 2.6.9-bb2 > uml (debian/testing). > > In detail ssh starts, but rejects any login attempts from localhost and > other hosts: > # ssh localhost > Connection closed by 127.0.0.1 I had this problem when I tried 2.6 with Debian/testing and never finished debugging it as I'm still not sure I haven't a local build problem. When I ran sshd in debugging mode, it told me that the crash happens in one of the PAM methods. Can you run sshd with -ddd as an option, try connecting, and post the daemon's output here? |
From: Allen C. <al...@us...> - 2004-11-24 18:54:46
|
Ssh failed to connect to sshd due to authentication problems. There are many things you can do to avoid this problem. Two possibilities are: (1) Set up ssh keys in your ~/.ssh directory to log in automatically. See ssh man page for more details. (2) Change the following settings in /etc/ssh/sshd_config and then restart sshd: PasswordAuthentication yes Also, since you are running ssh as root, you may need to set the following in /etc/ssh/sshd_config: PermitRootLogin yes On Wednesday 24 November 2004 12:30 pm, Jonas Meurer wrote: > On 24/11/2004 Allen Chan wrote: > > What does "ssh -v localhost" show? > > # ssh -v localhost > OpenSSH_3.8.1p1 Debian-8.sarge.3, OpenSSL 0.9.7d 17 Mar 2004 > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: Connecting to localhost [127.0.0.1] port 22. > debug1: Connection established. > debug1: identity file /root/.ssh/identity type -1 > debug1: identity file /root/.ssh/id_rsa type -1 > debug1: identity file /root/.ssh/id_dsa type -1 > debug1: Remote protocol version 2.0, remote software version > OpenSSH_3.8.1p1 Debian-8.sarge.3 debug1: match: OpenSSH_3.8.1p1 > Debian-8.sarge.3 pat OpenSSH* debug1: Enabling compatibility mode > for protocol 2.0 >[snip] > debug1: Authentications that can continue: > publickey,keyboard-interactive > debug1: Next authentication method: publickey > debug1: Trying private key: /root/.ssh/identity > debug1: Trying private key: /root/.ssh/id_rsa > debug1: Trying private key: /root/.ssh/id_dsa > debug1: Next authentication method: keyboard-interactive > Connection closed by 127.0.0.1 > |
From: Jonas M. <jo...@fr...> - 2004-11-24 22:28:16
|
On 24/11/2004 Allen Chan wrote: > Ssh failed to connect to sshd due to authentication problems. There > are many things you can do to avoid this problem. Two possibilities > are: > > (1) Set up ssh keys in your ~/.ssh directory to log in automatically. > See ssh man page for more details. > (2) Change the following settings in /etc/ssh/sshd_config and then > restart sshd: > PasswordAuthentication yes finally, there seem to be some more problems. after changing that, i tried to login as a normal user: # ssh jonas@localhost what happened, was that i ended up on a server of mine somewhere in the internet. this server isn't used by my machines in any way, so i hardly believe that 'nslookup localhost' gave it's ip-address. after doing this, 'host <any_machine>' gave segmentation fault. i've the strong feeling that my uml installation is full of bugs and minor mistakes, as a lot of strange or mysterious incidents happen here. bye jonas |
From: Blaisorblade <bla...@ya...> - 2004-11-25 11:31:51
|
On Wednesday 24 November 2004 23:28, Jonas Meurer wrote: > On 24/11/2004 Allen Chan wrote: > > Ssh failed to connect to sshd due to authentication problems. There > > are many things you can do to avoid this problem. Two possibilities > > are: > > > > (1) Set up ssh keys in your ~/.ssh directory to log in automatically. > > See ssh man page for more details. > > (2) Change the following settings in /etc/ssh/sshd_config and then > > restart sshd: > > PasswordAuthentication yes > finally, there seem to be some more problems. > after changing that, i tried to login as a normal user: > # ssh jonas@localhost > what happened, was that i ended up on a server of mine somewhere in the > internet. this server isn't used by my machines in any way, so i hardly > believe that 'nslookup localhost' gave it's ip-address. Hmm, localhost should give 127.0.0.1 and not anything else (check in /etc/hosts). Are you sure you don't have a IP conflict somewhere? If localhost resolves to the IP address of eth0, this would explain some problems. And there is a conflict, this could explain the rest. If this is not true, please post IP configuration (if you don't want to give the IP, just describe the class and the final value, without the subnet). > after doing this, 'host <any_machine>' gave segmentation fault. > i've the strong feeling that my uml installation is full of bugs and > minor mistakes, as a lot of strange or mysterious incidents happen here. > bye > jonas -- Paolo Giarrusso, aka Blaisorblade Linux registered user n. 292729 http://www.user-mode-linux.org/~blaisorblade |
From: Jonas M. <jo...@fr...> - 2004-11-25 22:26:23
|
On 25/11/2004 Blaisorblade wrote: > Hmm, localhost should give 127.0.0.1 and not anything else (check > in /etc/hosts). diana50:~# grep localhost /etc/hosts 127.0.0.1 localhost ::1 ip6-localhost ip6-loopback diana50:~# host localhost Segmentation fault i don't know why 'host' doesn't work but rather gives a Segmentation fault, but at least that's a new strange bug in my uml, that i believe nobody else has. > Are you sure you don't have a IP conflict somewhere? If localhost resolves to > the IP address of eth0, this would explain some problems. And there is a > conflict, this could explain the rest. i believe that my network is setup quite well. my real host has 192.168.23.34 as eth0, and 192.168.25.20 as tap0. it runs the uml_switch daemon. my uml has 192.168.25.24 as eth0 with 192.168.25.20 as gateway. i boot my uml with eth0=daemon, and connection to real host (and to internet) work quite well. even 'w3m http://localhost' shows the local apache startup page, so i'm quite confident that the problem is somewhere else than in my network setup. > If this is not true, please post IP configuration (if you don't want to give > the IP, just describe the class and the final value, without the subnet). is the information above enough, or do you need more details? bye jonas |
From: Jonas M. <jo...@fr...> - 2004-11-26 15:29:24
|
On 26/11/2004 Tim Warnock wrote: > > diana50:~# grep localhost /etc/hosts > > 127.0.0.1 localhost > > ::1 ip6-localhost ip6-loopback > > > > diana50:~# host localhost > > Segmentation fault > > What does your /etc/resolv.conf look like inside the uml? it has nameserver 192.168.23.34 search mejo.net mejo.net is my local domain name for network 192.168.23.0, and 192.168.23.34 is eth0 on my real host, which runs a bind9 daemon. bye jonas |
From: Allen C. <al...@us...> - 2004-11-24 17:09:34
|
What does "ssh -v localhost" show? What shows up in /var/log/auth.log? I recently hunted down a problem with sshd with one host that was corrected by adjusting a setting in /etc/hosts.allow. On Wednesday 24 November 2004 08:43 am, Jonas Meurer wrote: > hello, > > some services actually make problems with running in my kernel > 2.6.9-bb2 uml (debian/testing). > > In detail ssh starts, but rejects any login attempts from localhost > and other hosts: > # ssh localhost > Connection closed by 127.0.0.1 |
From: Jonas M. <jo...@fr...> - 2004-11-24 17:30:47
|
On 24/11/2004 Allen Chan wrote: > What does "ssh -v localhost" show? # ssh -v localhost OpenSSH_3.8.1p1 Debian-8.sarge.3, OpenSSL 0.9.7d 17 Mar 2004 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Connecting to localhost [127.0.0.1] port 22. debug1: Connection established. debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_3.8.1p1 Debian-8.sarge.3 debug1: match: OpenSSH_3.8.1p1 Debian-8.sarge.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.8.1p1 Debian-8.sarge.3 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'localhost' is known and matches the RSA host key. debug1: Found key in /root/.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /root/.ssh/identity debug1: Trying private key: /root/.ssh/id_rsa debug1: Trying private key: /root/.ssh/id_dsa debug1: Next authentication method: keyboard-interactive Connection closed by 127.0.0.1 > What shows up > in /var/log/auth.log? ahm nothing. nothing is printed to auth.log in the moment of ssh login attempt. bye jonas |
From: Blaisorblade <bla...@ya...> - 2004-11-25 05:19:22
|
On Wednesday 24 November 2004 14:43, Jonas Meurer wrote: > hello, > > some services actually make problems with running in my kernel 2.6.9-bb2 > uml (debian/testing). > In detail ssh starts, but rejects any login attempts from localhost and > other hosts: > # ssh localhost > Connection closed by 127.0.0.1 > as another example, Zope starts as well, but if i try to access it's > indexpage (http://localhost:9673), i get an empty page, without content. > any suggestions? Misconfigured the network or /etc/hosts or the hostname or the interfaces, maybe... > i read that there might be problems with kernel 2.6.9 and nodevfs. Not of this kind, I think... > Currently i use this setup, and i'll try with udev now. > bye > jonas Could you try something as simple as netcat (while running tcpdump) to verify what's going on? -- Paolo Giarrusso, aka Blaisorblade Linux registered user n. 292729 http://www.user-mode-linux.org/~blaisorblade |
From: Jonas M. <jo...@fr...> - 2004-11-25 22:19:46
|
On 25/11/2004 Blaisorblade wrote: > Misconfigured the network or /etc/hosts or the hostname or the interfaces, > maybe... i didn't have a /etc/hosts file, now i copied one from another host and modified it according to my hostname. hostname is 'diana50', and this is also in /etc/hosts ... i still have the same problems. > Could you try something as simple as netcat (while running tcpdump) to verify > what's going on? i don't know about netcat, but i can provide the output of tcpdump while i try to ssh from the real host to my uml. on my real host shell: jonas@realhost:~$ ssh 192.168.25.24 Connection closed by 192.168.25.24 jonas@realhost:~$ in my uml: diana50:~# tcpdump device eth0 entered promiscuous mode tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 22:17:29.377096 arp who-has 192.168.25.24 tell 192.168.25.20 22:17:29.401501 arp reply 192.168.25.24 is-at fe:fd:c0:a8:19:18 22:17:29.378306 IP 192.168.25.20.43543 > 192.168.25.24.ssh: S 4188329568:4188329568(0) win 5840 <mss 1460,sackOK,timestamp 30710171 0,nop,wscale 2> 22:17:29.378412 IP 192.168.25.24.ssh > 192.168.25.20.43543: S 2497851349:2497851349(0) ack 4188329569 win 5792 <mss 1460,sackOK,timestamp 71861 30710171,nop,wscale 2> 22:17:29.378922 IP 192.168.25.20.43543 > 192.168.25.24.ssh: . ack 1 win 1460 <nop,nop,timestamp 30710174 71861> 22:17:29.381140 IP 192.168.25.24.32769 > 192.168.23.34.domain: 40936+ PTR? 24.25.168.192.in-addr.arpa. (44) 22:17:29.389329 IP 192.168.25.24.ssh > 192.168.25.20.43543: P 1:42(41) ack 1 win 1448 <nop,nop,timestamp 71861 30710174> 22:17:29.390279 IP 192.168.23.34.domain > 192.168.25.24.32769: 40936 NXDomain 0/1/0 (121) 22:17:29.390401 IP 192.168.25.20.43543 > 192.168.25.24.ssh: . ack 42 win 1460 <nop,nop,timestamp 30710185 71861> 22:17:29.390414 IP 192.168.25.20.43543 > 192.168.25.24.ssh: P 1:42(41) ack 42 win 1460 <nop,nop,timestamp 30710185 71861> 22:17:29.391323 IP 192.168.25.24.32769 > 192.168.23.34.domain: 40937+ PTR? 20.25.168.192.in-addr.arpa. (44) 22:17:29.391405 IP 192.168.25.24.ssh > 192.168.25.20.43543: . ack 42 win 1448 <nop,nop,timestamp 71861 30710185> 22:17:29.398409 IP 192.168.25.20.43543 > 192.168.25.24.ssh: P 42:650(608) ack 42 win 1460 <nop,nop,timestamp 30710190 71861> 22:17:29.398454 IP 192.168.25.24.ssh > 192.168.25.20.43543: . ack 650 win 1752 <nop,nop,timestamp 71861 30710190> 22:17:29.400449 IP 192.168.25.24.ssh > 192.168.25.20.43543: P 42:650(608) ack 650 win 1752 <nop,nop,timestamp 71861 30710190> 22:17:29.401206 IP 192.168.23.34.domain > 192.168.25.24.32769: 40937 NXDomain 0/1/0 (121) 22:17:29.401299 IP 192.168.25.20.43543 > 192.168.25.24.ssh: P 650:674(24) ack 650 win 1764 <nop,nop,timestamp 30710196 71861> 22:17:29.402796 IP 192.168.25.24.32769 > 192.168.23.34.domain: 40938+ PTR? 34.23.168.192.in-addr.arpa. (44) 22:17:29.405184 IP 192.168.23.34.domain > 192.168.25.24.32769: 40938 ServFail 0/0/0 (44) 22:17:29.405342 IP 192.168.25.24.32769 > 192.168.23.34.domain: 40938+ PTR? 34.23.168.192.in-addr.arpa. (44) 22:17:29.405489 IP 192.168.23.34.domain > 192.168.25.24.32769: 40938 ServFail 0/0/0 (44) 22:17:29.408443 IP 192.168.25.24.ssh > 192.168.25.20.43543: P 650:802(152) ack 674 win 1752 <nop,nop,timestamp 71863 30710196> 22:17:29.411710 IP 192.168.25.20.43543 > 192.168.25.24.ssh: P 674:818(144) ack 802 win 2068 <nop,nop,timestamp 30710206 71863> 22:17:29.417204 IP 192.168.25.24.ssh > 192.168.25.20.43543: P 802:1266(464) ack 818 win 1752 <nop,nop,timestamp 71863 30710206> 22:17:29.419404 IP 192.168.25.20.43543 > 192.168.25.24.ssh: P 818:834(16) ack 1266 win 2372 <nop,nop,timestamp 30710214 71863> 22:17:29.440874 IP 192.168.25.24.ssh > 192.168.25.20.43543: . ack 834 win 1752 <nop,nop,timestamp 71867 30710214> 22:17:29.441012 IP 192.168.25.20.43543 > 192.168.25.24.ssh: P 834:882(48) ack 1266 win 2372 <nop,nop,timestamp 30710236 71867> 22:17:29.441163 IP 192.168.25.24.ssh > 192.168.25.20.43543: . ack 882 win 1752 <nop,nop,timestamp 71867 30710236> 22:17:29.441374 IP 192.168.25.24.ssh > 192.168.25.20.43543: P 1266:1314(48) ack 882 win 1752 <nop,nop,timestamp 71867 30710236> 22:17:29.441583 IP 192.168.25.20.43543 > 192.168.25.24.ssh: P 882:946(64) ack 1314 win 2372 <nop,nop,timestamp 30710236 71867> 22:17:29.456498 IP 192.168.25.24.32769 > 192.168.23.34.domain: 45324+ PTR? 20.25.168.192.in-addr.arpa. (44) 22:17:29.457111 IP 192.168.23.34.domain > 192.168.25.24.32769: 45324 NXDomain 0/1/0 (121) 22:17:29.457638 IP 192.168.25.24.ssh > 192.168.25.20.43543: P 1314:1394(80) ack 946 win 1752 <nop,nop,timestamp 71867 30710236> 22:17:29.457936 IP 192.168.25.20.43543 > 192.168.25.24.ssh: P 946:1042(96) ack 1394 win 2372 <nop,nop,timestamp 30710253 71867> 22:17:29.466209 IP 192.168.25.24.ssh > 192.168.25.20.43543: F 1394:1394(0) ack 1042 win 1752 <nop,nop,timestamp 71867 30710253> 22:17:29.467425 IP 192.168.25.20.43543 > 192.168.25.24.ssh: F 1042:1042(0) ack 1395 win 2372 <nop,nop,timestamp 30710262 71867> 22:17:29.467484 IP 192.168.25.24.ssh > 192.168.25.20.43543: . ack 1043 win 1752 <nop,nop,timestamp 71867 30710262> 192.168.25.20 is my real host, 192.168.25.24 is diana50, my uml. bye jonas |