Sane error on HP Photosmart 2570 All-In-One

[Piet de Vries]

Hi,

I just stumbled upon openDIAS for my personal filing needs. The features seem just enough for a home archive. I installed the latest version op openDAIS on a fresh virtual machine running Ubuntu Server 12.04LTS. For installation I used the .deb-file available on the openDAIS-site. I configured sane by using the hpsetup ulitilty which is part of HPLIP. My PhotoSmart is well recognized and printing works and also scanning from the command line works. BTW the printer is connected through Ethernet.

When I try to scan form openDAIS I get an error "Error while scanning: 3", from the log-file I learn that the error reads "Cannot start scanning: sane error = 3 (Device busy), return code =0"

I cannot figure out what could be wrong, openDAIS finds my scanner and from the command-line I find the scanner with the command scanimage -L both as root and a norma user. Als scanning whith the scanimage command works. I tried shutting down cups down but after that the scanner cannot be found any more.

Does someone have a solution?.

When I get openDIAS working to my satisfaction I will volunteer for translation of openDAIS to Dutch.

Kind regards,

Piet de Vries

[Wayne Booth]

Hi Piet,

Sorry to here you are having trouble.

Hopefully we can get to the bottom of your issue. To help in that, can you increase the logging level using the following command:

   opendiasconfig -s log_verbosity -v 4

Restart openDIAS, then re-attempt a scan, and post the log contents here.

Cheers.

Wayne Booth

[Piet de Vries]

Hi Wayne,

Google is giving me back 340 errors so maybe this will be my 4th reaction. I had already prepared a logfile with extra verbosity In text, Copy Paste the logfile looks like;

