Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionDennis Schridde
2012-04-26 13:15:52 UTC
Created attachment 580469[details]
Sample line from error_log
Description of problem:
When we try to print from a Fedora 16 or SL 6.2 machine on a CUPS server (config attached) running on a SL 6.2 server the print will fail in various ways (both examples from a SL 6.2 client accessed via ssh -X):
Using okular:
Okular will hang when selecting File/Print and ask for a password on the terminal it was started from. The cups server will log several lines similar to:
E ... Bad request line "<garbage>" from <my ip>"!
E ... Bad URI "<garbage>" in request!
Using evince:
Evince will show the list of printers, ask for the authentication details and everything appears normal. But the error_log of the cups server will show lines similar to the ones above, just this time they will continuously appear until the print dialogue is closed. After pressing "print", the file will not actually be printed, but is shown as "processing" in the cups job list instead. Cancelling the job keeps it in the job list as "cancelled" and does not remove it or allow other jobs to be printed.
The <garbage> part in the log will always start with the same 4 characters - see the attached file for a sample.
The effect does not depend on which file is being opened by evince or okular.
Version-Release number of selected component (if applicable):
cups-1.4.2-44.el6.x86_64 (on the cups server)
evince-2.28.2-14.el6_0.1.x86_64 (on the client)
kdegraphics-4.3.4-6.el6.x86_64 (on the client)
How reproducible:
Open the file using okular or evince and select File/Print from the menu.
It appears this has something to do with acroread trying to print and breaking the whole cups server in that process.
The current workaround we have is as follows:
1) Cancel the offending print jobs (which will never be completed)
2) Restart the cups service *twice*
3) Restart the printer
I have attached "Sample line from error_log". Since I do not know what information is contained in the log, I am hesitant to publicly post the complete file. May I send it to you in private?
Tim, are you sure this is a duplicate of bug #787884 ?
The cupsd.conf in comment #1 shows there's no encryption used (unlike in bug #787884). Also the latest comment in STR #3288 (which seems to be similar to bug #787884) shows that the problem could be somewhere in the encryption area.
There is encryption in use for the connections that fail (all of them in the supplied log).
The way it happens is:
client is accepted, and it sends "OPTIONS * HTTP/1.1". Following that, the connection enters encrypted mode.
Next there is a "POST / HTTP/1.1" but with no authentication data. Accordingly, the server sends 'WWW-Authenticate: Basic realm="CUPS"' and closes the connection.
However, immediately after that we get a "Bad request line" log message for that same client, followed by another call to cupsdCloseClient (i.e. it ends up being called twice for the same client).
devurandom: it might help us if you could attach the /etc/cups/client.conf file (or else ~/.cups/client.conf) from the client machine.
(In reply to comment #9)
> devurandom: it might help us if you could attach the
> /etc/cups/client.conf file (or else ~/.cups/client.conf) from the client
> machine.
$ ll /etc/cups/client.conf
-rw-r--r--. 1 root lp 0 Mar 29 13:35 /etc/cups/client.conf
$ cat ~/.cups/client.conf
ServerName print
Created attachment 580469 [details] Sample line from error_log Description of problem: When we try to print from a Fedora 16 or SL 6.2 machine on a CUPS server (config attached) running on a SL 6.2 server the print will fail in various ways (both examples from a SL 6.2 client accessed via ssh -X): Using okular: Okular will hang when selecting File/Print and ask for a password on the terminal it was started from. The cups server will log several lines similar to: E ... Bad request line "<garbage>" from <my ip>"! E ... Bad URI "<garbage>" in request! Using evince: Evince will show the list of printers, ask for the authentication details and everything appears normal. But the error_log of the cups server will show lines similar to the ones above, just this time they will continuously appear until the print dialogue is closed. After pressing "print", the file will not actually be printed, but is shown as "processing" in the cups job list instead. Cancelling the job keeps it in the job list as "cancelled" and does not remove it or allow other jobs to be printed. The <garbage> part in the log will always start with the same 4 characters - see the attached file for a sample. The effect does not depend on which file is being opened by evince or okular. Version-Release number of selected component (if applicable): cups-1.4.2-44.el6.x86_64 (on the cups server) evince-2.28.2-14.el6_0.1.x86_64 (on the client) kdegraphics-4.3.4-6.el6.x86_64 (on the client) How reproducible: Open the file using okular or evince and select File/Print from the menu.