/usr/lib/cups/backend/socket failed

Ray Stacey ray.stacey at cgi.com
Fri Sep 23 14:48:03 PDT 2011


Thanks, I applied the patch and my issue went away.

> This might be the SNMP supply level bug (STR #3875) that was fixed in CUPS 1.4.8.
>
> On Sep 22, 2011, at 7:13 AM, Ray Stacey wrote:
>
> >> Ray Stacey wrote:
> >>
> >>> I have a printer set up in production and yesterday it stopped working and
> >>> can't be resumed, error message is /usr/lib/cups/backend/socket failed.
> >>> I've tried deleting the printer and adding it back to no avail. I have the
> >>> same printer defined on another server, with the same version of CUPS and
> >>> it is working fine. Here is a snippet from the log:
> >>>
> >>>
> >>> D [22/Sep/2011:07:58:13 +0500] PID 12129 (/usr/lib/cups/filter/pstops) did
> >>> not catch or ignore signal 13. E [22/Sep/2011:07:58:13 +0500] PID 12130
> >>> (/usr/lib/cups/backend/socket) crashed on signal 8! D
> >>> [22/Sep/2011:07:58:13 +0500] PID 12128 (/usr/lib/cups/filter/texttops) did
> >>> not catch or ignore signal 13. I [22/Sep/2011:07:58:13 +0500] [Job 1629]
> >>> Backend returned status -8 (crashed) D [22/Sep/2011:07:58:13 +0500]
> >>> Discarding unused job-state-changed event... I [22/Sep/2011:07:58:13
> >>> +0500] [Job 1629] Printer stopped due to backend errors; please consult
> >>> the error_log file for details.
> >>
> >> Well, on most systems holds:
> >> signal 13	SIGPIPE
> >> signal 8	FPE
> >>
> >> where SIGPIPE means a process writes to a pipe but there is no one on the
> >> other end to read from this pipe, and FPE is a floating point exception.
> >>
> >> Without knowing anything about your configuration and system and hardware, I
> >> suspect you might have run into trouble with your floating point processor
> >> (I cannot imagine a condition the socket backend might run into something
> >> like exponent overflow or divide by zero or other plausible floating point
> >> error conditions).
> >>
> >> Helge
> >>
> >
> > We're running Solaris 10 x86, CUPS 1.4.7. All the other printers are fine, just this one stopped working. How can I debug this situation?
> > _______________________________________________
> > cups mailing list
> > cups at easysw.com
> > http://lists.easysw.com/mailman/listinfo/cups
>
> __________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>





More information about the cups mailing list