20121224180110:B772D740:INF: Setting default log verbosity to 4.
20121224180110:B772D740:INF: Using config file: /etc/opendias/opendias.conf
20121224180110:B772D740:INF: Which says the database is at: /var/lib/opendias
20121224180110:B772D740:DBG: database file is /var/lib/opendiasopenDIAS.sqlite3
20121224180110:B772D740:DBG: Dir structure is in-place, database should exist
20121224180110:B772D740:DBG: Checking for a populated database
20121224180110:B772D740:DBG: Run Query (852f870)
20121224180110:B772D740:DBG: We have one. So will check to see what verstion it is.
20121224180110:B772D740:DBG: Free recordset (852f870)
20121224180110:B772D740:DBG: Run Query (852f870)
20121224180110:B772D740:DBG: Database reports that it is version: 6
20121224180110:B772D740:DBG: Free recordset (852f870)
20121224180110:B772D740:INF: Connected to database
20121224180110:B772D740:INF: database opened
20121224180110:B772D740:DBG: Run Query (852f870)
20121224180110:B772D740:INF: Config setting: log_verbosity = 4
20121224180110:B772D740:INF: Moving log verbosity from 4 to 4
20121224180110:B772D740:INF: Config setting: scan_directory = /var/lib/opendias
20121224180110:B772D740:INF: Config setting: show_all_available = 1
20121224180110:B772D740:INF: Config setting: port = 8988
20121224180110:B772D740:INF: Config setting: log_directory = /var/log/opendias
20121224180110:B772D740:DBG: Free recordset (852f870)
20121224180110:B772D740:DBG: loading translation file: /usr/local/share/opendias/language.resource.en
20121224180110:B772D740:INF: Sane backend started
20121224180110:B772D740:INF: Sane command socket is open
20121224180110:B772D740:INF: ... Starting up the openDias service.
20121224180110:B772D740:INF: ready to accept connectons
20121224180120:B772BB40:DBG: Language setting (from header) is: en
20121224180120:B772BB40:INF: Serving request:
20121224180120:B772BB40:DBG: Serving root request
20121224180120:B772BB40:DBG: Language setting (from header) is: en
20121224180120:B772BB40:INF: Serving request: /style/common.css
20121224180120:B772BB40:DBG: Language setting (from header) is: en
20121224180120:B772BB40:INF: Serving request: /includes/jquery.js
20121224180120:B772BB40:DBG: Language setting (from header) is: en
20121224180120:B772BB40:INF: Serving request: /includes/openDias.language.js
20121224180120:B772BB40:DBG: Language setting (from header) is: en
20121224180120:B772BB40:INF: Serving request: /images/openDIAS_sml.png
20121224180120:B772BB40:DBG: Language setting (from header) is: en
20121224180120:B772BB40:INF: Serving request: /images/opendias.jpg
20121224180120:B772BB40:DBG: Language setting (from header) is: en
20121224180120:B772BB40:INF: Serving request: /images/cabinet.jpg
20121224180121:B772BB40:DBG: Language setting (from header) is: en
20121224180121:B772BB40:INF: Serving request: /images/texture.png
20121224180123:B772BB40:DBG: Language setting (from header) is: en
20121224180123:B772BB40:DBG: Run Query (b6e086e0)
20121224180123:B772BB40:DBG: Free recordset (b6e086e0)
20121224180123:B772BB40:DBG: Run Query (b6e086e0)
20121224180123:B772BB40:DBG: Free recordset (b6e086e0)
20121224180123:B772BB40:DBG: Access 'granted' to user on 192.168.200.170 for request: /acquire.html
20121224180123:B772BB40:INF: Serving request: /acquire.html
20121224180123:B772BB40:DBG: Language setting (from header) is: en
20121224180123:B772BB40:INF: Serving request: /includes/openDias.language.js
20121224180123:B772BB40:DBG: Language setting (from header) is: en
20121224180123:B772BB40:INF: Serving request: /includes/jquery.js
20121224180123:B772BB40:DBG: Language setting (from header) is: en
20121224180123:B772BB40:INF: Serving request: /includes/jquery-ui.min.js
20121224180123:B772BB40:DBG: Language setting (from header) is: en
20121224180123:B772BB40:INF: Serving request: /includes/sprintf-0.7-beta1.js
20121224180123:B772BB40:DBG: Language setting (from header) is: en
20121224180123:B772BB40:INF: Serving request: /style/common.css
20121224180123:B772BB40:DBG: Language setting (from header) is: en
20121224180123:B772BB40:INF: Serving request: /includes/jquery.canvas-loader.js
20121224180123:B772BB40:DBG: Language setting (from header) is: en
20121224180123:B772BB40:INF: Serving request: /style/jquery-ui.css
20121224180123:B772BB40:DBG: Language setting (from header) is: en
20121224180123:B772BB40:INF: Serving request: /includes/local/generic.resource
20121224180123:B772BB40:DBG: Language setting (from header) is: en
20121224180123:B772BB40:INF: Serving request: /includes/openDias.acquire.js
20121224180123:B772BB40:DBG: Language setting (from header) is: en
20121224180123:B772BB40:INF: Serving request: /includes/local/openDias.acquire.js.resource
20121224180124:B772BB40:DBG: Language setting (from header) is: en
20121224180124:B772BB40:INF: Serving request: /images/openDIAS_sml.png
20121224180124:B772BB40:DBG: Language setting (from header) is: en
20121224180124:B772BB40:INF: Serving request: /images/texture.png
20121224180124:B772BB40:DBG: Language setting (from header) is: en
20121224180124:B772BB40:DBG: Run Query (b6e086e0)
20121224180124:B772BB40:DBG: Free recordset (b6e086e0)
20121224180124:B772BB40:DBG: Run Query (b6e086e0)
20121224180124:B772BB40:DBG: Free recordset (b6e086e0)
20121224180124:B772BB40:DBG: Access 'granted' to user on 192.168.200.170 for request: /dynamic
20121224180124:B772BB40:DBG: Collected post data:
20121224180124:B772BB40:DBG:       action : getScannerList
20121224180124:B772BB40:INF: Processing request for: getScannerList
20121224180124:B772BB40:DBG: CLIENT: The command structure has been initalised and wants to send the command of: internalGetScannerList:en.
20121224180124:B772D740:DBG: SERVER: The sane command port has received an incomming connection.
20121224180124:B772D740:INF: SERVER: Sane dispatcher received the command: 'internalGetScannerList' with param of 'en'
20121224180127:B772D740:DBG: device(s) found
20121224180127:B772D740:DBG: sane_open
20121224180130:B772D740:DBG: loading translation file: /usr/local/share/opendias/language.resource.en
20121224180130:B772D740:ERR: cannot find result - returning the key instead
20121224180130:B772D740:DBG: Resolution setting detected as 'word list': lastIndex = 8
20121224180130:B772D740:DBG: index results 1 --> 75
20121224180130:B772D740:DBG: index results 2 --> 100
20121224180130:B772D740:DBG: index results 3 --> 150
20121224180130:B772D740:DBG: index results 4 --> 200
20121224180130:B772D740:DBG: index results 5 --> 300
20121224180130:B772D740:DBG: index results 6 --> 600
20121224180130:B772D740:DBG: index results 7 --> 1200
20121224180130:B772D740:DBG: index results 8 --> 2400
20121224180130:B772D740:DBG: Determined max resultion to be 2400
20121224180130:B772D740:DBG: sane_cancel
20121224180130:B772D740:DBG: sane_close
20121224180130:B772D740:DBG: SERVER: Going to send the response of: <?xml version='1.0' encoding='utf-8'?>
<Response><ScannerList%s><Devices><Device><vendor>Hewlett-Packard</vendor><model>Photosmart_2570_series</model><type>All-in-one</type><name>hpaio:/net/Photosmart_2570_series?zc=PhotoSmart</name><Formats><format>Grey Scale</format></Formats><max>2400</max><min>50</min><default>300</default><host>LOCAL_opendias_server</host></Device></Devices></ScannerList></Response>
20121224180130:B772D740:DBG: SERVER: Server has closed it's socket.
20121224180130:B772BB40:DBG: CLIENT: has closed its socket.
20121224180130:B772BB40:DBG: Caching the response.
20121224180130:B772BB40:DBG: RESPONSE WAS: <?xml version='1.0' encoding='utf-8'?>
<Response><ScannerList><Devices><Device><vendor>Hewlett-Packard</vendor><model>Photosmart_2570_series</model><type>All-in-one</type><name>hpaio:/net/Photosmart_2570_series?zc=PhotoSmart</name><Formats><format>Grey Scale</format></Formats><max>2400</max><min>50</min><default>300</default><host>LOCAL_opendias_server</host></Device></Devices></ScannerList></Response>
20121224180130:B772BB40:DBG: Serving the following content: <?xml version='1.0' encoding='utf-8'?>
<Response><ScannerList><Devices><Device><vendor>Hewlett-Packard</vendor><model>Photosmart_2570_series</model><type>All-in-one</type><name>hpaio:/net/Photosmart_2570_series?zc=PhotoSmart</name><Formats><format>Grey Scale</format></Formats><max>2400</max><min>50</min><default>300</default><host>LOCAL_opendias_server</host></Device></Devices></ScannerList></Response>
20121224180130:B772BB40:DBG: Language setting (from header) is: en
20121224180130:B772BB40:INF: Serving request: /images/jquery-ui/ui-bg_glass_50_3baae3_1x400.png
20121224180130:B772BB40:DBG: Language setting (from header) is: en
20121224180130:B772BB40:INF: Serving request: /images/jquery-ui/ui-bg_highlight-hard_100_f2f5f7_1x100.png
20121224180130:B772BB40:DBG: Language setting (from header) is: en
20121224180130:B772BB40:INF: Serving request: /images/jquery-ui/ui-bg_highlight-hard_100_deedf7_1x100.png
20121224180130:B772BB40:ERR: Could not open file: /usr/local/share/opendias/webcontent/images/jquery-ui/ui-bg_highlight-hard_100_deedf7_1x100.png
20121224180130:B772BB40:DBG: Language setting (from header) is: en
20121224180130:B772BB40:INF: Serving request: /images/jquery-ui/ui-bg_glass_80_d7ebf9_1x400.png
20121224180131:B772BB40:DBG: Language setting (from header) is: en
20121224180131:B772BB40:INF: Serving request: /images/jquery-ui/ui-bg_glass_100_e4f1fb_1x400.png
20121224180135:B772BB40:DBG: Language setting (from header) is: en
20121224180135:B772BB40:DBG: Run Query (b6e08b60)
20121224180135:B772BB40:DBG: Free recordset (b6e08b60)
20121224180135:B772BB40:DBG: Run Query (b6e08b60)
20121224180135:B772BB40:DBG: Free recordset (b6e08b60)
20121224180135:B772BB40:DBG: Access 'granted' to user on 192.168.200.170 for request: /dynamic
20121224180135:B772BB40:DBG: Collected post data:
20121224180135:B772BB40:DBG:       action : doScan
20121224180135:B772BB40:DBG:       deviceid : hpaio:/net/Photosmart_2570_series?zc=PhotoSmart
20121224180135:B772BB40:DBG:       format : Grey Scale
20121224180135:B772BB40:DBG:       pages : 1
20121224180135:B772BB40:DBG:       resolution : 300
20121224180135:B772BB40:DBG:       ocr : eng
20121224180135:B772BB40:DBG:       pagelength : 100
20121224180135:B772BB40:INF: Processing request for: doScan
20121224180135:B772BB40:DBG: Entering doScan
20121224180135:B772BB40:DBG: doScan setScanParam completed
20121224180135:B772BB40:DBG: doScan launching doScanningOperation
20121224180135:B772BB40:DBG: Leaving doScan
20121224180135:B772BB40:DBG: Serving the following content: <?xml version='1.0' encoding='utf-8'?>
<Response><DoScan><scanuuid>8dc12899-26a5-44a9-aa1d-43572463492a</scanuuid></DoScan></Response>
20121224180135:B61FFB40:DBG: CLIENT: The command structure has been initalised and wants to send the command of: internalDoScanningOperation:8dc12899-26a5-44a9-aa1d-43572463492a,en.
20121224180135:B772D740:DBG: SERVER: The sane command port has received an incomming connection.
20121224180135:B772BB40:DBG: Language setting (from header) is: en
20121224180135:B772BB40:DBG: Run Query (b6e0c370)
20121224180135:B772BB40:DBG: Free recordset (b6e0c370)
20121224180135:B772BB40:DBG: Run Query (b6e0c370)
20121224180135:B772BB40:DBG: Free recordset (b6e0c370)
20121224180135:B772BB40:DBG: Access 'granted' to user on 192.168.200.170 for request: /dynamic
20121224180135:B772BB40:DBG: Collected post data:
20121224180135:B772BB40:DBG:       action : getScanningProgress
20121224180135:B772BB40:DBG:       scanprogressid : 8dc12899-26a5-44a9-aa1d-43572463492a
20121224180135:B772BB40:INF: Processing request for: getScanning Progress
20121224180135:B772BB40:DBG: Run Query (b6e0c370)
20121224180135:B772BB40:DBG: Free recordset (b6e0c370)
20121224180135:B772BB40:DBG: Serving the following content: <?xml version='1.0' encoding='utf-8'?>
<Response><ScanningProgress><status>0</status><value>0</value></ScanningProgress></Response>
20121224180135:B772D740:INF: SERVER: Sane dispatcher received the command: 'internalDoScanningOperation' with param of '8dc12899-26a5-44a9-aa1d-43572463492a,en'
20121224180135:B772D740:DBG: doScanningOperation: sane initialized uuid(8dc12899-26a5-44a9-aa1d-43572463492a)
20121224180135:B772D740:DBG: sane_open
20121224180135:B772D740:DBG: doScanningOperation: updateScanProgess done
20121224180135:B772D740:DBG: Entering getScanParam
20121224180135:B772D740:DBG: Run Query (8588c50)
20121224180135:B772D740:DBG: Free recordset (8588c50)
20121224180135:B772D740:DBG: Leaving getScanParam
20121224180135:B772D740:DBG: getScanParam ready devName(hpaio:/net/Photosmart_2570_series?zc=PhotoSmart)
20121224180135:B772D740:DBG: Entering getScanParam
20121224180135:B772D740:DBG: Run Query (8588c50)
20121224180135:B772D740:DBG: Free recordset (8588c50)
20121224180135:B772D740:DBG: Leaving getScanParam
20121224180135:B772D740:DBG: Option 2: name='mode' title='Scan mode' type=string size=20 values=["Lineart", "Gray", "Color"] cap=soft-select,soft-detect
20121224180135:B772D740:DBG: sane_control_option (2, SANE_ACTION_SET_VALUE, "Gray") -> (SANE_STATUS_GOOD, "Gray")
20121224180135:B772D740:DBG: Option 3: name='resolution' title='Scan resolution' type=int size=4 unit=dpi values=[75, 100, 150, 200, 300, 600, 1200, 2400] cap=soft-select,soft-detect
20121224180135:B772D740:DBG: Entering getScanParam
20121224180135:B772D740:DBG: Run Query (8588c50)
20121224180135:B772D740:DBG: Free recordset (8588c50)
20121224180135:B772D740:DBG: Leaving getScanParam
20121224180135:B772D740:DBG: sane_control_option (3, SANE_ACTION_SET_VALUE, 300) -> (SANE_STATUS_GOOD, 300)
20121224180135:B772D740:DBG: Option 5: name='contrast' title='Contrast' type=int size=4 min=0, max=100, quant=0 cap=soft-select,soft-detect,inactive,advanced
20121224180135:B772D740:DBG: The option does not need to be set.
20121224180135:B772D740:DBG: Option 6: name='compression' title='Compression' type=string size=20 values=["None", "JPEG"] cap=soft-select,soft-detect,advanced
20121224180135:B772D740:DBG: Could not set authmatically
20121224180135:B772D740:DBG: Option 7: name='jpeg-quality' title='JPEG compression factor' type=int size=4 min=0, max=100, quant=0 cap=soft-select,soft-detect,advanced
20121224180135:B772D740:DBG: Could not set authmatically
20121224180135:B772D740:DBG: Option 8: name='batch-scan' title='Batch scan' type=bool size=4 cap=soft-select,soft-detect,advanced
20121224180135:B772D740:DBG: Could not set authmatically
20121224180135:B772D740:DBG: Option 9: name='source' title='Scan source' type=string size=20 values=["Flatbed"] cap=soft-select,soft-detect,advanced
20121224180135:B772D740:DBG: sane_control_option (9, SANE_ACTION_SET_VALUE, "Flatbed") -> (SANE_STATUS_GOOD, "Flatbed")
20121224180135:B772D740:DBG: Option 12: name='length-measurement' title='Length measurement' type=string size=20 values=["Unknown", "Approximate", "Padded"] cap=soft-select,soft-detect,advanced
20121224180135:B772D740:DBG: Could not set authmatically
20121224180135:B772D740:DBG: Option 13: name='tl-x' title='Top-left x' type=fixed size=4 unit=mm min=0.000000, max=215.899994, quant=0 cap=soft-select,soft-detect
20121224180135:B772D740:DBG: sane_control_option (13, SANE_ACTION_SET_VALUE, 0.000000) -> (SANE_STATUS_GOOD, 0.000000)
20121224180135:B772D740:DBG: Option 14: name='tl-y' title='Top-left y' type=fixed size=4 unit=mm min=0.000000, max=296.925995, quant=0 cap=soft-select,soft-detect
20121224180135:B772D740:DBG: sane_control_option (14, SANE_ACTION_SET_VALUE, 0.000000) -> (SANE_STATUS_GOOD, 0.000000)
20121224180135:B772D740:DBG: Option 15: name='br-x' title='Bottom-right x' type=fixed size=4 unit=mm min=0.000000, max=215.899994, quant=0 cap=soft-select,soft-detect
20121224180135:B772D740:DBG: sane_control_option (15, SANE_ACTION_SET_VALUE, 215.899994) -> (SANE_STATUS_GOOD, 215.899994)
20121224180135:B772D740:DBG: Option 16: name='br-y' title='Bottom-right y' type=fixed size=4 unit=mm min=0.000000, max=296.925995, quant=0 cap=soft-select,soft-detect
20121224180135:B772D740:DBG: Entering getScanParam
20121224180135:B772D740:DBG: Run Query (8588c50)
20121224180135:B772D740:DBG: Free recordset (8588c50)
20121224180135:B772D740:DBG: Leaving getScanParam
20121224180135:B772D740:DBG: sane_control_option (16, SANE_ACTION_SET_VALUE, 296.925995) -> (SANE_STATUS_GOOD, 296.925995)
20121224180135:B772D740:DBG: sane_start: setOptions returned request_resolution 300

20121224180135:B772D740:ERR: Cannot start scanning: sane error = 3 (Device busy), return code = 0
20121224180135:B772D740:DBG: SERVER: Going to send the response of:
20121224180135:B61FFB40:DBG: CLIENT: has closed its socket.
20121224180135:B61FFB40:DBG: RESPONSE WAS:
20121224180135:B772D740:DBG: SERVER: Server has closed it's socket.
20121224180136:B772BB40:DBG: Language setting (from header) is: en
20121224180136:B772BB40:DBG: Run Query (b6e088e0)
20121224180136:B772BB40:DBG: Free recordset (b6e088e0)
20121224180136:B772BB40:DBG: Run Query (b6e088e0)
20121224180136:B772BB40:DBG: Free recordset (b6e088e0)
20121224180136:B772BB40:DBG: Access 'granted' to user on 192.168.200.170 for request: /dynamic
20121224180136:B772BB40:DBG: Collected post data:
20121224180136:B772BB40:DBG:       action : getScanningProgress
20121224180136:B772BB40:DBG:       scanprogressid : 8dc12899-26a5-44a9-aa1d-43572463492a
20121224180136:B772BB40:INF: Processing request for: getScanning Progress
20121224180136:B772BB40:DBG: Run Query (b6e088e0)
20121224180136:B772BB40:DBG: Free recordset (b6e088e0)
20121224180136:B772BB40:DBG: Serving the following content: <?xml version='1.0' encoding='utf-8'?>
<Response><ScanningProgress><status>5</status><value>3</value></ScanningProgress></Response>
20121224180157:B772D740:INF: Received SIGUSR1 signal.
20121224180157:B772D740:INF: openDias service is shutting down....
20121224180157:B772D740:DBG: ... httpd service [done]
20121224180157:B772D740:DBG: ... sane command socket [done]
20121224180157:B772D740:DBG: ... sane backend [done]
20121224180157:B772D740:DBG: ... locale [done]
20121224180157:B772D740:DBG: ... database [done]
20121224180157:B772D740:DBG: Closing database
20121224180157:B772D740:INF: openDias service has shutdown.

