|Summary:||error running apache, and installing apache as a service|
|Product:||Apache httpd-2||Reporter:||Jamison <blackdragons13>|
|Component:||All||Assignee:||Apache HTTPD Bugs Mailing List <bugs>|
apache error log.
apache error log.
Description Jamison 2010-09-27 10:14:30 UTC
First trying to install apache 2.2 as a service it comes up with this "the service name is invalid." More help is available by typing net helpmsg 2185 if researched the sh** out of that and its like no one else with windows 7 is having this issue Second running apache everytime I run it as administrator it comes up with this the system cannot find the path specified and I cannot figure out what im doing wrong with it, but when I dont run it as administrator it comes up with this "<os 10048> only one usage of each sock address <protocol/network address/port> is normally permitted. : make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down unable to open logs" please give me any information you guys got about what may be causing this and how I could possibly fix this, it has been so frustrating reading all these posts that I thought were related to the issues and only coming to find out after 30 minutes read that it has nothing to do with apache and some other stupid program that comes up with similar issues.... so please any help would be highly appreciated.
Comment 1 Jamison 2010-09-27 10:30:45 UTC
Created attachment 26084 [details] apache error log. here is the log to what ive been trying to run
Comment 2 Jamison 2010-09-27 10:31:46 UTC
Created attachment 26085 [details] apache error log. second apache error log for other one I am trying to get running also.
Comment 3 William A. Rowe Jr. 2018-11-07 21:08:00 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd. As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd. If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question. If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with. Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.