Page 1 of 1

Apache won't start after adding some lines in httpd.conf

PostPosted: 14. February 2015 08:58
by RandV
I wasn't sure if I should post this in a XAMPP or Symfony forum, but since I have the XAMPP error log figured I'd try here. I'm trying to setup a better php development environment on my desktop utilizing a framework, and have been following a guide from this blog:
http://hazraphp.blogspot.ca/2009/09/symfony-on-xampp.html
(note: not sure how to make something a link on this forum, <a> tags don't seem tow ork)

Following the instructions near the end I was told to add these lines to the apache httpd.conf file, the directories of course have been changed to match my file system:

# Use name-based virtual hosting.
#
NameVirtualHost *:80

#default area for new web projects

ServerName web
DocumentRoot "B:\web"

#original xampp location

ServerName localhost
DocumentRoot "B:\xampp\htdocs"

#allow access for the shared sf directory

Allow from All

#sample symfony project

ServerName askeet
DocumentRoot "b:\web\askeet\web"
DirectoryIndex index.php
Alias /sf "b:\xampp\php\pear\data\symfony\web\sf"

AllowOverride All
Order allow,deny
Allow from All


Now when I run XAMPP and start apache, I get the usual:

11:45:56 PM [Apache] Error: Apache shutdown unexpectedly.
11:45:56 PM [Apache] This may be due to a blocked port, missing dependencies,
11:45:56 PM [Apache] improper privileges, a crash, or a shutdown by another method.
11:45:56 PM [Apache] Press the Logs button to view error logs and check
11:45:56 PM [Apache] the Windows Event Viewer for more clues
11:45:56 PM [Apache] If you need more help, copy and post this
11:45:56 PM [Apache] entire log window on the forums


And the error log says:

[Fri Feb 13 23:53:47.721120 2015] [ssl:warn] [pid 5680:tid 224] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Fri Feb 13 23:53:47.796124 2015] [core:warn] [pid 5680:tid 224] AH00098: pid file B:/xampp/apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Fri Feb 13 23:53:48.005136 2015] [ssl:warn] [pid 5680:tid 224] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Fri Feb 13 23:53:48.233149 2015] [mpm_winnt:notice] [pid 5680:tid 224] AH00455: Apache/2.4.10 (Win32) OpenSSL/1.0.1i PHP/5.6.3 configured -- resuming normal operations
[Fri Feb 13 23:53:48.233149 2015] [mpm_winnt:notice] [pid 5680:tid 224] AH00456: Apache Lounge VC11 Server built: Jul 17 2014 11:50:08
[Fri Feb 13 23:53:48.233149 2015] [core:notice] [pid 5680:tid 224] AH00094: Command line: 'b:\\xampp\\apache\\bin\\httpd.exe -d B:/xampp/apache'
[Fri Feb 13 23:53:48.235150 2015] [mpm_winnt:notice] [pid 5680:tid 224] AH00418: Parent: Created child process 4432
[Fri Feb 13 23:53:48.861185 2015] [ssl:warn] [pid 4432:tid 236] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Fri Feb 13 23:53:49.135201 2015] [ssl:warn] [pid 4432:tid 236] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Fri Feb 13 23:53:49.180204 2015] [mpm_winnt:notice] [pid 4432:tid 236] AH00354: Child: Starting 150 worker threads.


I'm trying to decipher it but as I'm a first timer with this it still looks like gibberish to me. Would be much appreciated if anyone can see what I'm doing wrong here?

Re: Apache won't start after adding some lines in httpd.conf

PostPosted: 14. February 2015 20:55
by Altrea
Search for a tutorial that is not broken

Re: Apache won't start after adding some lines in httpd.conf

PostPosted: 17. February 2015 08:34
by RandV
Altrea wrote:Search for a tutorial that is not broken


Well easier said than done, the tutorial I have is the most detailed step by step example I found... though yes it sucks it's from 2009, but I was able to work around that for the most part. I'll just take the question to an Apache forum, thanks.

Re: Apache won't start after adding some lines in httpd.conf

PostPosted: 17. February 2015 08:50
by Altrea
No, it not only sucks because it is old. It sucks because it is broken. Important directives like <VirtualHost> are missing (maybe because of HTML tag filters of that blog)