I hope you can solve the problem.

Kind regards,

Piet

[Wayne Booth]

Hi Piet,

Thanks for the post of your log.

Unfortunately it has not revealed anything that would explain the problems you have been having.

Therefore can I call on you further, to post some SANE debug logs?

Set SANE debugging using the following:

   export SANE_DEBUG_DLL=255

   export SANE_DEBUG_HPAIO=255

Then, start openDIAS using a non daemon mode:

   /usr/local/bin/opendias -d

(CTRL-C will close the program.) The SANE logs will be dumped to the console. 

Attempt a scan process, and post the dumped log.

Thanks.

Wayne

20121224180157:B772D740:...
Show original

[Piet de Vries]

Hi Wayne,

I did as you wrote and increased the debug-levels and ran openDIAS in non-deamon mode.

In the attachment you find the dump of the screenoutput. I also made a dump of the "scanimage -L" command in debug-mode, maybe it helps. The dump of a "scanimage > test.txt" results in a very large dump which I cannot save.

Hope to hear from you soon. I try to mail you the attachments through gmail because here the attachments cause error 340.

Kind regards,

Piet

[Wayne Booth]

Hi Piet,

Thanks for the logs. A lot of interesting stuff there, but nothing that points to any failure - except the "failed to open scan channel" - not much help.

