[sane-devel] scanbd on Raspberry Pi Connection Failed system_bus_socket

[Olaf Schirmer]

Hello Wilhelm

First of all I want to thank you for the fast reply on my question!
Please see below where I've tried to answer your questions. 

I've changed the runlevel links from S01scanbd to S04scanbd, where dbus has S02dbus.
It looks like the dbus daemon is writing the system_bus_socket file nevertheless after scanbd gets started.


########################
pi at raspberrypi:/var/run/dbus$ stat system_bus_socket 
  Datei: „system_bus_socket“
  Größe: 0         	Blöcke: 0          EA Block: 4096   Socket
Gerät: ch/12d	Inode: 2396        Verknüpfungen: 1
Zugriff: (0777/srwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Zugriff    : 2013-03-19 16:12:41.034860256 +0100
Modifiziert: 2013-03-19 16:11:23.280001416 +0100
Geändert   : 2013-03-19 16:11:23.280001416 +0100
 Geburt    : -
pi at raspberrypi:/var/run/dbus$ 
########################


The situation is the same as before :-(

########  SYSLOG ########
Mar 19 16:11:22 raspberrypi scanbd: /usr/local/bin/scanbd: Scanning for local-only devices
Mar 19 16:11:22 raspberrypi scanbd: /usr/local/bin/scanbd: Can't get the scbtn device list
Mar 19 16:11:22 raspberrypi scanbd: /usr/local/bin/scanbd: device list null
Mar 19 16:11:22 raspberrypi scanbd: /usr/local/bin/scanbd: start_scbtn_threads
Mar 19 16:11:22 raspberrypi scanbd: /usr/local/bin/scanbd: start the threads (0)
Mar 19 16:11:22 raspberrypi scanbd: /usr/local/bin/scanbd: start dbus thread
Mar 19 16:11:22 raspberrypi scanbd: /usr/local/bin/scanbd: dbus_init
Mar 19 16:11:22 raspberrypi scanbd: /usr/local/bin/scanbd: DBus connection error: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
#########################



Am 18.03.2013 um 16:09 schrieb Wilhelm:
> 
> please show the file-mode bits

-rwxr-xr-x 1 root staff 136630 Mär  8 10:49 /usr/local/bin/scanbd
-rwxr-xr-x 1 root staff 7740 Mär 14 14:25 /usr/local/etc/scanbd/scanbd.conf


scanbd is running as root
(root      1726     1  0 15:25 ?        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.
> 
> can you track this down to where it happens?

I am sorry, no. I've set the variable now in /etc/environment file
Now I can start scanbd in foreground with scanbd -f only

This is the first part of my scanbd.conf

######
# global settings
global {
        # turn on debugging
        
        # log to console
        debug   = true 

        # debug logging
        # 1=error, 2=warn, 3=info, 4-7=debug
        debug-level = 7
        
        # drop priviliges to this user
        #=============================
        # Linux: 
        # user    = saned # root
        # *BSD
        # user    = root
        user    = root

        # Group to be used
        #=================
        # Linux (most distributions use the lp group to access scanners)
        # group   = lp
        # ArchLinux (ArchLinux uses the scanner group)
        # group = scanner
        #
        # *BSD (no group lp here, use daemon instead)
        # group   = daemon # root
        #
        group   = root

        # the saned executable for manager-mode
        saned   = "/usr/sbin/saned"
        saned_opt  = {} # string-list
        saned_env  = { "SANE_CONFIG_DIR=/usr/local/etc/scanbd" } # list of environment vars for saned
############

> 
>> 
>> 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?
> 
> to place the init-script and add the run-level links should be enough ...

This are the runlevel links

pi at raspberrypi:/etc$ sudo find . -name "*scanbd*" -exec ls -la {} \;
-rw-r--r-- 1 root root 586 Mär 14 14:32 ./dbus-1/system.d/scanbd_dbus.conf
lrwxrwxrwx 1 root root 16 Mär 12 17:07 ./rc1.d/K01scanbd -> ../init.d/scanbd
lrwxrwxrwx 1 root root 16 Mär 19 15:19 ./rc2.d/S04scanbd -> ../init.d/scanbd
lrwxrwxrwx 1 root root 16 Mär 12 17:07 ./rc0.d/K01scanbd -> ../init.d/scanbd
lrwxrwxrwx 1 root root 16 Mär 12 17:07 ./rc4.d/S04scanbd -> ../init.d/scanbd
lrwxrwxrwx 1 root root 16 Mär 12 17:07 ./rc5.d/S04scanbd -> ../init.d/scanbd
lrwxrwxrwx 1 root root 16 Mär 12 17:07 ./rc3.d/S04scanbd -> ../init.d/scanbd
-rwxr-xr-x 1 root root 3908 Mär 15 17:20 ./init.d/scanbd
lrwxrwxrwx 1 root root 16 Mär 12 17:07 ./rc6.d/K01scanbd -> ../init.d/scanbd
pi at raspberrypi:/etc$ 


Thank you in advance for your help.

Olaf



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130319/fdb98bdb/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4145 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130319/fdb98bdb/attachment.bin>