apache2 crashed with SIGSEGV

Bug #221457 reported by Funatiker
234
This bug affects 4 people
Affects Status Importance Assigned to Milestone
apache2 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: apache2

After upgrade from Gutsy (64bit) to Hardy (64bit) crashes on startup although I expected a running Apache.
apache2: 2.2.8-1
Ubuntu Hardy Heron: 8.04

ProblemType: Crash
Architecture: amd64
Date: Thu Apr 24 16:44:18 2008
Disassembly: 0x2b621a7b0bcb:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/sbin/apache2
NonfreeKernelModules: nvidia
Package: apache2-mpm-prefork 2.2.8-1
PackageArchitecture: amd64
ProcCmdline: /usr/sbin/apache2 -t
ProcEnviron:
 LANG=C
 PATH=/usr/local/bin:/usr/bin:/bin
Signal: 11
SourcePackage: apache2
Stacktrace:
 #0 0x00002b621a7b0bcb in ?? ()
 #1 0x00002b621aac38f0 in ?? ()
 #2 0x0000000000000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
ThreadStacktrace:

Title: apache2 crashed with SIGSEGV
Uname: Linux 2.6.24-16-rt x86_64
UserGroups:

Revision history for this message
Funatiker (koehlerx) wrote :
Revision history for this message
Marcus Asshauer (mcas) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in apache2:
status: New → Incomplete
Revision history for this message
Whit (whit+ubuntu) wrote :

Just had the same crash, also on upgrade from 7.10 to 8.04 and AMD64. However, this is before rebooting the system, so don't know if it will be persistent.

Revision history for this message
Filipe Torres (filipe-jose) wrote :

Just happened to me too, after the first reboot after the upgrade process from 7.10 to 8.04 on AMD64.

Revision history for this message
wittend (wittend) wrote :

me too

Marcus Asshauer (mcas)
Changed in apache2:
status: Incomplete → Confirmed
Revision history for this message
Kaivalagi (m-buck) wrote :

Starts and stops okay, just the upgrade issue really

Revision history for this message
Kurepi Daniel (kurepi-daniel) wrote :

Cuando lo inicio nuevamente:

root@caa-laptop:~# /etc/init.d/apache2 start
 * Starting web server apache2 apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
httpd (pid 6307) already running
                                                                         [ OK ]

Revision history for this message
Aragorn Athelas Bilbo (aragornzonaopen) wrote :

I see message when type sudo in console :

Usage: /usr/sbin/sendmail -f <email address hidden> -h relayhost [OPTIONS] (use -H for help)

I don't now if this is the same problem.

Revision history for this message
Piers Lauder (pierslauder) wrote :

me too. upgrade error only, works otherwise.

Revision history for this message
John Franey (jjfraney) wrote :

Do you need another "me too"? ok? Me too.

Thanks,
John

Revision history for this message
Stefan Fritsch (sf-sfritsch) wrote :

This happens when the old apache is restarted when libaprutil1 has already been upgraded. It is fixed as soon as apache is upgraded, too. Probably the new libaprutil1 should conflict with the old apache2.2-common.

Revision history for this message
Astrodan (dholler01) wrote : Re: [Bug 221457] Re: apache2 crashed with SIGSEGV

Thank you very much for the info.

On Tue, 2008-05-06 at 20:58 +0000, sf wrote:
> This happens when the old apache is restarted when libaprutil1 has
> already been upgraded. It is fixed as soon as apache is upgraded, too.
> Probably the new libaprutil1 should conflict with the old
> apache2.2-common.
>

Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
?? ()

Revision history for this message
Marco Selvini (scinty04) wrote :

Errore ricevuto solamente dopo l'aggiornamento di versione. Al successivo riavvio tutto ok.

Revision history for this message
Todd Deshane (deshantm) wrote :

During my 7.10 to 8.04 upgrade, in the gnome-terminal I get the following message (since I ran update-manager from the terminal)

extracting '/tmp/tmpkC8cub/hardy.tar.gz'
authenticate '/tmp/tmpkC8cub/hardy.tar.gz' against '/tmp/tmpkC8cub/hardy.tar.gz.gpg'

This caused the upgrade to hang trying to configure/generate locales

Generating locales...
  en_AU.UTF-8...<HANG>

This then leads to the bug that dpkg -configure -a must be then run from the command line to re-configure the unconfigured packages. update-manager on next load, doesn't alert of the problem. I am pretty sure though that I saw discussion that that sort of thing was to be fixed either in or slightly after the hardy release.

Revision history for this message
Blaisorblade (p-giarrusso) wrote :

Me too. Even before rebooting, /etc/init.d/apache2 restart works.
Since I'm Italian, I can tell that Marco Selvini's comment says more or less the same:
"Error received just after the release upgrade. Everything was fine at the subsequent reboot."

Revision history for this message
Chuck Short (zulcss) wrote :

Im going to close this bug then.

chuck

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.