Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Hylafax not sending (faxq hanging?)
I _had_ this working, once, however it seems to have mysteriously broken,
and I am going nuts trying to find out why.
Attempting to send a fax hangs forever (that is, sendfax works ok, but
the job just sits on the server with a 'R' status) furthermore faxrm hangs
when trying to remove the job.
looking at the logs, and running 'top', faxq seems to be hanging. It forks
a copy of itself, and the forked proc sits there chewing massive amts of
cpu till I hit it w/ a kill -9. This happens, apparently just after it
converts the documents for transmission.
System info:
Debian 'potato' i386 system kernel 2.2.12
hylafax 4.0pl2 (installed from deb package: hylafax-server 4.0.2-12)
modem: usr sportster 56k
here's the relavent log bits:
Feb 2 18:06:30 sapphire FaxQueuer[8193]: servertracing = 0xFFFFF (line 7)
Feb 2 18:06:30 sapphire FaxQueuer[8193]: HylaFAX (tm) Version 4.0pl2
Feb 2 18:06:30 sapphire FaxQueuer[8193]: Copyright (c) 1990-1996 Sam Leffler
Feb 2 18:06:30 sapphire FaxQueuer[8193]: Copyright (c) 1991-1996 Silicon
Graphics, Inc.
Feb 2 18:06:30 sapphire HylaFAX[8195]: HylaFAX INET Protocol Server: restarted.
Feb 2 18:06:30 sapphire HylaFAX[8195]: HylaFAX Old Protocol Server:
restarted.
Feb 2 18:06:30 sapphire HylaFAX[8195]: HylaFAX SNPP Protocol Server:
restarted.
[ Note: I did a 'killall faxgetty' here for various *mumble* reasons ]
Feb 2 18:06:54 sapphire FaxGetty[4640]: CAUGHT SIGNAL 15
Feb 2 18:06:54 sapphire FaxGetty[4640]: CLOSE /dev/ttyS1
Feb 2 18:06:54 sapphire FaxQueuer[8193]: FIFO RECV "+ttyS1:D"
Feb 2 18:06:54 sapphire FaxQueuer[8193]: MODEM ttyS1: DOWN
Feb 2 18:06:55 sapphire FaxQueuer[8193]: FIFO RECV
"+ttyS1:N+1.541.488.6915"
Feb 2 18:06:55 sapphire FaxQueuer[8193]: MODEM ttyS1: NUMBER
+1.541.488.6915
Feb 2 18:06:55 sapphire FaxGetty[8197]: OPEN /dev/ttyS1
Feb 2 18:07:02 sapphire FaxGetty[8197]: MODEM U.S. ROBOTICS 56K FAX /
Feb 2 18:07:03 sapphire FaxQueuer[8193]: FIFO RECV "+ttyS1:RP3fd5e7ff:ff"
[ Here's the attempt to send a fax ]
Feb 2 18:07:58 sapphire FaxQueuer[8193]: FIFO RECV "Sclient/8201:16"
Feb 2 18:07:58 sapphire FaxQueuer[8193]: SUBMIT JOB 16
Feb 2 18:07:58 sapphire FaxQueuer[8193]: JOB 16 (suspended dest pri 127
tts 0:00 killtime 2:59:00): CREATE
Feb 2 18:07:58 sapphire FaxQueuer[8193]: Apply CanonicalNumber rules to
"4886925"
Feb 2 18:07:58 sapphire FaxQueuer[8193]: --> match rule "^[^+]", result now "+1
5414886925"
Feb 2 18:07:58 sapphire FaxQueuer[8193]: --> return result "+15414886925"
Feb 2 18:07:58 sapphire FaxQueuer[8193]: JOB 16 (ready dest +15414886925
pri 127 tts 0:00 killtime 2:59:00): READY
Feb 2 18:07:58 sapphire FaxQueuer[8193]: FIFO SEND client/8201 msg "S*"
Feb 2 18:07:58 sapphire FaxQueuer[8193]: JOB 16 (ready dest +15414886925
pri 127 tts 0:00 killtime 2:59:00): PROCESS
Feb 2 18:07:58 sapphire FaxQueuer[8193]: JOB 16 (active dest +15414886925
pri 127 tts 0:00 killtime 2:59:00): ACTIVE
Feb 2 18:07:58 sapphire FaxQueuer[8193]: JOB 16 (active dest +15414886925
pri 127 tts 0:00 killtime 2:59:00): PREPARE START
Feb 2 18:07:58 sapphire FaxQueuer[8203]: JOB 16 (active dest +15414886925
pri 127 tts 0:00 killtime 2:59:00): CONVERT DOCUMENT: bin/ps2fax -o
docq/doc16.cover;30 -r 98 -w 1728 -l 280 -m 4294967295 -1
docq/doc16.cover
Feb 2 18:08:00 sapphire FaxQueuer[8203]: JOB 16 (active dest +15414886925
pri 127 tts 0:00 killtime 2:58:58): CONVERT DOCUMENT: bin/ps2fax -o
docq/doc23.ps;30-r 98 -w 1728 -l 280 -m 4294967295 -1 docq/doc23.ps.16
[Here is where it hangs. proccess 8203 is now sitting there
chewing up 95% of my CPU and will do so as long as I let it.
I try 'faxrm 16' here. It hangs.]
Feb 2 18:14:51 sapphire FaxQueuer[8193]: FIFO RECV "Kclient/8223:16"
Feb 2 18:14:51 sapphire FaxQueuer[8193]: KILL JOB 16
Feb 2 18:14:51 sapphire FaxQueuer[8203]: CAUGHT SIGNAL 15, ABORT JOB
PREPARATION
[I have to do 'kill -9 8203' here to zap the offending faxq
process]
Feb 2 18:18:16 sapphire FaxQueuer[8193]: JOB 16 (active dest +15414886925
pri 127 tts 0:00 killtime 2:48:42): PREPARE DONE
Feb 2 18:18:16 sapphire FaxQueuer[8193]: JOB 16: bad exit status 0x9 from
sub-fork
Feb 2 18:18:16 sapphire FaxQueuer[8193]: NOTIFY: bin/notify "doneq/q16"
"killed" ""
Feb 2 18:18:16 sapphire FaxQueuer[8193]: JOB 16 (done dest +15414886925
pri 127 tts 0:00 killtime 2:48:42): DEAD
Feb 2 18:18:16 sapphire FaxQueuer[8193]: FIFO SEND client/8223 msg "K*"
Feb 2 18:18:16 sapphire FaxQueuer[8193]: JOB 16 (done dest +15414886925
pri 127 tts 0:00 killtime 2:48:42): DELETE
Basically any attempt to send gets the same result. Faxq forks and the
forked proc hangs just after converting the documents. (the documents are
in fact converted, I checked, and the converted tiffs are there in the
docq directory.) I then have to kill -9 the faxq sub-proc or else
it hangs up all of hylafax waiting for that job to finish.
I just can't get more info out of hylafax to begin to figure out what's
going on.
Has anyone here got the least clue where to go on this?
- M. Michael Dragon
Software/Systems Engineer, OptiMation, Inc.
541-488-6915 FAX: 541-488-6925