Re: r286615: /usr/libexec/ftpd broken!
Marcel Moolenaar wrote: > It would have been so nice if man(1) would have told you that there > were 2 ftpd manpages and that you need to specify which one you want. > That should raise an eyebrow right away... I was bitten by a similar issue in the past. I now alias 'man' to 'man -a': -a Display all manual pages instead of just the first found for each page argument. cheers, Jamie ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r286615: /usr/libexec/ftpd broken!
> On Aug 18, 2015, at 09:05, Benjamin Kaduk wrote: > >> On Tue, 18 Aug 2015, Garrett Cooper wrote: >> >> >>> On Aug 18, 2015, at 08:57, Slawa Olhovchenkov wrote: >>> >>> On Tue, Aug 18, 2015 at 11:38:47AM -0400, Benjamin Kaduk wrote: >>> On Tue, 18 Aug 2015, Marcel Moolenaar wrote: >> On Aug 17, 2015, at 10:15 PM, O. Hartmann >> wrote: >> >> Port security/heimdal installs its own ftpd with its appropriate >> manpages. > > Ugh :-( I would argue that heimdal should not be in the business of supplying an ftpd. Kerberos-enabled ftp basically does not offer any advantages over scp. >>> >>> OPENSSH_NONE_CIPHER is OFF by default, i.e. ftp can give more speed. >> >> More pragmatically, there are less ssh clients (openssh or bust really), >> whereas there are more ftp clients (Firefox, Chrome, ftp(1), python, >> etc). > > I specifically said "Kerberos-enabled ftp". The things you listed do not > appear to qualify. Fair enough >.> ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r286615: /usr/libexec/ftpd broken!
On Tue, 18 Aug 2015, Garrett Cooper wrote: > > > On Aug 18, 2015, at 08:57, Slawa Olhovchenkov wrote: > > > > On Tue, Aug 18, 2015 at 11:38:47AM -0400, Benjamin Kaduk wrote: > > > >> On Tue, 18 Aug 2015, Marcel Moolenaar wrote: > >> > On Aug 17, 2015, at 10:15 PM, O. Hartmann > wrote: > > Port security/heimdal installs its own ftpd with its appropriate > manpages. > >>> > >>> Ugh :-( > >> > >> I would argue that heimdal should not be in the business of supplying an > >> ftpd. Kerberos-enabled ftp basically does not offer any advantages over > >> scp. > > > > OPENSSH_NONE_CIPHER is OFF by default, i.e. ftp can give more speed. > > More pragmatically, there are less ssh clients (openssh or bust really), > whereas there are more ftp clients (Firefox, Chrome, ftp(1), python, > etc). I specifically said "Kerberos-enabled ftp". The things you listed do not appear to qualify. -Ben ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r286615: /usr/libexec/ftpd broken!
On Tue, Aug 18, 2015 at 09:01:27AM -0700, Garrett Cooper wrote: > > > On Aug 18, 2015, at 08:57, Slawa Olhovchenkov wrote: > > > > On Tue, Aug 18, 2015 at 11:38:47AM -0400, Benjamin Kaduk wrote: > > > >> On Tue, 18 Aug 2015, Marcel Moolenaar wrote: > >> > On Aug 17, 2015, at 10:15 PM, O. Hartmann > wrote: > > Port security/heimdal installs its own ftpd with its appropriate > manpages. > >>> > >>> Ugh :-( > >> > >> I would argue that heimdal should not be in the business of supplying an > >> ftpd. Kerberos-enabled ftp basically does not offer any advantages over > >> scp. > > > > OPENSSH_NONE_CIPHER is OFF by default, i.e. ftp can give more speed. > > More pragmatically, there are less ssh clients (openssh or bust > really), whereas there are more ftp clients (Firefox, Chrome, > ftp(1), python, etc). In this context you must talk about kerberos-enabled ftp client. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r286615: /usr/libexec/ftpd broken!
> On Aug 18, 2015, at 08:57, Slawa Olhovchenkov wrote: > > On Tue, Aug 18, 2015 at 11:38:47AM -0400, Benjamin Kaduk wrote: > >> On Tue, 18 Aug 2015, Marcel Moolenaar wrote: >> On Aug 17, 2015, at 10:15 PM, O. Hartmann wrote: Port security/heimdal installs its own ftpd with its appropriate manpages. >>> >>> Ugh :-( >> >> I would argue that heimdal should not be in the business of supplying an >> ftpd. Kerberos-enabled ftp basically does not offer any advantages over >> scp. > > OPENSSH_NONE_CIPHER is OFF by default, i.e. ftp can give more speed. More pragmatically, there are less ssh clients (openssh or bust really), whereas there are more ftp clients (Firefox, Chrome, ftp(1), python, etc). Cheers, -NGie ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r286615: /usr/libexec/ftpd broken!
On Tue, Aug 18, 2015 at 11:38:47AM -0400, Benjamin Kaduk wrote: > On Tue, 18 Aug 2015, Marcel Moolenaar wrote: > > > > On Aug 17, 2015, at 10:15 PM, O. Hartmann > > > wrote: > > > > > > Port security/heimdal installs its own ftpd with its appropriate manpages. > > > > Ugh :-( > > I would argue that heimdal should not be in the business of supplying an > ftpd. Kerberos-enabled ftp basically does not offer any advantages over > scp. OPENSSH_NONE_CIPHER is OFF by default, i.e. ftp can give more speed. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r286615: /usr/libexec/ftpd broken!
On Tue, 18 Aug 2015, Marcel Moolenaar wrote: > > On Aug 17, 2015, at 10:15 PM, O. Hartmann > > wrote: > > > > Port security/heimdal installs its own ftpd with its appropriate manpages. > > Ugh :-( I would argue that heimdal should not be in the business of supplying an ftpd. Kerberos-enabled ftp basically does not offer any advantages over scp. -Ben ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r286615: /usr/libexec/ftpd broken!
> On Aug 18, 2015, at 7:46 AM, O. Hartmann wrote: > > Am Tue, 18 Aug 2015 07:35:25 -0700 > Marcel Moolenaar schrieb: > >> >>> On Aug 17, 2015, at 10:15 PM, O. Hartmann >>> wrote: >>> >>> Port security/heimdal installs its own ftpd with its appropriate manpages. >> >> Ugh :-( >> >> It would have been so nice if man(1) would have told you that there >> were 2 ftpd manpages and that you need to specify which one you want. >> That should raise an eyebrow right away... >> > > A hint came from this list, so I checked via locate the existence of multiple > ftpd and > ftpd.8[.gz] - and yes, I found several. I circumvent the problem by applying > to man the > option "-M/usr/share/man" which brought up the the correct manpage. I think distinct sections would be nice: 1-9 base system 1P-9P ports/packages 1L-9L local manpages. > And if it would not be hard ebough, I figured, that deleting port > security/heimdal didn't > erase the manpage on the particular machine I tested with :-/ Cached manpage, I presume? -- Marcel Moolenaar mar...@xcllnt.net signature.asc Description: Message signed with OpenPGP using GPGMail
Re: r286615: /usr/libexec/ftpd broken!
On Tue, Aug 18, 2015 at 07:35:25AM -0700, Marcel Moolenaar wrote: > > > On Aug 17, 2015, at 10:15 PM, O. Hartmann > > wrote: > > > > Port security/heimdal installs its own ftpd with its appropriate manpages. > > Ugh :-( > > It would have been so nice if man(1) would have told you that there > were 2 ftpd manpages and that you need to specify which one you want. > That should raise an eyebrow right away... Some time ago man(1) show all ftpd manpages. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r286615: /usr/libexec/ftpd broken!
Am Tue, 18 Aug 2015 07:35:25 -0700 Marcel Moolenaar schrieb: > > > On Aug 17, 2015, at 10:15 PM, O. Hartmann > > wrote: > > > > Port security/heimdal installs its own ftpd with its appropriate manpages. > > Ugh :-( > > It would have been so nice if man(1) would have told you that there > were 2 ftpd manpages and that you need to specify which one you want. > That should raise an eyebrow right away... > > -- > Marcel Moolenaar > mar...@xcllnt.net > A hint came from this list, so I checked via locate the existence of multiple ftpd and ftpd.8[.gz] - and yes, I found several. I circumvent the problem by applying to man the option "-M/usr/share/man" which brought up the the correct manpage. And if it would not be hard ebough, I figured, that deleting port security/heimdal didn't erase the manpage on the particular machine I tested with :-/ pgpHJ2L1KMeys.pgp Description: OpenPGP digital signature
Re: r286615: /usr/libexec/ftpd broken!
> On Aug 17, 2015, at 10:15 PM, O. Hartmann wrote: > > Port security/heimdal installs its own ftpd with its appropriate manpages. Ugh :-( It would have been so nice if man(1) would have told you that there were 2 ftpd manpages and that you need to specify which one you want. That should raise an eyebrow right away... -- Marcel Moolenaar mar...@xcllnt.net signature.asc Description: Message signed with OpenPGP using GPGMail
Re: r286615: /usr/libexec/ftpd broken!
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, Hello every thing is all right! Port security/heimdal installs its own ftpd with its appropriate manpages. Whenever I read the manpage, I got this heimdal-installed one and so, the whole configuration for FreeBSD's own ftpd daemon was bullshit according to the heimdal's version. especially the missing option "-D" (necessary for FreeBSD's ftpd going into daemon mode) and much more crucial, -a, which reflects the IP address listening on for FreeBSD's ftpd and for heimdal's one reflecting the authentication method (-a plain for plaintext). So, this maybe for the record. I guess in rare caeses others could run into this trap, too. Regards and thanks for the patience, Oliver ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r286615: /usr/libexec/ftpd broken!
On Fri, 14 Aug 2015 13:45:33 +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 have real issues understanding FreeBSD's ftpd! > > Man page "ftpusers(5)" states, that an entry "username allow" will allow > access to ftpd. But every user listed in /etc/ftpusers is denied access, no > matter whether there is "allow" appended to the entry or not! This is > strange. Whenever I delete a user's name from that file I wish to have access > to the ftpd service, that user can login - but addig the users even as > "username allow" (no * in the file, nothing else but the initial users names) > access is denied. > > I managed so far to start the ftpd via inetd - the service running > from /etc/rc.conf is still impossible. But operations, not even a simple > "ls", are possible since the service dies ... > > Either I'm some kind of dull and do not understand this brillant peice of > software, or there is something really fishy. This may have already been answered, but... A quick examination at the top of /etc/ftpusers reveals: # $FreeBSD: ... $ # # list of users disallowed any ftp access. # read by ftpd(8). FWIW --Chris > > regards and nice weekend, > > oh > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r286615: /usr/libexec/ftpd broken!
Am Fri, 14 Aug 2015 14:06:25 +0100 Matthew Seaman schrieb: > On 08/14/15 12:45, O. Hartmann wrote: > > Man page "ftpusers(5)" states, that an entry "username allow" will allow > > access > > to ftpd. But every user listed in /etc/ftpusers is denied access, no matter > > whether there is "allow" appended to the entry or not! This is strange. > > Whenever I delete a user's name from that file I wish to have access to the > > ftpd service, that user can login - but addig the users even as "username > > allow" (no * in the file, nothing else but the initial users names) access > > is > > denied. > > If you've got a ftpusers(5) that presumably comes from some ported > software -- doesn't exist in the base system. There is pam_ftpusers(8) > in base, although that doesn't seem to be in use by default. After you mentioned this, I checked and you're correct!The manpage was installed by package heimdal-1.5.3_4 according with another ftpd located under /usr/local/libexec. > > Traditionally 'ftpusers' was just a plain list of usernames or groups > (indicated by a leading '@' character). According to ftpd(8) it lists > the people *not* allowed access via FTP. I got this. > > However, other implementations of FTP servers have adopted the ftpusers > file and expanded its capabilities in various ways, by adding some > additional flag fields for each username. It depends on what ftpd > you're using exactly what syntax is used there. Properly ported > software should really be using /usr/local/etc/ftpusers though. I use NanoBSD for some very small appliance/server system and use the FreeBSD base system to start with - avoiding unncessary package installation. Reading the heimdal man page, configuring then according to heimdal's /usr/local/etc/ftpusers's explanations and then running the FreeBSD ftpd from its natural starting point with the misconfigured /etc/ftpusers will end in a mess. So it is my fault. But anyway, cleaning up the mess doesn't resolve the weird issues with FreeBSD's own ftpd. > > Cheers, > > Matthew > > > > Thank you for that hint. Regards, Oliver pgplTNtEFYTUh.pgp Description: OpenPGP digital signature
Re: r286615: /usr/libexec/ftpd broken!
On 08/14/15 12:45, O. Hartmann wrote: > Man page "ftpusers(5)" states, that an entry "username allow" will allow > access > to ftpd. But every user listed in /etc/ftpusers is denied access, no matter > whether there is "allow" appended to the entry or not! This is strange. > Whenever I delete a user's name from that file I wish to have access to the > ftpd service, that user can login - but addig the users even as "username > allow" (no * in the file, nothing else but the initial users names) access is > denied. If you've got a ftpusers(5) that presumably comes from some ported software -- doesn't exist in the base system. There is pam_ftpusers(8) in base, although that doesn't seem to be in use by default. Traditionally 'ftpusers' was just a plain list of usernames or groups (indicated by a leading '@' character). According to ftpd(8) it lists the people *not* allowed access via FTP. However, other implementations of FTP servers have adopted the ftpusers file and expanded its capabilities in various ways, by adding some additional flag fields for each username. It depends on what ftpd you're using exactly what syntax is used there. Properly ported software should really be using /usr/local/etc/ftpusers though. Cheers, Matthew signature.asc Description: OpenPGP digital signature
Re: r286615: /usr/libexec/ftpd broken!
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 have real issues understanding FreeBSD's ftpd! Man page "ftpusers(5)" states, that an entry "username allow" will allow access to ftpd. But every user listed in /etc/ftpusers is denied access, no matter whether there is "allow" appended to the entry or not! This is strange. Whenever I delete a user's name from that file I wish to have access to the ftpd service, that user can login - but addig the users even as "username allow" (no * in the file, nothing else but the initial users names) access is denied. I managed so far to start the ftpd via inetd - the service running from /etc/rc.conf is still impossible. But operations, not even a simple "ls", are possible since the service dies ... Either I'm some kind of dull and do not understand this brillant peice of software, or there is something really fishy. regards and nice weekend, oh ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r286615: /usr/libexec/ftpd broken!
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 COMMANDPID 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 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.. It seems to me as ftpd never binds to a TCP port ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r286615: /usr/libexec/ftpd broken!
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 COMMANDPID 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 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. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r286615: /usr/libexec/ftpd broken!
> 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 COMMANDPID 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 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.. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r286615: /usr/libexec/ftpd broken!
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 COMMANDPID 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 ... ;-) > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" 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. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r286615: /usr/libexec/ftpd broken!
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 COMMANDPID 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 ... ;-) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r286615: /usr/libexec/ftpd broken!
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, Of course. Attached you'll find the output of truss -o file /usr/libexec/ftpd -l oh ftpd_truss.out Description: Binary data ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r286615: /usr/libexec/ftpd broken!
Hi, 2015-08-11 7:40 GMT+02:00 O. Hartmann : > While ftpd daemon was working in r286590, it isn't anymore in r286615. I overlooked this: this is a pretty small set of revisions. Thanks for that. Unfortunately, if I looked at those 25 changes, I wouldn't know which one to blame... -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands KvK-nr.: 62051717 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r286615: /usr/libexec/ftpd broken!
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, -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands KvK-nr.: 62051717 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r286615: /usr/libexec/ftpd broken!
On Tue, 11 Aug 2015 07:40:41 +0200 "O. Hartmann" wrote: > While ftpd daemon was working in r286590, it isn't anymore in r286615. > Starting the daemon make it silently rejecting to start and disappears. > > Even manually started with option -d or/and -i doesn't work anymore. > > Does anybody else see this phenomenon? Scary ... > > > Regards, > oh > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" Just recompiled everything with r286617. 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 ... ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
