Re: [hylafax-users] is there any version of hylafax that won't fail with corrupted pdf?

[Aidan Van Dyk <aidan@xxxxxxxx>]

* francesco messineo <francesco.messineo@xxxxxxxxx> [070605 08:22]:
> Hello all,
> 
> I'm running a quite large installation of hylafax. Our server sends at
> very least 3000 fax jobs per day.
> The main problem here is that we have sometimes fax jobs with pdf
> files that have problems and they fail the conversion when assigned to
> faxsend processes.

> When I first found this problem I was running hylafax 4.3.3 and the
> modems weren't released when a document failed, this, when a batch
> with more than a document was assigned to a modem lead to different
> faxsends beeing assigned to the same modem. A partial solution was to
> add MaxBatchJobs:           0 in the main config file. This solution,
> not only slows down our fax delivery (we have several document with
> same destination often), but in practice doesn't work because other
> documents waiting in the queue for failing (with document conversion
> error) destinations never are released and  we need to restart hylafax
> very often. This hasn't been solved in the 4.3.4 release.

Are you sure?  We definitely fixed a bug that *looks* like what you're
reporting.  When jobs were "batched" and a conversion of one document
failed, the modem was falsely released and caused multiple faxsends to
be running at the same time:

http://git.hylafax.org/?p=HylaFAX;a=commitdiff;h=f0fdee890ce2b42655643b06bf32dc891ea63926
  commit f0fdee890ce2b42655643b06bf32dc891ea63926
  Author: Aidan Van Dyk <aidan@xxxxxxxx>
  Date:   Tue May 8 19:24:00 2007 +0000

    faxq: Don't release modem from the middle of a batch

    Fix a bug where the modem is "released" in the middle of the batch.  If the
    preparation failes, and there are other jobs in the batch (before or after), we
    need to take care that delayJob/deleteJob don't release the modem, because we
    need it for the rest of the jobs.


> I also tried to download a compile a 4.4 CVS snapshot (about one month
> ago) but this was working even worse since faxq stopped to deliver ANY
> fax when  encountering conversion errors.
> Now the question is simple: is there available any hylafax version
> that would allow correct fax sending when encountering random document
> conversions?

And CVS for 4.4 was fixed shortly afterwards:

http://git.hylafax.org/?p=HylaFAX;a=commitdiff;h=e71be606abce1354e85505b78c0561aa0694f4d4
  commit e71be606abce1354e85505b78c0561aa0694f4d4
  Author: Aidan Van Dyk <aidan@xxxxxxxx>
  Date:   Mon May 28 18:17:41 2007 +0000

    faxq: prepareDone() should clear job modem when jobs fail

    Because modems are freed when the the batch done, we need to set
    remove it from the job if the job is dead/requeued/deleted.


a.



-- 
Aidan Van Dyk                                             aidan@xxxxxxxx
Senior Software Developer                          +1 215 825-8700 x8103
iFAX Solutions, Inc.                                http://www.ifax.com/

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