[Systems] Apache stalled on sunjammer today

Samuel Cantero scg at sugarlabs.org
Fri Sep 11 18:13:14 EDT 2015


Hi guys,

Same error today. I have applied the same steps.

Regards,

On Sun, Aug 23, 2015 at 4:55 PM, Samuel Cantero <scg at sugarlabs.org> wrote:

> Hi all,
>
> I've found the sunjammer http and https service on critical state on
> nagios. Apache error.log was reporting:
>
> [emerg] (2)No such file or directory: Couldn't initialize cross-process
> lock in child (/var/lock/apache2/accept.lock.7307) (1)
>
> [alert] Child 2435 returned a Fatal error... Apache is exiting!
>
> Does anyone have idea about this error? As you know, currently the mutex
> directive is configured to *flock*.
>
> When I tried to restart the apache service I got the following message:
>
> (98)Address already in use: make_sock: could not bind to address [::]:443
>
> (98)Address already in use: make_sock: could not bind to address
> 0.0.0.0:443
>
> no listening sockets available, shutting down
>
> So I had to kill -9 the apache process ID and after that apache was able
> to start.
>
> Regards,
>
> Samuel
>
> On Wed, Jul 22, 2015 at 9:14 AM, Bernie Innocenti <bernie at codewiz.org>
> wrote:
>
>> Thanks.
>>
>> At this point I think a big system upgrade would be less disruptive than
>> these outages. I'll try to get it done on a weekend (but not this coming
>> one, I already have other plans).
>>
>> On 22/07/15 04:53, Sam P. wrote:
>>
>>> So the same issue happened about 15 minutes ago.
>>>
>>> I restarted apache and postgress.  As Quozl suggested I removed the
>>> postgres semaphores.
>>>
>>> I also change the apache2 AcceptMutex option to flock.
>>>
>>>
>>> On Tue, 21 Jul 2015 1:59 am James Cameron <quozl at laptop.org
>>> <mailto:quozl at laptop.org>> wrote:
>>>
>>>     On Sat, Jul 18, 2015 at 08:01:10PM -0400, Bernie Innocenti wrote:
>>>      > SysV ipc resources are global and don't get released when a
>>> process
>>>      > crashes. So they are inherently prone to leaks.
>>>
>>>     Yes.  We use them on Netrek.  ;-)
>>>
>>>     Stop postgres, verify it is stopped, then use ipcs to identify the
>>>     resources and ipcrm to remove them.
>>>
>>>     Otherwise the issue will return.
>>>
>>>     Or, if you're in a hurry and don't want to re-learn syntax for
>>>     commands, reboot.  ;-)
>>>
>>>     --
>>>     James Cameron
>>>     http://quozl.linux.org.au/
>>>     _______________________________________________
>>>     Systems mailing list
>>>     Systems at lists.sugarlabs.org <mailto:Systems at lists.sugarlabs.org>
>>>     http://lists.sugarlabs.org/listinfo/systems
>>>
>>>
>>>
>>> _______________________________________________
>>> Systems mailing list
>>> Systems at lists.sugarlabs.org
>>> http://lists.sugarlabs.org/listinfo/systems
>>>
>>>
>>
>> --
>>  _ // Bernie Innocenti
>>  \X/  http://codewiz.org
>> _______________________________________________
>> Systems mailing list
>> Systems at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/systems
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/private/systems/attachments/20150911/f837d147/attachment.html>


More information about the Systems mailing list