Server 20.04 - sane is not responding

[David Fletcher]

On Sat, 2020-05-23 at 12:34 +0200, Oliver Grawert wrote:
> hi,
> Am Freitag, den 22.05.2020, 21:01 +0100 schrieb David Fletcher:
> > administrator at ServerIV:$ sudo systemctl unmask saned
> > [sudo] password for administrator: 
> > administrator at ServerIV:$ sudo systemctl enable --now saned
> > Synchronizing state of saned.service with SysV service script with
> > /lib/systemd/systemd-sysv-install.
> > Executing: /lib/systemd/systemd-sysv-install enable saned
> > Failed to enable unit: Unit file /lib/systemd/system/saned.service is
> > masked.
> 
> this either means the actual unit to switch back to when unmasking is
> not actually there or that your machine watched too many covid news and
> is too scared to take off the mask now ... 
> 
> try
> 
> sudo apt install sane-utils
> 
> see if the symlink to /dev/null is gone after this. if not, do the
> systemctl unmask and enable dance again, the unmasking should hopefully
>  work... (if that still doesnt work, just rm the symlink manually)

I now get:-
administrator at ServerIV:~$ sudo systemctl unmask saned
administrator at ServerIV:~$ sudo systemctl enable --now saned
saned.service is not a native service, redirecting to
systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable saned
administrator at ServerIV:~$ 

xsane still says no devices available.

I've even tried powering up the 14.04 system again and adding its new
address to /etc/sane.d/net.conf on the desktop and now that won't work
either! Grrrrr

I also added
RUN=yes
to /etc/default/saned as per
https://help.ubuntu.com/community/ScanningHowTo#Sharing_a_Scanner_Over_a_Network and it still won't work.

Does this shed any light on why?
administrator at ServerIV:~$ service saned start
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to start 'saned.service'.
Authenticating as: David Fletcher (administrator)
Password: 
==== AUTHENTICATION COMPLETE ===
Job for saned.service failed because the control process exited with
error code.
See "systemctl status saned.service" and "journalctl -xe" for details.
administrator at ServerIV:~$ systemctl status saned.service
● saned.service - LSB: SANE network scanner server
     Loaded: loaded (/etc/init.d/saned; generated)
     Active: failed (Result: exit-code) since Sat 2020-05-23 14:42:44
BST; 37s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 3707 ExecStart=/etc/init.d/saned start (code=exited,
status=1/FAILURE)

May 23 14:42:44 ServerIV saned[3707]:  * Starting SANE network scanner
server saned
May 23 14:42:44 ServerIV saned[3729]: saned (AF-indep+IPv6) from
sane-backends 1.0.29 starting up
May 23 14:42:44 ServerIV saned[3729]: do_bindings: [1] bind failed:
Address already in use
May 23 14:42:44 ServerIV saned[3729]: do_bindings: [0] bind failed:
Address already in use
May 23 14:42:44 ServerIV saned[3729]: do_bindings: couldn't bind an
address. Exiting.
May 23 14:42:44 ServerIV saned[3729]: FATAL ERROR; bailing out, waiting
for children...
May 23 14:42:44 ServerIV saned[3729]: bail_out: all children exited
May 23 14:42:44 ServerIV systemd[1]: saned.service: Control process
exited, code=exited, status=1/FAILURE
May 23 14:42:44 ServerIV systemd[1]: saned.service: Failed with result
'exit-code'.
May 23 14:42:44 ServerIV systemd[1]: Failed to start LSB: SANE network
scanner server.
administrator at ServerIV:~$ 

Something to do with ipv6 which I'm not using yet because Virgin Media
is still in the last century?

I've had enough of this for now. I know what SANE stands for but for me
today, it isn't. Off out for a walk if it's not raining.

Dave