[cups.general] cupsdAuthorize: No authentication data provided - error_log

Bryan Mason bmason at redhat.com
Tue Feb 8 15:39:34 PST 2011


On 02/08/2011 03:21 PM, Chris Hasler wrote:
> I have now deleted the three printer that contantly throw messages
> into the error_log.  After deleting them I shutdown cups and xinetd
> servers and restarted them.  Still the messages keep rolling in
> every few milliseconds.  How can I make this stop?!!!
[...]
>> Here's an example of the entries in the error_log on the 1.4.6 host.
>>
>> D [08/Feb/2011:16:55:15 -0600] cupsdSetBusyState: Not busy
>> D [08/Feb/2011:16:55:20 -0600] cupsdAcceptClient: 11 from 10.201.133.159:631 (IPv4)
>> D [08/Feb/2011:16:55:20 -0600] cupsdReadClient: 11 POST /printers/CIDGAB-4100N-5 HTTP/1.1
>> D [08/Feb/2011:16:55:20 -0600] cupsdSetBusyState: Active clients
>> D [08/Feb/2011:16:55:20 -0600] cupsdAuthorize: No authentication data provided.
>> D [08/Feb/2011:16:55:20 -0600] cupsdCloseClient: 11

Hi Chris,

It looks like the messages are debug messages.  Do you have

     LogLevel debug2

or

     LogLevel debug

set in /etc/cups/cupsd.conf?  If so, changing it to

     LogLevel warn

may stop the messages.  It won't stop the cause of the messages, but it 
should stop the messages from filling up error_log.

~ Bryan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6010 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://lists.cups.org/pipermail/cups/attachments/20110208/257caa95/attachment.bin>


More information about the cups mailing list