Proftpd died after start

Hi,
I've just update proftpd using portmaster to version 1.3.4b

Code:
portmaster -b proftpd-1.3.4a_2

The service starts correctly, but after a few seconds he died without any error
Code:
# /usr/local/etc/rc.d/proftpd start
Starting proftpd.
# /usr/local/etc/rc.d/proftpd status
proftpd is running as pid 51698.
# /usr/local/etc/rc.d/proftpd status
proftpd is running as pid 51698.
# /usr/local/etc/rc.d/proftpd status
proftpd is running as pid 51698.
# /usr/local/etc/rc.d/proftpd status
proftpd is not running.

No error or warning in /var/log/messages
No entry in /var/log/xferlog

I've try to remove the package, deinstall and reinstall the port, but nothing works :(
I'm running FreeBSD 9.0 STABLE

Any help? :q
 
I temporarily solved by using pure-ftp, but I'd like to know the cause and solution of this problem.
I installed and updated proftpd dozens of times on dozens of machines over the past 5 years. Never had a problem.

Any help is very appreciated :)
 
You fixed it? I have the same problem, ProFTPD died after a few seconds, no error or something like that. I run manually /usr/local/sbin/proftpd or /usr/local/etc/rc.d/proftpd start

and after start died in a few seconds :(
 
A two year old question with no answer. Not very encouraging and quite frustrating to say the least. :-(
 
Last edited by a moderator:
(What really bugs me about this is that it's a server that has been running for a couple of years now with no problem. ProFTPD used to be really easy to get running.)
 
My problem with ftp/proftpd come with the upgrade of FreeBSD. Didn't have any problem earlier. I have reproduced the problem on a fresh install with 10.1-RELEASE-p1 and the latest ftp/proftpd port to date. Must be a bug.
 
My problem with ftp/ProFTPD come with the upgrade of FreeBSD. Didn't have any problem earlier. I have reproduced the problem on a fresh install with 10.1-RELEASE-p1 and the latest ftp/ProFTPD port to date. Must be a bug.

I'm still down on 9.3 for the time being. The first server was a fresh install but the daemon wouldn't stay running. The second was after a portsnap to a server that had been running flawlessly for several years (also a 9.3 machine). Oh well, I'm just really glad I saw your reply. That did fix it. :-D (just made my day too!)
 
Back
Top