cron crashed with SIGSEGV in _init() after libc6/NSS upgrade

Bug #504847 reported by Matt Zimmerman
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eglibc (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: cron

I noticed the kernel logging segfaults from cron:

[2680656.645816] cron[32527]: segfault at 0 ip (null) sp bff38bc8 error 4 in libnss_nis-2.10.1.so (deleted)[110000+9000]
[2684256.769888] cron[29034]: segfault at 0 ip (null) sp bff38bc8 error 4 in libnss_nis-2.10.1.so (deleted)[110000+9000]
[2687856.272284] cron[23399]: segfault at 0 ip (null) sp bff38bc8 error 4 in libnss_nis-2.10.1.so (deleted)[110000+9000]
[2691456.718460] cron[17825]: segfault at 0 ip (null) sp bff38bc8 error 4 in libnss_nis-2.10.1.so (deleted)[110000+9000]
[2695056.347722] cron[12598]: segfault at 0 ip (null) sp bff38bc8 error 4 in libnss_nis-2.10.1.so (deleted)[110000+9000]
[2698655.941056] cron[7216]: segfault at 0 ip (null) sp bff38bc8 error 4 in libnss_nis-2.10.1.so (deleted)[110000+9000]

these happened at regular intervals, each time cron.hourly was run (17 minutes past the hour). I was able to capture this one with apport.

As you can see, cron is using an obsolete libnss_nis which has been deleted and replaced with a newer one (ibnss_nis-2.10.2.so). I believe crashes like this are the reason why NSS-using daemons get restarted on incompatible NSS upgrades, but that didn't happen in this case (cron has been running since days before the upgrade on both systems).

ProblemType: Crash
Architecture: i386
Date: Fri Jan 8 11:17:02 2010
Disassembly: 0x0: Cannot access memory at address 0x0
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/sbin/cron
Package: cron 3.0pl1-106ubuntu3
ProcCmdline: CRON
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: cron
StacktraceTop:
 ?? ()
 _init () from /lib/tls/i686/cmov/libpthread.so.0
 ?? () from /lib/ld-linux.so.2
 ?? () from /lib/ld-linux.so.2
 ?? () from /lib/ld-linux.so.2
Tags: lucid
Title: cron crashed with SIGSEGV in _init()
Uname: Linux 2.6.31-14-generic i686
UserGroups:

Revision history for this message
Matt Zimmerman (mdz) wrote :
affects: cron (Ubuntu) → eglibc (Ubuntu)
Matt Zimmerman (mdz)
tags: removed: need-i386-retrace
visibility: private → public
Steve Langasek (vorlon)
Changed in eglibc (Ubuntu):
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package eglibc - 2.11~20100104-0ubuntu3

---------------
eglibc (2.11~20100104-0ubuntu3) lucid; urgency=low

  * Upgrade the NSS min compat version to 2.11 in the maintainer scripts, to
    force maintainer restarts. LP: #504847.
  * debian/control: point Vcs-Bzr at a branch whose access rights match those
    of the archive.
 -- Steve Langasek <email address hidden> Fri, 08 Jan 2010 19:34:19 +0000

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

Other bug subscribers

Remote bug watches

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