Ubuntu
sane-backends package

Two saned processes and "bind failed: Address already in use"

Bug #656675 reported by jhansonxi
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
sane-backends (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Ubuntu 10.04 (Lucid Lynx) i386

Whenever saned starts it ends up with two processes running and the following log entries:

saned[1470]: bailing out, waiting for children...
saned[1470]: bail_out: all children exited
saned[4387]: saned (AF-indep+IPv6) from sane-backends 1.0.20 starting up
saned[4387]: do_bindings: [0] bind failed: Address already in use
saned[4388]: Now daemonized
saned[4388]: Dropped privileges to uid 118 gid 122

This occurs with both Inetd and daemon configurations. When it's stopped I can see that no other saned processes are running but when started two always show up along with the error.

This is mostly a cosmetic problem as network scanning through saned still functions.

Revision history for this message
jhansonxi (jhansonxi) wrote :

Possible upstream bug: https://alioth.debian.org/tracker/?func=detail&atid=410366&aid=312422&group_id=30186

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

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

Changed in sane-backends (Ubuntu):
status: New → Confirmed
Revision history for this message
mlx (myxal-mxl) wrote :

Has this changed in the 4 years since? I just tried saned on 12.04, then 14.04, and the same problem occurs on both of them.
Indeed, ps listing reveals 2 saned processes running, with only 1 of them being bound to only tcp6.

Revision history for this message
Steve Dodd (anarchetic) wrote :

Still seeing this in 18.04! Gave up, disabled /etc/init.d/saned, and used the systemd socket service - but this doesn't seem to advertise the saned server.

Revision history for this message
Steve Dodd (anarchetic) wrote :

OK, I think this is not a (huge) bug .. looking at saned code, it tries to bind v6 and v4 sockets separately. If /proc/sys/net/ipv6/bindv6only isn't set, binding v6 will also bind v4, making the later explicit v4 bind fail.

The second process is probably the one responsible for avahi advertisements.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.