For what it may be worth ...
The messages in both cases are a bit different from the normal logged messages.
Wed Oct 3 15:25:49 2018 vsftpd [pid 12912]: "" from "10.0.192.124":
vsf_sysutil_recv_peek*Wed Oct 3 15:38:56 2018 [pid 13254] CONNECT: Client
"10.0.192.124"*
Mon Oct 1 15:55:48 2018 vsftpd [pid 10431]: "jcb" from "192.168.1.238":
priv_sock_get_cmdMon Oct 1 15:55:49 2018 [pid 10587] CONNECT: Client
"192.168.1.238"
In the case of the error, the literal "vsftpd" (program name, command
name?) is present. Normal logged messages do not have this.
Turns out these error messages are issued from various routines using the
die() function call. The thread is terminated. Note the different pid in
the lines for both samples.
For example, the error I see comes from privsock.c
char
priv_sock_get_cmd(int fd)
{
char res;
int retval = vsf_sysutil_read_loop(fd, &res, sizeof(res));
if (retval != sizeof(res))
{
die("priv_sock_get_cmd");
}
return res;
}
Marks error is similar.
This results in a "500 OOPS: priv_sock_get_cmd" sent on the command
connection, which is already closed or being closed.
The "priv_sock_get_cmd" is then send to the vsftpd.log file. This execution
follows a chain of calls leading to logging.c and vsf_log_commom() which
calls vsf_log_do_log_to_file() which adds a '\n' to each string before
writting it to the log. So, just by looking at the code (3.0.3) I don't see
the error.
If I get in the mood, I might compile the source and trace down the error.
In Mark Pace's case, I suspect he could use the xferlog option instead of
the vsftpd.log. This would allow him to catch the transfers without all the
rest of the messages.
LOL. Don't know if this helps or if anyone really cares.
Regards,
Jeff
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
