On Fri, March 16, 2007 11:58 am, Charles Edge wrote:
> On 3/14/07 8:49 AM, "Patrick Schwisow" <email@hidden>
> wrote:
>
>> On Wed, March 14, 2007 10:28 am, Dan Shoop wrote:
>>> At 3:27 PM -0500 3/13/07, Patrick Schwisow wrote:
>>>
>>>> I was simply explaining
>>>> another possible reason apache is not starting. I don't see how this
>>>> is
>>>> any different that your assertion that the failure was caused by
>>>> misconfiguration
>>> I can safely claim this b/c it *was* the problem. Moreover [almost]
>>> every apache startup problem is a misconfiguration problem of some
>>> sort. There are a few arcane exceptions I can think of but even those
>>> could be classified as a misconfiguration.
>>
>> I should have been more precise. Your assertion was that "the failure
>> was
>> caused by misconfiguration of Apache (specifically, errors in one or
>> more
>> of the *.conf files caused apache to quit while starting up). My
>> explanation showed an alternative possibility (i.e. misconfiguration of
>> something else).
>
> I've actually seen many times when OS X Server will not start Apache
> following a crash (due to power or OS failure). I always keep a backup of
> my config for this type of situation which I see from time to time on
> servers with more than 5 or 10 SSL sites. You could say that the OS
> failure
> was caused by a misconfig or that the power failure was caused by a
> misconfig of a UPS (or a misconfig of the situation;). But other than
> that,
> there have been issues aside from misconfiguration specifically following
> crashes, where rebuilding the configuration files will fix the issue.
It sounds like Apache is failing to start due to corruption of its config
files caused by "abnormal shutdown". I think my brain may have checked
out for the weekend early... are you arguing with me or agreeing with me?
>>>>> *That* problem is likely the one of trying to start two services on
>>>>> the same port.
>>>>
>>>> I cannot say for certain that a port conflict was not the cause,
>>>
>>> Hence my use of the word "likely".
>>>
>> You've cut off the portion of my post which explained why this was
>> "UNlikely". However, short of restoring my server to its "broken state"
>> and doing more testing, I can't prove or disprove this assertion, so I
>> don't think it's worth debating.
>
--
Patrick Schwisow
Web Information Manager
Waukegan Public School District 60
http://www.waukeganschools.org/
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
This email sent to email@hidden
