[sane-devel] scanbd on Raspberry Pi Connection Failed system_bus_socket
Dear all Now some months later and still without an stable solution I want to summarise my experiences with scanbd and a Fujitsu Scansnap FI-5110/EOX2 scanner. I am running scanbd on a raspberry pi. Everything works great except one thing. If I close the cover and reopen it, scanbd will not restart the right way because I get a lot of Interation on dbus call errors. Both xinetd and scanbd will be stopped and started by a udev rule. No problems with that. Now the strange thing: 1. Reboot the machine with open cover = scanbd works fine 2. Cover close and reopen = Iteration on dbus call - error 3. Restart scanbd with open cover (service scanbd restart) = scanbd works fine. I've tried a lot of different users and rights for scanbd and xinetd, but couldn't find a solution . It seems that scanbd has to be started only when xinetd is running completely. How long does it take to start xinetd on a raspberry pi I did not measure. Maybe somewhere there is the answer for my question, but a little help from the developers here would be great. So let me say thank you in advance. Best regards Olaf -- View this message in context: http://sane.10972.n7.nabble.com/scanbd-on-Raspberry-Pi-Connection-Failed-system-bus-socket-tp17350p17772.html Sent from the SANE - Dev mailing list archive at Nabble.com.
[sane-devel] scanbd on Raspberry Pi Connection Failed system_bus_socket
Dear all In the meanwhile I removed and installed scanbd once again. But now I get an Iteration on dbus call error. If scanbd runs from command line with option f it works perfect but not with auto start. If scanbd ist started via rc$.d the Iteration on dbus call occurs. echo $SANE_CONFIG_DIR results in an empty line. The error leaves an entry every second in the syslog file. What can be the reason, please help. Here ist the syslog from boot: Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: debug on: level: 7 Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: daemonize Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: dropping privs to uid saned Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: dropping privs to gid lp Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: drop privileges to gid: 7 Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: Running as effective gid 7 Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: drop privileges to uid: 107 Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: Running as effective uid 107 Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: dbus_init Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager' Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: sane version 1.0 Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: Scanning for local-only devices Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: start_sane_threads Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: start dbus thread Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: timeout: 500 ms Apr 12 15:49:39 raspberrypi scanbd: /usr/local/bin/scanbd: Iteration on dbus call Apr 12 15:49:40 raspberrypi scanbd: /usr/local/bin/scanbd: Iteration on dbus call Apr 12 15:49:40 raspberrypi xinetd[1443]: Reading included configuration file: /etc/xinetd.d/chargen [file=/etc/xinetd.conf] [line=14] Apr 12 15:49:40 raspberrypi xinetd[1443]: Reading included configuration file: /etc/xinetd.d/daytime [file=/etc/xinetd.d/daytime] [line=28] Apr 12 15:49:40 raspberrypi xinetd[1443]: Reading included configuration file: /etc/xinetd.d/discard [file=/etc/xinetd.d/discard] [line=26] Apr 12 15:49:40 raspberrypi xinetd[1443]: Reading included configuration file: /etc/xinetd.d/echo [file=/etc/xinetd.d/echo] [line=25] Apr 12 15:49:40 raspberrypi xinetd[1443]: Reading included configuration file: /etc/xinetd.d/sane-port [file=/etc/xinetd.d/sane-port] [line=26] Apr 12 15:49:40 raspberrypi xinetd[1443]: Reading included configuration file: /etc/xinetd.d/time [file=/etc/xinetd.d/time] [line=12] -- View this message in context: http://sane.10972.n7.nabble.com/scanbd-on-Raspberry-Pi-Connection-Failed-system-bus-socket-tp17350p17471.html Sent from the SANE - Dev mailing list archive at Nabble.com.
[sane-devel] scanbd on Raspberry Pi Connection Failed system_bus_socket
Hello all I try to use a Rasperry Pi with Raspian Wheezy as a network scanner device. After I have installed /scanbd/ as described in the package-readme and some copying of files, I can use it in foreground with scanbd -f. The scanner is recognised an I can use scanner buttons as I want it. The problem is to load the daemon in background at system boot. The /var/log/syslog shows an error at starting up scanbd: Mar 18 10:27:18 raspberrypi scanbd: /usr/local/bin/scanbd: DBus connection error: Failed to connect to to socket /var/run/dbus/system_bus_socket: No such file or directory The scanbd gets started but does nothing. The missed file system_bus_socket exists in the meantioned directory. Its timestamp is equal to the log-entry (10:27:18) $ ps -ef |grep scan root 1729 1 0 10:27 ?00:00:00 /usr/local/bin/scanbd -c /usr/local/etc/scanbd/scanbd.conf Also it seams that the environment variable $SANE_CONFIG_DIR ist not set at boot because an echo-command prints an empty row. If I set the variable manually by using export export SANE_CONFIG_DIR=/usr/local/etc/scanbd I can run in background with scanbd -c /usr/local/etc/scanbd/scanbd.conf and everything runs as expected. Do I have something to change in boot process or with read permissions? Thanks in advance, guys. -- View this message in context: http://sane.10972.n7.nabble.com/scanbd-on-Raspberry-Pi-Connection-Failed-system-bus-socket-tp17350.html Sent from the SANE - Dev mailing list archive at Nabble.com.
