Bug 63881 - The server starts and terminates instantly if port 80 is blocked but there is nothing logged either from the startup or the error.
Summary: The server starts and terminates instantly if port 80 is blocked but there is...
Status: NEEDINFO
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.5-HEAD
Hardware: PC All
: P2 minor (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-25 10:50 UTC by James Brown
Modified: 2019-10-25 11:22 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Brown 2019-10-25 10:50:04 UTC
This is very simple but I just installed the latest version of XAMPP.  I ran the control panel and changed the listening port from 80.  I ran Apache and it showed up as running, puts out a pid in the control panel then terminates in about a quarter second.  I checked for logs, there were absolutely none.  I ended up running httpd from the command prompt and it told me port 80 was in use and died.  Again no logs.  The httpd.conf hadn't been changed by the control panel so still went to 80.  However, that does not change the fact that a few messages should have been logged in error or system logs.
Comment 1 Eric Covener 2019-10-25 11:22:14 UTC
Was anything logged in event viewer?