stefan
2020-02-04 13:30:01 UTC
Package: sane-utils
Version: 1.0.27-3.2
Severity: important
Manual starting of saned (as user saned) works. I can access the scanners remotley.
But if saned is started via systemd, it does not work. scanimage -L on a client does not find anything.
dpkg-reconfigure offers two otions. Run as standalone server and start on demand (using inetd) I tried out both but that makes no difference.
Is it possible to run saned permanently?
Regards Stefan
-- System Information:
Debian Release: 10.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.3.0-0.bpo.2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages sane-utils depends on:
ii adduser 3.118
ii debconf [debconf-2.0] 1.5.71
ii libavahi-client3 0.7-4+b1
ii libavahi-common3 0.7-4+b1
ii libc6 2.28-10
ii libieee1284-3 0.2.11-13
ii libjpeg62-turbo 1:1.5.2-2+b1
ii libpng16-16 1.6.36-6
ii libsane 1.0.27-3.2
ii libsystemd0 241-7~deb10u2
ii libusb-1.0-0 2:1.0.22-2
ii lsb-base 10.2019051400
ii update-inetd 4.49
sane-utils recommends no packages.
Versions of packages sane-utils suggests:
ii avahi-daemon 0.7-4+b1
pn unpaper <none>
-- Configuration Files:
/etc/default/saned changed:
RUN=yes
RUN_AS_USER=saned
/etc/sane.d/saned.conf changed:
localhost
192.168.1.0/24
-- debconf information:
* sane-utils/saned_scann
Version: 1.0.27-3.2
Severity: important
Manual starting of saned (as user saned) works. I can access the scanners remotley.
But if saned is started via systemd, it does not work. scanimage -L on a client does not find anything.
● saned.socket - saned incoming socket
Loaded: loaded (/lib/systemd/system/saned.socket; enabled; vendor preset: enabled)
Active: active (listening) since Tue 2020-02-04 13:56:52 CET; 6min ago
Listen: [::]:6566 (Stream)
Accepted: 1; Connected: 0;
Tasks: 0 (limit: 4915)
Memory: 68.0K
CGroup: /system.slice/saned.socket
Feb 04 13:56:52 ws2 systemd[1]: Listening on saned incoming socket.
● saned.service
Loaded: masked (Reason: Unit saned.service is masked.)
Active: inactive (dead)
I cannot unmask it.Loaded: loaded (/lib/systemd/system/saned.socket; enabled; vendor preset: enabled)
Active: active (listening) since Tue 2020-02-04 13:56:52 CET; 6min ago
Listen: [::]:6566 (Stream)
Accepted: 1; Connected: 0;
Tasks: 0 (limit: 4915)
Memory: 68.0K
CGroup: /system.slice/saned.socket
Feb 04 13:56:52 ws2 systemd[1]: Listening on saned incoming socket.
● saned.service
Loaded: masked (Reason: Unit saned.service is masked.)
Active: inactive (dead)
dpkg-reconfigure offers two otions. Run as standalone server and start on demand (using inetd) I tried out both but that makes no difference.
Feb 4 13:57:37 ws2 systemd[1]: Created slice system-saned.slice.
Feb 4 13:57:37 ws2 systemd[1]: Started Scanner Service (192.168.1.60:46168).
Feb 4 13:57:37 ws2 saned[1080]: saned (AF-indep+IPv6+systemd) from sane-backends 1.0.27 starting up
Feb 4 13:57:37 ws2 saned[1080]: check_host: access by remote host: ::ffff:192.168.1.60
Feb 4 13:57:43 ws2 saned[1080]: saned exiting
It seems that systemd starts on demand. Maybe this is the problem.Feb 4 13:57:37 ws2 systemd[1]: Started Scanner Service (192.168.1.60:46168).
Feb 4 13:57:37 ws2 saned[1080]: saned (AF-indep+IPv6+systemd) from sane-backends 1.0.27 starting up
Feb 4 13:57:37 ws2 saned[1080]: check_host: access by remote host: ::ffff:192.168.1.60
Feb 4 13:57:43 ws2 saned[1080]: saned exiting
Is it possible to run saned permanently?
Regards Stefan
-- System Information:
Debian Release: 10.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.3.0-0.bpo.2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages sane-utils depends on:
ii adduser 3.118
ii debconf [debconf-2.0] 1.5.71
ii libavahi-client3 0.7-4+b1
ii libavahi-common3 0.7-4+b1
ii libc6 2.28-10
ii libieee1284-3 0.2.11-13
ii libjpeg62-turbo 1:1.5.2-2+b1
ii libpng16-16 1.6.36-6
ii libsane 1.0.27-3.2
ii libsystemd0 241-7~deb10u2
ii libusb-1.0-0 2:1.0.22-2
ii lsb-base 10.2019051400
ii update-inetd 4.49
sane-utils recommends no packages.
Versions of packages sane-utils suggests:
ii avahi-daemon 0.7-4+b1
pn unpaper <none>
-- Configuration Files:
/etc/default/saned changed:
RUN=yes
RUN_AS_USER=saned
/etc/sane.d/saned.conf changed:
localhost
192.168.1.0/24
-- debconf information:
* sane-utils/saned_scann