cron — ProFTPD killed (signal 15) error — how to fix logrotate restart error? — Stack Overflow

Статья последний раз была обновлена 04.03.2023

ProFTPD on Ubuntu is being killed unexpectedly.

Log message:

$ tail /var/log/proftpd/proftpd.log.1
... ProFTPD killed (signal 15)
... ProFTPD 1.3.5rc3 standalone mode SHUTDOWN

Diagnosis: the time of the message is the same time that cron runs the logrotate command.

Google searches turn up various info about ProFTPD having a glitch on Debian-based systems due to log files, log rotations, and the ProFTPD server not restarting.

I will add a bounty for a solution to this. I’ve posted a workaround answer too, in case it’s helpful for others.

        asked May 14 ’14 at 23:14

closed as off-topic by Brad Larson Jun 20 ’14 at 21:52

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions on professional server- or networking-related infrastructure administration are off-topic for Stack Overflow unless they directly involve programming or programming tools. You may be able to get help on Server Fault." – Brad Larson

If this question can be reworded to fit the rules in the help center, please edit the question.

Cross-reference:                     – 0xC0000022L Jun 4 ’14 at 2:34

up vote 36 down vote accepted

Here’s a workaround solution thanks to

The problem is due to ProFTPD not stopping in time to be restarted.

The workaround is to edit the service file, to add a retry.


Find this line:

start-stop-daemon --stop --signal $SIGNAL --quiet --pidfile "$PIDFILE"

Change to this:

start-stop-daemon --stop --signal $SIGNAL --retry 1 --quiet --pidfile "$PIDFILE"

This change solved it for me.

Suggestions for improvements are most welcome.

        answered May 14 ’14 at 23:23
As I read comments in, its better to remove sleep 1 to avoid race condition. So it will become:  start-stop-daemon —stop —signal $SIGNAL —retry 1 —quiet —pidfile "$PIDFILE"                     – digz6666 Jul 20 ’14 at 6:06
@digz6666 Thanks, that’s good new info; I’m updating the answer.                     – joelparkerhenderson Jul 21 ’14 at 22:26
Thanks, this worked for me!                     – Luke Cousins Mar 1 at 9:36

The problem could also be having a password protected certificate then the service fails when automatically restarted w/o human intervention.

read here.

        answered May 22 ’14 at 14:42

Not the answer you’re looking for?                                   Browse other questions tagged cron logrotate proftpd  or ask your own question.                      

Губарь Маргарита Александровна