Ubuntu
squid3 package

squid3 crashed with SIGABRT in fatal_dump()

Bug #930252 reported by Sidnei da Silva on 2012-02-10

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	squid3 (Ubuntu)	Fix Released	Critical	Unassigned

Bug Description

Happens at startup on precise. I have squid3 installed as a dep to squid-deb-proxy.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: squid3 3.1.18-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
Uname: Linux 3.2.0-15-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Thu Feb 9 00:13:19 2012
ExecutablePath: /usr/sbin/squid3
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64+mac (20111208)
ProcCmdline: /usr/sbin/squid3 -N -f /etc/squid-deb-proxy/squid-deb-proxy.conf
ProcEnviron: PATH=(custom, no user)
Signal: 6
SourcePackage: squid3
StacktraceTop:
raise () from /lib/x86_64-linux-gnu/libc.so.6
abort () from /lib/x86_64-linux-gnu/libc.so.6
fatal_dump ()
xcalloc ()
?? ()
Title: squid3 crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Tags:

Related branches

lp:ubuntu/precise/squid3

Revision history for this message

Sidnei da Silva (sidnei) wrote on 2012-02-10:

Dependencies.txt Edit (2.8 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (854 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (8.5 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (761 bytes, text/plain; charset="utf-8")
Registers.txt Edit (651 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-13:

StacktraceTop:
fatal_dump (message=0x9e7840 "xcalloc: Unable to allocate 4035364077 blocks of 1 bytes!\n") at tools.cc:534
xcalloc (n=18446744073449948397, sz=1) at util.c:698
cacheDigestInit (cd=0x1177be0, capacity=443628308, bpe=5) at CacheDigest.cc:66
storeDigestResize () at store_digest.cc:545
storeDigestRebuildResume () at store_digest.cc:327

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-13: Stacktrace.txt

Stacktrace.txt Edit (2.8 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-13: ThreadStacktrace.txt

ThreadStacktrace.txt Edit (2.9 KiB, text/plain)

Changed in squid3 (Ubuntu):
importance:	Undecided → Medium
summary:	- squid3 crashed with SIGABRT in raise() + squid3 crashed with SIGABRT in fatal_dump()
tags:	removed: need-amd64-retrace

Chris Halse Rogers (raof) on 2012-02-21

Changed in squid3 (Ubuntu):
status:	New → Confirmed

Revision history for this message

Chris Halse Rogers (raof) wrote on 2012-02-21:

cache.log Edit (5.0 KiB, text/plain)

I'm seeing this too; I'm attaching the /var/log/squid-deb-proxy/cache.log, which seems to indicate that squid is attempting to allocate approximately 10PB of memory for swap. This, obviously, fails; hence the abort.

I think this might have to do with corrupted files in /var/cache/squid-deb-proxy; after blowing away that directory, squid-deb-proxy will successfully start. Until it fails again - maybe the problem is unclean shutdown?

Revision history for this message

Chris Halse Rogers (raof) wrote on 2012-02-21:

swap.state Edit (432 bytes, application/octet-stream)

And here's swap.state from the broken /var/cache/squid-deb-proxy

Revision history for this message

Chris Halse Rogers (raof) wrote on 2012-02-21:

From #squiddev:

18:31 <yadi> a bungled attempt to fix endian bugs earlier resulted in swap.state corruption in those releases. It should be fixed in 3.1.19. If you can blow away the cache_dir during the upgrade its faster, or just blow away all swap.state files while squid is shutdown before starting .19
18:33 <RAOF> But 3.1.18 will consistently produce swap.state files that are broken in this way? Time to merge a new version of squid into Ubuntu, then.
18:33 <yadi> yes.

Changed in squid3 (Ubuntu):
status:	Confirmed → Triaged
importance:	Medium → Critical

Chris Halse Rogers (raof) on 2012-02-21

visibility:

private → public

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-02-21:

This bug was fixed in the package squid3 - 3.1.19-1ubuntu1

---------------
squid3 (3.1.19-1ubuntu1) precise; urgency=low

  * Merge from Debian testing. Remaining changes:
    + debian/control:
      - Update maintainer.
    + debian/squid3.upstart, debian/rules, squid3.resolvconf,
      debian/squid3.postinst, debian/squid3.postrm, debian/squid3.preinst,
      debian/squid3.prerm: Convert init script to upstart
    + debian/control, debian/patches/99-ubuntu-ssl-cert-snakeoil: Use
     snakeoil certificates.
    + debian/logrotate: Use sar-reports rather than sarg-maint. (LP: 26616)
    + debian/patches/90-cf.data.ubuntu.dpatch: Add an example refresh pattern
      for debs. (foundations-lucid-local-report spec)
    + Add transitional dummy packages
  * New upstream bugfix release fixes swap.state corruption, so squid will
    now start after a reboot. (LP: #930252)

squid3 (3.1.19-1) unstable; urgency=low

  * New upstream release
    - Removed patch integrated upstream
      + 19-adaptation-compile

* debian/rules
- Enabled WCCPv2 support (Closes: #654877)
-- Christopher James Halse Rogers <email address hidden> Tue, 21 Feb 2012 18:51:26 +1100

Changed in squid3 (Ubuntu):
status:	Triaged → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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

Ubuntusquid3 package

squid3 crashed with SIGABRT in fatal_dump()

Bug Description

Related branches

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
squid3 package