Re: 1.7.7: after upgrade lost ability to login via ssh
On Feb 8 21:14, Gerry Reno wrote: Something else I just discovered after upgrading to 1.7.7 is that I now have lost the ability to login via ssh. I have OpenSSH installed and running sshd as a service. Both password and keys accepted. But now neither means will work. # ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Fri Feb 4 17:19:26 2011 from LOCAL_CLIENT_MACHINE Connection to MACHINE_IP closed. So I increased verbosity but did not see anything obvious. http://cygwin.com/ml/cygwin/2011-02/msg00236.html Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.7: after upgrade lost ability to login via ssh
On 02/09/2011 05:54 AM, Corinna Vinschen wrote: On Feb 8 21:14, Gerry Reno wrote: Something else I just discovered after upgrading to 1.7.7 is that I now have lost the ability to login via ssh. I have OpenSSH installed and running sshd as a service. Both password and keys accepted. But now neither means will work. # ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Fri Feb 4 17:19:26 2011 from LOCAL_CLIENT_MACHINE Connection to MACHINE_IP closed. So I increased verbosity but did not see anything obvious. http://cygwin.com/ml/cygwin/2011-02/msg00236.html Corinna Looking around the only thing I can find is in the /var/log/sshd.log: Could not load host key: /etc/ssh_host_ecdsa_key Could not load host key: /etc/ssh_host_ecdsa_key Could not load host key: /etc/ssh_host_ecdsa_key Not sure this is related to the login problem. What is a ecdsa key? How do you generate it? Regards, Gerry -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.7: after upgrade lost ability to login via ssh
On Feb 9 11:34, Gerry Reno wrote: On 02/09/2011 05:54 AM, Corinna Vinschen wrote: On Feb 8 21:14, Gerry Reno wrote: Something else I just discovered after upgrading to 1.7.7 is that I now have lost the ability to login via ssh. I have OpenSSH installed and running sshd as a service. Both password and keys accepted. But now neither means will work. # ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Fri Feb 4 17:19:26 2011 from LOCAL_CLIENT_MACHINE Connection to MACHINE_IP closed. So I increased verbosity but did not see anything obvious. http://cygwin.com/ml/cygwin/2011-02/msg00236.html Corinna Looking around the only thing I can find is in the /var/log/sshd.log: Could not load host key: /etc/ssh_host_ecdsa_key Could not load host key: /etc/ssh_host_ecdsa_key Could not load host key: /etc/ssh_host_ecdsa_key Not sure this is related to the login problem. No. It's just a message. What is a ecdsa key? http://cygwin.com/ml/cygwin-announce/2011-01/msg00016.html How do you generate it? $ man ssh-keygen Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.7: after upgrade lost ability to login via ssh
On 02/08/2011 11:07 PM, Larry Hall (Cygwin) wrote: On 2/8/2011 9:14 PM, Gerry Reno wrote: Something else I just discovered after upgrading to 1.7.7 is that I now have lost the ability to login via ssh. I have OpenSSH installed and running sshd as a service. Both password and keys accepted. But now neither means will work. # ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Fri Feb 4 17:19:26 2011 from LOCAL_CLIENT_MACHINE Connection to MACHINE_IP closed. So I increased verbosity but did not see anything obvious. # ssh -v -i keypair1.pem Administrator@MACHINE_IP OpenSSH_5.2p1, OpenSSL 0.9.8k-fips 25 Mar 2009 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to MACHINE_IP [MACHINE_IP] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file keypair1.pem type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8 Does reverting OpenSSH to 5.7 make a difference? Downgraded to 5.7: bash-4.1$ sshd --version sshd: unknown option -- - OpenSSH_5.7p1, OpenSSL 0.9.8r 8 Feb 2011 From client: ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Wed Feb 9 12:54:08 2011 from LOCAL_CLIENT_IP Connection to MACHINE_IP closed. Nope. Still have the same problem. Connection is made but immediately closes. Regards, Gerry -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.7: after upgrade lost ability to login via ssh
On 02/09/2011 04:56 PM, Gerry Reno wrote: On 02/08/2011 11:07 PM, Larry Hall (Cygwin) wrote: On 2/8/2011 9:14 PM, Gerry Reno wrote: Something else I just discovered after upgrading to 1.7.7 is that I now have lost the ability to login via ssh. I have OpenSSH installed and running sshd as a service. Both password and keys accepted. But now neither means will work. # ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Fri Feb 4 17:19:26 2011 from LOCAL_CLIENT_MACHINE Connection to MACHINE_IP closed. So I increased verbosity but did not see anything obvious. # ssh -v -i keypair1.pem Administrator@MACHINE_IP OpenSSH_5.2p1, OpenSSL 0.9.8k-fips 25 Mar 2009 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to MACHINE_IP [MACHINE_IP] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file keypair1.pem type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8 Does reverting OpenSSH to 5.7 make a difference? Downgraded to 5.7: bash-4.1$ sshd --version sshd: unknown option -- - OpenSSH_5.7p1, OpenSSL 0.9.8r 8 Feb 2011 From client: ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Wed Feb 9 12:54:08 2011 from LOCAL_CLIENT_IP Connection to MACHINE_IP closed. Nope. Still have the same problem. Connection is made but immediately closes. I'm suspecting this is related to running Cygwin 1.7. In looking back though some notes I started having bash shell problems after upgrading from 1.5 to 1.7. Now on 1.7 if I try to run bash as a login shell it just gets Bad address or segfault errors and immediately exits the shell which also probably affects 'ssh'. I don't remember having any bash problems when I was running Cygwin 1.5 on this machine. My notes reflect screen copies showing bash able to run as a login shell without any problem. Regards, Gerry -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.7: after upgrade lost ability to login via ssh
On 02/09/2011 05:07 PM, Gerry Reno wrote: On 02/09/2011 04:56 PM, Gerry Reno wrote: On 02/08/2011 11:07 PM, Larry Hall (Cygwin) wrote: On 2/8/2011 9:14 PM, Gerry Reno wrote: Something else I just discovered after upgrading to 1.7.7 is that I now have lost the ability to login via ssh. I have OpenSSH installed and running sshd as a service. Both password and keys accepted. But now neither means will work. # ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Fri Feb 4 17:19:26 2011 from LOCAL_CLIENT_MACHINE Connection to MACHINE_IP closed. So I increased verbosity but did not see anything obvious. # ssh -v -i keypair1.pem Administrator@MACHINE_IP OpenSSH_5.2p1, OpenSSL 0.9.8k-fips 25 Mar 2009 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to MACHINE_IP [MACHINE_IP] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file keypair1.pem type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8 Does reverting OpenSSH to 5.7 make a difference? Downgraded to 5.7: bash-4.1$ sshd --version sshd: unknown option -- - OpenSSH_5.7p1, OpenSSL 0.9.8r 8 Feb 2011 From client: ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Wed Feb 9 12:54:08 2011 from LOCAL_CLIENT_IP Connection to MACHINE_IP closed. Nope. Still have the same problem. Connection is made but immediately closes. I'm suspecting this is related to running Cygwin 1.7. In looking back though some notes I started having bash shell problems after upgrading from 1.5 to 1.7. Now on 1.7 if I try to run bash as a login shell it just gets Bad address or segfault errors and immediately exits the shell which also probably affects 'ssh'. I don't remember having any bash problems when I was running Cygwin 1.5 on this machine. My notes reflect screen copies showing bash able to run as a login shell without any problem. And I did test with today's release of Bash 4.1.9-3 and nothing improved, same Bad address and segfault errors: bash-4.1$ bash --version GNU bash, version 4.1.9(3)-release (i686-pc-cygwin) Regards, Gerry -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.7: after upgrade lost ability to login via ssh
On 2/9/2011 5:07 PM, Gerry Reno wrote: On 02/09/2011 04:56 PM, Gerry Reno wrote: On 02/08/2011 11:07 PM, Larry Hall (Cygwin) wrote: On 2/8/2011 9:14 PM, Gerry Reno wrote: Something else I just discovered after upgrading to 1.7.7 is that I now have lost the ability to login via ssh. I have OpenSSH installed and running sshd as a service. Both password and keys accepted. But now neither means will work. # ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Fri Feb 4 17:19:26 2011 from LOCAL_CLIENT_MACHINE Connection to MACHINE_IP closed. So I increased verbosity but did not see anything obvious. # ssh -v -i keypair1.pem Administrator@MACHINE_IP OpenSSH_5.2p1, OpenSSL 0.9.8k-fips 25 Mar 2009 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to MACHINE_IP [MACHINE_IP] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file keypair1.pem type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8 Does reverting OpenSSH to 5.7 make a difference? Downgraded to 5.7: bash-4.1$ sshd --version sshd: unknown option -- - OpenSSH_5.7p1, OpenSSL 0.9.8r 8 Feb 2011 From client: ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Wed Feb 9 12:54:08 2011 from LOCAL_CLIENT_IP Connection to MACHINE_IP closed. Nope. Still have the same problem. Connection is made but immediately closes. I'm suspecting this is related to running Cygwin 1.7. In looking back though some notes I started having bash shell problems after upgrading from 1.5 to 1.7. Now on 1.7 if I try to run bash as a login shell it just gets Bad address or segfault errors and immediately exits the shell which also probably affects 'ssh'. I don't remember having any bash problems when I was running Cygwin 1.5 on this machine. My notes reflect screen copies showing bash able to run as a login shell without any problem. Yep, that's the way we all run by default (see cygwin.bat). I agree that if you're having problems getting bash to behave, it's best to focus on that issue first. Your ssh problems may just be another symptom of the same thing. How about sending cygcheck output (http://cygwin.com/problems.html)? There may be something helpful in that which someone on the list might pick up on. -- Larry _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.7: after upgrade lost ability to login via ssh
On 2/9/2011 5:56 PM, Gerry Reno wrote: On 02/09/2011 05:35 PM, Larry Hall (Cygwin) wrote: On 2/9/2011 5:07 PM, Gerry Reno wrote: On 02/09/2011 04:56 PM, Gerry Reno wrote: On 02/08/2011 11:07 PM, Larry Hall (Cygwin) wrote: On 2/8/2011 9:14 PM, Gerry Reno wrote: Something else I just discovered after upgrading to 1.7.7 is that I now have lost the ability to login via ssh. I have OpenSSH installed and running sshd as a service. Both password and keys accepted. But now neither means will work. # ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Fri Feb 4 17:19:26 2011 from LOCAL_CLIENT_MACHINE Connection to MACHINE_IP closed. So I increased verbosity but did not see anything obvious. # ssh -v -i keypair1.pem Administrator@MACHINE_IP OpenSSH_5.2p1, OpenSSL 0.9.8k-fips 25 Mar 2009 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to MACHINE_IP [MACHINE_IP] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file keypair1.pem type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8 Does reverting OpenSSH to 5.7 make a difference? Downgraded to 5.7: bash-4.1$ sshd --version sshd: unknown option -- - OpenSSH_5.7p1, OpenSSL 0.9.8r 8 Feb 2011 From client: ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Wed Feb 9 12:54:08 2011 from LOCAL_CLIENT_IP Connection to MACHINE_IP closed. Nope. Still have the same problem. Connection is made but immediately closes. I'm suspecting this is related to running Cygwin 1.7. In looking back though some notes I started having bash shell problems after upgrading from 1.5 to 1.7. Now on 1.7 if I try to run bash as a login shell it just gets Bad address or segfault errors and immediately exits the shell which also probably affects 'ssh'. I don't remember having any bash problems when I was running Cygwin 1.5 on this machine. My notes reflect screen copies showing bash able to run as a login shell without any problem. Yep, that's the way we all run by default (see cygwin.bat). I agree that if you're having problems getting bash to behave, it's best to focus on that issue first. Your ssh problems may just be another symptom of the same thing. How about sending cygcheck output (http://cygwin.com/problems.html)? There may be something helpful in that which someone on the list might pick up on. Ok, ran a new cygcheck and attached it. OK, thanks. What went wrong with the first installation? I notice that this is using TS. Can you try experiment with this machine locally? Or perhaps just try: http://cygwin.com/faq-nochunks.html#faq.setup.setup-fails-on-ts -- Larry _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.7: after upgrade lost ability to login via ssh
On 02/09/2011 06:43 PM, Larry Hall (Cygwin) wrote: On 2/9/2011 5:56 PM, Gerry Reno wrote: On 02/09/2011 05:35 PM, Larry Hall (Cygwin) wrote: On 2/9/2011 5:07 PM, Gerry Reno wrote: On 02/09/2011 04:56 PM, Gerry Reno wrote: On 02/08/2011 11:07 PM, Larry Hall (Cygwin) wrote: On 2/8/2011 9:14 PM, Gerry Reno wrote: Something else I just discovered after upgrading to 1.7.7 is that I now have lost the ability to login via ssh. I have OpenSSH installed and running sshd as a service. Both password and keys accepted. But now neither means will work. # ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Fri Feb 4 17:19:26 2011 from LOCAL_CLIENT_MACHINE Connection to MACHINE_IP closed. So I increased verbosity but did not see anything obvious. # ssh -v -i keypair1.pem Administrator@MACHINE_IP OpenSSH_5.2p1, OpenSSL 0.9.8k-fips 25 Mar 2009 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to MACHINE_IP [MACHINE_IP] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file keypair1.pem type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8 Does reverting OpenSSH to 5.7 make a difference? Downgraded to 5.7: bash-4.1$ sshd --version sshd: unknown option -- - OpenSSH_5.7p1, OpenSSL 0.9.8r 8 Feb 2011 From client: ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Wed Feb 9 12:54:08 2011 from LOCAL_CLIENT_IP Connection to MACHINE_IP closed. Nope. Still have the same problem. Connection is made but immediately closes. I'm suspecting this is related to running Cygwin 1.7. In looking back though some notes I started having bash shell problems after upgrading from 1.5 to 1.7. Now on 1.7 if I try to run bash as a login shell it just gets Bad address or segfault errors and immediately exits the shell which also probably affects 'ssh'. I don't remember having any bash problems when I was running Cygwin 1.5 on this machine. My notes reflect screen copies showing bash able to run as a login shell without any problem. Yep, that's the way we all run by default (see cygwin.bat). I agree that if you're having problems getting bash to behave, it's best to focus on that issue first. Your ssh problems may just be another symptom of the same thing. How about sending cygcheck output (http://cygwin.com/problems.html)? There may be something helpful in that which someone on the list might pick up on. Ok, ran a new cygcheck and attached it. OK, thanks. What went wrong with the first installation? I notice that this is using TS. Can you try experiment with this machine locally? Or perhaps just try: http://cygwin.com/faq-nochunks.html#faq.setup.setup-fails-on-ts I reduced DEP down to just Windows executables and dlls and then rebooted. And it actually seemed to make the problem worse: bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ So DEP in is play here but sort of inverse from what I'd expect. There was no switch now to totally disable it. I guess they want you to fiddle with the registry to turn it all the way off. Regards, Gerry -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation:
Re: 1.7.7: after upgrade lost ability to login via ssh
On 02/09/2011 07:21 PM, Gerry Reno wrote: On 02/09/2011 06:43 PM, Larry Hall (Cygwin) wrote: On 2/9/2011 5:56 PM, Gerry Reno wrote: On 02/09/2011 05:35 PM, Larry Hall (Cygwin) wrote: On 2/9/2011 5:07 PM, Gerry Reno wrote: On 02/09/2011 04:56 PM, Gerry Reno wrote: On 02/08/2011 11:07 PM, Larry Hall (Cygwin) wrote: On 2/8/2011 9:14 PM, Gerry Reno wrote: Something else I just discovered after upgrading to 1.7.7 is that I now have lost the ability to login via ssh. I have OpenSSH installed and running sshd as a service. Both password and keys accepted. But now neither means will work. # ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Fri Feb 4 17:19:26 2011 from LOCAL_CLIENT_MACHINE Connection to MACHINE_IP closed. So I increased verbosity but did not see anything obvious. # ssh -v -i keypair1.pem Administrator@MACHINE_IP OpenSSH_5.2p1, OpenSSL 0.9.8k-fips 25 Mar 2009 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to MACHINE_IP [MACHINE_IP] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file keypair1.pem type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8 Does reverting OpenSSH to 5.7 make a difference? Downgraded to 5.7: bash-4.1$ sshd --version sshd: unknown option -- - OpenSSH_5.7p1, OpenSSL 0.9.8r 8 Feb 2011 From client: ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Wed Feb 9 12:54:08 2011 from LOCAL_CLIENT_IP Connection to MACHINE_IP closed. Nope. Still have the same problem. Connection is made but immediately closes. I'm suspecting this is related to running Cygwin 1.7. In looking back though some notes I started having bash shell problems after upgrading from 1.5 to 1.7. Now on 1.7 if I try to run bash as a login shell it just gets Bad address or segfault errors and immediately exits the shell which also probably affects 'ssh'. I don't remember having any bash problems when I was running Cygwin 1.5 on this machine. My notes reflect screen copies showing bash able to run as a login shell without any problem. Yep, that's the way we all run by default (see cygwin.bat). I agree that if you're having problems getting bash to behave, it's best to focus on that issue first. Your ssh problems may just be another symptom of the same thing. How about sending cygcheck output (http://cygwin.com/problems.html)? There may be something helpful in that which someone on the list might pick up on. Ok, ran a new cygcheck and attached it. OK, thanks. What went wrong with the first installation? I notice that this is using TS. Can you try experiment with this machine locally? Or perhaps just try: http://cygwin.com/faq-nochunks.html#faq.setup.setup-fails-on-ts I reduced DEP down to just Windows executables and dlls and then rebooted. And it actually seemed to make the problem worse: bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ So DEP in is play here but sort of inverse from what I'd expect. There was no
Re: 1.7.7: after upgrade lost ability to login via ssh
On 02/09/2011 08:04 PM, Gerry Reno wrote: On 02/09/2011 07:21 PM, Gerry Reno wrote: On 02/09/2011 06:43 PM, Larry Hall (Cygwin) wrote: On 2/9/2011 5:56 PM, Gerry Reno wrote: On 02/09/2011 05:35 PM, Larry Hall (Cygwin) wrote: On 2/9/2011 5:07 PM, Gerry Reno wrote: On 02/09/2011 04:56 PM, Gerry Reno wrote: On 02/08/2011 11:07 PM, Larry Hall (Cygwin) wrote: On 2/8/2011 9:14 PM, Gerry Reno wrote: Something else I just discovered after upgrading to 1.7.7 is that I now have lost the ability to login via ssh. I have OpenSSH installed and running sshd as a service. Both password and keys accepted. But now neither means will work. # ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Fri Feb 4 17:19:26 2011 from LOCAL_CLIENT_MACHINE Connection to MACHINE_IP closed. So I increased verbosity but did not see anything obvious. # ssh -v -i keypair1.pem Administrator@MACHINE_IP OpenSSH_5.2p1, OpenSSL 0.9.8k-fips 25 Mar 2009 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to MACHINE_IP [MACHINE_IP] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file keypair1.pem type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8 Does reverting OpenSSH to 5.7 make a difference? Downgraded to 5.7: bash-4.1$ sshd --version sshd: unknown option -- - OpenSSH_5.7p1, OpenSSL 0.9.8r 8 Feb 2011 From client: ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Wed Feb 9 12:54:08 2011 from LOCAL_CLIENT_IP Connection to MACHINE_IP closed. Nope. Still have the same problem. Connection is made but immediately closes. I'm suspecting this is related to running Cygwin 1.7. In looking back though some notes I started having bash shell problems after upgrading from 1.5 to 1.7. Now on 1.7 if I try to run bash as a login shell it just gets Bad address or segfault errors and immediately exits the shell which also probably affects 'ssh'. I don't remember having any bash problems when I was running Cygwin 1.5 on this machine. My notes reflect screen copies showing bash able to run as a login shell without any problem. Yep, that's the way we all run by default (see cygwin.bat). I agree that if you're having problems getting bash to behave, it's best to focus on that issue first. Your ssh problems may just be another symptom of the same thing. How about sending cygcheck output (http://cygwin.com/problems.html)? There may be something helpful in that which someone on the list might pick up on. Ok, ran a new cygcheck and attached it. OK, thanks. What went wrong with the first installation? I notice that this is using TS. Can you try experiment with this machine locally? Or perhaps just try: http://cygwin.com/faq-nochunks.html#faq.setup.setup-fails-on-ts I reduced DEP down to just Windows executables and dlls and then rebooted. And it actually seemed to make the problem worse: bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$
Re: 1.7.7: after upgrade lost ability to login via ssh
On 02/09/2011 08:21 PM, Gerry Reno wrote: On 02/09/2011 08:04 PM, Gerry Reno wrote: On 02/09/2011 07:21 PM, Gerry Reno wrote: On 02/09/2011 06:43 PM, Larry Hall (Cygwin) wrote: On 2/9/2011 5:56 PM, Gerry Reno wrote: On 02/09/2011 05:35 PM, Larry Hall (Cygwin) wrote: On 2/9/2011 5:07 PM, Gerry Reno wrote: On 02/09/2011 04:56 PM, Gerry Reno wrote: On 02/08/2011 11:07 PM, Larry Hall (Cygwin) wrote: On 2/8/2011 9:14 PM, Gerry Reno wrote: Something else I just discovered after upgrading to 1.7.7 is that I now have lost the ability to login via ssh. I have OpenSSH installed and running sshd as a service. Both password and keys accepted. But now neither means will work. # ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Fri Feb 4 17:19:26 2011 from LOCAL_CLIENT_MACHINE Connection to MACHINE_IP closed. So I increased verbosity but did not see anything obvious. # ssh -v -i keypair1.pem Administrator@MACHINE_IP OpenSSH_5.2p1, OpenSSL 0.9.8k-fips 25 Mar 2009 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to MACHINE_IP [MACHINE_IP] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file keypair1.pem type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8 Does reverting OpenSSH to 5.7 make a difference? Downgraded to 5.7: bash-4.1$ sshd --version sshd: unknown option -- - OpenSSH_5.7p1, OpenSSL 0.9.8r 8 Feb 2011 From client: ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Wed Feb 9 12:54:08 2011 from LOCAL_CLIENT_IP Connection to MACHINE_IP closed. Nope. Still have the same problem. Connection is made but immediately closes. I'm suspecting this is related to running Cygwin 1.7. In looking back though some notes I started having bash shell problems after upgrading from 1.5 to 1.7. Now on 1.7 if I try to run bash as a login shell it just gets Bad address or segfault errors and immediately exits the shell which also probably affects 'ssh'. I don't remember having any bash problems when I was running Cygwin 1.5 on this machine. My notes reflect screen copies showing bash able to run as a login shell without any problem. Yep, that's the way we all run by default (see cygwin.bat). I agree that if you're having problems getting bash to behave, it's best to focus on that issue first. Your ssh problems may just be another symptom of the same thing. How about sending cygcheck output (http://cygwin.com/problems.html)? There may be something helpful in that which someone on the list might pick up on. Ok, ran a new cygcheck and attached it. OK, thanks. What went wrong with the first installation? I notice that this is using TS. Can you try experiment with this machine locally? Or perhaps just try: http://cygwin.com/faq-nochunks.html#faq.setup.setup-fails-on-ts I reduced DEP down to just Windows executables and dlls and then rebooted. And it actually seemed to make the problem worse: bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash: /etc/profile.d/lapack0.sh: Bad address bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done) bash-4.1$ (for p in $(ls /etc/profile.d/*.sh);do . $p;done)
1.7.7: after upgrade lost ability to login via ssh
Something else I just discovered after upgrading to 1.7.7 is that I now have lost the ability to login via ssh. I have OpenSSH installed and running sshd as a service. Both password and keys accepted. But now neither means will work. # ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Fri Feb 4 17:19:26 2011 from LOCAL_CLIENT_MACHINE Connection to MACHINE_IP closed. So I increased verbosity but did not see anything obvious. # ssh -v -i keypair1.pem Administrator@MACHINE_IP OpenSSH_5.2p1, OpenSSL 0.9.8k-fips 25 Mar 2009 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to MACHINE_IP [MACHINE_IP] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file keypair1.pem type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8 debug1: match: OpenSSH_5.8 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.2 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) 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 'MACHINE_IP' is known and matches the RSA host key. debug1: Found key in /root/.ssh/known_hosts:49 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,password,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: keypair1.pem debug1: read PEM private key done: type RSA debug1: Authentication succeeded (publickey). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessi...@openssh.com debug1: Entering interactive session. debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 Last login: Tue Feb 8 11:18:47 2011 from LOCAL_CLIENT_MACHINE debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug1: client_input_channel_req: channel 0 rtype e...@openssh.com reply 0 debug1: channel 0: free: client-session, nchannels 1 Connection to MACHINE_IP closed. Transferred: sent 2224, received 2144 bytes, in 2.9 seconds Bytes per second: sent 764.9, received 737.4 debug1: Exit status 0 The session looks like its connected ok but then it immediately disconnects. Anyone else seen this on upgrade or have an idea how to fix this? Regards, Gerry -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.7: after upgrade lost ability to login via ssh
On 2/8/2011 9:14 PM, Gerry Reno wrote: Something else I just discovered after upgrading to 1.7.7 is that I now have lost the ability to login via ssh. I have OpenSSH installed and running sshd as a service. Both password and keys accepted. But now neither means will work. # ssh -i keypair1.pem Administrator@MACHINE_IP Last login: Fri Feb 4 17:19:26 2011 from LOCAL_CLIENT_MACHINE Connection to MACHINE_IP closed. So I increased verbosity but did not see anything obvious. # ssh -v -i keypair1.pem Administrator@MACHINE_IP OpenSSH_5.2p1, OpenSSL 0.9.8k-fips 25 Mar 2009 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to MACHINE_IP [MACHINE_IP] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file keypair1.pem type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8 Does reverting OpenSSH to 5.7 make a difference? -- Larry _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
