network communication failure

Asked by justwantin

First off, I am using slack-13 and HPLIP-3.9.4b and, yes,understand you do not test on Slackware. I can troubleshoot and test but I don't know what so perhaps you can still help.

I have a headless nfsfileserver/printserver and have configured an hp930c and psc2355 via ssh using hp-setup -i then hp-makeuri. The printers are recognised on the client by applications and I can print to them from gui applications as well as using the cli command lp-cups. However I can not access the scanner (psc2355) which I have previously been been able to up until recently by configuring sane on client and server and using hpoj.

The scanner is working. I can scan using the command scanimage cli on the server as the same user as on the client. Scanimage -L finds nothing on the client.

When I run hp-check on the server there are no errors reported just ttwo Reportlab errors. When I run it on a client I have this:

# warning: Reportlab not installed. Fax coverpages disabled.
# warning: Please install version 2.0+ of Reportlab for coverpage support.
# error: Unable to communicate with device (code=12): hp:/usb/PSC_2350_series?serial=MY493C10JCKJ
# error: Device not found
# error: Unable to communicate with device (code=12): hp:/usb/DeskJet_930C?serial=HU14C1N017JJ
# error: Device not found

At one time and one time only this morning I was able to have both printers available on this client with hp-toolbox and changed settings from Letter to A4 on both before loosing communication again.

I can live without using hp-toolbox but I would like to have scanning on this client and I believe this communication problem is behind my inability to scan

I have checked ports and they are listed in /etc/services, there is no firewall used on either machine, snmp is running on both machines, permissions are correct, and unless there has been a change sane is configured correctly for both client and server.

Could you please note any other possible causes of this problem for me to follow up on?

TIA

Question information

Language:
English Edit question
Status:
Answered
For:
HPLIP Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Aaron Albright (albrigha-deactivatedaccount) said :
#1

Run:

groups

and post the output.

Also run:

su -c "tail -f /var/log/syslog"

try and scan and post the output in the syslog.

Thanks!

Aaron

Revision history for this message
justwantin (frmrick) said :
#2

Thanks for coming back on this. Here's the output of groups on my server a.k.a box, and this workstation.

rick@box:~$ groups
users lp audio video cdrom plugdev power scanner saned
rick@rick:~$ groups
users lp audio video cdrom plugdev power scanner vboxusers

I know have scanning. I decided to be quick and dirty by editing MODE from 660 to 666 which has me able to scan from client but the groups were as you see them before I changed the udev rule.

I still cannot check the status of these printers. right now I can right click the hplip icon in my panel and see that both printers have been id'd and that there are "no events" reported.but if I open up the device manager the printers now have error symbols alongside and the device manager give me the failed comms 5012 message. I once briefly had comms with both printers long enough to change paper settings from Letter to A-4 but then lost it before I could even figure out why I was able to get through

I have been able to print all along, I can scan now and I can always log into cups on the server to do printer settings but it would be nice to know why I can't "communicate" with hplip. If you have any suggestions of what to look at I'll have a squizz.

Revision history for this message
Aaron Albright (albrigha-deactivatedaccount) said :
#3

Are there any errors in the syslog?

Try running hp-info -i -g and posting that output.

Thanks!

Aaron

Revision history for this message
justwantin (frmrick) said :
#4

Here's syslog before and after changing MODE to 666 on the client. I had done that already on the server and then had scanning.

(before)
Sep 30 04:07:55 rick python: io/hpmud/musb.c 1104: unable to open hp:/usb/PSC_2350_series?serial=MY493C10JCKJ
Sep 30 04:07:55 rick python: hp-info[3649]: error: Unable to communicate with device (code=12): hp:/usb/PSC_2350_series?serial=MY493C10JCKJ
Sep 30 04:07:55 rick python: hp-info[3649]: error: Error opening device (Device not found).
(after)
Sep 30 04:23:17 rick python: io/hpmud/musb.c 1104: unable to open hp:/usb/PSC_2350_series?serial=MY493C10JCKJ
Sep 30 04:23:17 rick python: hp-info[3758]: error: Unable to communicate with device (code=12): hp:/usb/PSC_2350_series?serial=MY493C10JCKJ
Sep 30 04:23:17 rick python: hp-info[3758]: error: Error opening device (Device not found).

This is syslog after opening the hp device manager

Sep 30 04:26:11 rick python: hp-toolbox[3765]: warning: Reportlab not installed. Fax coverpages disabled.
Sep 30 04:26:11 rick python: hp-toolbox[3765]: warning: Please install version 2.0+ of Reportlab for coverpage support.
Sep 30 04:26:12 rick python: io/hpmud/musb.c 1104: unable to open hp:/usb/PSC_2350_series?serial=MY493C10JCKJ
Sep 30 04:26:12 rick python: hp-systray(hpdio)[3605]: error: Unable to communicate with device (code=12): hp:/usb/PSC_2350_series?serial=MY493C10JCKJ
Sep 30 04:26:12 rick python: hp-systray(hpdio)[3605]: error: Device not found
Sep 30 04:26:12 rick python: io/hpmud/musb.c 1104: unable to open hp:/usb/DeskJet_930C?serial=HU14C1N017JJ
Sep 30 04:26:12 rick python: hp-systray(hpdio)[3605]: error: Unable to communicate with device (code=12): hp:/usb/DeskJet_930C?serial=HU14C1N017JJ
Sep 30 04:26:12 rick python: hp-systray(hpdio)[3605]: error: Device not found