I've done some searching on that response, and it sounds like a common message.

Most of peoples problems seam to resolved by either:

Configuring printer queues using 

su -c "hp-setup"

eg: https://answers.launchpad.net/hplip/+question/59235

or,

restarting avahi

eg: http://askubuntu.com/questions/153746/xsane-failed-to-open-device-hpaio-net-photosmart-c5100-serieszc-hp5180-err

If either of these does not work, can you post the output of "hp-check -rt"

Also, you say you can scan using the command line. Was that using the hp uti8lity? or using the sane backend (eg from xsane or xscanimage). If it was via the hp utility, can you ensure things are setup correctly with sane and attempt a scan using xscanimage?

Hopefully, we can get to the bottom of your problems soon.

Regards

Wayne

[Piet de Vries]

Hi Wayne,

For the last few hours I have been fiddling with openDIAS but so far openDAIS has won, it is quite persistent in it's error 3.

First I made a scan form the commandline using the command 'scanimage --format tiif >> test.tiff', this works so the scanner is recognized and functional. I ran this command as root because openDIAS also runs ar root. BTW I did indeed use the HP-SETUP utility to install the printer/scanner.

After that is tried restarting AVAHI which seemed like al logt shot to me but stranger things have happened. Restarting AVAHI had no result.

I started running the hp-chek utility and that utility gave errors and warnings, I solved all errors en did noth bother about the remaining warnings. After solving the errors openDIAS kept giving error 3. Now quite desperate I decided to purge the whole HPLIP-package. After a reboot I reinstalled HPLIP and again ran openDIAS. Error 3 on scanning.

