From owner-freebsd-stable@FreeBSD.ORG Tue Mar 11 19:21:38 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D3D55AC9 for ; Tue, 11 Mar 2014 19:21:38 +0000 (UTC) Received: from mail-vc0-x22d.google.com (mail-vc0-x22d.google.com [IPv6:2607:f8b0:400c:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8B5522EE for ; Tue, 11 Mar 2014 19:21:38 +0000 (UTC) Received: by mail-vc0-f173.google.com with SMTP id il7so4059430vcb.18 for ; Tue, 11 Mar 2014 12:21:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HLrVIKs501XcbsKGaM9/2fE2xVs4mnbjhz7PqMHYN+g=; b=oD3bcDokKFY6HtBiUMrTyf31Sb86TsaYOp2cA2b66YY0rW73xYbl9xbvagtFrabvRQ ayvEHbrSrLS2o207KsuGG1jBJUWjNFLCsA2kKy6KC9PMNQYKYjIAZJNCflt34Rb4hEeQ b8DgOxgqi9C+4ty6NFwsF21Lm0a3US/zYJG9PFOfhVwY9csb2r5vNGF8U+Mq6oqf9OLS vI3OvWGhDJyyzGHYo5Q/E5ocM1klIaW0YX3WTK7zeA0jCf404rfmngQpQ+RQXelBfmKe MiZiZvYUtfkcOKexO5QRoo5Ctp4TxyPKTtiDlqHKsDpmgjEuWXbRNVlGsguX5LFCSjQb nPww== MIME-Version: 1.0 X-Received: by 10.58.255.233 with SMTP id at9mr29949576ved.20.1394565697655; Tue, 11 Mar 2014 12:21:37 -0700 (PDT) Received: by 10.220.150.132 with HTTP; Tue, 11 Mar 2014 12:21:37 -0700 (PDT) In-Reply-To: References: <20140311155948.GR32089@funkthat.com> <531F606D.1030203@sentex.net> Date: Tue, 11 Mar 2014 14:21:37 -0500 Message-ID: Subject: Re: Two odd problems with STABLE-10 r262921 From: Karl Denninger To: Mike Tancsa Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Mar 2014 19:21:38 -0000 PS: I am not using "pf"; I AM using ipfw. On Tue, Mar 11, 2014 at 2:20 PM, Karl Denninger < tickerguydenninger@gmail.com> wrote: > Uh, yuck. > > [karl@NewFS ~/tmp]$ scp small outsidebox:xxx > small 100% 741 0.7KB/s > 00:00 > [karl@NewFS ~/tmp]$ scp xxx outsidebox:xxx > xxx 0% 0 0.0KB/s > --:-- ETAWrite failed: Permission denied > lost connection > [karl@NewFS ~/tmp]$ > > "xxx" is a file containing several megabytes of data. "outsidebox" is a > machine for which I have a cert and can scp back and forth. Coming FROM > there with a large file is fine. > > Something is very broken in the network code and I have nothing showing up > in the logs or on the console. > > It's not sendmail -- it's the system itself. > > This is an embedded Intel gigabit chipset (em1) on a Supermicro > motherboard and was working fine under 9.2. > > Ideas? This one will force me to find a way to roll back if I can't find > and fix it immediately. > > > > On Tue, Mar 11, 2014 at 2:13 PM, Mike Tancsa wrote: > >> On 3/11/2014 1:24 PM, Karl Denninger wrote: >> >>> Yeah it hasn't changed...... I turned on verbose logging and I'm not >>> getting anything in the logs on it -- what's even more-odd is that I can >>> telnet to port 25 on the MX gateway and hand-feed an email in there, and >>> it >>> works. If I turn off the signatures, it ALSO works. >>> Mar 11 12:13:59 NewFS sm-mta[11023]: s2BGax4D095381: SYSERR(root): >>> putbody: >>> write error: Permission denied >>> Mar 11 12:13:59 NewFS sm-mta[11023]: s2BGax4D095381: SYSERR(root): >>> timeout >>> writing message to gmail-smtp-in.l.google.com.: Permission denied >>> >> >> My initial guess is also firewall issue (permission denied).. A tcpdump >> of the packets after the sending host could help verify that. >> >> Perhaps a long shot, but the bug fixed in this commit >> >> http://svnweb.freebsd.org/base?view=revision&revision=263029 >> >> might also point to such behaviour, if states were being prematurely >> being expired ? I am thinking it would be a pretty busy box. >> >> Also, for debugging sendmail issues, I usually crank up on the command >> line >> >> given the Queue ID of >> >> Is2BFqO9e075993 >> >> sendmail -q -qIs2AKaMQp067733 -OLogLevel=15 -v >> >> >> >> >> ---Mike >> >> >> -- >> ------------------- >> Mike Tancsa, tel +1 519 651 3400 >> Sentex Communications, mike@sentex.net >> Providing Internet services since 1994 www.sentex.net >> Cambridge, Ontario Canada http://www.tancsa.com/ >> > >