Date: Tue, 11 Aug 2015 11:01:16 -0700 From: Garrett Cooper <yaneurabeya@gmail.com> To: "O. Hartmann" <ohartman@zedat.fu-berlin.de> Cc: Ed Schouten <ed@nuxi.nl>, freebsd-current <freebsd-current@freebsd.org>, "marcel@freebsd.org" <marcel@freebsd.org> Subject: Re: r286615: /usr/libexec/ftpd broken! Message-ID: <8EE69EF5-9B5B-42D3-B7C3-781CFB11C4B0@gmail.com> In-Reply-To: <20150811150158.661063da@freyja.zeit4.iv.bundesimmobilien.de> References: <20150811074041.6700e943@freyja.zeit4.iv.bundesimmobilien.de> <20150811104451.2031fff2@freyja.zeit4.iv.bundesimmobilien.de> <CABh_MKm9tD=Fa1MZTGLUkF=MF7y%2Bf8Oy6n3oy5Ty93pWrBohHA@mail.gmail.com> <20150811140536.5bc82e6f@freyja.zeit4.iv.bundesimmobilien.de> <20150811150158.661063da@freyja.zeit4.iv.bundesimmobilien.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Aug 11, 2015, at 06:01, O. Hartmann <ohartman@zedat.fu-berlin.de> wrote= : >=20 > On Tue, 11 Aug 2015 14:05:36 +0200 > "O. Hartmann" <ohartman@zedat.fu-berlin.de> wrote: >=20 >> On Tue, 11 Aug 2015 13:18:14 +0200 >> Ed Schouten <ed@nuxi.nl> wrote: >>=20 >>> Hi there, >>>=20 >>> 2015-08-11 10:44 GMT+02:00 O. Hartmann <ohartman@zedat.fu-berlin.de>: >>>> 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 ... >>>=20 >>> That's annoying. We should fix that. >>>=20 >>> 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. >>>=20 >>> In the meantime, could you maybe run truss(8) over ftpd and send us the >>> output? >>>=20 >>> Thanks, >>=20 >> I found one of our boxes, running >>=20 >> FreeBSD 11.0-CURRENT #0 r286562: Mon Aug 10 08:14:52 CEST 2015 amd64 >>=20 >> which runs ftpd without problems (started via service ftpd onestart): >>=20 >> 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 *:* >>=20 >>=20 >> ... as expected ... and the daemon is running for several minutes for now= ... >>=20 >> I will update the system as well and then ... see ... ;-) >=20 > Well, after the update to FreeBSD 11.0-CURRENT #1 r286625: Tue Aug 11 14:0= 9:55 > CEST 2015 amd64, ftpd is still working! This box is the only one that doe= s > 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 week= s ago. I'm trying to update my box and I'm seeing a ton of complaints about u= nbound 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 sta= rted causing this..=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8EE69EF5-9B5B-42D3-B7C3-781CFB11C4B0>