[sane-devel] Scanbd fails to start with multiple scanners (and no paper loaded)

[Wilhelm]

Hi Greg,

please

1) post your scabd config files
2) provide scanbd version information

I see a page-load event with no script defined - looks strange.

You said that there wasn't any paper load: so the page-load event get
fired without any paper load action? More strange.

3) Can please give the full log from scanbd startup till crash.

Does the problem remain with only one scanner?


Am 20.05.2015 um 16:49 schrieb Greg Kontos:
> Hello,
> 
>  
> 
> I’m running scanbd on a debian machine with version 1.0.25 of the
> sane-backend.  I installed scanbd using apt-get, sane-backend was
> compiled from a git clone.  I’m using two fujitsu fi-7160 scanners in my
> setup.  The problem: If there is no paper loaded in at least one
> scanner, scanbd.service will exit the main process and abort.  This
> failure will at a variety of times depending on the circumstances.  It
> will happen during startup of the machine.  It will also happen after a
> few minutes after a scan process is complete.  This post-scan behavior
> is not 100% replicable. 
> 
>  
> 
> The following is /var/log/syslog after a system restart.  : (I can
> provide a more detailed log if that will be helpful)
> 
>  
> 
> May 20 09:36:40 hp6300pro-23 systemd[1151]: Starting Paths.
> 
> May 20 09:36:40 hp6300pro-23 systemd[1151]: Reached target Paths.
> 
> May 20 09:36:40 hp6300pro-23 systemd[1151]: Starting Timers.
> 
> May 20 09:36:40 hp6300pro-23 systemd[1151]: Reached target Timers.
> 
> May 20 09:36:40 hp6300pro-23 systemd[1151]: Starting Sockets.
> 
> May 20 09:36:40 hp6300pro-23 systemd[1151]: Reached target Sockets.
> 
> May 20 09:36:40 hp6300pro-23 systemd[1151]: Starting Basic System.
> 
> May 20 09:36:40 hp6300pro-23 systemd[1151]: Reached target Basic System.
> 
> May 20 09:36:40 hp6300pro-23 systemd[1151]: Starting Default.
> 
> May 20 09:36:40 hp6300pro-23 systemd[1151]: Reached target Default.
> 
> May 20 09:36:40 hp6300pro-23 systemd[1151]: Startup finished in 4ms.
> 
> May 20 09:37:06 hp6300pro-23 scanbd: /usr/sbin/scanbd: trigger action
> for page-loaded for device fujitsu:fi-7160:188290 with script (null)
> 
> May 20 09:37:07 hp6300pro-23 scanbd: /usr/sbin/scanbd: trigger action
> for page-loaded for device fujitsu:fi-7160:187984 with script (null)
> 
> May 20 09:40:13 hp6300pro-23 scanbd[542]: scanbd: sane.c:852: sane_poll:
> Assertion `st->triggered_option < st->num_of_options_with_scripts' failed.
> 
> May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: dbus match
> type='signal',interface='org.freedesktop.Hal.Manager'
> 
> May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger
> action for page-loaded for device fujitsu:fi-7160:188290 with script (null)
> 
> May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger
> action for page-loaded for device fujitsu:fi-7160:187984 with script (null)
> 
> May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger
> action for page-loaded for device fujitsu:fi-7160:188290 with script (null)
> 
> May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger
> action for page-loaded for device fujitsu:fi-7160:188290 with script (null)
> 
> May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger
> action for page-loaded for device fujitsu:fi-7160:188290 with script (null)
> 
> May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger
> action for page-loaded for device fujitsu:fi-7160:188290 with script (null)
> 
> May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger
> action for page-loaded for device fujitsu:fi-7160:187984 with script (null)
> 
> May 20 09:40:13 hp6300pro-23 systemd[1]: scanbd.service: main process
> exited, code=killed, status=6/ABRT
> 
> May 20 09:40:13 hp6300pro-23 systemd[1]: Unit scanbd.service entered
> failed state.
> 
>  
> 
> It may be worth noting that there was no paper loaded in the scanners
> when this log file was created.  Also, after the service exits, the
> scanners can both be found using scanimage –L.
> 
>  
> 
> Currently I’ve found a work around : If a piece of paper is kept loaded
> in the scanners, the process starts properly after boot and seems to
> stay active.  Should my use case work with scanbd?  Does anyone know of
> a better work around?  Perhaps there is an option or setting that I have
> overlooked?  Thank you for any help with this issue.
> 
>  
> 
> Thanks,
> G Kontos
> 
> 
> 
> Greg Kontos
> LIMS Integration Specialist
> 
> Innovative Diagnostic Laboratory
> 8751 Park Central Drive, Suite 200
> Richmond, VA 23227
> Phone: (804) 261-3340 ext.1846
> Cell Phone:
> Fax: (804) 515-7291
> gkontos at myinnovativelab.com <mailto:gkontos at myinnovativelab.com>
> 
> Visit our website: www.myinnovativelab.com <http://www.myinnovativelab.com>
> 
> <http://>
> 
> CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents,
> files or previous e-mail messages attached to it contain confidential
> and/or privileged information meant for the listed recipient(s) only.
> You may not distribute or share this correspondence without written
> authorization from the above author.
> 
> If you are not the intended recipient, or a person responsible for
> delivering it to the intended recipient, you are hereby notified that
> any disclosure, copying, distribution or use of any of the information
> contained in or attached to this transmission is STRICTLY PROHIBITED. If
> you have received this transmission in error, please immediately notify
> me by reply e-mail and destroy the original transmission and its
> attachments without saving them in any manner.
> 
> 
> 
> 
> 


-- 
Wilhelm