Package: sane-utils Version: 1.0.24-8 Severity: normal saned does not accept any connections on my scan server after the upgrade to jessie and to systemd.
as suggested in README.Debian, i've run `systemctl enable saned.socket` to run saned via systemd. whenever a connection comes in i get the following output in journalctl: Jul 09 17:50:15 poseidon-print systemd[1]: Starting Scanner Service (10.13.13.129:35845)... Jul 09 17:50:15 poseidon-print systemd[1]: Started Scanner Service (10.13.13.129:35845). Jul 09 17:50:15 poseidon-print saned[1863]: saned (AF-indep+IPv6) from sane-backends 1.0.24 starting up Jul 09 17:50:15 poseidon-print saned[1863]: check_host: access by remote host: localhost Jul 09 17:50:15 poseidon-print saned[1863]: init: bad status=22 or procnum=1 Jul 09 17:50:15 poseidon-print saned[1863]: saned exiting i've had access list issues before (now that saned takes connections as sockets, i had to replace the 10.13.13.0/24 previously in the saned.conf file with localhost), but that seems to be resolved. saned runs fine when stopping the saned.socket service and running /usr/sbin/saned -d10 as the user saned. -- System Information: Debian Release: jessie Kernel: Linux 43.16.0-4-amd64 Shell: /bin/sh linked to /bin/dash Init: systemd (via /sbin/init) sorry for the abbreviated system information, the scan server doesn't run reportbug. -- debconf information excluded -- To use raw power is to make yourself infinitely vulnerable to greater powers. -- Bene Gesserit axiom
signature.asc
Description: Digital signature
