Prev · NextSTR #3288: Spurious 'Bad request line "^W^C^A" from M.N.O.P!' messages in error_log

Status:4 - Pending
Priority:2 - Low, e.g. a documentation error or undocumented side-effect
Scope:3 - Applies to all machines and operating systems
Subsystem:Scheduler
Summary:Spurious 'Bad request line "^W^C^A" from M.N.O.P!' messages in error_log
Version: -feature
Created By:murdie
Assigned To:mike
Fix Version:Unassigned
Update Notification:

Receive EMails Don't Receive EMails


Trouble Report Files:

Name/Time/Date/Filename/Size
murdie: 10:08 Aug 13, 2009
 
server.cupsd.conf (4k)
 
murdie: 10:09 Aug 13, 2009
 
client.cupsd.conf (3k)
 

Trouble Report Dialog:

Name/Time/Date/Text
murdie: 10:08 Aug 13, 2009
 
Our error_log file is filled with error messages such as:

E [13/Aug/2009:17:46:08 +0100] Bad request line "^W^C^A" from M.N.O.P!

They appear to be (almost) harmless, though they can obscure error messages reporting a more harmful situation, so we would like to get rid of them. Occasionally, we see apparent garbling other than "^W^C^A", which can spread over several 80-character lines.

I attach our server and client cupsd.conf files (with IP addresses bowdlerized!)

John A. Murdie

 
murdie: 02:28 Aug 14, 2009
 
I forgot to mention - and just in case it's needed - the install uses Open SSL 0.9.8h and MIT Kerberos 1.6.3.

John A. Murdie

 
mike: 14:21 Sep 22, 2009
 
Leaving as pending, however we have been unable to reproduce this bug...
 
murdie: 04:21 Apr 23, 2010
 
Still getting these messages with 1.4.3. Again, being short, they don't seem to do any harm, though if they were to be longer (as previously seen) they obscure the contents of the error_log file.

At a loss how to investigate this, but will have a go.

John A. Murdie

 
murdie: 03:41 Oct 25, 2010
 
Still getting these messages with 1.4.4.
 
pipitas: 05:31 Dec 07, 2010
 
I remember having seen similar messages in CUPS logs recently. System was RHEL-5.5/CUPS-1.3.7. They were experimenting with Kerberos too...

Apparently the logs turned to "clean" again after removing Kerberos from the environment.

 
mike: 12:22 Jan 03, 2011
 
Kurt - thanks for the data point, and John's system is also using Kerberos. Something to look at, maybe GSSAPI isn't working properly after an error?
 
mike: 09:50 Feb 21, 2011
 
OK, moving this to CUPS 1.5 (was 1.3.10)

Will not be addressed in CUPS 1.4.x...

 
mike: 23:58 May 19, 2011
 
I'm still not able to reproduce this, but will keep the bug open in the hopes of doing so and fixing in a future release.
 
endzone: 14:42 Aug 07, 2011
 
Hi,

I am having the reported problem between a CUPS 1.3.9 server and 1.3.9/1.4.6 clients.

I found a minimal example where the problem appears *most* of the time, not always:

Server: /etc/cups/cups.conf:
---
LogLevel                info

Listen          *:631

# SSL encryption when using authentication
ServerCertificate       <cert-file>
ServerKey               <key-file>

# Restrict access to the server...
<Location />
        AuthType        Basic
        Require         valid-user
        Order           allow,deny
</Location>
---

Client: /etc/cups/client.conf
---
ServerName <server>
Encryption Required
---


Now, when I do a simple "lpq" on the client I get an error:
---
Bad request line "" from <client-ip>!
---
in about 90% of the trials.

If I remove the "Encryption Reqired" from the client.conf on the client, the error message disappears!

Hope that helps..?