atop crash with SIGFPE in acctprocnt()

Bug #1022865 reported by Torsten Krah
458
This bug affects 79 people
Affects Status Importance Assigned to Milestone
atop (Debian)
Fix Released
Unknown
atop (Ubuntu)
Fix Released
High
Unassigned
Xenial
New
Undecided
Unassigned
Zesty
New
Undecided
Unassigned

Bug Description

Running atop does result in SIGFPE - Trace does read like this:

Reading symbols from /usr/bin/atop...Reading symbols from /usr/lib/debug/usr/bin/atop...done.
done.
(gdb) run
Starting program: /usr/bin/atop

Program received signal SIGFPE, Arithmetic exception.
0x0000000000407173 in acctprocnt () at acctproc.c:598
598 acctproc.c: Datei oder Verzeichnis nicht gefunden.
(gdb) bt
#0 0x0000000000407173 in acctprocnt () at acctproc.c:598
#1 0x00000000004034a0 in engine () at atop.c:815
#2 main (argc=<optimized out>, argv=<optimized out>) at atop.c:651

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: atop 1.26-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-3.3-generic 3.5.0-rc5
Uname: Linux 3.5.0-3-generic x86_64
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
Date: Tue Jul 10 10:26:55 2012
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64+mac (20110427.1)
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: atop
UpgradeStatus: Upgraded to precise on 2012-06-04 (35 days ago)

Revision history for this message
Torsten Krah (tkrah) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in atop (Ubuntu):
status: New → Confirmed
Revision history for this message
martin suchanek (martin-suc) wrote :

error appeared in vivd development branch:

lsb_release -rd
Description: Ubuntu Vivid Vervet (development branch)
Release: 15.04

apt-cache policy atop
atop:
  Installed: 1.26-2
  Candidate: 1.26-2
  Version table:
 *** 1.26-2 0
        500 http://archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
        100 /var/lib/dpkg/status

tags: added: vivid
Changed in atop (Ubuntu):
importance: Undecided → High
Revision history for this message
Bodo Brance (bodobr) wrote :

Floating point exception in Ubuntu 16.04 also.
Really, is this tool so unimportant that the bug is not fixed?

summary: - atop crash with SIGFPE
+ atop crash with SIGFPE in acctprocnt()
no longer affects: dabo
Revision history for this message
draco (draco31-fr) wrote :

Debian bug reports a new version of atop has been uploaded to experimental.
Could it be available for testing on Ubuntu too ?

Changed in atop (Debian):
status: Unknown → Incomplete
Changed in atop (Debian):
status: Incomplete → Fix Released
Revision history for this message
Ralph Navarro (ralph-navarrocomputing) wrote :

When will this be fixed in Ubuntu 16.04 LTS?

Revision history for this message
Paul Sokolovsky (pfalcon) wrote :

Indeed, this still happens with 16.04. More weird, this happens without user running atop, just system suddenly pops up an window that atop crashed. Why on earth Ubuntu runs atop behind user's back?

Revision history for this message
Luke Faraone (lfaraone) wrote :

This should be fixed in Artful by 2.2.6-4 -- the upload of 2.2.4-1~exp1 in Debian appears to have resolved this issue.

Changed in atop (Ubuntu):
status: Confirmed → Fix Released
Vinson Lee (vlee)
tags: added: xenial
Revision history for this message
Remy van Elst (raymii) wrote :

How likely is that this fix will be backported into 16.04? It's an LTS so otherwise I'll be dealing with this for a few more years...

Revision history for this message
Acceptable Name (metta-crawler) wrote :

@pfalcon atop is run at midnight from cron, see the atop manual page for details. This is why you get "spontaneous" crash dialogs about atop.

@raymii If you are on 16.04 you can fetch the update from Debian Sid.

Add two files:

$ cat /etc/apt/preferences.d/debian-atop
Explanation: This file is for atop pinning
Explanation: See /etc/apt/sources.list.d/debian-sid.list for debian entries.

Package: *
Pin: release o=Debian,n=sid
Pin-Priority: -1

Package: atop
Pin: release o=Debian,n=sid
Pin-Priority: 500

--------

$ cat /etc/apt/sources.list.d/debian-sid.list
## Added for atop
## see /etc/apt/preferences.d/debian-atop for pinning.
##
deb http://httpredir.debian.org/debian sid main
# deb-src http://httpredir.debian.org/debian sid main

Revision history for this message
müzso (bit2) wrote :

To @metta-crawler's solution: you don't have to turn to Debian for a fix. The next Ubuntu LTS (bionic) does include the updated atop version.

Adopting the same approach for Bionic ...
(Note: I use 400 for Bionic package priorities so a dependency missing from Xenial can be fetched from there)

$ cat /etc/apt/preferences.d/20_ubuntu-bionic.pref

Explanation: Bionic should be only a fallback in case something is not available from your primary repos
Package: *
Pin: release v=18.04,o=Ubuntu
Pin-Priority: 400

Explanation: Bionic should be only a fallback in case something is not available from your primary repos
Package: *
Pin: release v=18.04,o=Canonical
Pin-Priority: 400

Explanation: fix for atop crashes (https://bugs.launchpad.net/ubuntu/+source/atop/+bug/1022865)
Package: atop
Pin: release v=18.04,o=Ubuntu
Pin-Priority: 600

--------

$ cat /etc/apt/sources.list.d/ubuntu-bionic.list

# Bionic repos only for selected packages (see the respective file in /etc/apt/preferences.d)
deb http://archive.ubuntu.com/ubuntu bionic main restricted multiverse universe
deb-src http://archive.ubuntu.com/ubuntu bionic main restricted multiverse universe

deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted multiverse universe
deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted multiverse universe

deb http://security.ubuntu.com/ubuntu bionic-security main restricted multiverse universe
deb-src http://security.ubuntu.com/ubuntu bionic-security main restricted multiverse universe

deb http://archive.canonical.com/ubuntu bionic partner
deb-src http://archive.canonical.com/ubuntu bionic partner

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.