TJ Saunders

Per https://github.com/proftpd/proftpd/issues/1314#issuecomment-1427011255, I'm re-examining code differences between 1.3.7e and 1.3.8. One that pertains to FTPS is the support for TLSv1.3. In your downloads, can you see which TLS protocol version...

If you're able to build ProFTPD from source, I recommend trying out the latest code in the `master` branch. I've made a couple of recent changes that may help in...

In addition, I've also filed https://github.com/proftpd/proftpd/issues/1729 to track support for KTLS via `SSL_sendfile` usage.

What does your `proftpd.conf` look like?

Interesting! From reading MySQL docs, I think this is occurring because of the "searched SQL UPDATE", _i.e._: ``` SQLNamedQuery updatecount UPDATE "count=count+1, accessed=now() WHERE userid='%u'" ftpuser ``` In this `UPDATE`...

In addition to the above, I should also have `mod_sql_mysql` look for these deadlock errors (`mysql_errno()` return value of [`ER_LOCK_DEADLOCK`](https://dev.mysql.com/doc/mysql-errors/8.0/en/server-error-reference.html#error_er_lock_deadlock), it appears), and retry the UPDATE (and INSERT?) statement a...

For my reference, `mod_sql_postgres` uses the [`PQresultStatus()`](https://www.postgresql.org/docs/current/libpq-exec.html#LIBPQ-PQRESULTSTATUS) function, which doesn't have any documented deadlock-looking errors. And `mod_sql_sqlite` already handles "database busy" errors with retries. This current behavior -- lacking retrying...

Could you try out https://github.com/proftpd/proftpd/pull/1668, see if it helps remedy this issue for you?

@maltris Would it be possible to see the rest of your ProFTPD configuration, to aid me in reproducing this behavior locally? Thanks!

For these files being uploaded via FTP, FTPS, or SFTP?