The problem seems to have disappeared for me on Lucid.
** Changed in: darkstat (Ubuntu)
Status: Triaged = Invalid
--
darkstat does not start on boot
https://bugs.launchpad.net/bugs/249038
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I can reproduce the problem with darkstat 3.0.712-1 on Jaunty. The
problem is (piping darkstat --verbose --no-daemon through
/usr/bin/logger at boot time):
error: pcap_open_live(): eth0: That device is not up
Changing the boot order via update-rc.d doesn't fix this problem for me.
darkstat
If I disable NetworkManager and add e1000 to /etc/modules and configure
eth0 via /etc/network/interfaces, then darkstat starts up just fine (!).
Hew, is your Debian Lenny system using NetworkManager?
Even though it starts up, darkstat 3.0.712-1 on Jaunty can't decode TCP
traffic because of the
The problem still exists with Jaunty, even when using S99darkstat.
Starting manually still works, which is what I'm doing each session. I
tested with Debian Lenny and Darkstat works fine there, it runs on
startup like it should.
--
darkstat does not start on boot
Unfortunately your workaround isn't working for me (on Jaunty). Manually
executing 'sudo /etc/init.d/darkstat start' works, and also produces the
two processes (possibly another bug).
--
darkstat does not start on boot
https://bugs.launchpad.net/bugs/249038
You received this bug notification
I'm now use a fresh installed ubuntu 8.10 server 32bit (at the time of
my last post i used the 8.10 desktop 32bit). Both versions on the same
machine. Experiencing the same behaviour after installing darkstat,
solved it with the same solution. Darkstat Version is 3.0.708-2.
Maybe You want to try
Same problem here, but i found a workaround.
Three commands in the shell:
sudo su
update-rc.d -f darkstat remove
update-rc.d darkstat defaults 89
Now darkstat starts later in the boot process. This brings darkstat to
work, maybe because NetworkManager or another Prog is confusing darkstat
at
