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