[hylafax-users] Unable to open scheduler FIFO: No such device or address.
Erik Morton
sends approximately 5,000 faxes per week. Submitted a job results in
the following error: 460 Failed to submit job 163363: Unable to open
scheduler FIFO: No such device or address. I'm not sure the version
number of Hylafax but it was new in the summer of 06 (sorry about that!)
I have the following FIFO in /var/spool/hylafax
prw------- 1 uucp uucp 0 Feb 28 00:49 FIFO
prw------- 1 uucp uucp 0 Feb 28 00:48 FIFO.ttyps00
prw------- 1 uucp uucp 0 Feb 28 00:42 FIFO.ttyps01
prw------- 1 uucp uucp 0 Feb 28 00:32 FIFO.ttyps02
prw------- 1 uucp uucp 0 Feb 28 00:30 FIFO.ttyps03
prw------- 1 uucp uucp 0 Feb 28 00:38 FIFO.ttyps04
prw------- 1 uucp uucp 0 Feb 28 00:36 FIFO.ttyps05
prw------- 1 uucp uucp 0 Feb 28 00:35 FIFO.ttyps06
prw------- 1 uucp uucp 0 Feb 28 00:41 FIFO.ttyps07
prw------- 1 uucp uucp 0 Jun 7 2007 FIFO.ttyps15
We have a digiport server that is in front of 7 Fax Modems, so those
devices in /var/spool are "virtual". I really have no idea how to
troubleshoot this issue and would love some help. The same thing
happened yesterday and I had to restart the port server, each modem,
and hylafax (twice) to get faxes going again. The only difference was
that yesterday sendfax would hang forever, and now it returns the error.
Thank you in advance for any help! We are running on RedHat Enterprise
4.
Erik
____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-us...@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail sa...@ifax.com.*
Aidan Van Dyk
> I have a Hylafax installation in a send only environment that usually
> sends approximately 5,000 faxes per week. Submitted a job results in
> the following error: 460 Failed to submit job 163363: Unable to open
> scheduler FIFO: No such device or address. I'm not sure the version
> number of Hylafax but it was new in the summer of 06 (sorry about that!)
That error comes when hfaxd cannot open the faxq FIFO.
Is faxq running?
--
Aidan Van Dyk ai...@ifax.com
Senior Software Developer +1 215 825-8700 x8103
iFAX Solutions, Inc. http://www.ifax.com/
Aidan Van Dyk
> Thank you. Faxq was not running.
>
> % sudo /etc/init.d/hylafax stop
> Shutting down HylaFAX queue manager (faxq): [FAILED]
> Shutting down HylaFAX server (hfaxd): [ OK ]
>
>
> I have restarted it and was able to fax. What first step should I take
> to trouble shoot why faxq "crashed"?
Sure, if you have decent logginng we may be able to see what happend.
Look for all the 'FaxQueuer' messages in syslog.
a.
--
Aidan Van Dyk ai...@ifax.com
Senior Software Developer +1 215 825-8700 x8103
iFAX Solutions, Inc. http://www.ifax.com/
Aidan Van Dyk
> Feb 28 02:01:03 mail FaxQueuer[18801]: Assertion failed "QLink::remove: item not on a list", file "QLink.c++" line 53.
That was the bug, but this is your problem:
> Feb 28 09:54:54 mail FaxQueuer[17177]: HylaFAX (tm) Version 4.3.0
If you're sticking with HylaFAX 4.3, you should upgrade to 4.3.7, which
has all known bugs fixed. I believe this particular bug was fixed in
July 2006 for 4.3.1.
Erik Morton
% sudo /etc/init.d/hylafax stop
Shutting down HylaFAX queue manager (faxq): [FAILED]
Shutting down HylaFAX server (hfaxd): [ OK ]
I have restarted it and was able to fax. What first step should I take
to trouble shoot why faxq "crashed"?
Thanks!
Erik
Erik Morton
faxes.
Then:
Feb 28 00:49:34 mail FaxQueuer[18801]: JOB 155343 (active dest
+15183153766118 pri 116 tts 0:00 killtime 1:01:40): CMD DONE: exit
status 0
Feb 28 00:49:34 mail FaxQueuer[18801]: JOB 155343 (sleeping dest
+15183153766118 pri 115 tts 0:00 killtime 1:01:40): SEND INCOMPLETE:
requeue for 5:00; No carrier detected
Feb 28 00:54:34 mail FaxQueuer[18801]: JOB 155343 (sleeping dest
+15183153766118 pri 115 tts 0:00 killtime 56:40): CMD DONE: exit
status 0
Feb 28 00:54:35 mail FaxQueuer[18801]: JOB 155343: REJECT: Too many
attempts to dial: 12, max 12
Feb 28 00:54:35 mail FaxQueuer[18801]: NOTIFY: bin/notify "doneq/
q155343" "rejected" ""
Feb 28 00:54:36 mail FaxQueuer[18801]: NOTIFY exit status: 0 (15170)
Feb 28 02:01:03 mail FaxQueuer[18801]: JOB 155362 (blocked dest
+15188853752 pri 127 tts 0:00 killtime 0:00): KILL TIME EXPIRED
Feb 28 02:01:03 mail FaxQueuer[18801]: Assertion failed
"QLink::remove: item not on a list", file "QLink.c++" line 53.
Feb 28 09:54:54 mail FaxQueuer[17177]: HylaFAX (tm) Version 4.3.0
Feb 28 09:54:54 mail FaxQueuer[17177]: Copyright (c) 1990-1996 Sam
Leffler
Feb 28 09:54:54 mail FaxQueuer[17177]: Copyright (c) 1991-1996 Silicon
Graphics, Inc.
Feb 28 09:54:54 mail FaxQueuer[17177]: JOB 155401 (failed dest
+15182122102591 pri 127 tts 0:00 killtime 0:00): KILL TIME EXPIRED
Feb 28 09:54:54 mail FaxQueuer[17177]: NOTIFY: bin/notify "doneq/
q155401" "timedout" ""
etc.....
I restarted all of Hylafax at 9:54
I'm getting a lot of kill time expired, but that is to be expected as
the queue has been full for several hours and I think our timeout is 3
hours.
Thanks again.
Erik
Erik Morton
in the archive or elsewhere on upgrading? Or is it straightforward?
Also, do you know of any bandaids that I could apply to prevent this
(they were running strong for 10 months at approximately 3,000 faxes/
week with no issues) before I am able to upgrade?
Erik
Aidan Van Dyk
> Excellent. Thank you very much. Are there any good documents available
> in the archive or elsewhere on upgrading? Or is it straightforward?
Upgrading to the latest bug-fix release in 4.3 *should now* be a straight
forward affair. That said, the 4.3.0/4.3.1 release happened before
HylaFAX.org had set on a more straight forward bug-fix release style,
and one large "feature" was added to 4.3.1 that could affect your
upgrade, namely templates for faxrcvd/notify/pollrcvd. So I would watch
out if you're doing anything "special" with faxrcvd/notify, but other
than that, it should be painless.
But since 4.3.1, any of big-fix version of HylaFAX (n.n.X) is intended
to be a straight-forward bug-fix only upgrade.
So if you're using 4.3, should should upgrade to the latest 4.3.X with
no pain (except the just mentioned template change that came in 4.3.1).
And if you're using 4.4, you should always upgrade to the latest 4.4.X
Any new features/changes only go into CVS, and new versions (HylaFAX
A.B) are released, after which any A.B.X will only be bugfixes, while
new features/changes keep going in to head, which is destined to
eventually be HylafAX C.D (where [C,D] > [A,B])
> Also, do you know of any bandaids that I could apply to prevent this
> (they were running strong for 10 months at approximately 3,000 faxes/
> week with no issues) before I am able to upgrade?
If memory servers right, it only happens on "timed out" jobs, so if you
set the job killtime high enough, it shouldn't be hit.
Erik Morton
It keeps crashing. When I restart Hylafax I get a lot of defunct
faxq's and what appears to be two faxq processes running. Any idea
what is going on and how I can recover? Thanks in advance.
$ps aux|grep faxq
uucp 18479 0.0 0.0 7424 1732 ? Ss 13:34 0:00 /usr/
sbin/faxq
uucp 18481 0.0 0.0 0 0 ? Z 13:34 0:00 [faxq]
<defunct>
uucp 18483 0.0 0.0 0 0 ? Z 13:34 0:00 [faxq]
<defunct>
uucp 18497 0.0 0.0 0 0 ? Z 13:34 0:00 [faxq]
<defunct>
uucp 18906 0.0 0.0 0 0 ? Z 13:34 0:00 [faxq]
<defunct>
uucp 18916 0.0 0.0 0 0 ? Z 13:34 0:00 [faxq]
<defunct>
uucp 19198 0.0 0.0 0 0 ? Z 13:34 0:00 [faxq]
<defunct>
uucp 19203 0.0 0.0 0 0 ? Z 13:34 0:00 [faxq]
<defunct>
uucp 19214 0.0 0.0 0 0 ? Z 13:34 0:00 [faxq]
<defunct>
uucp 19236 0.0 0.0 0 0 ? Z 13:34 0:00 [faxq]
<defunct>
uucp 19269 0.0 0.0 0 0 ? Z 13:34 0:00 [faxq]
<defunct>
uucp 19284 0.0 0.0 0 0 ? Z 13:34 0:00 [faxq]
<defunct>
uucp 19326 0.0 0.0 0 0 ? Z 13:34 0:00 [faxq]
<defunct>
uucp 19360 0.0 0.0 0 0 ? Z 13:34 0:00 [faxq]
<defunct>
uucp 19472 0.0 0.0 0 0 ? Z 13:34 0:00 [faxq]
<defunct>
uucp 19613 0.0 0.0 0 0 ? Z 13:34 0:00 [faxq]
<defunct>
uucp 19635 0.0 0.0 0 0 ? Z 13:34 0:00 [faxq]
<defunct>
uucp 19742 0.0 0.0 0 0 ? Z 13:34 0:00 [faxq]
<defunct>
uucp 21009 0.0 0.0 8256 1724 ? Ss 13:39 0:00 /usr/
sbin/faxq
uucp 21010 0.0 0.0 0 0 ? Z 13:39 0:00 [faxq]
<defunct>
uucp 21013 0.0 0.0 0 0 ? Z 13:39 0:00 [faxq]
<defunct>
uucp 21016 0.0 0.0 0 0 ? Z 13:39 0:00 [faxq]
<defunct>
uucp 21191 0.0 0.0 0 0 ? Z 13:39 0:00 [faxq]
<defunct>
uucp 21285 0.0 0.0 0 0 ? Z 13:39 0:00 [faxq]
<defunct>
uucp 21695 0.0 0.0 0 0 ? Z 13:39 0:00 [faxq]
<defunct>
uucp 21864 0.0 0.0 0 0 ? Z 13:39 0:00 [faxq]
<defunct>
uucp 21912 0.0 0.0 0 0 ? Z 13:39 0:00 [faxq]
<defunct>
uucp 21987 0.0 0.0 0 0 ? Z 13:39 0:00 [faxq]
<defunct>
uucp 22008 0.0 0.0 0 0 ? Z 13:39 0:00 [faxq]
<defunct>
uucp 22033 0.0 0.0 0 0 ? Z 13:39 0:00 [faxq]
<defunct>
uucp 22064 0.0 0.0 0 0 ? Z 13:39 0:00 [faxq]
<defunct>
uucp 22107 0.0 0.0 0 0 ? Z 13:39 0:00 [faxq]
<defunct>
uucp 22109 0.0 0.0 0 0 ? Z 13:39 0:00 [faxq]
<defunct>
uucp 22165 0.0 0.0 0 0 ? Z 13:39 0:00 [faxq]
<defunct>