Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 551
  • Last Modified:

httpd and vsftpd conflict


I'm not very familiar with tcp or config files in Linux.  I'm am trying to set up a FTP site using vsftp running on Redhat Linux Enterpise ES3.  I can get vsftpd to run fine when httpd is not running and httpd runs fine when vsftpd is not running.  

If httpd is running and I start vsftpd I get this message:

[root@argosy root]# service vsftpd start
Starting vsftpd for vsftpd:                                [  OK  ]
[root@argosy root]# service vsftpd status
vsftpd dead but subsys locked
[root@argosy root]#

If vsftpd is running and I start httpd I get this message:

Starting httpd: (98)Address already in use: make_sock: could not bind to address 'myhost':21
no listening sockets available, shutting down
Unable to open logs!

  • 2
1 Solution
Usually, httpd should not do anything with port 21. Sometimes port 81 is used as a secondary http port, so this might be a mistake in apache configs.

Start with /etc/httpd/conf/httpd.conf and all files in /etc/httpd/conf.d and find out why port 21 was used. Most likely you'll find a declaration of a virtualhost that is incorrect.
mwclassenAuthor Commented:
What I found was that /etc/httpd/conf.d/ssl.conf was listening on the same address.  I commented the line out and now they both get along.  Will that cause problems elsewhere?

Thanks, m1tk4
Whatever was there in ssl.conf with :21 is not something that is shipped by default, so you better ask the person who did this change in ssl.conf.

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now