apache2 crashed with SIGSEGV in <signal handler called>()

Bug #1678325 reported by Toni on 2017-03-31

This bug report will be marked for expiration in 38 days if no further activity occurs. (find out why)

12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apache2 (Ubuntu)
Medium
Unassigned

Bug Description

The error apears when not using apache2.
Is not a fresh install of apache2

Description: Ubuntu Zesty Zapus (development branch)
Release: 17.04

apache2:
  Instalados: 2.4.25-3ubuntu2
  Candidato: 2.4.25-3ubuntu2
  Tabla de versión:
 *** 2.4.25-3ubuntu2 500
        500 http://es.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: apache2-bin 2.4.25-3ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
Uname: Linux 4.10.0-14-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
Date: Thu Mar 30 18:15:04 2017
ExecutablePath: /usr/sbin/apache2
InstallationDate: Installed on 2017-03-24 (7 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
ProcCmdline: /usr/sbin/apache2 -k start
ProcEnviron:
 PATH=(custom, no user)
 LANG=C
Signal: 11
SourcePackage: apache2
StacktraceTop:
 ?? ()
 <signal handler called>
 apr_pool_destroy () from /usr/lib/x86_64-linux-gnu/libapr-1.so.0
 apr_pool_destroy () from /usr/lib/x86_64-linux-gnu/libapr-1.so.0
 ?? ()
Title: apache2 crashed with SIGSEGV in <signal handler called>()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Toni (toni-man) wrote :
information type: Private → Public

StacktraceTop:
 ?? ()
 <signal handler called>
 apr_pool_destroy () from /tmp/apport_sandbox_JKVtev/usr/lib/x86_64-linux-gnu/libapr-1.so.0
 apr_pool_destroy () from /tmp/apport_sandbox_JKVtev/usr/lib/x86_64-linux-gnu/libapr-1.so.0
 destroy_and_exit_process.isra ()

Changed in apache2 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
ChristianEhrhardt (paelzer) wrote :

Hi,
sorry I did not fully understand "The error apears when not using apache2. Is not a fresh install of apache2"

"not used" => installed from repositories but not "used" apache2 so it still is in the default conf?

"not a fresh install of apache2" => did you upgrade from somewhere, this seems to be a fresh 17.04 install what was there before?

Did you mean you have other apaches installed or an older version e.g. build manually?
In those cases I'v seen such crashes e.g. due to libraries referring to things that are no more there after switching from manual to archive provided versions by stale files from the manual install.

For now this does not hold enough information to debug, please try to outline your setup and clarify the questions I have asked - then please set the bug back to new. Until then there is not much more I can do.

Changed in apache2 (Ubuntu):
status: New → Incomplete
Toni (toni-man) wrote :

Hi
I installed Apache some days ago and it works well. I test some html files in the server without problems. Another day, after one hour using the computer ( not using the apache server) this error appears.
I have a fresh 17.04 install. Apache was installed from the Zesty repository. Only one apache installed and no manual build.

Changed in apache2 (Ubuntu):
status: Incomplete → New
ChristianEhrhardt (paelzer) wrote :

Very interesting,
thank you Toni for getting back with these Details.

Since on your system were no debugging symbols the stack traces so far don't tell me anything reasonable.

Some questions to sort this out:
- Is apache itself still working right now for you or is it down since?
- Does such a crash re-occur if you are running restart&status
   $ systemctl restart apache2
   $ systemctl status apache2
- Furthermore if anything comes to your mind on your setup that could trigger this let us know.

Also following [1] you could install debug symbols.
In your case all you need after making them available should be installed via:
$ apt install apache2-dbgsym libapr1-dbg apache2-bin-dbgsym apache2-utils-dbgsym

With that in place you can re-report the improved symbols to this bug via "apport-collect" I'd think. You can also check with apport-retrace locally if you think all symbols are available.

Since I had no way to reproduce it I also have checked [2] but have seen no similar issues so far.

[1]: https://wiki.ubuntu.com/Debug%20Symbol%20Packages
[2]: https://errors.ubuntu.com/?release=Ubuntu%2017.04&package=apache2-bin&period=day

Changed in apache2 (Ubuntu):
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers