I have the same bug on 1.3.5~rc3-2.1. invoking restart manually gives ok for stop and ok for start, but the service is not actually started. adding a sleep 2 between stop and start in the init.d-script resolves the issue. This is running proftpd in StandAlone-mode.
>>I just had this bug start happening to me, and it happens even without logrotate being involved. Just running: >> /etc/init.d/proftpd restart Logrotate invokes a restart of proftpd after rotation, so - in effect - running logrotate or restarting proftpd manually results in the same parts of the init.d script being run. The funny thing is that adding the sleep command totally changes the output of the init.d-script. This is without sleep: root@nas /etc/proftpd # /etc/init.d/proftpd restart [ ok ] Stopping ftp server: proftpd. [ ok ] Starting ftp server: proftpd. (proftpd is not running now) And this is with sleep: root@nas /etc/proftpd # /etc/init.d/proftpd restart [ ok ] Stopping ftp server: proftpd. [....] Starting ftp server: proftpd2014-01-14 11:02:58,517 nas proftpd[3921] nas.weily.lan: 127.0.1.1:21 masquerading as x.x.x.x . ok
