[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kroupware
Subject:    Re: Installation of Kolab 2.4 on Centos 6.2
From:       "Jeroen van Meeuwen (Kolab Systems)" <vanmeeuwen () kolabsys ! com>
Date:       2012-05-10 14:37:25
Message-ID: 87258ceea9a5d006a1ae058e7a17584c () kolabsys ! com
[Download RAW message or body]

On 2012-05-10 14:48, Heiner Markert wrote:
> Am Thursday 10 May 2012 14:28:59 schrieb Nazeer:
>> I Don't understand how something can be blocking port 80... before 
>> doing the
>> setup, I checked if anything was running on port 80 and there was 
>> nothing
>> running
>>
>> I then get the error... its on a fresh Centos 6.2 install
>>
>> The first time its starts httpd fine, then it stops and starts it 
>> again and
>> that's when the error appears...
>>
>
> Yes, the error occurs because httpd did not really stop - notice that
> "failed" already appears when httpd should stop. Then, obviously, 
> port
> 80 is still blocked and if you try to start httpd again, it does not
> work. The "quick and dirty" way that might resolve a one-time failure
> in httpd is to reboot, that's why I suggested to try that first.
>

I'm inclined to conclude we attempt to restart httpd too fast, and it 
has not at all completed starting up yet by the time we do.

A simple killall -9 httpd, service httpd start should do the trick.

Kind regards,

Jeroen van Meeuwen

-- 
Systems Architect, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
m: +44 74 2516 3817
w: http://www.kolabsys.com

pgp: 9342 BF08

_______________________________________________
Kolab-users mailing list
Kolab-users@kolab.org
https://www.intevation.de/mailman/listinfo/kolab-users
[prev in list] [next in list] [prev in thread] [next in thread]