To make sure everything installed en worked nicely after the re-installation of HPLIP I ran the ' scanimgae --format tif > test.tiff' command again and again a nice result.

During this testing I developed the idea that openDIAS might issue a scancommand that is not compatible with my scanner and therefore cause an error. Could you mail me the command that openDIAS would issue tot the scanner so I might try that command from the commandline?

Enclosed you find a dump of the HP-CHECK command, a logfile from openDIAS and a transscription of the actions I took today. Again 340 errors on the attachments, I will mail them through GMAIL.

Kind regards,

Piet

[Piet de Vries]

Hi Wayne,

Enclosed the logfiles I made from the suggestions you made earlier.

Kind regards,

Piet

[Wayne Booth]

Hi,

Thanks for the details provided. I understand this is frustrating for you, but please know that I'll continue to support you until we get things working for you. Please bare with us.

That said, and based on the details you've provided, I'm not convinced this is an openDIAS problem.

let me explain: openDIAS uses the SANE libraries to interface with attached scanners. Some command line tools such as the hplip config command and scanimage do not use the same code pathways as a apps using the sane-api to control devices.

An app that I've found to be a good litmus test for openDIAS is "simple-scan" (which uses the sane-api as openDIAS does). So, if you can get a good image scanned via "simple-scan" then the problem is with openDIAS. Otherwise it points to a problem with the local config/device.

Therefore, can you attempt a scan using "simple-scan", if it works then can you include the SANE debug information of that run (as described above "export SANE_DEBUG_DLL=255; export SANE_DEBUG_HPAIO=255"), and there is no point doing the below.

