21 reputation
3
bio website
location
age
visits member for 1 year, 11 months
seen Aug 20 at 10:48

May
28
awarded  Popular Question
Dec
4
comment Can't start Apache - Address already in use - httpd is stopped
Thanks for your answer. It is running, but isn't working, if you see what I mean? It's not accepting incoming requests. I have killed it and started it manually and it works fine. Turns out that it's because of a passphrased SSL certificate, but removing the passphrase just introduces a new fault. I've edited the original to elaborate further
Dec
4
comment Can't start Apache - Address already in use - httpd is stopped
I now realise why they're running differently. If you notice my edit in the original question, it's because I've now installed the SSL certificates on two of the VHosts and one requires a passkey. I've now removed that
Dec
4
awarded  Student
Dec
4
revised Can't start Apache - Address already in use - httpd is stopped
added 1207 characters in body; added 2 characters in body
Nov
30
comment Can't start Apache - Address already in use - httpd is stopped
OK, appreciate that. Maybe if I explain why I find it unusual? We set this up as a standard EC2 instance and when you start it and do a service httpd status you will see Apache is running. We created the VPC EC2 instance from a snapshot of this machine and the behaviour is now different. Now the service isn't running, but Apache is. That's why I'm confused. Why two identical images are behaving differently depending on whether they're standard EC2 or running in a VPC
Nov
29
comment Can't start Apache - Address already in use - httpd is stopped
What struck me is that last three lines of the netstat result. In the AWS VPC Security Group, I have only allowed four TCP ports: 22, 80, 443 and 3306. MySQL isn't yet installed, so I'm not surprised to not see it in the list. Seeing httpd and sshd holding those particular ports leads me to believe that it's probably the AWS platform itself that's doing this, but only via VPC and not standard EC2 instances?
Nov
29
comment Can't start Apache - Address already in use - httpd is stopped
OK, apparently someone thinks "This question does not show any research effort; it is unclear or not useful". I accept that maybe it was a little unclear in that I'd originally stated that Apache was not running when clearly it is. What I meant was that it's not running as a service, which is how it was configured to run, so I don't understand how it's running or why. Yes, I killed the processes and that allowed me to start the service, but I don't understand why it's started already. Nor do I understand why it's like this every reboot. Any help?
Nov
29
awarded  Editor
Nov
29
revised Can't start Apache - Address already in use - httpd is stopped
added 82 characters in body
Nov
29
asked Can't start Apache - Address already in use - httpd is stopped