ntop does not install correctly with no 'eth0' device
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ntop (Debian) |
Fix Released
|
Unknown
|
|||
ntop (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: ntop
Background:
This computer only has a loopback and ra0 device (it had an eth0, but I turned it off via the bios after it got zapped by lightning).
outpost@
Description: Ubuntu 9.04
Release: 9.04
outpost@
ntop:
Installed: (none)
Candidate: 3:3.3-11ubuntu1
Version table:
3:
500 http://
What I expected to happen:
ntop to install and the daemon to start automatically
What actually happened:
outpost@
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
The following NEW packages will be installed:
librrd4{a} ntop
0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/2902kB of archives. After unpacking 11.6MB will be used.
Do you want to continue? [Y/n/?] y
Writing extended state information... Done
Preconfiguring packages ...
eth0: error fetching interface information: Device not found
Selecting previously deselected package librrd4.
(Reading database ... 129249 files and directories currently installed.)
Unpacking librrd4 (from .../librrd4_
Selecting previously deselected package ntop.
Unpacking ntop (from .../ntop_
Processing triggers for man-db ...
Setting up librrd4 (1.3.1-4ubuntu1) ...
Setting up ntop (3:3.3-11ubuntu1) ...
eth0: error fetching interface information: Device not found
Starting network top daemon: eth0: error fetching interface information: Device not found
ERR: interface eth0 is DOWN...
Tue Jul 21 09:19:48 2009 NOTE: Interface merge enabled by default
Tue Jul 21 09:19:48 2009 Initializing gdbm databases
ntop not started. Read /usr/share/
invoke-rc.d: initscript ntop, action "start" failed.
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Writing extended state information... Done
outpost@
The package installs, but the daemon is not set up correctly and does not run out of the gate. Shouldn't it automatically pick out a working network device before trying to start it?
Changed in ntop (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in ntop (Debian): | |
status: | Unknown → Fix Committed |
Changed in ntop (Debian): | |
status: | Fix Committed → Fix Released |
Setting up ntop (3:4.0.3+dfsg1-2) ...
Starting network top daemon: ERR: interface eth0 is DOWN...
will not start network top daemon!
My ethernet device is br0, the physical device is eth2.