/usr/lib/cups/backend/http failed - how can I fix?

[Lloyd R. Prentice]

Hi,

Printing failed when I inadvertently upgraded my Debian Sarge system to Etch. I reinstalled CUPS, added a printer through localhost:631/admin, and tried a test print. Result: /usr/lib/cups/backend/http failed.

I've searched the web for references to this problem; found a few, but I can't see how they relate to my problem. One site suggested that */backend/http and */backend/ipp should have more generous privileges. I  tried their suggestion of opening up privileges, but problem persisted.

Beyond the above I haven't been able to find documentation of */backend/http, its function, clues as to why it should fail, or what to check out when it fails.

More background below.

Many thanks for your help,

Lloyd R. Prentice


Network:

- My HP Photosmart P1100 printer is served via USB from an Infrant ReadyNAS 600 NV+ network attached storage device.

- On the same local network is Cube, the Debian system noted above, and WinSys, a Windows XP system. All are served by DHCP.

-- I can ping nas from Cube

-- I can't ping WinSys from Cube, but not sure that's relevant to current problem.

Printer Configuration:

-- I configured printer device as Internet Printing Protocol (http); device uri as http://nas/631/ipp/

cupsd.conf

-- partial listing -- not sure it's correct;

# Only listen for connections from the local machine.
Listen localhost:631
Listen /var/run/cups/cups.sock

# Show shared printers on the local network.
Browsing On
BrowseProtocols CUPS
BrowseOrder allow,deny
BrowseAddress @LOCAL
BrowseAllow @LOCAL

# Default authentication type, when authentication is required...
DefaultAuthType Basic

# Restrict access to the server...
<Location />
  Order allow,deny
  Allow from @LOCAL
</Location>

Clues:

-- I can print a NotePad file from WinSys