However, if "simple-scan" does not work (you get the same problem - it could be reported differently), it would give weight towards my theory that there is some problem with 'sane taking to the device over the network'. (btw: have you tried this device by direct USB connection?). There are lots of reports of similar problems (device busy on net connected hplip devices) on the web. The following seems to match your symptoms closely (although it's on an older Ubuntu) https://answers.launchpad.net/hplip/+question/28585 It suggests enabling snmp public read/write. A stab in the dark, but worth a try (fyi I have no ideas how to configure snmp).

Thanks for sticking with it, while we get your problems sorted out. Hopefully we're narrowing down all the potentials and a resolution will present itself soon.

Regards.

Wayne.

[Piet de Vries]

Hi Wayne,

The moment of frustration was just temporary and it the best moment to quit testing....

Today I continued testing based on you reply. What I did was the following;

1. on my VM I installed simple-scan with a whole bunch of dependencies
2. after that I used TASKSEL to install the KDE-environmet
3. after a reboot I performed a scan with simple-scan which resulted in a nice scan
4. now I tried to perform a scan through openDIAS, which failed in error : 3
5. now I tried to perform a scan through openDIAS form a local web-browser, the previous attempt was from a remote web-browser, and this one also failed in error : 3
6. on a different VM with Kubuntu 12.10 I tried to install openDIAS which failed because of dependencies
7. after solving most of the dependencies openDIAS still would not install and this is because openDIAS expects the packages libmicrohttpd5 and libleptonica which have been upgraded to libmicrohttpd10 and liblep3, bit off-topic but anyway.
8. went back to my first VM and increased the log-levels
   
9. performed a scan with simple-scan, success
   
10. performed a scan with openDIAS in non-deamon-mode, error : 3

Enclosed you find the 2 logs, one from simple-scan and the other from openDIAS. The logfiles go to your GMAIL directly, there seems to be a problem in sending attachments I constantly get error 340 An error has occurred while communicating to the server (Er is een fout opgetreden (nr. 340) bij het communiceren met de server.)

I hope these logs help to identify the problem I'am facing. In the meantime I want to show my appreciation to you by translating openDIAS to the Dutch language. In /usr/local/share I find the web-pages both in English and German but I ques these are the end-result of a process using a language file. Can you mail me a language-file so I can start translating?

Hope to hear from you soon and have a nice start of the new year!

Kind regards,

Piet

[Piet de Vries]

Hi Wayne,

Enclosed you find the logs form simple-scan and openDIAS.

Kind regards,

Piet

[Wayne Booth]

Hi Piet,

Thanks for the information and continued testing.

Based on your feedback, I've made some changes to openDIAS.

A new .deb file with this updates is enclosed.

Can you try this version and let me know if it helps.

Regards

Wayne.

[Piet de Vries]

Hi Wayne,

I did some testing with the new .deb but first I prurged the older version of openDIAS.

The new versions still gives error : 3, so i increased the debuglevel of both openDIAS and sane and tried to scan again. I will mail you the logs from both openDIAS and sane throuhg gmail

Simple-scan still works so no new log was made.

Kind regards,

Piet

[Wayne Booth]

Hi,

Sorry to here that.

I've prepared a new version for you.

Can you give this a try. No need for logs if this does not work (we're kinda into trial-and-error)

Cheers

Wayne

[Piet de Vries]

Hi Wayne,

Earlier this morning I prepared a fresh VM for trial and error. I'am sorry to say that openDIAS came up with error : 3. To rule things out I also installed the latest test-version on my older VM, after first purging the installed openDIAS-version. On the older VM also error : 3.

I wait for a new try.

Kind regards,

Piet


  

[Wayne Booth]

Hi Piet,

The only different in terms of the command each application sends to the sane backend is, openDIAS requests "Grey" and simplescan is asking for a "Colour" image.

I have created a version of openDIAS that requests a colour image and enclosed it here. Can you give this a try. 

On success or failure, can you also try a simplescan in "Grey" (by setting it to "Text"), just to see what happens.

Cheers.

Wayne

[Piet de Vries]

Hi Wayne,

On the VM withe the graphical environment instaaled I tried to make a grayscale /text-scan and this went OK. The scan was acquired pretty fast and looked perfect. After that I purged the previous version of openDIAS and after that I installed the version you prepared earlier today.Trying a scan from openDIAS resulted in Error: 3, the same error as earlier.

I also tried the newer version on my other, much cleaner VM, and on that machine I also got Error : 3. So no luck so far.

Kind regards,

Piet

[Wayne Booth]

Hi Piet,

OK.

I've taken some drastic action now and recoded the scanner setup routines.

We're now setting each config parameter in a different order (other than was returned y the scanner).

Hopefully this will made some difference for you.

Please could you try the enclosed package.

Cheers

Wayne

[Piet de Vries]

Hi Wayne,

By now I can re-install openDIAS blindly.

On my clean VM I purged the previous version of openDIAS and installed the latest version. After hitting the scan button I still get Error : 3. If I try to scan again, in the same session, i get error a008, Error while talking to the server. This happend during the proces of searching for scanners. OpenDIAS seems to have crashed and restarting the service is the only solution. After Error : 3 openDIAS does not crash instantly, I can go back to Home and Document List without any problem, reloading these pages doesn't give any problem. It crashes at the moment I goto the Acquire New screen, during the Scacnning For Devices phase. I did some other experimenting and openDIAS came with error : 4 when I pulled back the resolution  to 50dpi. Pulling the resolution to 2400dpi resulted in error : 3, and some other resolutions also resulted in error : 3. Only at 50dpi I get error : 4, 100dpi gives error : 3.

On the other VM i get the same results. Simple Scan still works perfect in both Colour- and Text-mode.

My VM's are ready for a new round of testing.

Kind regards,

Piet

[Wayne Booth]

Hi,

Believe it or not, I think your last comments are encouraging :)

I think we're getting somewhere.

I've therefore fixed the things that are causing the crashes (what I think is causing them). Hopefully this will be our last test version.

Can you install the enclosed version and let me know the outcome. If this does not work,please can you include then openDIAS log and  sane log as previously described.

Many thanks for your continued testing on this issue.

Regards

Wayne

[Piet de Vries]

Hi Wayne,

Still no luck....

I ran your latest version and the tried things like I did yesterday. Scanning still results in error : 3. During a first retry openDIAS does not always crash instantly, but sometimes it does after the second try. The crash now also happend when I pushed the scan-button but not on the first scan attempt. openDIAS still also crashes during the search for a scanner. On the console ther was a nice core dump. openDIAS did give an error : 4 on scanning on 50dpi.

Enclosed you find the logfiles I generated today. The logfiles go to your Gmail since I got error 340 while posting this message with the attachments.

I keep hanging on and look forward to a new try.

Kind regards,

Piet

[Wayne Booth]

Hi Piet,

That's not good news.

Although I think it does lay to rest the assumption that there is something wrong with the order of parameters being set.

I've done some more reading around on the subject of BUSY signal from HP devices. A lot of people are getting them. One did trigger my interest, that he sometimes didn't get the error. Therefore I've changed tack on this bug. Maybe the scanner reports BUSY, because it's not ready to start scanning yet! Thinking about it, this makes more and more sense. openDIAS almost instantly starts scanning after setting it's last device parameter. However, other application (simple-scan for instance), has a natural pause before starting the scanning attempt.

So, I've created a new version that waits for a while if a BUSY signal has been triggered, then tried again. Hopefully this will get things moving???? (please!!!)

BTW, the error 4 you are seeing is related to the fact your scanner cannot set a resolution of 50. For now, just don't do that, and I'll fix that up in a separate bug fix.

Have a try and do let me know,

Cheers.

Wayne

[Piet de Vries]

Hi Wayne,

Things got worse

I installed the latest version, after purging the previous version, and that went OK. Trying to start the service give an error: Starting opendias: Cannot open log file /tmp/opendias_tmp/var/log/opendias/opendias.log.

I made the requested directory by hand and on starting openDIAS crashes instantly. The logfile says: Could not open PID lock file. Exiting.

So far for this short testrun.

Looking forward to a newer and better release.

Kind regards,

Piet

[Wayne Booth]

Hi Piet, 

Arggg, I've packaged a test binary in your deb.

Please see a revised package with a real production binary.

Hopefully this will help.

Regards

Wayne

[Piet de Vries]

Hi Wayne,

I tried the correct version and have some good news. The Error : 3 is gone but openDIAS hangs after pushing the Scan-button. The message "Setting up the scanner" does not go away. The webinterface is still reacting and I can go to the other options. When I go back to the Aquire New screen ther is a messag that the "Details are nor current" because the sane-subsystem is busy.

I prepared logfiles and they are in your GMail-box. I had trouble ending openDIAS using CTRL-C so I did an ACPI-shutdown of the machine. Rather brute but by than openDIAS had spend almost 5 minutes on seemingly doing nothing.

When I start openDIAS after the reboot there is a new document-record in the Document List. The record is empy, no picture no extracted text onlu the scandate and the default document tite and default document date are filled.

Kind regards,

Piet

[Wayne Booth]

Hi,

This was not good news. It turns out that I've sent another foo-bar version.

When a busy signal has been found, I wanted things to wait for half a second before trying again. Unfortunately, I've set it to wait for 500 seconds (in error).

I've enclosed a new version that will wait for a better length of time. Can you give this a try?

If this version does not work, I'm going to pick up a Photosmart 2570 (I've seen a few on ebay for a reasonable price), so I can get these problems nailed.

