Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[hylafax-users] Re: puzzle
kees <kees@schoen.nl> writes:
> I'm running the beta with the protocol patches and it looks well.
> However sometimes I receive the following mail:
>
> =======================================
>
> To: FaxMaster@schoen3.schoen.nl
> From: The HylaFAX Receive Agent <fax@schoen.nl>
> Subject: facsimile not received
>
> An attempt to receive facsimile on ttyS1 failed because:
>
>
>
> ---- Transcript of session follows ----
>
> Jun 05 15:59:50.15: [ 255]: SESSION BEGIN 00000380 31104208681
> Jun 05 15:59:50.15: [ 255]: <-- [4:ATA\r]
> Jun 05 15:59:59.40: [ 255]: --> [5:+FCON]
> Jun 05 15:59:59.40: [ 255]: ANSWER: FAX CONNECTION
> Jun 05 15:59:59.40: [ 255]: RECV FAX: begin
> Jun 05 16:00:01.33: [ 255]: --> [29:+FTSI: " +31 10 412XXXX"]
> Jun 05 16:00:01.33: [ 255]: REMOTE TSI "+31 10 412XXXX"
> Jun 05 16:00:01.44: [ 255]: --> [22:+FDCS: 0,3,0,2,1,0,0,0]
> Jun 05 16:00:01.44: [ 255]: REMOTE wants 9600 bit/s
> Jun 05 16:00:01.44: [ 255]: REMOTE wants page width 1728 pixels in 215 mm
> Jun 05 16:00:01.44: [ 255]: REMOTE wants unlimited page length
> Jun 05 16:00:01.44: [ 255]: REMOTE wants 3.85 line/mm
> Jun 05 16:00:01.44: [ 255]: REMOTE wants 2-D MR
> Jun 05 16:00:03.41: [ 255]: --> [2:OK]
> Jun 05 16:00:03.41: [ 255]: <-- [7:AT+FDR\r]
> Jun 05 16:00:05.07: [ 255]: --> [5:+FCFR]
> Jun 05 16:00:05.07: [ 255]: --> [22:+FDCS: 0,3,0,2,1,0,0,0]
> Jun 05 16:00:05.07: [ 255]: REMOTE wants 9600 bit/s
> Jun 05 16:00:05.07: [ 255]: REMOTE wants page width 1728 pixels in 215 mm
> Jun 05 16:00:05.07: [ 255]: REMOTE wants unlimited page length
> Jun 05 16:00:05.07: [ 255]: REMOTE wants 3.85 line/mm
> Jun 05 16:00:05.07: [ 255]: REMOTE wants 2-D MR
> Jun 05 16:00:05.77: [ 255]: --> [7:CONNECT]
> Jun 05 16:00:05.77: [ 255]: RECV: begin page
> Jun 05 16:00:05.77: [ 255]: RECV: send trigger 022
> Jun 05 16:00:32.15: [ 255]: RECV: 31421 bytes of data, 1168 total lines
> Jun 05 16:00:32.15: [ 255]: --> [8:+FPTS: 1]
> Jun 05 16:00:33.37: [ 255]: --> [7:+FET: 2]
> Jun 05 16:00:33.37: [ 255]: RECV recv EOP (no more pages or documents)
> Jun 05 16:00:33.37: [ 255]: --> [2:OK]
> Jun 05 16:00:33.37: [ 255]: RECV send MCF (message confirmation)
> Jun 05 16:00:33.37: [ 255]: RECV FAX (00000380): from +31 10 412XXXX,
> page 1 in 0:30, INF, 3.85 line/mm, 2-D MR
> Jun 05 16:00:33.37: [ 255]: RECV FAX (00000380): recvq/fax00067.tif from +31 10 4124139, route to <unspecified>, 1 pages in 0:34
> Jun 05 16:00:33.41: [ 255]: <-- [7:AT+FDR\r]
> Jun 05 16:00:37.28: [ 255]: --> [8:+FHNG: 0]
> Jun 05 16:00:37.28: [ 255]: REMOTE HANGUP: Normal and proper end of connection (code 0)
> Jun 05 16:00:37.28: [ 255]: RECV FAX: bin/faxrcvd "recvq/fax00067.tif" "ttyS1" "00000380" ""
>
> ==================================================================
>
> The resulting tif file is 8 bytes long:
>
> 0000 49 49 2a 00 00 00 00 00 II*.....
> 0008
Maybe there is no space left on the disk? Check /var/log/daemon.log for
something like "RECV: recvq/fax00067.tif: write error".
> So there is no error but also no resulting file. I've seen that in the
> past with version v4.0pl2 as well.
There *is* an error but Hylafax just reports it and don't remove the broken
file:
[from CopyQuality.c++]
/*
* Write a strip of raw data to the receive file.
*/
void
FaxModem::flushRawData(TIFF* tif, tstrip_t strip, u_char* buf, u_int cc)
{
recvTrace("%u bytes of data, %lu total lines", cc, recvEOLCount);
if (TIFFWriteRawStrip(tif, strip, buf, cc) == -1)
serverTrace("RECV: %s: write error", TIFFFileName(tif));
}
[...]
Maybe I'll fix this someday...
Hope to hear from you soon,
Dmitry
____________________ HylaFAX(tm) Users Mailing List _______________________
To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null