<\/a> <\/h2>\ncupsd<\/b>(8) normally maintains three log files: access_log<\/i> to track requests that are submitted to the scheduler, error_log<\/i> to track progress and errors, and page_log<\/i> to track pages that are printed. Configuration directives in cupsd.conf<\/b>(5) and cups-files.conf<\/b>(5) control what information is logged and where it is stored.<\/p>\n
ACCESS LOG FILE FORMAT<\/b>
The access_log<\/i> file lists each HTTP resource that is accessed by a web browser or client. Each line is in an extended version of the so-called “Common Log Format” used by many web servers and web reporting tools:<\/p>\n
host group user date-time<\/i> “method resource version<\/i>” status bytes
ipp-operation ipp-status<\/i><\/p>\n
For example:<\/p>\n
10.0.1.2 – – [01\/Dec\/2005:21:50:28 +0000] “POST \/ HTTP\/1.1” 200 317
CUPS-Get-Printers successful-ok-ignored-or-substituted-attributes
localhost – – [01\/Dec\/2005:21:50:32 +0000] “GET \/admin HTTP\/1.1”
200 0 – –
localhost – – [01\/Dec\/2005:21:50:32 +0000] “POST \/ HTTP\/1.1”
200 157 CUPS-Get-Printers
successful-ok-ignored-or-substituted-attributes
localhost – – [01\/Dec\/2005:21:50:32 +0000] “POST \/ HTTP\/1.1”
200 1411 CUPS-Get-Devices –
localhost – – [01\/Dec\/2005:21:50:32 +0000] “GET \/admin HTTP\/1.1”
200 6667 – –<\/p>\n
The host<\/i> field will normally only be an IP address unless you have enabled the HostNameLookups directive in the cupsd.conf<\/i> file or if the IP address corresponds to your local machine.<\/p>\n
The group<\/i> field always contains “-“.<\/p>\n
The user<\/i> field is the authenticated username of the requesting user. If no username and password is supplied for the request then this field contains “-“.<\/p>\n
The date-time<\/i> field is the date and time of the request in local time and is in the format “[DD\/MON\/YYYY:HH:MM:SS +ZZZZ]”.<\/p>\n
The method<\/i> field is the HTTP method used: “GET”, “HEAD”, “OPTIONS”, “POST”, or “PUT”. “GET” requests are used to get files from the server, both for the web interface and to get configuration and log files. “HEAD” requests are used to get information about a resource prior to a “GET”. “OPTIONS” requests are used to upgrade connections to TLS encryption. “POST” requests are used for web interface forms and IPP requests. “PUT” requests are used to upload configuration files.<\/p>\n
The resource<\/i> field is the filename of the requested resource.<\/p>\n
The version<\/i> field is the HTTP specification version used by the client. For CUPS clients this will always be “HTTP\/1.1”.<\/p>\n
The status<\/i> field contains the HTTP result status of the request, as follows:<\/p>\n\n\n| <\/td>\n | \n 200<\/p>\n<\/td>\n | <\/td>\n | \n Successful operation.<\/p>\n<\/td>\n<\/tr>\n |
\n| <\/td>\n | \n 201<\/p>\n<\/td>\n | <\/td>\n | \n File created\/modified successfully.<\/p>\n<\/td>\n<\/tr>\n |
\n| <\/td>\n | \n 304<\/p>\n<\/td>\n | <\/td>\n | \n The requested file has not changed.<\/p>\n<\/td>\n<\/tr>\n |
\n| <\/td>\n | \n 400<\/p>\n<\/td>\n | <\/td>\n | \n Bad HTTP request; typically this means that you have a malicious program trying to access your server.<\/p>\n<\/td>\n<\/tr>\n |
\n| <\/td>\n | \n 401<\/p>\n<\/td>\n | <\/td>\n | \n Unauthorized, authentication (username + password) is required.<\/p>\n<\/td>\n<\/tr>\n |
\n| <\/td>\n | \n 403<\/p>\n<\/td>\n | <\/td>\n | \n Access is forbidden; typically this means that a client tried to access a file or resource they do not have permission to access.<\/p>\n<\/td>\n<\/tr>\n |
\n| <\/td>\n | \n 404<\/p>\n<\/td>\n | <\/td>\n | \n The file or resource does not exist.<\/p>\n<\/td>\n<\/tr>\n |
\n| <\/td>\n | \n 405<\/p>\n<\/td>\n | <\/td>\n | \n URL access method is not allowed; typically this means you have a web browser using your server as a proxy.<\/p>\n<\/td>\n<\/tr>\n |
\n| <\/td>\n | \n 413<\/p>\n<\/td>\n | <\/td>\n | \n Request too large; typically this means that a client tried to print a file larger than the MaxRequestSize allows.<\/p>\n<\/td>\n<\/tr>\n |
\n| <\/td>\n | \n 426<\/p>\n<\/td>\n | <\/td>\n | \n Upgrading to TLS-encrypted connection.<\/p>\n<\/td>\n<\/tr>\n |
\n| <\/td>\n | \n 500<\/p>\n<\/td>\n | <\/td>\n | \n Server error; typically this happens when the server is unable to open\/create a file – consult the error_log file for details.<\/p>\n<\/td>\n<\/tr>\n |
\n| <\/td>\n | \n 501<\/p>\n<\/td>\n | <\/td>\n | \n The client requested encryption but encryption support is not enabled\/compiled in.<\/p>\n<\/td>\n<\/tr>\n |
\n| <\/td>\n | \n 505<\/p>\n<\/td>\n | <\/td>\n | \n HTTP version number not supported; typically this means that you have a malicious program trying to access your server.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n The bytes<\/i> field contains the number of bytes in the request. For POST requests the bytes field contains the number of bytes of non-IPP data that is received from the client.<\/p>\n The ipp-operation<\/i> field contains either “-” for non-IPP requests or the IPP operation name for POST requests containing an IPP request.<\/p>\n The ipp-status<\/i> field contains either “-” for non-IPP requests or the IPP status code name for POST requests containing an IPP response.<\/p>\n ERROR LOG FILE FORMAT<\/b>
The error_log<\/i> file lists messages from the scheduler – errors, warnings, etc. The LogLevel directive in the cupsd.conf<\/b>(5) file controls which messages are logged:<\/p>\n level date-time message<\/p>\n For example:<\/p>\n I [20\/May\/1999:19:18:28 +0000] [Job 1] Queued on \u2019DeskJet\u2019 by \u2019mike\u2019.
D [20\/May\/1999:19:18:28 +0000] [Job 1] argv[0]=”DeskJet”
D [20\/May\/1999:19:18:28 +0000] [Job 1] argv[1]=”1″
D [20\/May\/1999:19:18:28 +0000] [Job 1] argv[2]=”mike”
D [20\/May\/1999:19:18:28 +0000] [Job 1] argv[3]=”myjob”
D [20\/May\/1999:19:18:28 +0000] [Job 1] argv[4]=”1″
D [20\/May\/1999:19:18:28 +0000] [Job 1] argv[5]=”media=
na_letter_8.5x11in sides=one-sided”
D [20\/May\/1999:19:18:28 +0000] [Job 1] argv[6]=”\/var\/spool\/cups\/
d000001-001″
I [20\/May\/1999:19:21:02 +0000] [Job 2] Queued on \u2019DeskJet\u2019 by \u2019mike\u2019.
I [20\/May\/1999:19:22:24 +0000] [Job 2] Canceled by \u2019mike\u2019.<\/p>\n The level<\/i> field contains the type of message:<\/p>\n\n\n| <\/td>\n | \n A<\/p>\n<\/td>\n | <\/td>\n | \n Alert message (LogLevel alert)<\/p>\n<\/td>\n | <\/td>\n<\/tr>\n | \n| <\/td>\n | \n C<\/p>\n<\/td>\n | <\/td>\n | \n Critical error message (LogLevel crit)<\/p>\n<\/td>\n | <\/td>\n<\/tr>\n | \n| <\/td>\n | \n D<\/p>\n<\/td>\n | <\/td>\n | \n Debugging message (LogLevel debug)<\/p>\n<\/td>\n | <\/td>\n<\/tr>\n | \n| <\/td>\n | \n d<\/p>\n<\/td>\n | <\/td>\n | \n Detailed debugging message (LogLevel debug2)<\/p>\n<\/td>\n | <\/td>\n<\/tr>\n | \n| <\/td>\n | \n E<\/p>\n<\/td>\n | <\/td>\n | \n Normal error message (LogLevel error)<\/p>\n<\/td>\n | <\/td>\n<\/tr>\n | \n| <\/td>\n | \n I<\/p>\n<\/td>\n | <\/td>\n | \n Informational message (LogLevel info)<\/p>\n<\/td>\n | <\/td>\n<\/tr>\n | \n| <\/td>\n | \n N<\/p>\n<\/td>\n | <\/td>\n | \n Notice message (LogLevel notice)<\/p>\n<\/td>\n | <\/td>\n<\/tr>\n | \n| <\/td>\n | \n W<\/p>\n<\/td>\n | <\/td>\n | \n Warning message (LogLevel warn)<\/p>\n<\/td>\n | <\/td>\n<\/tr>\n | \n| <\/td>\n | \n X<\/p>\n<\/td>\n | <\/td>\n | \n Emergency error message (LogLevel emerg)<\/p>\n<\/td>\n | <\/td>\n<\/tr>\n<\/table>\n The date-time<\/i> field contains the date and time of when the page started printing. The format of this field is identical to the data-time field in the access_log<\/i> file.<\/p>\n The message<\/i> field contains a free-form textual message. Messages from job filters are prefixed with “[Job NNN]” where “NNN” is the job ID.<\/p>\n PAGE LOG FILE FORMAT<\/b>
The page_log<\/i> file lists the total number of pages (sheets) that are printed. By default, each line contains the following information:<\/p>\n printer user job-id date-time<\/i> total<\/b> num-sheets job-billing
job-originating-host-name job-name media sides<\/i><\/p>\n For example the entry for a two page job called “myjob” might look like:<\/p>\n DeskJet root 1 [20\/May\/1999:19:21:06 +0000] total 2 acme-123
localhost myjob na_letter_8.5x11in one-sided<\/p>\n The PageLogFormat directive in the cupsd.conf<\/b>(5) file can be used to change this information.<\/p>\n The printer<\/i> field contains the name of the printer that printed the page. If you send a job to a printer class, this field will contain the name of the printer that was assigned the job.<\/p>\n The user<\/i> field contains the name of the user (the IPP requesting-user-name attribute) that submitted this file for printing.<\/p>\n The job-id<\/i> field contains the job number of the page being printed.<\/p>\n The date-time<\/i> field contains the date and time of when the page started printing. The format of this field is identical to the data-time field in the access_log<\/i> file.<\/p>\n The num-sheets<\/i> field provides the total number of pages (sheets) that have been printed on for the job.<\/p>\n The job-billing<\/i> field contains a copy of the job-billing or job-account-id attributes provided with the IPP Create-Job or Print-Job requests or “-” if neither was provided.<\/p>\n The job-originating-host-name<\/i> field contains the hostname or IP address of the client that printed the job.<\/p>\n The job-name<\/i> field contains a copy of the job-name attribute provided with the IPP Create-Job or Print-Job requests or “-” if none was provided.<\/p>\n The media<\/i> field contains a copy of the media or media-col\/media-size attribute provided with the IPP Create-Job or Print-Job requests or “-” if none was provided.<\/p>\n The sides<\/i> field contains a copy of the sides attribute provided with the IPP Create-Job or Print-Job requests or “-” if none was provided.<\/p>\n | |