HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
Re: [hylafax-users] Problems with blocked faxes
After another batch of faxes this morning, I found roughly ten faxes in
the blocked state. I checked the syslog and it looks like HylaFax tried
to requeue the faxes a couple of times, but eventually gave up.
I restarted the server and one fax started sending while the rest
blocked again. After the first one finished sending, a second one was
also resent, but the rest are still in the blocked state and have not
been retried since.
Blocked faxes are suppose to be retried periodically, until they're
sent, right?
On a side note, I have MaxConcurrentJobs: 1, so why is this even
happening in the first place?
On Tue, 2007-11-13 at 08:59 -0600, Justin Hendrickson wrote:
> Every night I have a large stack of faxes being sent. Frequently, some
> of those faxes are going to the same number, so some get blocked due to
> concurrent calls. After whatever delay HylaFax assigns to a blocked
> call, almost all of the blocked faxes are eventually sent out
> successfully. Here's an example of one such faxes syslog entries:
>
>
> Nov 12 15:58:14 localhost FaxQueuer[5186]: SUBMIT JOB 27316
> Nov 12 15:58:16 localhost HylaFAX[18350]: Filesystem has SysV-style file
> creation semantics.
> Nov 12 15:58:16 localhost HylaFAX[18350]: What we have here is a PDF
> file
> Nov 12 16:25:12 localhost FaxQueuer[5186]:
> NOTIFY: /var/www/bravoforms/scripts/hylafax_notify.php "sendq/q27316"
> "blocked" ""
> Nov 12 16:29:34 localhost FaxSend[20149]: SEND FAX: JOB 27316 DEST
> 12166428771 COMMID 000030968 DEVICE '/dev/ttyS0' FROM 'IPTCI
> <IPTCI@xxxxxxxxxxxxx>' USER lp
> Nov 12 16:30:07 localhost FaxSend[20149]: SEND FAX: JOB 27316 SENT in
> 0:18
> Nov 12 16:31:13 localhost FaxSend[20149]: SEND FAX: JOB 27316 SENT in
> 1:05
> Nov 12 16:31:16 localhost FaxQueuer[5186]:
> NOTIFY: /var/www/bravoforms/scripts/hylafax_notify.php "doneq/q27316"
> "done" "1:54"
>
>
> Unfortunately, there's always a couple of stubborn ones that never seem
> to become unblocked. Here's an example of one such blocked faxes syslog
> entries:
>
>
> Nov 12 16:00:28 localhost FaxQueuer[5186]: SUBMIT JOB 27340
> Nov 12 16:00:29 localhost HylaFAX[18753]: Filesystem has SysV-style file
> creation semantics.
> Nov 12 16:00:29 localhost HylaFAX[18753]: What we have here is a PDF
> file
> Nov 12 16:25:12 localhost FaxQueuer[5186]:
> NOTIFY: /var/www/bravoforms/scripts/hylafax_notify.php "sendq/q27340"
> "blocked" ""
> Nov 13 05:00:17 localhost FaxQueuer[29723]:
> NOTIFY: /var/www/bravoforms/scripts/hylafax_notify.php "sendq/q27340"
> "blocked" ""
>
>
> Note: cron restarts the HylaFax server at 5AM every day.
>
> As you can see, the fax blocked at 4:25PM and never sent until the
> HylaFax server was restarted.
>
> Does anyone know why this would happen?
>
> I'm running HylaFax 4.3.0. Here's my config file for reference:
>
>
> LogFacility: daemon
> CountryCode: 1
> AreaCode: 952
> LongDistancePrefix: 1
> InternationalPrefix: 011
> DialStringRules: etc/dialrules
> ServerTracing: 1
> NotifyCmd: "/var/www/bravoforms/scripts/hylafax_notify.php"
> MaxBatchJobs: 1
> MaxConcurrentJobs: 1
>
>
> ____________________ 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*
>
____________________ 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*