Re: [hylafax-users] hylafax loses modems

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Jitse,

HylaFAX faxq (via the dispatcher) is supposed to initializes the modem 
before calling on faxsend.  The status will change to "Waiting for modem 
to come ready" when faxq is preparing the image file if you are running 
faxgetty because faxq sets a lockfile for the modem which faxgetty 
detects, and so faxgetty changes the status.  faxq then will change it to 
"Initializing" after the job preparation is done and when faxq is ready to 
invoke faxsend.

If there is some error with faxq initializing the modem then it *should* 
(this is just what I'm thinking, not what the code says) return the job to 
the queue and then move on to the next job.  These jobs that get returned 
to the queue should get attempted at the next pass, sometime later.

If you're seeing jobs get "stuck" to one modem permanently then either the 
job is being submitted with a specified modem (rather than a group of 
modems) or there is a problem with faxq.

I must admit, though, that if you're having this kind of error commonly 
with as many as half of your outbound modem pool, then you *could* try to 
improve HylaFAX fax's resiliance here, but honestly, the *real* problem is 
that your modems are not functioning right.

Lee.


On Sun, 8 May 2005, Jitse Groen wrote:

> Hello everybody,
> 
> Since we switched to USB modems we are experiencing strange problems with 
> modems getting 'lost'. We send out large numbers (tens of thousands a 
> month) of faxes. When the servers and hylafax start, everything is 
> alright, but after a while (varying from half an hour to several days) 
> some faxjobs seem to 'wait'. The fax does not get sent nor is assigned to 
> a modem according to faxstat. When looking at the processes (ps) however 
> it is clear that it IS assigned to a modem (for example ttySHSF0). 
> 
> It seems the following command
> faxsend -m ttySHSF0 sendq/q3846
> is not executed properly. In faxstat the job simply waits and ttySHSF0-
> status is either 'Initializing' or 'Waiting for modem to come ready'. 
> 
> The problem is that hylafax does not realise that there is a problem and 
> just keeps on sending jobs to that modem resulting in large numbers of 
> faxes being stalled. We also had for instance 4 out of 8 modems 'waiting' 
> causing great problems. We have several faxservers, all having the same 
> problem.
> 
> Any ideas?
> 
> Thanks,
> 
> Jitse
> 
> 
> 
> ____________________ 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 expensive HylaFAX(tm) support, mail sales@xxxxxxxxx*
> 


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