I ran hp-info on both server and client, I'll give the output server first and then client. Sorry there's no option for code or quotes on the list so it'll look the same as everything else :^( I'm oonly posting the sections with the errors

(server)
Enter number 0...1 for device (q=quit) ?0
hp-info[3445]: debug: Device URI: hp:/usb/PSC_2350_series?serial=MY493C10JCKJ
hp-info[3445]: debug: Printer: None
error: Unable to connect to dbus session bus.
hp-info[3445]: debug: URI: backend=hp, is_hp=True, bus=usb, model=PSC_2350_series, serial=MY493C10JCKJ, dev=, host=, port=1
hp-info[3445]: debug: Model/UI model: PSC_2350_series/HP PSC 2350 Series

(client)
Enter number 0...1 for device (q=quit, <enter>=default: 0*) ?0
hp-info[3758]: debug: Device URI: hp:/usb/PSC_2350_series?serial=MY493C10JCKJ
hp-info[3758]: debug: Printer: None
hp-info[3758]: debug: Connecting to com.hplip.StatusService (try #1)...
hp-info[3758]: debug: URI: backend=hp, is_hp=True, bus=usb, model=PSC_2350_series, serial=MY493C10JCKJ, dev=, host=, port=1
hp-info[3758]: debug: Model/UI model: PSC_2350_series/HP PSC 2350 Series

hp:/usb/PSC_2350_series?serial=MY493C10JCKJ

hp-info[3758]: debug: Opening device: hp:/usb/PSC_2350_series?serial=MY493C10JCKJ (not for printing)
hp-info[3758]: debug: I/O mode=6
hp-info[3758]: debug: Sending event 5012 to hpssd...
error: Unable to communicate with device (code=12): hp:/usb/PSC_2350_series?serial=MY493C10JCKJ
hp-info[3758]: debug: Exception: 2 (Device not found)
error: Error opening device (Device not found).

I'm quessing it's to do with dbus (obviously)

"error: Unable to connect to dbus session bus. "

Any suggestions on what to look at next?

Revision history for this message
Aaron Albright (albrigha-deactivatedaccount) said :
#5

Run:

lsusb

and

/usr/share/cups/backend/hp

and post the outputs.

Aaron

Revision history for this message
justwantin (frmrick) said :
#6

lsusb shows printers but there is no /usr/share/cups/backend/hp. Is this something that should install there when installing hplip or does it belong to cups?

root@box:/home/rick# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 03f0:1204 Hewlett-Packard DeskJet 930c
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 03f0:4911 Hewlett-Packard PSC 2350
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@box:/home/rick# /usr/share/cups/backend/hp
bash: /usr/share/cups/backend/hp: No such file or directory
root@box:/home/rick# ls /usr/share/cups
banners calibrate.ppm charmaps charsets data drv fonts model profiles templates

Revision history for this message
Launchpad Janitor (janitor) said :
#7

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
justwantin (frmrick) said :
#8

I could not run /usr/share/cups/backend/hp. This executable was not installed in that path. What package does it belong to?

Revision history for this message
Naga Samrat Chowdary, Narla (samrat-hplip) said :
#9

Please uninstall currenly installed HPLIP-3.9.4b and if any HPLIP package from package manager too.

Please download the latest HPLIP 3.9.8 from "http://hplipopensource.com/hplip-web/gethplip.html"
Please configure with
for 32 bit machine "./configure --prefix=/usr"
for 64 bit machine "./configure --prefix=/usr --libdir=/usr/lib64"
then execute "make" and "make install"

Please post the "hp-check -t" if the same problem persists.

Thank you for supporting HPLIP,
Naga Samrat.

Revision history for this message
justwantin (frmrick) said :
#10

Thank you Naga, I thought this was going to wxpire again. I will have a go first chance I have. I'm quite busy ATM and while I'd like to see HPLIP working correctly on my network I can print as is for now without it.

Revision history for this message
Naga Samrat Chowdary, Narla (samrat-hplip) said :
#11

Can you please try the same with HPLIP 3.9.10 and confirm it.
Please remove if any hplip default package coming under package manager and if any previously you installed.

please remove if any previously installed printer queues and add the printer using "hp-setup".
Please post the "hp-check -t" if the problem persists.

Thank you for supporting HPLIP,
Naga Samrat.

Can you help with this problem?

Provide an answer of your own, or ask justwantin for more information if necessary.

To post a message you must log in.