[hylafax-users] faxq dying and scheduling problems

[james@occinc.com]

i am running hylafax rev 4.1rc2 on Solaris 2.6.  i have a bank of 9
USR 56k modems attached to a Central Data Systems SCSI terminal
server.  i am running a send-only environment using faxmodem, not
faxgetty.  i have automated fax submission with scripts, using the
command:

    sendfax -nwNt1 -T1 -hportno@localhost -d##### filename

i have a large volume of tickets to transmit, so all the modems have
jobs submitted to them continually for long periods of time.  what i
observe with the faxstat command over a period of 60 to 90 minutes is
that out of the bank of 9 modems, only 5 to 7 of them are ever
actively sending a fax while 2 to 4 of them are always "waiting for
modem to come ready".  eventually, faxstat will report that "faxq is
not running", at which point of course, faxes stop going out
completely.  what i have observed in the log file are many of these
messages:

Jun 26 14:52:40 saturn FaxQueuer[21480]: Lost trigger for client/28339
Jun 26 14:57:26 saturn FaxQueuer[21480]: Lost trigger for client/1020
Jun 26 14:57:26 saturn FaxQueuer[21480]: Lost trigger for client/28339
Jun 26 15:06:35 saturn FaxQueuer[21480]: Lost trigger for client/14966
Jun 26 15:06:35 saturn FaxQueuer[21480]: Lost trigger for client/1020
Jun 26 15:06:35 saturn FaxQueuer[21480]: Lost trigger for client/28339

and these messages, which seems to immediately preceed faxq dying:

Jun 26 15:58:42 saturn FaxQueuer[21480]: TRIGGER: syntax error, non-hex event mask in "J<377>0010"
Jun 26 15:58:42 saturn FaxQueuer[21480]: Trigger 66 deleted with 1 references

any help resovling this problem is appreciated, thank you.

--
James Myers






____________________ HylaFAX(tm) Users Mailing List _______________________
 To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null