Bug#779078: apache2-bin: event mpm: child segfault in notify_suspend causes parent to exit during log rotation

2015-05-10 Thread Stefan Fritsch
Hi, On Tuesday 05 May 2015 14:01:56, Michael Ablassmeier wrote: we recently migrated over an OTRS instance from another system to debian jessie and it appears we may have the same issue, sporadic segfauls, but we do not use the event_mpm but the default worker: [Tue May 05 13:02:19.929973

Bug#779078: apache2-bin: event mpm: child segfault in notify_suspend causes parent to exit during log rotation

2015-05-05 Thread Michael Ablassmeier
hi, we recently migrated over an OTRS instance from another system to debian jessie and it appears we may have the same issue, sporadic segfauls, but we do not use the event_mpm but the default worker: [Tue May 05 13:02:19.929973 2015] [mpm_worker:notice] [pid 41460:tid 14028953424]

Bug#779078: apache2-bin: event mpm: child segfault in notify_suspend causes parent to exit during log rotation

2015-04-01 Thread Stefan Fritsch
Hi Chris, On Tuesday 24 February 2015 09:36:58, Chris Boot wrote: We have been experiencing segmentation faults in apache2 when using the event MPM in jessie. These manifest themselves with log entries I have uploaded a fix to unstable. It would be great if you could grab 2.4.10-11 from there

Bug#779078: apache2-bin: event mpm: child segfault in notify_suspend causes parent to exit during log rotation

2015-03-18 Thread jaroslav
We got hit by this bug too and reported it to upstream. See https://bz.apache.org/bugzilla/show_bug.cgi?id=57268 , applying the patch suggested in there to Debian source solved the issue for us. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

Bug#779078: apache2-bin: event mpm: child segfault in notify_suspend causes parent to exit during log rotation

2015-02-24 Thread Chris Boot
Package: apache2-bin Version: 2.4.10-9 Severity: important Dear maintainers, We have been experiencing segmentation faults in apache2 when using the event MPM in jessie. These manifest themselves with log entries that look like: [Thu Feb 19 14:26:22.477619 2015] [core:notice] [pid 14018:tid