Problems with sshd
I manage a small hobby website for some friends. The system has been running fine for quite a while, but suddenly the owners are having problems using WinSCP to transfer files to the server. The only thing that has changed recently is their internet service, and I'm inclined to think that's the cause. They are using a Verizon hotspot, whatever that is. (They live in the country, and options for internet service are limited.) But I'm the thorough sort, so I've enabled verbose logging and been googling for possible causes. One thing I've noticed is that their IP address changes quite frequently, but this snippet from the log shows that it also happens with the same IP. (I changed the username to protect their privacy.) Checking the archived logs, which go back several months, the error: ssh_msg_send: write entry appears occasionally whenever they login using WinSCP, so I assume it's some incompatibility about the program that rears its ugly head from time to time. I suspect it has no significance wrt this particular problem. Any thoughts on possible things to check for would be most welcome. Jul 15 07:19:33 www sshd[55490]: subsystem request for sftp Jul 15 07:30:03 www sshd[55529]: Accepted keyboard-interactive/pam for user from 166.248.39.94 port 40850 ssh2 Jul 15 07:30:03 www sshd[55544]: subsystem request for sftp Jul 15 07:39:56 www sshd[55564]: error: ssh_msg_send: write Jul 15 07:43:14 www sshd[55570]: error: ssh_msg_send: write Jul 15 07:46:39 www sshd[55596]: Accepted keyboard-interactive/pam for user from 166.248.39.94 port 40851 ssh2 Jul 15 07:46:40 www sshd[55608]: subsystem request for sftp Jul 15 07:49:31 www sshd[55610]: Accepted keyboard-interactive/pam for user from 166.248.39.172 port 27437 ssh2 Jul 15 07:49:32 www sshd[55613]: subsystem request for sftp Jul 15 07:56:59 www sshd[55634]: Accepted keyboard-interactive/pam for user from 166.248.39.172 port 27436 ssh2 Jul 15 07:57:00 www sshd[55637]: subsystem request for sftp Jul 15 08:26:15 www sshd[55751]: Accepted keyboard-interactive/pam for user from 166.248.39.172 port 27440 ssh2 Jul 15 08:26:15 www sshd[55755]: subsystem request for sftp Jul 15 08:30:59 www sshd[55779]: Accepted keyboard-interactive/pam for user from 166.248.39.172 port 48390 ssh2 Jul 15 08:30:59 www sshd[55782]: subsystem request for sftp Jul 15 08:47:07 www sshd[55852]: Accepted keyboard-interactive/pam for user from 166.248.39.172 port 27446 ssh2 Jul 15 08:47:07 www sshd[55855]: subsystem request for sftp Jul 15 09:01:26 www sshd[55897]: error: ssh_msg_send: write Jul 15 10:55:48 www sshd[56416]: Accepted keyboard-interactive/pam for user from 166.248.39.172 port 27426 ssh2 Jul 15 10:55:49 www sshd[56419]: subsystem request for sftp Jul 15 11:44:02 www sshd[56579]: Accepted keyboard-interactive/pam for user from 166.248.39.172 port 27449 ssh2 Jul 15 11:44:03 www sshd[56595]: subsystem request for sftp Jul 15 11:48:22 www sshd[56615]: Accepted keyboard-interactive/pam for user from 166.248.39.172 port 27433 ssh2 Jul 15 11:48:22 www sshd[56618]: subsystem request for sftp Jul 15 11:51:24 www sshd[56624]: Accepted keyboard-interactive/pam for user from 166.248.39.172 port 51389 ssh2 Jul 15 11:51:24 www sshd[56627]: subsystem request for sftp Jul 15 12:04:22 www sshd[56717]: Accepted keyboard-interactive/pam for user from 166.248.39.172 port 27430 ssh2 Jul 15 12:04:22 www sshd[56720]: subsystem request for sftp Jul 15 12:08:35 www sshd[56725]: Accepted keyboard-interactive/pam for user from 166.248.39.172 port 51383 ssh2 Jul 15 12:08:36 www sshd[56728]: subsystem request for sftp Jul 15 12:11:55 www sshd[56755]: Accepted keyboard-interactive/pam for user from 166.248.39.172 port 51361 ssh2 Jul 15 12:11:56 www sshd[56758]: subsystem request for sftp Jul 15 12:36:39 www sshd[56855]: Accepted keyboard-interactive/pam for user from 166.248.39.172 port 21268 ssh2 Jul 15 12:36:39 www sshd[56858]: subsystem request for sftp Jul 15 12:44:02 www sshd[56863]: Accepted keyboard-interactive/pam for user from 166.248.39.172 port 27452 ssh2 Jul 15 12:44:02 www sshd[56879]: subsystem request for sftp Jul 15 12:49:20 www sshd[56904]: Accepted keyboard-interactive/pam for user from 166.248.39.172 port 27454 ssh2 Jul 15 12:49:20 www sshd[56907]: subsystem request for sftp Jul 15 12:53:25 www sshd[56918]: Accepted keyboard-interactive/pam for user from 166.248.39.172 port 27424 ssh2 Jul 15 12:53:25 www sshd[56921]: subsystem request for sftp Jul 15 12:57:42 www sshd[56951]: Accepted keyboard-interactive/pam for user from 166.248.39.172 port 27425 ssh2 Jul 15 12:57:42 www sshd[56954]: subsystem request for sftp Paul Schmehl, If it isn't already obvious, my opinions are my own and not those of my employer. ** When intelligence argues with stupidity and bias, intelligence is bound to lose; intelligence has limits, but stupidity and bias have none.
Re: Problems with sshd
On 7/15/2011 10:12 PM, Paul Schmehl wrote: I manage a small hobby website for some friends. The system has been running fine for quite a while, but suddenly the owners are having problems using WinSCP to transfer files to the server. The only thing that has changed recently is their internet service, and I'm inclined to think that's the cause. They are using a Verizon hotspot, whatever that is. (They live in the country, and options for internet service are limited.) mobile hotspot - cellphone data connection rebroadcast on local wifi (google mifi). I've used Verizon's. Quality of the connection depends on the quality of the cellphone signal, and can range from very good to connected but unusable. But I'm the thorough sort, so I've enabled verbose logging and been googling for possible causes. One thing I've noticed is that their IP address changes quite frequently, but this snippet from the log shows that it also happens with the same IP. (I changed the username to protect their privacy.) They will get a new IP every time the device disconnects/reconnects. If they aren't turning it off and back on, this is an indicator of the connection dropping completely. Checking the archived logs, which go back several months, the error: ssh_msg_send: write entry appears occasionally whenever they login using WinSCP, so I assume it's some incompatibility about the program that rears its ugly head from time to time. I suspect it has no significance wrt this particular problem. We use winscp (occasionally over cellular) and get no such errors. I'm guessing the message means it couldn't write to the socket because the connection dropped. Any thoughts on possible things to check for would be most welcome. I think it's an inadequate data connection. Sometimes repositioning the mifi will help -- try the other side of the house or near a window. -- Noel Jones ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Problems with SSHD
Hi, I am having a big problem with the OpenSSH Daemon on my server. Whenever I am connected to the server and the connection is idle for a few seconds it gets disconnected. It's almost impossible to work from remote on the server when the connection is always getting dropped. The server is running FreeBSD angmar.domain.com 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 and the SSHD installed by sysinstall OpenSSH_4.5p1 FreeBSD-20061110, OpenSSL 0.9.7e-p1 25 Oct 2004 . I tried a complete FreeBSD reinstall but it did not help, I tried various settings like KeepAlive TCPKeepAlive but they did not help either. I upgraded OpenSSL to 0.9.8e and I installed OpenSSH 4.6p1 but it did not solve the problem. When I run SSH with loglevel debug I see this in the auth.log when I am getting disconnected: Read error from remote host 192.168.2.100: Connection reset by peer . When I use strace to monitor the process I see this on disconnect 643 wait4(-1, [WIFEXITED(s) WEXITSTATUS(s) == 0], WNOHANG, NULL) = 4975 643 wait4(-1, 0xbfbfdc9c, WNOHANG, NULL) = -1 ECHILD (No child processes) 643 syscall_416(0x14, 0, 0xbfbfdc20) = 0 643 syscall_417(0xbfbfdcd0) = -1 (errno 4) 643 select(7, [3 4], NULL, NULL, NULL unfinished ... I tried to find information's about syscall_417 but had no luck with that. I am stuck here and have no idea what to do. When I am connected to the server by FTP I don't get disconnected when the connection is idle ( no nohup or so being sent ) and when I connect by Telnet I also don't get disconnected when the connection is idle. I am not sure if I should add the dmesg output here for sys specs or not. I don't do it now but can give it if needed. I installed Debian on another HDD of the server today and I am not having any problems there. No SSH disconnects all the time. Thanks for any help. -Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with SSHD
On Sun, 11 Mar 2007 23:24:13 +0100 Alexander Schlichting [EMAIL PROTECTED] wrote: Hi, I am having a big problem with the OpenSSH Daemon on my server. Whenever I am connected to the server and the connection is idle for a few seconds it gets disconnected. It's almost impossible to work from remote on the server when the connection is always getting dropped. The server is running FreeBSD angmar.domain.com 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 and the SSHD installed by sysinstall OpenSSH_4.5p1 FreeBSD-20061110, OpenSSL 0.9.7e-p1 25 Oct 2004 . I tried a complete FreeBSD reinstall but it did not help, I tried various settings like KeepAlive TCPKeepAlive but they did not help either. I upgraded OpenSSL to 0.9.8e and I installed OpenSSH 4.6p1 but it did not solve the problem. When I run SSH with loglevel debug I see this in the auth.log when I am getting disconnected: Read error from remote host 192.168.2.100: Connection reset by peer . When I use strace to monitor the process I see this on disconnect 643 wait4(-1, [WIFEXITED(s) WEXITSTATUS(s) == 0], WNOHANG, NULL) = 4975 643 wait4(-1, 0xbfbfdc9c, WNOHANG, NULL) = -1 ECHILD (No child processes) 643 syscall_416(0x14, 0, 0xbfbfdc20) = 0 643 syscall_417(0xbfbfdcd0) = -1 (errno 4) 643 select(7, [3 4], NULL, NULL, NULL unfinished ... I tried to find information's about syscall_417 but had no luck with that. I am stuck here and have no idea what to do. When I am connected to the server by FTP I don't get disconnected when the connection is idle ( no nohup or so being sent ) and when I connect by Telnet I also don't get disconnected when the connection is idle. I am not sure if I should add the dmesg output here for sys specs or not. I don't do it now but can give it if needed. I installed Debian on another HDD of the server today and I am not having any problems there. No SSH disconnects all the time. Thanks for any help. -Alex out of curiosity, what kind of nic is in the machine, and did you try swapping it with another? cheers, jonathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems with sshd on FreeBSD 4.11-RELEASE
Hello, For reasons that I don't want to go into here, I have recently downgraded my principal FreeBSD server from 6.1 to 4.11-RELEASE. I did this by installing a fresh copy of FreeBSD 4.11 on a clean HD, and then I rsync'd all of my data over. Everything has been working fine, until I tried to SSH to the box this afternoon. While everything was working fine this morning, now sshd hangs up immediately on all clients that attempt to connect. In / var/log/messages, I see errors like this for every ssh connection attempt: May 31 15:21:06 redefine sshd[8543]: error: ssh_dss_sign: sign failed May 31 15:21:06 redefine sshd[8543]: fatal: mm_answer_sign: key_sign failed Google hasn't enlightened me at all. This was *just* working a few hours ago, and now, nada. Does anyone on this list have any ideas? Thanks, -Andy Reitz. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with sshd on FreeBSD 4.11-RELEASE
On May 31, 2006, at 3:26 PM, Andrew Reitz wrote: Hello, For reasons that I don't want to go into here, I have recently downgraded my principal FreeBSD server from 6.1 to 4.11-RELEASE. I did this by installing a fresh copy of FreeBSD 4.11 on a clean HD, and then I rsync'd all of my data over. Everything has been working fine, until I tried to SSH to the box this afternoon. While everything was working fine this morning, now sshd hangs up immediately on all clients that attempt to connect. In /var/log/messages, I see errors like this for every ssh connection attempt: May 31 15:21:06 redefine sshd[8543]: error: ssh_dss_sign: sign failed May 31 15:21:06 redefine sshd[8543]: fatal: mm_answer_sign: key_sign failed Google hasn't enlightened me at all. This was *just* working a few hours ago, and now, nada. Does anyone on this list have any ideas? Curiously, I just restarted sshd, and now things are working again. Has anybody ever seen this before? -Andy. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with sshd on FreeBSD 4.11-RELEASE
You may have an old key on the system you are ssh'ing to the downgraded server. Clear your ssh keys and try it again. -Derek At 05:26 PM 5/31/2006, Andrew Reitz wrote: Hello, For reasons that I don't want to go into here, I have recently downgraded my principal FreeBSD server from 6.1 to 4.11-RELEASE. I did this by installing a fresh copy of FreeBSD 4.11 on a clean HD, and then I rsync'd all of my data over. Everything has been working fine, until I tried to SSH to the box this afternoon. While everything was working fine this morning, now sshd hangs up immediately on all clients that attempt to connect. In / var/log/messages, I see errors like this for every ssh connection attempt: May 31 15:21:06 redefine sshd[8543]: error: ssh_dss_sign: sign failed May 31 15:21:06 redefine sshd[8543]: fatal: mm_answer_sign: key_sign failed Google hasn't enlightened me at all. This was *just* working a few hours ago, and now, nada. Does anyone on this list have any ideas? Thanks, -Andy Reitz. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Problems with sshd on FreeBSD 4.11-RELEASE
Curiously, I just restarted sshd, and now things are working again. Has anybody ever seen this before? -Andy. We had problems as well with FreeBSD 4.11 and sshd service hanging or breaking because of an OPENSSL lib which are required to run OpenSSH. Since then we moved out of 4.11 to 5.x ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
