Using pure-ftpd but proftpd still try's to start?

Richard G

Verified User
Joined
Jul 6, 2008
Messages
14,187
Location
Maastricht
I'm confused.

I'm using pure-ftpd on all the servers.

But suddenly I just notice this happening on one of our servers, and already for a couple of days.

Dec 27 04:18:04 server14 proftpd[4890]: 85.10.xx.xx - Failed binding to ::, port 21: Address already in use
Dec 27 04:18:04 server14 proftpd[4890]: 85.10.xx.xx - Check the ServerType directive to ensure you are configured correctly.
Dec 27 04:18:04 server14 proftpd[4890]: 85.10.xx.xx - Unable to start proftpd; check logs for more details
Dec 27 04:18:04 server14 proftpd[4909]: 85.10.xx.xx - Failed binding to ::, port 21: Address already in use
Dec 27 04:18:04 server14 proftpd[4909]: 85.10.xx.xx - Check the ServerType directive to ensure you are configured correctly.
Dec 27 04:18:04 server14 proftpd[4909]: 85.10.xx.xx - Unable to start proftpd; check logs for more details

This happens several time a day and just like on the other servers, this is what chkconfig says:
proftpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off

Now how can it be that on this one server proftpd is still trying to start?
 
@Ben: Thank you for your reply. But as you can see from my quoted chkconfig line (unfortunately it shows smilies too), I don't need to do the chkconfig proftpd off, because it's already off.
Also to stop the proftpd service won't help.

Ofcourse I can remove the /etc/init.d/proftpd start script, but this still does not explain what is trying to start proftpd. And I rather search for causes, then just remove the startscript which probably would only cause error lines that the start script could not be found. :)
 
This only removes the configuration option to be able to set proftpd to on or off on startup.
It exists on all my other servers so there should be no need to remove. At this point it's set to off, so removing it won't make any difference.

I'm looking for a real solution or rather the cause of the problem.
 
@Ben29: removing it does not explain what's causing it, neither is this a solution because you have to remove more.
Because there are also startup scripts present in /etc/rc.0.d and /etc/rc1.d etc. and some more stuff.

So for removing this is the best solution:
rpm -e proftpd proftpd-standalone

Then it really will stop if I'm correct.

However, it still does not explain why every 3 days (I checked this), proftpd try's to start, while it's disabled. It shouldn't be that way in an operating system, so I'm still looking for somebody who still knows a good answer to that question.
 
seeing references to proftpd in backup task logs too even though its never been installed.
odd.
I have not noticed the startup in logs but could have overlooked it, but I am not seeing any issues either so have not prioritized finding the reason.
 
There is indeed no priority in finding the reason. It's just to satisfy my curiousity about why.
I can understand that it could happen in backup tasks. A backup script could be calling proftpd some how.

I only found it in /var/log/messages but maybe a user has some backup crontab which was calling it some way so you might be pointing to the cause.
 
I saw it first when no users on system (except admin) and testing backups, so if there is some task calling it I would think its base install related. have not had chance to track it down though
 
It might be some command which looks if proftpd is present and if yes trying to use it. Because I don't see it anymore after removing proftpd by using the rpm -e command I stated.
 
going to run that cmd momentarily, thanks for posting it.
wondering if centos 6.4/5 installed this.
 
No it's installed by DA custombuild when installing proftpd which is standard.
I changed from proftpd to pure-ftpd on all servers and that's the reason I don't need proftpd anymore.
 
did 2 fresh installs over last week and pure was the default with CB2, yet still had this showing up.
pro was never installed on my server, wonder if theres a dependency for some of the CB options enabled by default. cannot think of any that would have any ftp dependency though. dunno, just thinking out loud at this point.
 
since I ran that cmd and removed it I am not seeing mention anymore, but that probably also means I cannot track it all down to see how/why it happened.
all in all I am fine with this now, while it would be nice to know at least there is a corrective action.
 
think I may see why. in directadmin.conf are these line
ftpconfig=/etc/proftpd.conf
ftppasswd=/etc/proftpd.passwd
ftpvhosts=/etc/proftpd.vhosts.conf
wonder if thats why
 
Back
Top