Re: [gentoo-user] Re: CUPS -- fails better!

[Nick Rout]

On Tue, 31 Jan 2006 00:36:04 +0100
Harm Geerts wrote:

> On Monday 30 January 2006 23:00, maxim wexler wrote:
> > I [30/Jan/2006:14:52:31 -0700] Started backend
> > /usr/lib/cups/backend/parallel (PID 5870) for job 23.
> > E [30/Jan/2006:14:52:31 -0700] PID 5869 stopped with
> > status 3!
> > I [30/Jan/2006:14:52:31 -0700] Hint: Try setting the
> > LogLevel to "debug" to find out more.
> >
> > ditto, nothing prints
> >
> > Oh, and changing debug level in cupsd.conf doesn't
> > have any effect. I saved the file; do I have to logout
> > and in again?
> You'll need to restart cups after changing the config.
> e.g.: /etc/init.d/cups restart
>
> with loglevel set to debug cups will print more information on each step it
> takes. But with the current error you can already make an educated guess.
> /usr/lib/cups/backend/parallel dies with errorcode 3, so this is where you've
> got to start looking. I wouldn't be suprised if it's a permission problem
> like Mick says.

No look closer, that is NOT what it says!!

It says "PID 5869 stopped with status 3!"  PID 5869 is foomatic-rip (see two lines above, not quoted above, but in maxim's message)

"Started filter /usr/lib/cups/filter/foomatic-rip (PID 5869) for job
23."

parallel is the next PID 5870

google found a few references to foomatic-rip status 3. 

But anyway rasing the debug level may pinpoint it better. I have often
found problems with versions of ghostscript when you get ripping
problems with cups, but that may be a red herring :-)




>
> You could try running /usr/lib/cups/backend/parallel from a console to see
> what happens (as the same user as cups is running under!)
> --
> gentoo-user@g.o mailing list

-- 
Nick Rout <nick@×××××××.nz>

-- 
gentoo-user@g.o mailing list