[sane-devel] where is my socket error?
ToddAndMargo
ToddAndMargo at zoho.com
Sat Nov 25 03:15:52 UTC 2017
Dear List,
This is a systemd question:
I have saned.socket and saned at .service configured.
When I put a trace on journalctl (-efx) and fire up PDF Creator,
I get the following. Please note that the crypographic stuff
only happens when I press the scan button on PDF Creator. I
duplicated it three times. This computer is luks encrypted.
Where is the error?
Many thanks,
-T
Nov 24 19:09:44 foo.bar.local systemd[1]: Started Scanner Service
(127.0.0.1:54998).
-- Subject: Unit saned at 3-127.0.0.1:6566-127.0.0.1:54998.service has
finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit saned at 3-127.0.0.1:6566-127.0.0.1:54998.service has finished
starting up.
--
-- The start-up result is done.
Nov 24 19:09:44 foo.bar.local systemd[1]: Starting Scanner Service
(127.0.0.1:54998)...
-- Subject: Unit saned at 3-127.0.0.1:6566-127.0.0.1:54998.service has
begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit saned at 3-127.0.0.1:6566-127.0.0.1:54998.service has begun
starting up.
Nov 24 19:09:44 foo.bar.local systemd[1]: Starting Cryptography Setup
for lin-bak...
-- Subject: Unit systemd-cryptsetup at lin\x2dbak.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-cryptsetup at lin\x2dbak.service has begun starting up.
Nov 24 19:09:44 foo.bar.local saned[9893]: saned (AF-indep+IPv6) from
sane-backends 1.0.24 starting up
Nov 24 19:09:44 foo.bar.local saned[9893]: check_host: access by remote
host: localhost
Nov 24 19:09:44 foo.bar.local saned[9893]: init: access by host
localhost denied
Nov 24 19:09:44 foo.bar.local saned[9893]: saned exiting
Nov 24 19:09:44 foo.bar.local systemd-cryptsetup[9894]: crypt_load()
failed on device /dev/sdb1.
Nov 24 19:09:44 foo.bar.local systemd-cryptsetup[9894]: Failed to
activate: Invalid argument
Nov 24 19:09:44 foo.bar.local systemd[1]:
systemd-cryptsetup at lin\x2dbak.service: main process exited, code=exited,
status=1/FAILURE
Nov 24 19:09:44 foo.bar.local systemd[1]: Failed to start Cryptography
Setup for lin-bak.
-- Subject: Unit systemd-cryptsetup at lin\x2dbak.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-cryptsetup at lin\x2dbak.service has failed.
--
-- The result is failed.
Nov 24 19:09:44 foo.bar.local systemd[1]: Dependency failed for
dev-mapper-lin\x2dbak.device.
-- Subject: Unit dev-mapper-lin\x2dbak.device has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dev-mapper-lin\x2dbak.device has failed.
--
-- The result is dependency.
Nov 24 19:09:44 foo.bar.local systemd[1]: Job
dev-mapper-lin\x2dbak.device/start failed with result 'dependency'.
Nov 24 19:09:44 foo.bar.local systemd[1]: Unit
systemd-cryptsetup at lin\x2dbak.service entered failed state.
Nov 24 19:09:44 foo.bar.local systemd[1]:
systemd-cryptsetup at lin\x2dbak.service failed.
Nov 24 19:10:01 foo.bar.local systemd[1]: Started Session 42 of user root.
-- Subject: Unit session-42.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-42.scope has finished starting up.
--
-- The start-up result is done.
Nov 24 19:10:01 foo.bar.local systemd[1]: Starting Session 42 of user root.
-- Subject: Unit session-42.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-42.scope has begun starting up.
Nov 24 19:10:01 foo.bar.local CROND[9912]: (root) CMD (/usr/lib64/sa/sa1
1 1)
More information about the sane-devel
mailing list