Results 1 to 10 of 11
Hello,
I have a problem when starting apache.
I get:
Starting httpd: (98 )Address already in use: make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down
...
- 01-09-2012 #1Just Joined!
- Join Date
- Jan 2012
- Posts
- 12
apache (could not bind to address 0.0.0.0:443)
Hello,
I have a problem when starting apache.
I get:
Starting httpd: (98 )Address already in use: make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down
Unable to open logs
[FAILED]
Running:
gives:Code:ps aux |grep httpd
root 7889 0.0 0.0 61224 760 pts/0 S+ 11:05 0:00 grep httpd
All posts I have seen online suggest that I need to have some process running. But it does not look that I have.
Please help, Tom
- 01-09-2012 #2should tell you if there is something occupying that portCode:
netstat -pantu | grep 443
linux user # 503963
- 01-09-2012 #3
It may also be, that you have multiple listen statements in the apache conf.
What is the output of:
Code:grep 443 /etc/httpd/*
You must always face the curtain with a bow.
- 01-09-2012 #4Just Joined!
- Join Date
- Jan 2012
- Posts
- 12
Thanks guys.
Booth commands do not display any result.
It might be that conf file might be wrong but I have run off ideas what might be wrong...
Tom
- 01-09-2012 #5
Sorry, it should be
There must be at least one match.Code:grep -r 443 /etc/httpd/*
You must always face the curtain with a bow.
- 01-09-2012 #6Just Joined!
- Join Date
- Jan 2012
- Posts
- 12
I do have response after running
but because I do not have more than 15 posts on my account I can not post itCode:grep -r 443 /etc/httpd/*
- 01-09-2012 #7
You cannot use links with < 15 posts, but afaik you are able to post text.
It would be good to use code tags like above.You must always face the curtain with a bow.
- 01-09-2012 #8
If code tags should fail, delete all http:// from your text
You must always face the curtain with a bow.
- 01-09-2012 #9Just Joined!
- Join Date
- Jan 2012
- Posts
- 12
I have deleted it and the system still does not take it

Today is not a good day for me
I have sent you private message with the response I got to the command.
You can post it for me so other people see it...
Thanks
- 01-09-2012 #10
I can, but I wont. Because I am not a proxy

Anyway, your apache conf files
contain "Listen 443" on multiple places.Code:/etc/httpd/conf/httpd.conf /etc/httpd/conf.d/ssl.conf /etc/httpd/conf.d/ssl.ori /etc/httpd/conf.d/ssl.ori.2
The ssl.ori* are probably not included, but ssl.conf is.
From the grep result I can also guess, that there might be other overlapping parts.
The "could not bind" error should go away, if you delete the second Listen 443, but it might be good to review all the config files.You must always face the curtain with a bow.


Reply With Quote