Hi,
On 2021-12-18 9:52 a.m., Brian Potkin wrote:
Machine A has a USB-connected Epson Stylus Photo RX420 shared on the
network (192.168.7.0/24) in saned.conf. Machine B has an UMAX Astra
2400S using a SCSI connection and is also shared. Bothe scanners
work well from their respective machines.
On machine C net.conf contains the IP addresses of A and B. Running
'SANE_DEBUG_NET=128 scanimage -L' give the Epson as didcovered but
not the UMAX. Puzzling. Any suggestions?
[17:12:59.501052] [sanei_debug] Setting debug level of net to 128.
[17:12:59.501610] [net] sane_init: authorize != null, version_code != null
[17:12:59.501703] [net] sane_init: SANE net backend version 1.0.14
(AF-indep+IPv6) from sane-backends 1.0.31-debian
[17:12:59.501779] [net] sane_init: Client has little endian byte order
[17:12:59.501851] [net] sane_init: searching for config file
[17:12:59.502118] [net] sane_init: connect timeout set to 60 seconds
[17:12:59.502205] [net] sane_init: trying to add 192.168.7.20
[17:12:59.502370] [net] add_device: adding backend 192.168.7.20
[17:12:59.508038] [net] add_device: backend 192.168.7.20 added
[17:12:59.508173] [net] sane_init: trying to add 192.168.7.40
[17:12:59.508251] [net] add_device: adding backend 192.168.7.40
[17:12:59.511861] [net] add_device: backend 192.168.7.40 added
[17:12:59.512017] [net] sane_init: done reading config
[17:12:59.512118] [net] sane_init: evaluating environment variable
SANE_NET_HOSTS
[17:12:59.512217] [net] sane_init: evaluating environment variable
SANE_NET_TIMEOUT
[17:12:59.525890] [net] sane_init: done
[17:12:59.526126] [net] sane_get_devices: local_only = 0
[17:12:59.526275] [net] connect_dev: trying to connect to 192.168.7.40
[17:12:59.527935] [net] connect_dev: [0] connection succeeded (IPv4)
[17:12:59.528161] [net] connect_dev: sanei_w_init
[17:12:59.528960] [net] connect_dev: net_init (user=brian, local version=1.0.3)
[17:12:59.536461] [net] net_avahi_browse_callback: CACHE_EXHAUSTED
[17:13:00.537897] [net] net_avahi_browse_callback: ALL_FOR_NOW
[17:13:09.723768] [net] connect_dev: freeing init reply (status=Success, remote
version=1.0.3)
[17:13:09.724077] [net] connect_dev: done
[17:13:10.060260] [net] sane_get_devices: got 192.168.7.40:epson2:libusb:005:003
[17:13:10.060563] [net] connect_dev: trying to connect to 192.168.7.20
[17:13:10.062680] [net] connect_dev: [0] connection succeeded (IPv4)
[17:13:10.062908] [net] connect_dev: sanei_w_init
[17:13:10.063357] [net] connect_dev: net_init (user=brian, local version=1.0.3)
[17:13:10.098176] [net] connect_dev: freeing init reply (status=Success, remote
version=1.0.3)
[17:13:10.098412] [net] connect_dev: done
[17:13:10.141432] [net] sane_get_devices: finished (1 devices)
[17:13:11.279651] [net] sane_exit: exiting
[17:13:11.279903] [net] net_avahi_cleanup: stopping thread
[17:13:11.286575] [net] net_avahi_cleanup: done
[17:13:11.286823] [net] sane_exit: closing dev 0x20d6890, ctl=6
[17:13:11.287337] [net] sane_exit: closing dev 0x20d4430, ctl=7
[17:13:11.288089] [net] sane_exit: finished.
You could try to enable debugging in the saned configuration at the
machine with the SCSI scanner. This might reveal some information. How
you do this depends on how saned is being run.
saned has a -d option to output diag. You can ask it to output to stderr
with the --stderr option, although I think that the default is for it to
go to the syslog.
In addition, you could add the appropriate SANE_DEBUG_* env variable
into the saned environment to switch on diag for the backend appropriate
for your scanner.
Hope this helps.
Cheers,
Ralph