Regards

Wayne

[Piet de Vries]

Hi Wayne,

I tried your latest release and things seem to go better, at least the interface showed me a screen I had never seen before. After hitting the Scan-button a quick message appears about creating a record and setting u the scanner. After that I get a progress bar with the message "Scanning in progress" and this message stays on the screen while the scanner is doing nothing.

I will mail you the new logfiles to your GMail-account later this evening.

In your reaction you wrote you're going to buy a 2570 printer/scanner to solve the problem which is great. In the meantime I can start translating, so please mail me the language-file or explain to me how I can supply you with the Dutch translations.

Kind regards,

Piet

[Wayne Booth]

Hi Piet,

Just a quick note to let you know that I've not forgotten about you. Finding it a bit more difficult sourcing a scanner that same as yours. I'm still following up on leads though, so will get back to you shortly.

Cheers

Wayne.

[Piet de Vries]

Hi Wayne,

No problem, there is no hurry. Have you thought about my offer to start working on the Dutch translations of openDIAS? While you search for a 2570 scanner I can start translating. I'am quite convinced that you can solve the problems with my scanner easily because sane can already use it.

Kind regards,

Piet

[Wayne Booth]

Hi Piet,

Good news, I have located a scanner and it's on it's way to me now. I should be able to get working on a resolution for you - shortly!

As requested, I have generated a language pack for 'Dutch' (I've added it to the language dropdown selector as 'Nederlands' - I hope that is correct).

This is enclosed. 

Simply, it should be a case of updating the key/value pairs to the correct local phrase.

Many thanks for your efforts and good luck with the task.

I'll chat soon.

Wayne

[Piet de Vries]

Hi Wayne,

OK, good news. I'am curios about the reason why my photosmart will not scan from openDIAS and, of course, I'am curious about your solution.

The language selection ' Nederlands'  is correct. Next week I start translating and as soon as I think I'am finished I will mail you the result.

We keep in touch

Kind regards

Piet

[Wayne Booth]

Hi Piet,

I have received my testing printer/scanner, and had a chance to do some experiments.

It looks like it's a bug with the HPAIO backend for SANE, whereby it will not allow re-opening of a device.

I've therefore opened an upstream bug:

https://bugs.launchpad.net/hplip/+bug/1113872

Feel free to subscribe to that bug report (so you can see progress).

As you can see the bug can be prompted to surface even using other applications (see bug report for details). We'll see what HPLIP say.

Regards

Wayne

[Wayne Booth]

Hi Piet,

I've created a version of openDIAS that works around the HPLIP bug I found at the weekend.

Basically, we're re-initialising the SANE subsystem each time we use it. Highly inefficient, but it gets things moving.

Please can you try the enclosed version out and see if it works for you (works for me with my new 2570).

Cheers.

Wayne

[Piet de Vries]

Hi Wayne,

Today I tried the newly prepared version of openDIAS and scanning now works! GREAT! Maybe a highly inefficient solution but for now i's very effective. This working version makes translating also easier because I can see where the different texts are used and in what context. I already made quite some progress in translating openDIAS, most texts have been translated and I only have to do a check and translate the ' story' on the home-page.

The last version of openDIAS does not work perfect because the OCR-results doesn't get stored in the database. When I perform a scan openDIAS tells me that it is performing OCR, and the logfile shows quite a good OCR (loglevel increased to 4) but still nothing in the database. Right after the OCR-text in the logfile it says;
DBG: scanprogressid: long number
INF: Processing request for: Get ScanningProgress
ERR: cannot find the result - returning the key instead

Another, minor, thing is that in the document list the columns Type and Date get mingled.

Thanks so far and you hear from me soon.

Piet