Version-Release number of selected component: httpd-2.4.4-6.fc19 Additional info: reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/sbin/httpd -DFOREGROUND crash_function: apr_getnameinfo executable: /usr/sbin/httpd kernel: 3.10.4-300.fc19.x86_64 runlevel: N 5 uid: 0 Truncated backtrace: Thread no. 1 (3 frames) #0 apr_getnameinfo at network_io/unix/sockaddr.c:621 #1 ap_get_local_host at util.c:2093 #2 ap_fini_vhost_config at vhost.c:565
Created attachment 785719 [details] File: backtrace
Created attachment 785721 [details] File: cgroup
Created attachment 785723 [details] File: core_backtrace
Created attachment 785725 [details] File: dso_list
Created attachment 785726 [details] File: environ
Created attachment 785728 [details] File: limits
Created attachment 785730 [details] File: maps
Created attachment 785732 [details] File: open_fds
Created attachment 785733 [details] File: proc_pid_status
Created attachment 785734 [details] File: var_log_messages
I have no idea what caused the abort - Apache has not been configured and is in the fresh install state reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/sbin/httpd -DFOREGROUND crash_function: apr_getnameinfo executable: /usr/sbin/httpd kernel: 3.10.6-200.fc19.i686.PAE package: httpd-2.4.6-2.fc19 reason: Process /usr/sbin/httpd was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 0
This looks like the same bug as Bug 958652, which should be fixed already in glibc and also workarounded in apr-1.4.7. According to DSO attachment, you have apr-1.4.6, so updating to newer APR should fix this bug. I'm closing this one as WORKSFORME, because the fix is already in latest F19, you just don't have that update ;). Feel free to reopen if this happens again with latest APR package.