From owner-freebsd-stable Thu Oct 25 18:38:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pimout1-int.prodigy.net (pimout1-ext.prodigy.net [207.115.63.77]) by hub.freebsd.org (Postfix) with ESMTP id A96C837B401 for ; Thu, 25 Oct 2001 18:38:24 -0700 (PDT) Received: from cliff (adsl-64-171-26-9.dsl.sntc01.pacbell.net [64.171.26.9]) by pimout1-int.prodigy.net (8.11.0/8.11.0) with SMTP id f9Q1cLI211476; Thu, 25 Oct 2001 21:38:22 -0400 Message-ID: <000501c15dc0$fd6f5340$6401a8c0@cliff> From: "Shaklee3" To: Cc: References: <21127483.1004058082060.JavaMail.imail@pugsly.excite.com> Subject: Re: 4.4-STABLE machine unusable (was Re: Openssh) Date: Thu, 25 Oct 2001 18:53:19 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-Mimeole: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hey I won't criticize you. I thought that was my dsl doing it but it does not happen on my windows box. Whenever I start doing something that involves traffic on my freebsd box it will not respond remotely for about 30 seconds. Whats up with it? ----- Original Message ----- From: To: Cc: ; ; ; ; Sent: Thursday, October 25, 2001 6:01 PM Subject: 4.4-STABLE machine unusable (was Re: Openssh) > Guys, > > You can say all you like, but something in stable is totally fscked up. As > soon as I log in and start doing anything that involves a bit of traffic > (e.g. tailing a file), the connection freezes and I have to kill it. sshd > doesn't die, so I can log in again. I can reproducibly freeze it by > doing... well practically anything: > > tail /var/log/messages, vi, cat, etc. all freeze the connection. Strangely > enough, > > head /var/log/messages > > works fine. > > At first I thought there was something wrong with the hardware, and that > perhaps the disks were screwed, that the recent filesystem changes caused > it, that pipe() was broken, lots of other things. But everything points to > ssh. > > "slogin -1" seems to work a bit longer, but also eventually freezes. > > Note that BPF is compiled in, so maybe there is some weird interaction > between ssh and bpf (as Colin Legendre suggested). > > I also thought it was a networking problem, but this machine is colocated > next to a Sun E450 with a similar setup (same subnet), which works fine. > > The client ssh I tried were all 2.9p2 (Solaris) and I think 2.9.9p2 > (Solaris). I also tried to log in from other FreeBSD machines (4.2 and > 4.3), but the effect was the same. > > $ make world > makeworld.log & > > generated a 6Mb file as expected. However, I could neither head nor tail > it. > > Interesting is that Putty (Windows SSH client) doesn't seem to have this > problem. I used it for quite a while and it didn't freeze. > > Please help me figure out what's going on. I don't have physical access to > the box, and without the ability to view or edit files there's very little I > can do. scp from a remote machine freezes. scp to a remote machine > freezes. There's no telnet or ftp. How can I even diagnose the problem? > > I am running out of ideas... :( > > John Wilson > > > > > > _______________________________________________________ > Send a cool gift with your E-Card > http://www.bluemountain.com/giftcenter/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message