1cupsd-logs(5) Apple Inc. cupsd-logs(5)
2
3
4
6 cupsd-logs - cupsd log files (access_log, error_log, and page_log)
7
9 cupsd(8) normally maintains three log files: access_log to track
10 requests that are submitted to the scheduler, error_log to track
11 progress and errors, and page_log to track pages that are printed.
12 Configuration directives in cupsd.conf(5) and cups-files.conf(5) con‐
13 trol what information is logged and where it is stored.
14
15 ACCESS LOG FILE FORMAT
16 The access_log file lists each HTTP resource that is accessed by a web
17 browser or client. Each line is in an extended version of the so-
18 called "Common Log Format" used by many web servers and web reporting
19 tools:
20
21 host group user date-time "method resource version" status bytes
22 ipp-operation ipp-status
23
24 For example:
25
26 10.0.1.2 - - [01/Dec/2005:21:50:28 +0000] "POST / HTTP/1.1" 200 317
27 CUPS-Get-Printers successful-ok-ignored-or-substituted-attributes
28 localhost - - [01/Dec/2005:21:50:32 +0000] "GET /admin HTTP/1.1"
29 200 0 - -
30 localhost - - [01/Dec/2005:21:50:32 +0000] "POST / HTTP/1.1"
31 200 157 CUPS-Get-Printers
32 successful-ok-ignored-or-substituted-attributes
33 localhost - - [01/Dec/2005:21:50:32 +0000] "POST / HTTP/1.1"
34 200 1411 CUPS-Get-Devices -
35 localhost - - [01/Dec/2005:21:50:32 +0000] "GET /admin HTTP/1.1"
36 200 6667 - -
37
38 The host field will normally only be an IP address unless you have
39 enabled the HostNameLookups directive in the cupsd.conf file or if the
40 IP address corresponds to your local machine.
41
42 The group field always contains "-".
43
44 The user field is the authenticated username of the requesting user.
45 If no username and password is supplied for the request then this field
46 contains "-".
47
48 The date-time field is the date and time of the request in local time
49 and is in the format "[DD/MON/YYYY:HH:MM:SS +ZZZZ]".
50
51 The method field is the HTTP method used: "GET", "HEAD", "OPTIONS",
52 "POST", or "PUT". "GET" requests are used to get files from the
53 server, both for the web interface and to get configuration and log
54 files. "HEAD" requests are used to get information about a resource
55 prior to a "GET". "OPTIONS" requests are used to upgrade connections
56 to TLS encryption. "POST" requests are used for web interface forms
57 and IPP requests. "PUT" requests are used to upload configuration
58 files.
59
60 The resource field is the filename of the requested resource.
61
62 The version field is the HTTP specification version used by the client.
63 For CUPS clients this will always be "HTTP/1.1".
64
65 The status field contains the HTTP result status of the request, as
66 follows:
67
68 200 Successful operation.
69
70 201 File created/modified successfully.
71
72 304 The requested file has not changed.
73
74 400 Bad HTTP request; typically this means that you have a mali‐
75 cious program trying to access your server.
76
77 401 Unauthorized, authentication (username + password) is
78 required.
79
80 403 Access is forbidden; typically this means that a client tried
81 to access a file or resource they do not have permission to
82 access.
83
84 404 The file or resource does not exist.
85
86 405 URL access method is not allowed; typically this means you
87 have a web browser using your server as a proxy.
88
89 413 Request too large; typically this means that a client tried
90 to print a file larger than the MaxRequestSize allows.
91
92 426 Upgrading to TLS-encrypted connection.
93
94 500 Server error; typically this happens when the server is
95 unable to open/create a file - consult the error_log file for
96 details.
97
98 501 The client requested encryption but encryption support is not
99 enabled/compiled in.
100
101 505 HTTP version number not supported; typically this means that
102 you have a malicious program trying to access your server.
103
104 The bytes field contains the number of bytes in the request. For POST
105 requests the bytes field contains the number of bytes of non-IPP data
106 that is received from the client.
107
108 The ipp-operation field contains either "-" for non-IPP requests or the
109 IPP operation name for POST requests containing an IPP request.
110
111 The ipp-status field contains either "-" for non-IPP requests or the
112 IPP status code name for POST requests containing an IPP response.
113
114 ERROR LOG FILE FORMAT
115 The error_log file lists messages from the scheduler - errors, warn‐
116 ings, etc. The LogLevel directive in the cupsd.conf(5) file controls
117 which messages are logged:
118
119 level date-time message
120
121 For example:
122
123 I [20/May/1999:19:18:28 +0000] [Job 1] Queued on 'DeskJet' by 'mike'.
124 D [20/May/1999:19:18:28 +0000] [Job 1] argv[0]="DeskJet"
125 D [20/May/1999:19:18:28 +0000] [Job 1] argv[1]="1"
126 D [20/May/1999:19:18:28 +0000] [Job 1] argv[2]="mike"
127 D [20/May/1999:19:18:28 +0000] [Job 1] argv[3]="myjob"
128 D [20/May/1999:19:18:28 +0000] [Job 1] argv[4]="1"
129 D [20/May/1999:19:18:28 +0000] [Job 1] argv[5]="media=
130 na_letter_8.5x11in sides=one-sided"
131 D [20/May/1999:19:18:28 +0000] [Job 1] argv[6]="/var/spool/cups/
132 d000001-001"
133 I [20/May/1999:19:21:02 +0000] [Job 2] Queued on 'DeskJet' by 'mike'.
134 I [20/May/1999:19:22:24 +0000] [Job 2] Canceled by 'mike'.
135
136 The level field contains the type of message:
137
138 A Alert message (LogLevel alert)
139
140 C Critical error message (LogLevel crit)
141
142 D Debugging message (LogLevel debug)
143
144 d Detailed debugging message (LogLevel debug2)
145
146 E Normal error message (LogLevel error)
147
148 I Informational message (LogLevel info)
149
150 N Notice message (LogLevel notice)
151
152 W Warning message (LogLevel warn)
153
154 X Emergency error message (LogLevel emerg)
155
156 The date-time field contains the date and time of when the page started
157 printing. The format of this field is identical to the data-time field
158 in the access_log file.
159
160 The message field contains a free-form textual message. Messages from
161 job filters are prefixed with "[Job NNN]" where "NNN" is the job ID.
162
163 PAGE LOG FILE FORMAT
164 The page_log file lists each page or group of pages that are sent to a
165 printer. By default, each line contains the following information:
166
167 printer user job-id date-time page-number num-copies job-billing
168 job-originating-host-name job-name media sides
169
170 printer user job-id date-time total num-impressions job-billing
171 job-originating-host-name job-name media sides
172
173 For example the entries for a two page job called "myjob" might look
174 like:
175
176 DeskJet root 1 [20/May/1999:19:21:05 +0000] 1 1 acme-123
177 localhost myjob na_letter_8.5x11in one-sided
178 DeskJet root 1 [20/May/1999:19:21:05 +0000] 2 1 acme-123
179 localhost myjob na_letter_8.5x11in one-sided
180
181 DeskJet root 1 [20/May/1999:19:21:06 +0000] total 2 acme-123
182 localhost myjob na_letter_8.5x11in one-sided
183
184 The PageLogFormat directive in the cupsd.conf(5) file can be used to
185 change this information.
186
187 The printer field contains the name of the printer that printed the
188 page. If you send a job to a printer class, this field will contain
189 the name of the printer that was assigned the job.
190
191 The user field contains the name of the user (the IPP requesting-user-
192 name attribute) that submitted this file for printing.
193
194 The job-id field contains the job number of the page being printed.
195
196 The date-time field contains the date and time of when the page started
197 printing. The format of this field is identical to the data-time field
198 in the access_log file.
199
200 The page-number and num-copies fields contain the page number and num‐
201 ber of copies being printed of that page. For printers that cannot
202 produce copies on their own, the num-copies field will always be 1.
203
204 Lines containing the keyword "total" have a num-impressions field
205 instead which provides the total number of impressions (sides) that
206 have been printed on for the job.
207
208 The job-billing field contains a copy of the job-billing or job-
209 account-id attributes provided with the IPP Create-Job or Print-Job
210 requests or "-" if neither was provided.
211
212 The job-originating-host-name field contains the hostname or IP address
213 of the client that printed the job.
214
215 The job-name field contains a copy of the job-name attribute provided
216 with the IPP Create-Job or Print-Job requests or "-" if none was pro‐
217 vided.
218
219 The media field contains a copy of the media or media-col/media-size
220 attribute provided with the IPP Create-Job or Print-Job requests or "-"
221 if none was provided.
222
223 The sides field contains a copy of the sides attribute provided with
224 the IPP Create-Job or Print-Job requests or "-" if none was provided.
225
227 cupsd(8), cupsd.conf(5), cups-files.conf(5), CUPS Online Help
228 (http://localhost:631/help)
229
231 Copyright © 2007-2017 by Apple Inc.
232
233
234
23511 June 2014 CUPS cupsd-logs(5)