Commit | Line | Data |
---|---|---|
2117e02e MW |
1 | .TH qmail-log 5 |
2 | .SH NAME | |
3 | qmail-log \- the qmail activity record | |
4 | .SH DESCRIPTION | |
5 | .B qmail-send | |
6 | prints a series of lines describing its activities. | |
7 | Each possible line is described below. | |
212b6f5d | 8 | .SH "STATUS" |
2117e02e | 9 | .TP |
212b6f5d | 10 | .B status: local \fIl\fB/\fIL\fB remote \fIr\fB/\fIR\fB ... |
2117e02e | 11 | .B qmail-send |
212b6f5d MW |
12 | is waiting for |
13 | .I l | |
14 | local deliveries | |
15 | and | |
16 | .I r | |
17 | remote deliveries. | |
18 | The concurrency limits are | |
19 | .I L | |
20 | and | |
21 | .IR R . | |
2117e02e | 22 | .TP |
212b6f5d | 23 | .B status: exiting |
2117e02e MW |
24 | .B qmail-send |
25 | is done. | |
26 | .SH "FATAL PROBLEMS" | |
27 | .TP | |
28 | .B alert: cannot start: ... | |
29 | .B qmail-send | |
30 | is unable to prepare itself for delivering messages; | |
31 | it is giving up. | |
32 | This normally indicates a serious configuration error, | |
33 | but it can be caused by a temporary lack of resources. | |
34 | .TP | |
35 | .B alert: oh no! lost ... | |
36 | One of the other daemons has died. | |
37 | .B qmail-send | |
38 | will exit as soon as possible. | |
39 | .SH "SERIOUS PROBLEMS" | |
40 | .TP | |
41 | .B alert: unable to append to bounce message... | |
42 | .B qmail-send | |
43 | is unable to record a permanent failure, | |
44 | usually because the disk is full. | |
45 | This is a very serious problem; | |
46 | .B qmail-send | |
47 | cannot proceed without recording the results. | |
48 | It will try again in ten seconds. | |
49 | .TP | |
50 | .B alert: out of memory... | |
51 | .B qmail-send | |
52 | tried to allocate more memory and failed. | |
53 | It will try again in ten seconds. | |
54 | .TP | |
55 | .B alert: unable to opendir... | |
56 | .B qmail-send | |
57 | is having trouble reading a file list from disk, | |
58 | usually because the system's file descriptor table is full, | |
59 | but possibly because permissions are set incorrectly. | |
60 | It will try again in ten seconds. | |
61 | .TP | |
62 | .B alert: unable to switch back... | |
63 | .B qmail-send | |
64 | was sent SIGHUP, | |
65 | and it is unable to reenter the queue directory. | |
66 | This is a very serious problem; | |
67 | .B qmail-send | |
68 | cannot proceed outside the queue directory. | |
69 | It will try again in ten seconds. | |
70 | .TP | |
71 | .B alert: unable to reread... | |
72 | .B qmail-send | |
73 | was sent SIGHUP, | |
74 | but it is unable to read the new controls. | |
75 | It will continue operating with the original controls. | |
76 | .SH "MESSAGES" | |
77 | .TP | |
78 | .B new msg \fIm\fB | |
79 | .B qmail-send | |
80 | is going to preprocess a queued message. | |
81 | The message number, | |
82 | .IR m , | |
83 | is its disk inode number. | |
84 | After a message is removed from the queue, | |
85 | its number can be reused immediately. | |
86 | .TP | |
87 | .B info msg \fIm\fB: bytes \fIb\fB from <\fIs\fB> qp \fIq\fB uid \fIu\fB | |
88 | Message | |
89 | .I m | |
90 | contains | |
91 | .I b | |
92 | bytes; | |
93 | its envelope sender is | |
94 | .IR s ; | |
95 | it was queued by a user with user ID | |
96 | .IR u . | |
97 | .I q | |
98 | is a long-term queue identifier, | |
99 | the process ID of the | |
100 | .B qmail-queue | |
101 | that queued the message. | |
102 | .TP | |
103 | .B bounce msg \fIm\fB qp \fIq\fB | |
104 | Message | |
105 | .I m | |
106 | had some delivery failures. | |
107 | The long-term queue identifier of the bounce (or double-bounce) message | |
108 | is | |
109 | .IR q . | |
110 | .TP | |
111 | .B triple bounce: discarding ... | |
112 | Message | |
113 | .I m | |
114 | had some delivery failures, | |
115 | but it is already a double-bounce message, | |
116 | so it must be thrown away. | |
117 | Triple-bounce messages do not exist. | |
118 | .TP | |
119 | .B end msg \fIm\fB | |
120 | .B qmail-send | |
121 | is about to remove | |
122 | message | |
123 | .I m | |
124 | from the queue. | |
125 | .SH "DELIVERIES" | |
126 | .TP | |
127 | .B starting delivery \fId\fB: msg \fIm\fB to ... | |
128 | .B qmail-send | |
129 | is telling | |
130 | .B qmail-lspawn | |
131 | or | |
132 | .B qmail-rspawn | |
133 | to deliver message | |
134 | .I m | |
135 | to one recipient. | |
136 | The delivery number, | |
137 | .IR d , | |
138 | starts at 1 and increases by 1 for each new delivery. | |
139 | .TP | |
140 | .B delivery \fId\fB: success: ... | |
141 | Delivery | |
142 | .I d | |
143 | was successful. | |
144 | .TP | |
145 | .B delivery \fId\fB: failure: ... | |
146 | Delivery | |
147 | .I d | |
148 | failed permanently. | |
149 | The message will bounce. | |
150 | .TP | |
151 | .B delivery \fId\fB: deferral: ... | |
152 | Delivery | |
153 | .I d | |
154 | failed temporarily. | |
155 | This recipient will be retried later. | |
156 | .TP | |
157 | .B delivery \fId\fB: report mangled, will defer | |
158 | There is a serious bug in | |
159 | .B qmail-lspawn | |
160 | or | |
161 | .BR qmail-rspawn . | |
162 | This recipient will be retried later. | |
163 | .SH "WARNINGS" | |
164 | .TP | |
165 | .B internal error: delivery report out of range | |
166 | .B qmail-lspawn | |
167 | or | |
168 | .B qmail-rspawn | |
169 | has supplied a report on a nonexistent delivery. | |
170 | This is a serious bug. | |
171 | .TP | |
172 | .B qmail-clean unable to clean up ... | |
173 | For some reason | |
174 | .B qmail-clean | |
175 | is unable to remove the indicated file. | |
176 | It will try again later. | |
177 | .TP | |
178 | .B trouble fsyncing ... | |
179 | .B qmail-send | |
180 | was unable to write to disk the results of preprocessing a queued message. | |
181 | It will try again later. | |
182 | .TP | |
183 | .B trouble in select | |
184 | There is an operating system bug. | |
185 | .TP | |
186 | .B trouble injecting bounce message... | |
187 | .B qmail-send | |
188 | was unable to queue a bounce message, | |
189 | usually because the disk is full. | |
190 | It will try again later. | |
191 | .TP | |
192 | .B trouble marking ... | |
193 | .B qmail-send | |
194 | was unable to record the result of a successful or permanently | |
195 | unsuccessful delivery. | |
196 | This means that the delivery will be tried again later. | |
197 | .TP | |
198 | .B trouble opening ... | |
199 | .B qmail-send | |
200 | was unable to open the list of local or remote recipients | |
201 | for a message. | |
202 | It will try again later. | |
203 | .TP | |
204 | .B trouble reading ... | |
205 | Either | |
206 | .B qmail-send | |
207 | is unable to read a recipient list, | |
208 | or it is unable to read the envelope of a queued | |
209 | message, or it is out of memory. | |
210 | Whatever it was doing, it will try again later. | |
211 | .TP | |
212 | .B trouble writing to ... | |
213 | .B qmail-send | |
214 | was unable to preprocess a queued message, | |
215 | usually because the disk is full. | |
216 | It will try again later. | |
217 | .TP | |
218 | .B unable to create ... | |
219 | .B qmail-send | |
220 | was unable to preprocess a queued message, | |
221 | usually because the disk is out of inodes. | |
222 | It will try again later. | |
223 | .TP | |
224 | .B unable to open ... | |
225 | .B qmail-send | |
226 | is unable to read the envelope of a queued message | |
227 | for preprocessing. | |
228 | It will try again later. | |
229 | .TP | |
230 | .B unable to start qmail-queue... | |
231 | .B qmail-send | |
232 | is unable to queue a bounce message, | |
233 | usually because the machine is almost out of memory. | |
234 | It will try again later. | |
235 | .TP | |
236 | .B unable to stat ... | |
237 | .B qmail-send | |
238 | is unable to obtain information about a file that should exist. | |
239 | It will try again later. | |
240 | .TP | |
241 | .B unable to unlink ... | |
242 | .B qmail-send | |
243 | is unable to remove a file. | |
244 | It will try again later. | |
245 | .TP | |
246 | .B unable to utime ... | |
247 | .B qmail-send | |
248 | is about to exit, | |
249 | and it is unable to record on disk | |
250 | the next scheduled delivery time for a message. | |
251 | The message will be retried as soon as | |
252 | .B qmail-send | |
253 | is restarted. | |
254 | .TP | |
255 | .B unknown record type in ... | |
256 | There is a serious bug in either | |
257 | .B qmail-queue | |
258 | or | |
259 | .BR qmail-send . | |
260 | .SH "SEE ALSO" | |
261 | qmail-send(8) |