> do_bindings: [0] bind failed: Address already in use

This seems like you have more than one process listening for an incoming
connection to saned.

Please see the last three sections of /usr/share/doc/sane-
utils/README.Debian. These each describe a different method of enabling
the daemon (inetd, systemd, or sysvinit). You should only be using one
method.

Note that with inetd or systemd, the saned process is not started until
there is an actual connection. However it will be listening on TCP port
6566. Please check the output of "ss -p -l -t" to see what process(es)
are listening on this port.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1888928

Title:
  "getaddrinfo for local hostname failed: No address associated with
  hostname" for  IPv4 to IPv6 converted address

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I am trying to setup saned for remote scanning, but without luck. On
  server side I have allowed 192.168.1.0/24 subnet, but remote host does
  not find a scanner. During investigation I found the following in
  server's logs:

  Jul 25 11:40:42 X saned[4167]: bailing out, waiting for children...
  Jul 25 11:40:42 X saned[4167]: bail_out: all children exited
  Jul 25 11:40:42 X saned[4299]: saned (AF-indep+IPv6) from sane-backends 
1.0.30 starting up
  Jul 25 11:40:42 X saned[4299]: do_bindings: [0] bind failed: Address already 
in use
  Jul 25 11:40:42 X saned[4300]: Now daemonized
  Jul 25 11:40:43 X saned[4314]: check_host: access by remote host: 
::ffff:192.168.1.2
  Jul 25 11:40:43 X saned[4314]: check_host: getaddrinfo for local hostname 
failed: No address associated with hostname
  Jul 25 11:40:43 X saned[4314]: init: access by host ::ffff:192.168.1.2 denied
  Jul 25 11:40:43 X saned[4314]: quit: exiting

  
  It looks to me like it is treating the IPv4 to IPv6 converted address as a 
hostname and trying to resolve it, what of course fails. This looks like a bug 
for me. Adding "::ffff:192.168.1.2" to access list does not resolve the problem.

  
  # sysctl -a | grep "net.ipv6.bindv6only"
  net.ipv6.bindv6only = 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1888928/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to