arpwatch uses 100% cpu when net disconnects on laptop

Bug #357462 reported by Teunis Peters
42
This bug affects 9 people
Affects Status Importance Assigned to Milestone
arpwatch (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: arpwatch

don't use arpwatch on a laptop. it uses 100% cpu load if the network disconnects - a frequent occurrence when travelling.

this is a severe bug causing heat shutdown of system.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: arpwatch 2.1a13-2.1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: arpwatch
Uname: Linux 2.6.28-11-generic i686

Revision history for this message
Teunis Peters (teunis) wrote :
Revision history for this message
Francis Russell (francis-russell) wrote :

Just to note, running /etc/init.d/networking restart will have the same effect. I'm now using karmic, and due to an ordering issue between resolvconf and networking startup I find myself having to restart networking just so that machine has the correct DNS settings then killing arpwatch.

Revision history for this message
prower2000@hotmail.com (prower2000-gmail) wrote :

I can confirm that this bug exists in Karmic's version of arpwatch as well. Steps to reproduce:

1) start arpwatch running (or install it, it's started automatically if you do)
2) disable networking to your PC via the NetworkManager applet and re-enable it
3) check top, arpwatch is now using up 100% CPU in the background and continues to do so until restarted

Revision history for this message
Stefan Lasiewski (stefanlasiewski) wrote :

I've reproduced this on a desktop environment using wired Ethernet. This host does not use wireless.

Steps to reproduce:

1. Start aprwatch
2. Reboot the router, or disconnect the network cable to the router.
3. Check top, and see that arpwatch is using 100% of the CPU.

    PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
    1672 arpwatch 20 0 19536 2676 2560 R 99 0.1 797:40.63 arpwatch

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

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

Changed in arpwatch (Ubuntu):
status: New → Confirmed
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.