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

Bug #1681014 reported by Alexandre on 2017-04-08
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apache2 (Ubuntu)
Medium
Unassigned

Bug Description

Erro interno

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: apache2-bin 2.4.25-3ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
Uname: Linux 4.10.0-13-generic x86_64
ApportVersion: 2.20.4-0ubuntu3
Architecture: amd64
Date: Fri Apr 7 23:44:49 2017
ExecutablePath: /usr/sbin/apache2
InstallationDate: Installed on 2017-04-07 (1 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
ProcCmdline: /usr/sbin/apache2 -k start
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 LANG=C
SegvAnalysis:
 Segfault happened at: 0x7f77cd9f233a: nopw 0x0(%rax,%rax,1)
 PC (0x7f77cd9f233a) ok
 source "0x0(%rax,%rax,1)" (0x0000000e) not located in a known VMA region (needed readable region)!
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: apache2
StacktraceTop:
 ?? ()
 <signal handler called>
 __do_global_dtors_aux () from /lib/x86_64-linux-gnu/libnss_nis.so.2
 _dl_fini () at dl-fini.c:235
 __run_exit_handlers (status=0, listp=0x7f77cdd795d8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:83
Title: apache2 crashed with SIGSEGV in <signal handler called>()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Alexandre (alexandrepls) wrote :

StacktraceTop:
 ?? ()
 <signal handler called>
 __do_global_dtors_aux () from /tmp/apport_sandbox_Wsb7TQ/lib/x86_64-linux-gnu/libnss_nis.so.2
 _dl_fini () at dl-fini.c:235
 __run_exit_handlers (status=0, listp=0x7f77cdd795d8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:83

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

Hi Alexandre,
as far as I can see that does not contain private info in the dump.
So lets mark it public and merge with related issues.

In fact this seems to be occurring every now and then, but what is needed would be a more reliable way to reproduce - therefore combining efforts by Dup'ing it onto one bug.

information type: Private → Public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers