When "syslog_enable=YES" in /etc/vsftpd/vsftpd.conf, ftp-client can not connect to ftp-server. All he gets is: $ ftp FQDN Connected to FQDN (IP). 500 OOPS: priv_sock_get_cmd Without "syslog_enable=YES" everything works as expected (but no ftp-logs sent to syslog, of course). This bug is present in the latest stable (3.0.2-r1) as well as in ~amd64 (3.0.2-r2). Reproducible: Always
Temporary solution: to add "seccomp_sandbox=NO" to /etc/vsftpd/vsftpd.conf. I'm not sure what it does (undocumented in vsftpd.conf manpage) but it works.
*** This bug has been marked as a duplicate of bug 443898 ***
I am NOT sure this is duplicate of 443898 bug. Bug-report 443898 simply says this error happens and does not state any conditions (I suppose with default configuration). Maybe it was so in net-ftp/vsftpd-3.0.0 But in this bug ftp-client gets error *only* if vsftpd-server has syslog_enable=YES in vsftpd.conf (which is not default), and the rest of config-parameters remain in default. I made test with vsftpd.conf modified this way (actually default settings): syslog_enable=NO seccomp_sandbox=YES No problem was detected, vsftpd works as expected. Another test (again, no problem detected): syslog_enable=NO seccomp_sandbox=NO Temporary fix as suggested previously also works without problem: syslog_enable=YES seccomp_sandbox=NO So the only config-combination that causes problem is: syslog_enable=YES seccomp_sandbox=YES Bug-report 443898 does not says anything about this (it actually makes no comment on syslog_enable), while this bug-report discovered conditions which must be met for this bug to occur...
We will not track the seccomp_sandbox problem in two separate bugs.
