Re: [hylafax-users] modem (or faxgetty?) hangs "receiving from ..."

[Patrick Fromberg <patrick.fromberg@xxxxxxxxx>]

Lee Howard wrote:
> On 2003.12.05 12:57 Aidan Van Dyk wrote:
>
> > So, it definately seems like it's stuck in a system call.  It seems
> > it's
> > not actually "doing" anything (CPU wise), correct?)  The output of
> > strace should be able to tell us what system call it's doing.
>
>
>  From my earlier analysis, I believe that faxgetty is looping in 
> ModemServer::getModemLine() for the modem to respond with +FPS.  The 
> modem never does respond with +FPS, however (so a Class 2 firmware bug 
> is triggering a HylaFAX problem here).  ModemPageDoneTimeout is supposed 
> to control how long faxgetty waits in getModemLine(), but 
> ModemPageDoneTimeout doesn't seem to be working - so we loop forever 
> waiting for +FPS.

I saw this on a class 1 modem too, but I am not absoultely sure, if it 
was exactly the same.

> ModemPageDoneTimeout is, by default, exceptionally large, 180000.  I 

I did this, I patched libfaxserver.so.4.1.7 with the debug patch and
I will do a stack trace on faxgetty process when problem arises.

But what does the ModemPageDoneTimeout solve? The modem will go wrong 
for one hour and then work again? Thats ok, if faxes are rejected in the 
mean time, or better, if the modem does not even answer meanwhile.

BTHW I have not set ModemPageStartTimeout. Shall I do that too?

> don't know if that has some factor on the 
> (perhaps because it exceeds a 
> 16-bit integer size), so that's why I've asked them to test with 
> ModemPageDoneTimeout set to 60000.
>
> Lee.


--
Patrick Fromberg
bytes & more Softwareentwicklung GmbH
Ligsalzstraße 31
80339 München
Tel.:  (089) 500 777 - 71
Fax : (089) 500 777 - 50

____________________ 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@xxxxxxxxxxxx*