ubuntu 11.10 darkstat can`t start

Bug #902153 reported by Boris
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
darkstat (Ubuntu)
Fix Released
Medium
Unassigned
Precise
Won't Fix
Medium
Unassigned

Bug Description

I`m install darkstat on ubunru 11.10 server.
After installation i have this:

skat@SkatServ:~/darkstat-3.0.714$ sudo darkstat -i eth0
 8301: error: getaddrinfo(NULL,667) failed: Name or service not known: Device or resource busy

So i think it`s mean that port (667) is busy, but it`s free:

skat@SkatServ:~/darkstat-3.0.714$ nmap localhost

Starting Nmap 5.21 ( http://nmap.org ) at 2011-12-09 17:17 MSK
Nmap scan report for localhost (127.0.0.1)
Host is up (0.00092s latency).
Not shown: 999 closed ports
PORT STATE SERVICE
22/tcp open ssh

Nmap done: 1 IP address (1 host up) scanned in 0.16 seconds

Hope it` helpfull

Revision history for this message
Boris (worldskat) wrote :

I`ve install it from repository

Revision history for this message
Emil Mikulic (darkmoon) wrote :

Strange. Try specifying the bind address (-b cmdline flag)

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

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

Changed in darkstat (Ubuntu):
status: New → Confirmed
Revision history for this message
Søren Holm (sgh) wrote :

adding "-b 0.0.0.0" works..... but whyyyyy ?

Revision history for this message
Emil Mikulic (darkmoon) wrote :

It took a while to get the binding code right after IPv6 support was added. Could you please build the latest version from git and tell me if it still has this problem on your system?

git clone http://unix4lyfe.org/git/darkstat
cd darkstat
# important:
git checkout work
autoconf
autoheader
./configure --with-chroot-dir=/tmp
make
sudo ./darkstat -i eth0 --verbose --no-daemon

Revision history for this message
Boris (worldskat) wrote :

I`m test it, it`s ok.

Revision history for this message
Boris (worldskat) wrote :

I mean problem is gone.

Revision history for this message
Emil Mikulic (darkmoon) wrote :

Good to hear! This will be fixed in the next release (of darkstat) then.

Daniel Hahler (blueyed)
Changed in darkstat (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → Medium
Revision history for this message
Daniel Hahler (blueyed) wrote :

I can confirm that this is fixed with version 3.0.715-1 (in Ubuntu Quantal).

I think a StableReleaseUpdate would make sense to get this fix into Ubuntu Precise, too.

Changed in darkstat (Ubuntu):
status: Triaged → Fix Released
Changed in darkstat (Ubuntu Precise):
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in darkstat (Ubuntu Precise):
status: New → Confirmed
Revision history for this message
Steve Langasek (vorlon) wrote :

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release

Changed in darkstat (Ubuntu Precise):
status: Confirmed → Won't Fix
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.