Mailinglist Archive: opensuse (4634 mails)

< Previous Next >
Re: [opensuse] Lost printing
  • From: Johannes Meixner <jsmeix@xxxxxxx>
  • Date: Wed, 20 Dec 2006 13:19:54 +0100 (CET)
  • Message-id: <Pine.LNX.4.64.0612201244060.14668@xxxxxxxxxxxxxx>

Hello,

On Dec 19 22:22 Rikard Johnels wrote (shortened):
> On Tuesday 19 December 2006 11:00, Johannes Meixner wrote:
> > On Dec 18 18:25 Rikard Johnels wrote (shortened):
> > > All i get (In every case) is bad request.
> > >
> > > lpr -H 192.168.1.16:631 -P Lj4 -J test.printing olyckan
> > > lpr: Bad Request
> > >
> > > lp -h 192.168.1.16:631 -d Lj4 -t test.printing olyckan
> > > lp: Bad Request
> >
> > I know about this problem which happens only occasionally when
> > a CUPS 1.2 client sends jobs to a CUPS 1.1 server but usually
> > the same command works after some retries which makes it very
> > difficult to find the actual reason.
> >
> > If you like to debug, see
> > http://en.opensuse.org/SDB:CUPS_in_a_Nutshell
> > "If problems are encountered"
> >
> > Perhaps you are lucky and you get a meaningful error message in
> > /var/log/cups/error_log on the CUPS server (i.e. on 192.168.1.16).
...
>
> Client: rpm -qa cups > cups-1.2.0-0.1

We never provided CUPS version 1.2.0 officially.

ftp://ftp.suse.com/pub/people/kssingvo/unsupported/CUPS/
is only for testing, note the "unsupported" and see
ftp://ftp.suse.com/pub/people/kssingvo/unsupported/CUPS/README.txt
------------------------------------------------------------------
The cups-1.2.0 release is still problematic
...
Install at own risk!
...
Be aware! (Installation) support is lost, if any of these
packages becomes installed.
------------------------------------------------------------------

openSUSE 10.2 is our first product where we have CUPS 1.2
and here we have CUPS version 1.2.7.

There have been tons of bug fixes in CUPS 1.2, see
http://www.cups.org/relnotes.php
In particular note the entry about "Increased the HTTP and
IPP read timeouts" and the matching "software trouble report"
http://www.cups.org/str.php?L1719
which might be the actual cause of this problem (or at least
related to the problem).

Only if the problem persists with CUPS version 1.2.7, we are
interested in further debugging (in particular because for me the
problem happened while I used the above mentioned test version
1.2.0 but it did not happen again since I use openSUSE 10.2) and
we will not debug a CUPS version which we never had in our products.


> Server: cups-1.1.23-21
>
> So that might be the cause..
>
> Erroro log on .16: (Server)
...
> E [17/Dec/2006:03:08:30 +0100] ReadClient: 5 IPP Read Error!
> E [17/Dec/2006:03:33:23 +0100] ReadClient: 6 IPP Read Error!
> E [18/Dec/2006:18:17:53 +0100] ReadClient: 5 IPP Read Error!
> E [18/Dec/2006:18:18:51 +0100] ReadClient: 5 IPP Read Error!
> E [18/Dec/2006:18:19:04 +0100] ReadClient: 5 IPP Read Error!
> E [18/Dec/2006:18:19:25 +0100] ReadClient: 5 IPP Read Error!
> E [18/Dec/2006:18:20:58 +0100] ReadClient: 5 IPP Read Error!
> I [18/Dec/2006:18:28:49 +0100] Adding start banner page "none" to job 3.
> I [18/Dec/2006:18:28:49 +0100] Adding end banner page "none" to job 3.
> I [18/Dec/2006:18:28:49 +0100] Job 3 queued on 'Lj4' by 'root'.
> I [18/Dec/2006:18:28:49 +0100] Started filter /usr/lib/cups/filter/texttops
> (PID 5183) for job 3.
> I [18/Dec/2006:18:28:49 +0100] Started filter /usr/lib/cups/filter/pstops (PID
> 5184) for job 3.
> I [18/Dec/2006:18:28:49 +0100] Started
> filter /usr/lib/cups/filter/foomatic-rip (PID 5185) for job 3.
> I [18/Dec/2006:18:28:49 +0100] Started backend /usr/lib/cups/backend/parallel
> (PID 5186) for job 3.

As you did not write what you did while those messages appear
in eror_log I can only guess that after several failed attempts
(which result "IPP Read Error"), the same command finally worked
and leads to "job 3" which is exactly my experience.

The "IPP Read Error" alone does not help to find the actual reason.

Note what I wrote you and see
http://en.opensuse.org/SDB:CUPS_in_a_Nutshell
"If problems are encountered"
how to get more useful information for debugging.

In this particular case check if even "LogLevel debug2" may be
required in this particular case to get some meaningful debug
information and note that the debug information for exactly
one failed attempt is sufficient.


Kind Regards
Johannes Meixner
--
SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@xxxxxxx
90409 Nuernberg, Germany WWW: http://www.suse.de/
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >