Bug#827693: marked as done (apache2 is geting a lot of segmentation fault)
Your message dated Sat, 31 Mar 2018 14:53:41 +0200 (CEST)
with message-id <alpine.DEB.2.11.1803311453170.22988@manul.sfritsch.de>
and subject line Re: Bug#827693: adding logs and gdb
has caused the Debian Bug report #827693,
regarding apache2 is geting a lot of segmentation fault
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
827693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827693
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: apache2 is geting a lot of segmentation fault
- From: Wojtas <gsoftwg@gmail.com>
- Date: Sun, 19 Jun 2016 20:57:04 +0200
- Message-id: <20160619185704.18744.76928.reportbug@ns3023045.ip-149-202-197.eu>
Package: apache2
Version: 2.4.10-10+deb8u4
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- Package-specific info:
-- System Information:
Debian Release: 8.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14.32-xxxx-grs-ipv6-64 (SMP w/8 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages apache2 depends on:
ii apache2-bin 2.4.10-10+deb8u4
ii apache2-data 2.4.10-10+deb8u4
ii apache2-utils 2.4.10-10+deb8u3
ii dpkg 1.17.26
ii lsb-base 4.1+Debian13+nmu1
ii mime-support 3.58
ii perl 5.20.2-3+deb8u1
ii procps 2:3.3.9-9
Versions of packages apache2 recommends:
ii ssl-cert 1.0.35
Versions of packages apache2 suggests:
pn apache2-doc <none>
pn apache2-suexec-pristine | apache2-suexec-custom <none>
ii links [www-browser] 2.8-2+b3
ii lynx-cur [www-browser] 2.8.9dev1-2+deb8u1
Versions of packages apache2-bin depends on:
ii libapr1 1.5.1-3
ii libaprutil1 1.5.4-1
ii libaprutil1-dbd-sqlite3 1.5.4-1
ii libaprutil1-ldap 1.5.4-1
ii libc6 2.19-18+deb8u4
ii libldap-2.4-2 2.4.40+dfsg-1+deb8u1
ii liblua5.1-0 5.1.5-7.1
ii libpcre3 2:8.35-3.3
ii libssl1.0.0 1.0.1k-3+deb8u2
ii libxml2 2.9.1+dfsg1-5
ii perl 5.20.2-3+deb8u1
ii zlib1g 1:1.2.8.dfsg-2+b1
Versions of packages apache2-bin suggests:
pn apache2-doc <none>
pn apache2-suexec-pristine | apache2-suexec-custom <none>
ii links [www-browser] 2.8-2+b3
ii lynx-cur [www-browser] 2.8.9dev1-2+deb8u1
Versions of packages apache2 is related to:
ii apache2 2.4.10-10+deb8u4
ii apache2-bin 2.4.10-10+deb8u4
-- Configuration Files:
/etc/apache2/apache2.conf changed [not included]
/etc/init.d/apache2 changed [not included]
/etc/logrotate.d/apache2 changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: 827693-done@bugs.debian.org
- Subject: Re: Bug#827693: adding logs and gdb
- From: Stefan Fritsch <sf@sfritsch.de>
- Date: Sat, 31 Mar 2018 14:53:41 +0200 (CEST)
- Message-id: <alpine.DEB.2.11.1803311453170.22988@manul.sfritsch.de>
- In-reply-to: <4021668.lyDyLLtS3Y@k>
- References: <CADJQf67Oi7rJXctN4raEvFRqdp4z6gRSY7VFCBG-VYEa_pp0yA@mail.gmail.com> <4021668.lyDyLLtS3Y@k>
No response from submitter. Closing
On Sat, 25 Jun 2016, Stefan Fritsch wrote:
> Hi,
>
> can you provide "bt full" of thread 5? Or simply "thread apply all bt
> full"?. The "bt full" output you have sent is from a different,
> uninteresting thread.
>
> It seems someone passes an invalid pointer to libc's setenv()
> function. But it's impossible to say how this happened.
>
> Maybe you want to try if the segfaults go away when switching to
> mpm_prefork. Depending on what external libraries you are using, you
> may have some threading issues in your perl code. If you haven't
> already, you should probably read this:
> https://perl.apache.org/docs/2.0/user/coding/coding.html#Threads_Coding_Issues_Under_mod_perl
>
> Cheers,
> Stefan
>
>
--- End Message ---
Reply to: