35 comment

1. Sir,

   I have already used above commands but still the problem persist. When i use netstat then no pid/program name displays associated with it as below output.

   netstat -tulpn | grep :80

   tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN –

   Please help me in this situation what should i do.

   thankyou.

   vijay

2. you must sudo netstat or it won’t show you everything (sudo killall also)

3. Try to killall -9 php – this should solve your problem

4. The post has helped us a lot.

5. Is this step are applicable for Ubuntu 7.10? , if trying step no2 killall -9 httpd displaying no process kill however if trying to run step 3 its displying no such file or directory

6. Shortest solution to my problem. Thanks!

7. Thanks. Worked great !!

8. Thanks heaps, it solves my problem

   But do you know why it causes it? Looks like the apache2 crashes then it didn’t shut down the connection to port 80?

9. Some linux builds are configured to include conf.d/ssl.conf which binds to the hosts IP at port 443. This will generate the same error mentioned here.

   I resolved the problem by deleting the VirtualHost block in /etc/conf.d/ssl.conf and commenting out the Listen 443 directive.

   One might run into this if they define their own instance with SSL enabled.

10. Stop iis server from windows service
    (administrator tool -> services – > world wide web)

    And Start Apache

    1. Really? Really? Windows server? More like an oxymoron. Have fun playing as a “point ‘n’ click” admin wannabe, you little n00blet.

11. Ok. I had the same issue. I was running Apache2 so after running the:

    sudo netstat -tulpn| grep :80

    I saw that apache2 was listening to that port. I shut all apache2 services down by doing the following:

    sudo killall -9 apache2

    Then ran:
    netstat -tulpn| grep :80
    to see if there was anything left open. If no results, the process was killed.

    Then start up your apache2 services using:

    sudo /etc/init.d/apache2 start

    This resolved my problems! Hope this helps others. What a freakin pain!!!!!

    1. @Flyboy, thanks a lot, was helpful for me.

12. Saved me @$$, tanks!

13. Thanks for the comment to take out ssl :443. That’s what been stopping my restarting httpd.

14. Yes! Thanks for your post… you saved me :-)

15. it does’t help me…^(

16. And what if the system reboots? Than again port 80 is in use. So
    # netstat -tulpn| grep :80
    If port 80 is bind to httpd, kill all process:
    # killall -9 httpd
    Now start the httpd:
    # /etc/init.d/httpd start
    fixes the symtoms but it is not the solution.

17. Thank you so much, great post helpful

18. Thank you so much , This post solved my problem.

19. Thanks a lot, you saved my time :)

20. FIRST and foremost thing don’t keep more than 1 ssl config file in /etc/httpd/conf.d/ folder

21. Hi,

    I am also having same problem. I have killed and restarted the httpd, afterwards tried to start my server but it didnt worked….

22. Now its working thankssss………….

23. Screwed up almost 100s of pages for the solution of this issue…Just a small command “Killall” gave me a way from dark light..thkx guys….

24. How can I know that my board MAC address is already in use or it’s free to use. That means How can I identify that someone else is using my Board’s Mac address or not ? Please post the command if it’s available.

    Thanks in advance

25. If you are trying to bind to port 80, you may also want to try disabling selinux to see if that is an issue.

    echo 0 > /selinux/config /selinux/config <-enable

    The above tmp. sets that seeing and reboot clears it. To permanently set it to disabled

    vi /etc/selinux/config

    change
    SELINUX=enforcing
    to
    SELINUX=disabled

    Reboot or put in the temp change above until you can reboot.

26. Thanks, Ted Sheckler. What you mentioned is correct. There were two declarations of 443.

27. Great . Ted Sheckler

    here is best way to disable selinux ! kloxo is need to disable it :)
    change
    SELINUX=enforcing
    to
    SELINUX=disabled

28. hey.
    thanks a lot. it saved a lot of time.

29. Hi,

    Thanks for the post. It helped in getting up the server once again and save time & effort.
    RedHat & Httpd

30. Omg thank you!!!

31. Thank you my friend. You solved my problem

    1. This error is possible due to many reasons. one of the is as below.

       If you have configured your apache with a listen address that is hitting 80 or 443 and if there is a duplicate entry in the same file, you would see this issue.
       Ex: Listen marsp1uat01-indianrails.com:80 (You see if this is configured more than once in the same .conf file)
       So, just remove the duplicate entry, save the .conf file and try to start it.

32. Thank you Frend

    Still, have a question? Get help on our forum!