/usr/lib/cups/backend/socket failed

[DanMc]

After playing with the script for an hour, I realized it was just my typo. 
beh:/  not  beh://

"DanMc" <cupsadmin at elgin.edu> wrote in message 
news:29094-cups.general at news.easysw.com...
> I'm having the same problem on 1.1.23  If a printers is offline (powered 
> off, out of paper) cups eventually stops the queue because of the non-zero 
> error message from the backend.
>
> I searched around in the group archives, and found this has been the case 
> for a long time, and there's a nice fellow who wrote a perl script backend 
> wrapper.
>
> http://www.linux-foundation.org/en/OpenPrinting/Database/BackendErrorHandler
>
> I just dropped this in as:
>
> /usr/lib/cups/backend-available/beh
> chmod 755
> Made a symlink in: /usr/lib/cups/backend/beh
>
> Just now edited one of my device URIs to call 
> beh://1/0/120/http://room42lj4000.corp.com:631/ipp/port1
>
> The web page describes it all.  I'm testing it now, but looks like an 
> exact match to the problem.  It's not working just yet.  I'm getting an 
> errorcode 9 from the script.  This isn't a code that's defined in the 
> script, so it's probably a perl error.  I'll post an update when I figure 
> that out.
>
> E [10/Apr/2007:16:54:27 -0500] PID 7369 (/usr/lib/cups/backend/beh) 
> stopped with status 9!
>
> It's running this, which seems to be an incorrect parameter...
> /usr/bin/perl /usr/lib/cups/backend/beh 82141 root Test Page 1 
> job-uuid=urn:uuid:184340f9-11af-3356-4df6-d151c1512531
>
> -DanMc
>
> "Leon Stringer" <leon.stringer at ntlworld.com> wrote in message 
> news:29088-cups.general at news.easysw.com...
>>> >I upgraded from CUPS 1.1.19 to 1.2.10 last week. Since then I've been 
>>> >called to non-printing printers and found that the status in the CUPS 
>>> >web interface is "stopped" with the message:
>>> >
>>> >   /usr/lib/cups/backend/socket failed
>>> >
>>> Have you checked permissions on all cups directories? That was the
>>> problem I had when I was getting that error.
>>>
>>
>> Thanks for your reply. The permissions look right. And I'd expect a 
>> permissions issue to be consistent rather than intermittent?
>>
>> # ls -l /usr/lib/cups
>> total 28
>> drwxr-xr-x    2 root     root         4096 Mar 31 16:16 backend
>> drwxr-xr-x    2 root     root         4096 Mar 31 16:16 cgi-bin
>> drwxr-xr-x    2 root     root         4096 Mar 31 16:16 daemon
>> drwxr-xr-x    2 root     root         4096 Mar 31 16:12 driver
>> drwxr-xr-x    2 root     root         4096 Mar 31 16:16 filter
>> drwxr-xr-x    2 root     root         4096 Mar 31 16:16 monitor
>> drwxr-xr-x    2 root     root         4096 Mar 31 16:16 notifier
>>
>
>