1HYLAFAX-LOG(5F) HYLAFAX-LOG(5F)
2
6 log/* - session log files
7
9 Files in the log directory in the HylaFAX spooling area contain log‐
10 ging/tracing information about transmit and receive sessions. One file
11 exists for each inbound or outbound call, with the filename of the form
12 ``cXXXXXXXX'' where XXXXXXXX is a decimal sequence number termed a com‐
13 munication identifier. The amount and kind of tracing information that
14 is recorded for a call is defined by the SessionTracing parameter spec‐
15 ified in the modem configuration file; see hylafax-config(5F).
16 Note that logging/tracing information generated by the server outside
18 of a session is directed to the syslog(3) service and is controlled by
19 the LogFacility and ServerTracing parameters specified in the modem
20 configuration file.
21 [NB: The remainder of this manual page is out of date.]
23
25 The following messages may appear when server operation tracing (bit 1)
26 is enabled:
27 MODEM: Unknown type "%s" ignored. The ModemType configuration parame‐
29 ter was not recognized.
30 MODEM %s %s/%s. This message is generated each time the modem is reset
32 and made ready for use.
33 %s: Can not lock device.. The UUCP lockfile for the modem could not be
35 created because another process has a lockfile already in place.
36 %s: Can not open modem (%m). open(2) on the special device file for
38 the modem failed; the error status is presented; c.f. intro(2).
39 %s: Can not open modem (timed out).. open(2) on the special device
41 file blocked and was timed out. This typically is because the system
42 does not support a non-blocking mechanism for opening the device and
43 the presented interface requires that carrier be present before the
44 open can succeed.
45 %s: setuid root failed (%m). The server process was unable to estab‐
47 lish root privileges. This is usually caused by server being improp‐
48 erly installed.
49 %s: fcntl: %m. The server was unable to turn off the O_NDELAY bit on
51 the open modem file descriptor after doing a non-blocking open of the
52 modem device special file.
53 schedctl: %m. (Only on Silicon Graphics systems.) A schedctl(2) sys‐
55 tem call to set the server process priority failed.
56 sched policy=%d, priority=%d. (Only on POSIX compliant systems.)
58 Describes a setscheduler(2) system call to enhance real-time job sched‐
59 uling.
60 Unable to set %s scheduling parameters: %m. (Only on SVR4-style sys‐
62 tems.) A priocntl system call to set the server process priority
63 failed.
64 priocntl(%s): %m. (Only on SVR4-style systems.) A priocntl system
66 call to get the current process scheduling information failed.
67 sched policy=%d, priority=%d. (Only on POSIX-compliant systems.)
69 Indicates a possible change in the system job scheduling due to use of
70 PriorityScheduling
71 %s: Can not deduce modem type.. The server was unable to reset and
73 initialize the modem. This can be caused by many things: wrong device
74 filename, improper cabling, incorrect modem type, incorrect modem con‐
75 figuration, etc.
76 RECV: Permission denied (unacceptable client TSI). A receive request
78 was denied because the client was denied access through the TSI access
79 control list mechanism; c.f. tsi(5F).
80 RECV: Unable to create file "%s" for received data. The server was
82 unable to create a file for writing the received facsimile data. Check
83 the permission on the recvq subdirectory. Beware also that the server
84 uses tempnam(3) to create these files and the presence of the TMPDIR
85 environment variable may cause the server to try to create files in a
86 directory other than the recvq directory.
87 RECV data in "%s". This is an information message; the received fac‐
89 simile is being placed in the specified filename.
90 RECV: empty file "%s" deleted. A receive operation terminated without
92 any good pages being received; consequently the empty file is deleted.
93 ACCEPT TSI "%s". The TSI received during a receive operation was
95 accepted and the receive will continue.
96 REJECT TSI "%s". The TSI received during a receive operation was
98 rejected and the receive will be aborted at the next opportunity.
99 POLL: Unable to create file "%s" for received data. The server was
101 unable to create a file for the polled data. See also above under
102 ``RECV: Unable...''.
103 POLL: empty file "%s" deleted. A poll operation terminated without any
105 good pages being received; consequently the empty file is deleted.
106 internal muckup, lost polling request. This message should not appear;
108 it indicates the server went to do a poll but did not find the user-
109 specified poll request in its job description; c.f. sendq(5F).
110 SEND FAILED: %s. A transmission failed for the reason shown.
112 SEND: Can not open document file "%s", dirnum %d. The server was
114 unable to open the TIFF document file that was to be transmitted.
115 SEND: Can not set directory in document file "%s", dirnum %d. The
117 server was unable to access the TIFF directory associated with the next
118 page to transmit. The document file and directory number for the page
119 are shown.
120 SEND: %s "%s", dirnum %d. A transmission failed because three attempts
122 were made to transmit the same page. The full reason for the failure
123 is displayed along with the document filename and directory number of
124 the page that failed.
125 SEND: Document is not in a Group 3-compatible format (file %s, compres‐
127 sion %d). The TIFF document submitted for transmission was not was not
128 compressed with CCITT T.4 compression; the TIFF compression code number
129 is shown. This is treated as a fatal error and the job is aborted.
130 REJECT: Document was encoded with 2DMR, but client does not support
132 this data format. The document to be transmitted was encoded using the
133 optional 2DMR form of the CCITT T.4 standard, but the client capabili‐
134 ties indicate this data format is not supported. This is not a fatal
135 error; the server will disconnect and reimage the document using 1DMH
136 encoding.
137 REJECT: Client does not support document page width, max remote page
139 width %u, image width %lu. The document to be transmitted was imaged
140 using a page width that is not supported by the client. This is not a
141 fatal error; the server will disconnect and reimage the document using
142 the newly discovered client capabilities.
143 REJECT: High resolution document is not supported by client, image res‐
145 olution %g line/mm. The document to be transmitted was imaged using 7
146 line/mm, but the client only supports 3.85 line/mm. This is not a
147 fatal error; the server will disconnect and reimage the document using
148 the newly discovered client capabilities.
149 REJECT: Client does not support document page length, max remote page
151 length %d mm, image length %lu rows (%.2f mm). The document to be
152 transmitted was imaged using a page length that is not supported by the
153 client. This is not a fatal error; the server will disconnect and
154 reimage the document using the newly discovered client capabilities.
155 ABORT: job abort requested. The server received a request on a command
157 FIFO file to abort the current send/receive job.
158 ANSWER: Can not lock modem device. The server went to answer an incom‐
160 ing call, but found the device locked for use by another process. This
161 is the usual scenario that takes place when an outbound call is made
162 through the modem: the echo from data written to the modem causes the
163 fax server to wakeup, only to discover the UUCP lockfile for the outgo‐
164 ing call. The fax server will discard its handle on the modem and wait
165 for the lockfile to be removed.
166 ANSWER: FAX CONNECTION. The server is initiating service for an incom‐
168 ing facsimile call.
169 ANSWER: DATA CONNECTION. The server is initiating service for an
171 incoming data call.
172 ANSWER: Data connections are not permitted. The server rejected an
174 incoming data call because the configured GettyArgs parameter is null.
175 ANSWER: Could not switch modem to data service. The server was unable
177 to initiate service for an incoming data call because of some problem
178 in setting up the modem for data use.
179 ANSWER: VOICE CONNECTION. The server is initiating service for an
181 incoming voice call.
182 ANSWER: Could not switch modem to voice service. The server was unable
184 to initiate service for an incoming voice call because of some problem
185 in setting up the modem for voice use.
186 ANSWER: %s. An error was detected by the modem layer while setting up
188 an incoming call.
189 GETTY: could not create. The server was unable to create an internal
191 data structure used to track a getty process.
192 GETTY: can not fork. The server was unable to fork(2) a new process in
194 order to startup the getty program.
195 runGetty::setregid: %m.
197 runGetty::setreuid: %m. The server was unable to change the process
198 identity before starting up the getty program.
199 GETTY: start pid %u, "%s". The server has started up a getty program
201 to service the incoming data call. The getty process identifier is
202 displayed along with the arguments passed to the program.
203 GETTY: terminated, exit status %#o. The server has reaped a getty
205 process which it started up.
206 Parse error in dial string rules "%s". The dial string rules in the
208 specified file contain a syntax error. The dialtest(8C) program should
209 be used to debug the problem.
210 Unknown answer type "%s". The AnswerRotary configuration parameter has
212 an invalid answer type string; consult hylafax-config(5F).
213 Syntax error, missing ':' in "%s".
215 Syntax error, missing quote mark in "%s".
216 Unknown configuration parameter "%s" ignored. A syntax error was
217 encountered in the server configuration file or in a message received
218 through the FIFO special file.
219
221 The following messages may appear when the facsimile protocol tracing
222 (bit 2) is enabled:
223 %s: %s (Phase B). An error occurred during Phase B of Group 3 protocol
225 processing.
226 Bad HDLC terminating flag received.. During Class 1 ECM; a terminating
228 flag for an HDLC frame was corrupt.
229 DELAY %u ms. A %u-millisecond delay was done on the host.
231 DIAL %s. The phone number %s was dialed. Note that this is the phone
233 number passed as an argument to the ModemDialCmd parameter and so may
234 not include additional dialing prefixes sent to the modem.
235 Error sending T.30 prologue frames. An error occurred while trying to
237 transmit the T.30 DCS frames.
238 HDLC frame length invalid. An ECM HDLC protocol message was exces‐
240 sively long.
241 HDLC frame not byte-oriented. Trailing byte: %#x. An ECM HDLC proto‐
243 col message was received with a number of bits incompatible with neces‐
244 sary byte-orientation.
245 HDLC frame too short (%u bytes). An HDLC protocol message was not at
247 least 3 bytes long outside of ECM protocol or at least 5 bytes long
248 within ECM protocol.
249 HDLC frame with bad address field %#x. An HDLC protocol message was
251 sent/received with an address field other than 0xff.
252 HDLC frame with bad control field %#x. An HDLC protocol message was
254 sent/received with an invalid control field.
255 MODEM ERROR: %s. While waiting for a modem response/result an error
257 was encountered (e.g. an ``ERROR'' result code).
258 MODEM protocol botch ("%s"), cannot parse PPR. The Class 2 modem
260 driver encountered an error parsing the post-page response code in a
261 ``+FPTS:'' status message.
262 MODEM protocol botch, can not parse "%s". The Class 2 modem driver
264 encountered an error parsing the displayed session capabilities string.
265 This is usually due to a communication problem between host and modem
266 (though it can also be caused by bogus modem firmware).
267 MODEM protocol botch: OK without +FPTS:. The Class 2 modem driver
269 encountered an error in the host-modem protocol for receiving facsim‐
270 ile. While waiting for the post-page status (``+FPTS:''), an ``OK''
271 result was received first. This should never happen.
272 MODEM protocol botch: +FET: without +FPTS:. The Class 2 modem driver
274 encountered an error in the host-modem protocol for receiving facsim‐
275 ile. While waiting for the post-page status (``+FPTS:''), a ``+FET:''
276 status message was received first. This should never happen.
277 POLL with CIG "%s". A poll operation is beginning; the Calling Sub‐
279 scriber Identification string that is transmitted to the peer is dis‐
280 played.
281 POLL: begin. The server is beginning a polled receive operation.
283 POLL: end. The server just completed a polled receive operation.
285 POLL: %s (begin). The specified error message occurred when initiating
287 the poll operation.
288 POLL: %s (end). The specified error message occurred while terminating
290 the poll operation.
291 Problem receiving post-page HDLC frame. An error occurred while
293 receiving the HDLC frame that is expected to hold the post-page mes‐
294 sage.
295 Problem sending TCF data. An error occurred while sending the TCF data
297 during training.
298 RECV PPM: %s. The specified post-page message was received during a
300 receive operation.
301 RECV PPR: %s. The specified post-page response was transmitted during
303 a receive operation.
304 RECV training at %s %s. During a receive operation, begin training at
306 the specified modulation and signalling rate.
307 RECV: begin. The server is beginning a receive operation.
309 RECV: end. The server just completed a receive operation.
311 RECV: %d bytes of data. During a receive operation the specified num‐
313 ber of bytes of facsimile data were received for the current page.
314 RECV: %lu bytes, %lu total rows. During a receive operation the speci‐
316 fied number of bytes of facsimile data were received. The current run‐
317 ning total of rows in the current page being received is also dis‐
318 played.
319 RECV: %s (begin). The specified error message occurred when initiating
321 the receive operation.
322 RECV: %s (end). The specified error message occurred while terminating
324 the receive operation.
325 RECV: TCF %u bytes, %u%% non-zero, %u zero-run. When receiving train‐
327 ing, the received TCF had the specified number of bytes of which a cer‐
328 tain percentage was non-zero and the longest consecutive run of zero
329 data was found.
330 RECV: reject TCF (too many non-zero, max %u%%). The received TCF was
332 deemed unacceptable because there was too high a percentage of non-zero
333 data in it. The Class1TCFMaxNonZero configuration parameter controls
334 this decision.
335 RECV: reject TCF (zero run too short, min %u). The received TCF was
337 deemed unacceptable because the longest run of zero data was too short.
338 The Class1TCFMinZero configuration parameter controls this decision.
339 RECV: bad code word 0x%x, len %d, row %lu.
341 RECV: begin page. During a receive operation a new page of data is
343 about to received on the high speed message carrier.
344 RECV: end page. During a receive operation, receipt of page of data on
346 the high speed message carrier just completed.
347 RECV frame FCS check failed. During ECM protocol, a received HDLC
349 frame was received which fails the CRC check and the frame was marked
350 as corrupt.
351 RECV: premature EOF. The server did not receive <DLE><ETX> to signal
353 the end of a page of facsimile data during a page receive operation.
354 REMOTE supports POSTSCRIPT transfer.
356 REMOTE does not support POSTSCRIPT transfer. The peer does or does not
357 support the Adobe POSTSCRIPT transfer extensions to the T.30 protocol.
358 RECV: Missing EOL after 5 seconds. The server timed out while receiv‐
360 ing page data. This typically is caused by a flow control configura‐
361 tion problem that causes data from the modem to the host to be stopped.
362 RECV: %u bytes of data, %lu total lines. While receiving page data, %u
364 bytes of raw data were received; the current total number of rows in
365 the page are also displayed.
366 RECV: %lu bad lines %lu consecutive bad lines. After the completion of
368 a page receive, the total number of rows received in error and the max‐
369 imum consecutive rows that were received in error are printed. These
370 numbers should always be zero unless copy quality checking is done in
371 the host.
372 RECV received %u frames of block %u of page %u. When the server does
374 Class 1 ECM; a complete block has been received with a given number of
375 frames for a named page.
376 RECV received assumed RCP frame with block end. When the server does
378 Class 1 ECM; the block-end indicator was received without a proper RCP
379 frame and the receipt of an RCP frame was therefore assumed or feigned.
380 RECV received frame number %u. When the server does Class 1 ECM; the
382 numbered image frame has been received.
383 RECV received RCP frame. When the server does Class 1 ECM; the first
385 RCP frame was received, which signifies the end of the image block.
386 RECV: REJECT page quality, %u%% good lines (%u%% required). When the
388 server does copy quality checking; the received page is deemed to have
389 unacceptable quality because the percentage of good rows in the page is
390 too low. This check is controlled by the PercentGoodLines configura‐
391 tion parameter.
392 RECV: REJECT page quality, %u-line run (max %u). When the server does
394 copy quality checking; the received page is deemed to have unacceptable
395 quality because the maximum consecutive rows that were received in
396 error exceeds the threshold specified by the MaxBadLines configuration
397 parameter.
398 RECV sent fourth PPR. During Class 1 ECM; the server has rejected a
400 received image block consecutively four times at which point the sender
401 is allowed to either continue to retransmit the block or to end
402 retransmissions.
403 REMOTE HANGUP: %s (code %s). The modem returned a hangup status code
405 (``+FHNG:'' or ``+FHS:'') to the host. This indicates a protocol prob‐
406 lem that was determined within the modem; there is usually nothing that
407 the server can do to work around such errors.
408 REMOTE TSI "%s". During a receive operation, the specified TSI was
410 received. This string is checked against the TSI access control list
411 described in tsi(5F).
412 REMOTE best format %s. The peers' ``best'' data format according to
414 the received DIS frame. ``Best'' here is based on the belief that
415 2DMMR data is better than 2DMR with optional uncompressed data, is bet‐
416 ter than 2DMR data, is better than 1DMH data.
417 REMOTE best rate %s. The peers' best signalling rate according to the
419 received DIS frame.
420 REMOTE best vres %s. The peers' best vertical resolution according to
422 the received DIS frame.
423 REMOTE has document to POLL. The peer indicates it has a document that
425 is available for retrieval.
426 REMOTE max %s. The peers' maximum page width/length according to the
428 received DIS frame.
429 REMOTE supports error correction. The peer supports the optional Error
431 Correct Mode (ECM) according to the received DIS frame.
432 REMOTE wants %s. The received DCS frame indicates the peer wants the
434 specified capability.
435 SEND file "%s". The specified file is about to be transmitted.
437 SEND 1D RTC.
439 SEND 2D RTC. A 1D- or 2D-encoded Return To Control (RTC) packet was
440 sent to terminate the transmission of a page of facsimile data.
441 SEND begin page. A page of facsimile data is about to be transmitted
443 on the high speed message carrier.
444 SEND end page. The transmission of a page of facsimile data on the
446 high speed message carrier was completed.
447 SEND training at %s %s. Training is about to be sent to the peer using
449 the specified modulation and signalling rate.
450 SENT %u bytes of data. The specified amount of raw facsimile page data
452 was transmitted on the high speed message carrier.
453 TRAINING failed.
455 TRAINING succeeded. Peer training succeeded or failed. When sending
456 this is based on a message returned by the peer. When receiving this
457 is based on an analysis of the received TCF data.
458 USE %s. Use the specified session capability during a send or receive.
460 The capability is based on the peers' best capabilities, the capabili‐
461 ties of the modem, and, when transmitting, the characteristics of the
462 document.
463
465 The following messages may appear when modem operation tracing (bit 3)
466 is enabled:
467 MODEM set baud rate: %d baud, input flow %s, output flow %s. The DTE-
469 DCE communication rate was set %d bits/sec on the host and the speci‐
470 fied flow control method was setup for data received from the modem
471 (input) and transmitted to the modem (output).
472 MODEM set baud rate: %d baud (flow control unchanged). The DTE-DCE
474 communication rate was changed without modifying the current flow con‐
475 trol setup.
476 MODEM set XON/XOFF/NOW: input %s, output %s.
478 MODEM set XON/XOFF/DRAIN: input %s, output %s.
479 MODEM set XON/XOFF/FLUSH: input %s, output %s. The software flow con‐
480 trol setup for data exchanged between host and modem was changed. The
481 NOW , DRAIN , and FLUSH , actions indicate whether the operation is
482 done immediately, after any pending data is transmitted to the modem,
483 or after pending data is discarded. On input XON/XOFF characters are
484 either ignored (passed through to the server uninterpreted) or inter‐
485 preted (by the system's terminal driver in order to control the flow of
486 data). Likewise, on output XON/XOFF characters are either disabled
487 (not generated by the terminal driver), or generated (by the terminal
488 driver to effect flow control of data from the modem to the host).
489 MODEM input buffering enabled.
491 MODEM input buffering disabled. On systems that buffer input data in
492 the operating system before delivering it to applications the server
493 will enable and disable buffering as best it can in those cases where
494 low input latency is critical.
495 TIMEOUT: %s. A timeout occurred while doing a modem-related operation;
497 typically reading or writing data.
498 Error #%u reading from modem. An error was returned by a read(2) sys‐
500 tem call. This usually happens when the modem prematurely drops the
501 DCD signal.
502
504 The following messages may appear when modem communication tracing (bit
505 4) is enabled:
506 --> [%d:%s]. A %d-byte line of data was received from the modem.
508 Printable data are displayed.
509 <-- data [%d]. %d bytes of unprintable data were sent to the modem,
511 typically facsimile data.
512 <-- [%d:%s]. %d bytes of printable data were sent to the modem. The
514 data are displayed.
515
517 The following messages may appear when timeout tracing (bit 5) is
518 enabled:
519 start %d second timer,
520 stop timer (stop the current timeout before it expires), and
521 stop timer - timer expired (the current timeout expired.)
522
524 When tracing of raw HDLC frames (bit 6) is enabled each frame sent and
525 received is logged: <-- HDLC<%u:%.*s> for sent frames and -->
526 HDLC<%u:%.*s> for received frames. These messages indicate that a %u-
527 byte long HDLC frame was sent or received. The first byte should
528 always be 0xff, the address field specified for dialup communication.
529 The second byte should be a frame control field. The contents of the
530 frame is displayed as sequence of bytes in hexadecimal.
531
533 When binary input/output (bit 7) is traced there are two types of mes‐
534 sages logged: <-- <%u:%.*s> for data sent to the modem and -->
535 <%u:%.*s> for data received from the modem. Each message indicates
536 that %u bytes of data were transferred. The data is displayed as a
537 sequence of bytes in hexadecimal.
538
540 Bit 8 controls the tracing of state transitions in the facsimile
541 server. There are currently eight states:
542 State Description
543 BASE during startup and initialization
544 RUNNING normal operation
545 MODEMWAIT waiting for the modem to come ready after a reset
546 LOCKWAIT waiting for a UUCP lockfile to be removed
547 GETTYWAIT waiting for a getty process to terminate
548 SENDING transmitting a facsimile
549 ANSWERING answering an incoming telephone call
550 RECEIVING receiving a facsimile
551 STATE CHANGE: %s -> %s (timeout %ld). The server is changing its
553 internal state. The timeout (in seconds) is used when polling for
554 asynchronous events such as a modem becoming ready.
555 STATE CHANGE: %s -> %s. The server is changing its internal state
557 without starting a timeout.
558
560 Bit 9 controls the tracing the management of the job queue.
561 SEND NOT READY: "%s" in %s. It was not time to send the specified job;
563 it will be requeued for the indicated time interval.
564 SEND BLOCKED BY CONCURRENT CALL: "%s" in %s. The specified job is
566 blocked by another call to the same phone number; it will be requeued
567 for the indicated time interval.
568 SEND BLOCKED BY CONCURRENT JOB: "%s" by "%s". The specified job is
570 blocked by another job to the same phone number; it will be requeued
571 for the indicated time interval.
572 JOB "%s". The specified job is about to be processed.
574 CONVERT POSTSCRIPT: "%s". The server is about to invoke the POSTSCRIPT
576 interpreter to image a document; the shell command used is displayed.
577 JOB TIMER START %s. The timer used to control scanning of the job
579 queue is started with the displayed value.
580 JOB TIMER STOP (Q head %s tts %s). The timer used to control scanning
582 of the job queue is stopped. The job at the head of the queue and that
583 job's time-to-send are displayed.
584 JOB TIMER STOP (Q empty). The timer used to control scanning of the
586 job queue is stopped. The job queue was found to be empty.
587
589 When doing copy quality checking during a receive operation the follow‐
590 ing messages may be logged if bit 10 is set:
591 RECV/CQ: adjusting for trailing noise (%lu run). The total number of
593 rows of data in the received page is adjusted (downward) by %lu. This
594 is done to handle the case where garbage data are received after the
595 RTC resulting in some number of consecutive bad rows after the page
596 data.
597 RECV/CQ: Invalid %s code word, row %lu, x %d. An invalid 1D- or 2D-
599 T.4 code word was encountered on the specified row and horizontal off‐
600 set within the row. When this occurs the server will scan for an EOL
601 code and then regenerate the bad row with the last good row of data.
602 RECV/CQ: Premature EOL (%s), row %lu, x %d. An EOL code was encoun‐
604 tered before a complete row of pixels was received. When this occurs
605 the server will discard the bad row and replace it with the last good
606 row that was received.
607 RECV/CQ: Bad %s pixel count, row %lu, x %d. A row of data was received
609 with pixel count greater than the negotiated page width. When this
610 occurs the server will discard the bad row and replace it with the last
611 good row that was received.
612 RECV/CQ: Panic, bad %s decoding state, row %lu, x %d. The decoder
614 state machine was found in a bad internal state. When this occurs the
615 server will scan for an EOL code and regenerate the row using the last
616 good received row.
617
619 faxq(8C), faxgetty(8C), faxsend(8C), hylafax-config(5F)
620 May 12, 1996 HYLAFAX-LOG(5F)