From owner-freebsd-current@freebsd.org Wed Aug 12 05:25:08 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 275C599FF33 for ; Wed, 12 Aug 2015 05:25:08 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D38E4B80; Wed, 12 Aug 2015 05:25:07 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtp (envelope-from ) id <1ZPOXA-002qvO-CA>; Wed, 12 Aug 2015 07:25:04 +0200 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=freyja.zeit4.iv.bundesimmobilien.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (envelope-from ) id <1ZPOXA-000zx8-4N>; Wed, 12 Aug 2015 07:25:04 +0200 Date: Wed, 12 Aug 2015 07:24:58 +0200 From: "O. Hartmann" To: Garrett Cooper Cc: Ed Schouten , freebsd-current , "marcel@freebsd.org" Subject: Re: r286615: /usr/libexec/ftpd broken! Message-ID: <20150812072458.513d4d1d@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <8EE69EF5-9B5B-42D3-B7C3-781CFB11C4B0@gmail.com> References: <20150811074041.6700e943@freyja.zeit4.iv.bundesimmobilien.de> <20150811104451.2031fff2@freyja.zeit4.iv.bundesimmobilien.de> <20150811140536.5bc82e6f@freyja.zeit4.iv.bundesimmobilien.de> <20150811150158.661063da@freyja.zeit4.iv.bundesimmobilien.de> <8EE69EF5-9B5B-42D3-B7C3-781CFB11C4B0@gmail.com> Organization: FU Berlin X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 87.138.105.249 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Aug 2015 05:25:08 -0000 On Tue, 11 Aug 2015 11:01:16 -0700 Garrett Cooper wrote: > > > On Aug 11, 2015, at 06:01, O. Hartmann wrote: > > > > On Tue, 11 Aug 2015 14:05:36 +0200 > > "O. Hartmann" wrote: > > > >> On Tue, 11 Aug 2015 13:18:14 +0200 > >> Ed Schouten wrote: > >> > >>> Hi there, > >>> > >>> 2015-08-11 10:44 GMT+02:00 O. Hartmann : > >>>> ftpd starts sometimes, sporadically, and dies somewhere in the process. > >>>> Connections to the ftpd aren't possible. Sockstat doesn't even show up a > >>>> TCP/IP socket (21, ftp/tcp) where the daemon is supposed to listen for > >>>> incoming connection - I see only udp4 (connecting to > >>>> local_unbound/127.0.0.1:53). This is strange ... > >>> > >>> That's annoying. We should fix that. > >>> > >>> I recently made some changes to shutdown(2), but a grep reveals that > >>> ftpd doesn't call that function anywhere. Phew! The last changes made > >>> to ftpd are related to libxo. Adding marcel@, just to be sure. > >>> > >>> In the meantime, could you maybe run truss(8) over ftpd and send us the > >>> output? > >>> > >>> Thanks, > >> > >> I found one of our boxes, running > >> > >> FreeBSD 11.0-CURRENT #0 r286562: Mon Aug 10 08:14:52 CEST 2015 amd64 > >> > >> which runs ftpd without problems (started via service ftpd onestart): > >> > >> USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN > >> ADDRESS root ftpd 23139 3 dgram -> /var/run/logpriv > >> root ftpd 23139 5 tcp6 *:21 *:* > >> root ftpd 23139 6 tcp4 *:21 *:* > >> > >> > >> ... as expected ... and the daemon is running for several minutes for > >> now ... > >> > >> I will update the system as well and then ... see ... ;-) > > > > Well, after the update to FreeBSD 11.0-CURRENT #1 r286625: Tue Aug 11 > > 14:09:55 CEST 2015 amd64, ftpd is still working! This box is the only one > > that does nameresolution via DNS (external), while all non-functional > > systems do not have DNS resolution and work with local_unbound name > > resolving. > > Something is indeed weird with DNS under some circumstances as of a few weeks > ago. I'm trying to update my box and I'm seeing a ton of complaints about > unbound handing back A records instead of AAAA ones. My machine is on an IPv4 > NAT network, but I still find it odd how my last update a few weeks ago > started causing this.. Just another observation: ftpd dies whenever the hostname isn't set - do not know whether this is a bug or feature. On CURRENT r286625, not running unbound, ftpd can be started, lasts a couple of seconds and then drops sometimes out with the weird message "hostname nor servername provided, or not known" - or it drops silently. Hostname is set. the issue doesn't resolve if unbound is started. A box running CURRENT r286223 starts ftpd without the weird dropings and lasts until it is stopped.