HylaFAX The world's most advanced open source fax server |
Hey all, CentOS release 5.3 (Final) hylafax-enterprise-4.1.4-rhel5 ( I realize it's enterprise but figured that this is an issue most likely not related to it ) Current Kill time - now +6 hour Recently I have noticed that we are getting A LOT of KILL TIME EXPIRED errors in /var/log/messages. We send out over 400 pages a day during the week with most of them happening kind of at the same time. We have a job that will query a database to see what it needs to send out and then will send the faxes. Part of me thinks that faxq is having issues and dies so I set up a script to run every night at 1am to stop hylafax, 'killall faxq', then start hylafax in hopes that this resolves the issue. I think that this is the issue because when I am informed that "faxes don't seem to be going out", I will look at 'faxstat -s' and see hundreds of faxes in the queue prompting me to stop hylafax, kill faxq and then restart it. I have a Brooktrout card with 12 channels dedicated to outbound faxing so I doubt I am sending too many faxes at once. Our FaxNotify script has been edited so that it uses custom in-house scripts to change the status of the fax in our database. I added a line for time outs, but does a timedout fax even go through etc/FaxNotify? echo "$failedline" | grep -i "timedout" > /dev/null 2>&1If hylafax attempts to send a fax and it fails, does it go to the end of the queue or does it hold up the batch until it's killtime has expired? Do you guys have any suggestions on what I can do to resolve the KILL TIME EXPIRED errors? I have a Nagios server and am in the process of setting up the queue monitoring so that I can monitor the queue for when it gets out of hand during these times. Thanks, Adam
|