Re: [hylafax-users] Junk in logfile since upgrading to 4.3.3

["Ulf Zimmermann" <ulf@xxxxxxxxxxxxxx>]

> -----Original Message-----
> From: Lee Howard [mailto:faxguy@xxxxxxxxxxxxxxxx]
> Sent: Thursday, May 17, 2007 09:13
> To: Ulf Zimmermann
> Cc: hylafax-users@xxxxxxxxxxx
> Subject: Re: [hylafax-users] Junk in logfile since upgrading to 4.3.3
> 
> Aidan Van Dyk wrote:
> 
> >* Ulf Zimmermann <ulf@xxxxxxxxxxxxxx> [070516 17:47]:
> >
> >
> >>>May 16 14:41:32.37: [ 5278]: --> [22:+FDCS: 1,B,0,2,0,2,0,0]
> >>>May 16 14:41:32.37: [ 5278]: REMOTE wants 28800 bit/s
> >>>May 16 14:41:32.37: [ 5278]: REMOTE wants A4 page width (215 mm)
> >>>May 16 14:41:32.37: [ 5278]: REMOTE wants unlimited page length
> >>>May 16 14:41:32.37: [ 5278]: REMOTE wants 7.7 line/mm
> >>>May 16 14:41:32.37: [ 5278]: REMOTE wants 1-D MH
> >>>May 16 14:41:32.37: [ 5278]: REMOTE wants T.30 Annex C, half duplex
ECM
> >>>May 16 14:41:32.37: [ 5278]: --> [7:CONNECT]
> >>>May 16 14:41:32.37: [ 5278]: RECV: begin page
> >>>May 16 14:41:32.37: [ 5278]: RECV: send trigger 021
> >>>May 16 14:41:32.37: [ 5278]: Copy quality checking performed by
host
> >>>May 16 14:41:39.67: [ 5278]: RECV: 32728 bytes of data, 1103 total
> lines
> >>>May 16 14:41:45.80: [ 5278]: RECV: 32766 bytes of data, 1831 total
> lines
> >>>May 16 14:42:47.07: [ 5278]: RECV: Missing EOL after 5 seconds
> >>>
> >>>
> >
> >faxgetty believed it had an EOF raised as it was receiving the Phase
C
> >data.  This made it hangup/giveup.   But meanwhile, the modem (Eicon
> >DIVA I'm assuming) was continuing to send us more image data.
> >
> >
> >
> >>>May 16 14:42:47.07: [ 5278]: REMOTE HANGUP: Missing EOL after 5
seconds
> (section 3.2/T.4) (code 91)
> >>>May 16 14:42:47.07: [ 5278]: RECV FAX (000005257):
> recvq/fax000002589.tif from XXXXXXXXXXXX, route to <unspecified>, 0
pages
> in 1:15
> >>>May 16 14:42:47.07: [ 5278]: RECV FAX: Missing EOL after 5 seconds
> (section 3.2/T.4)
> >>>May 16 14:42:47.07: [ 5278]: <-- [6:AT+FK\r]
> >>>May 16 14:42:54.47: [ 5278]: --> [130:<SNIP BINARY DATA>]
> >>>May 16 14:42:54.47: [ 5278]: --> [49:<SNIP BINARY DATA>]
> >>>May 16 14:42:54.47: [ 5278]: --> [619:<SNIP BINARY DATA>]
> >>>
> 
> It's likely that this is either a very rare case, or that this was
> introduced by some recent change to your Eicon drivers/firmware.  I
> doubt that it has anything to do with your 4.3.3 upgrade.
> 
> Note that 60 seconds transpire between the point where the last chunk
of
> data is received and where either HylaFAX finally gives up or the
modem
> actually sends EOF.  Notice that the modem does not honor the abort
> request (AT+FK).  Note that yet another 7 seconds transpire before the
> modem starts redelivering data.
> 
> So, basically the modem was probably hung in a long-running ECM
> procedure... one that ran 67 seconds for a block to get through!
Either
> HylaFAX gives up (60 seconds with nothing from the modem is a long
time
> - and it takes a lot of trust in the modem to ignore that and simply
> wait on it eternally) or the modem actually did send EOF by error.
> 
> Lee.

It is random senders, I need to go back and see how many times I have
gotten it. This is on the server we send and receive up to about 1,500
pages a day, I think I have seen one every other day, so not that often.
Yes, this is Eicon DIVA.

Ulf.


____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*