[hylafax-users] failed notifications although the fax is transmitted successfully (using capi)

[Sandro Poppi <spoppi@xxxxxxx>]

Hi there,

I'm using hylafax 4.2 cvs 2004-04-16 on RedHat 9 and 
capi4hylafax-01.02.00 with my Fritz! card PCI.

Whenever I send a fax e.g. to myself via openoffice 1.1 I can receive it 
but I get a failed notification. It seems that c2faxsend segfaults after 
doing its job but I didn't find a corefile. Here is a sample log of the 
issue:

Apr 18 11:23:30 pluto FaxQueuer[5448]: SUBMIT JOB 7
Apr 18 11:23:30 pluto FaxQueuer[5448]: JOB 7 (suspended dest  pri 127 
tts 0:00 killtime 2:59:00): CREATE
Apr 18 11:23:30 pluto FaxQueuer[5448]: JOB 7 (ready dest +xxxxxxxxxxxx 
pri 127 tts 0:00 killtime 2:59:00): READY
Apr 18 11:23:30 pluto FaxQueuer[5448]: JOB 7 (ready dest +xxxxxxxxxxxx 
pri 127 tts 0:00 killtime 2:59:00): PROCESS
Apr 18 11:23:30 pluto FaxQueuer[5448]: JOB 7 (active dest +xxxxxxxxxxxx 
pri 127 tts 0:00 killtime 2:59:00): ACTIVE
Apr 18 11:23:30 pluto FaxQueuer[5448]: JOB 7 (active dest +xxxxxxxxxxxx 
pri 127 tts 0:00 killtime 2:59:00): PREPARE START
Apr 18 11:23:30 pluto FaxQueuer[5460]: JOB 7 (active dest +xxxxxxxxxxxx 
pri 127 tts 0:00 killtime 2:59:00): CONVERT DOCUMENT: bin/ps2fax -o 
docq/doc7.ps;01 -r 196 -w 1728 -l 297 -m 4294967295 -1 docq/doc7.ps.7
Apr 18 11:23:30 pluto FaxQueuer[5448]: JOB 7 (active dest +xxxxxxxxxxxx 
pri 127 tts 0:00 killtime 2:59:00): PREPARE DONE
Apr 18 11:23:30 pluto FaxQueuer[5448]: JOB 7 (active dest +xxxxxxxxxxxx 
pri 127 tts 0:00 killtime 2:59:00): CMD START /usr/bin/c2faxsend -m 
faxCAPI sendq/q7 (PID 5465)
Apr 18 11:23:30 pluto kernel: kcapi: appl 4 up
Apr 18 11:23:31 pluto kernel: capidrv-1: incoming call ,1,2,xxxxxx
Apr 18 11:23:31 pluto kernel: capidrv-1: patching si2=2 to 0 for VBOX
Apr 18 11:23:31 pluto kernel: isdn_net: Incoming call without OAD, 
assuming '0'
Apr 18 11:23:31 pluto kernel: isdn_net: call from 0 -> 0 xxxxxx ignored
Apr 18 11:23:31 pluto kernel: isdn_tty: Incoming call without OAD, 
assuming '0'
Apr 18 11:23:31 pluto kernel: isdn_tty: call from 0 -> xxxxxx ignored
Apr 18 11:23:31 pluto kernel: capidrv-1: incoming call ,1,0,xxxxxx ignored
Apr 18 11:23:31 pluto kernel: kcapi: appl 4 ncci 0x10101 up
Apr 18 11:23:40 pluto kernel: kcapi: appl 3 ncci 0x20201 up
Apr 18 11:23:46 pluto kernel: kcapi: appl 4 ncci 0x10101 down
Apr 18 11:23:46 pluto kernel: kcapi: appl 3 ncci 0x20201 down
Apr 18 11:23:46 pluto FaxQueuer[5448]: JOB 7 (active dest +xxxxxxxxxxxx 
pri 127 tts 0:00 killtime 2:58:44): CMD DONE: exit status 0xb
Apr 18 11:23:46 pluto FaxQueuer[5448]: JOB 7: Send program terminated 
abnormally with exit status 0xb
Apr 18 11:23:46 pluto FaxQueuer[5448]: NOTIFY: bin/notify "doneq/q7" 
"failed" "0:16"
Apr 18 11:23:46 pluto kernel: kcapi: appl 4 down
Apr 18 11:23:46 pluto kernel: kcapi: recv_handler: applid 4 ? 
(LISTEN_CONF                ID=004 #0x0000 LEN=0014
Apr 18 11:23:46 pluto kernel:   Controller/PLCI/NCCI            = 0x1
Apr 18 11:23:46 pluto kernel:   Info                            = 0x0
Apr 18 11:23:46 pluto kernel: )
Apr 18 11:23:46 pluto FaxQueuer[5448]: JOB 7 (failed dest +xxxxxxxxxxxx 
pri 127 tts 0:00 killtime 2:58:44): SEND DONE: 0:16
Apr 18 11:23:46 pluto FaxQueuer[5448]: JOB 7 (failed dest +xxxxxxxxxxxx 
pri 127 tts 0:00 killtime 2:58:44): DEAD
Apr 18 11:23:46 pluto FaxQueuer[5448]: JOB 7 (failed dest +xxxxxxxxxxxx 
pri 127 tts 0:00 killtime 2:58:44): DELETE
Apr 18 11:23:46 pluto FaxQueuer[5448]: NOTIFY exit status: 0 (5468)

Did anyone else also experience that, and can ideally provide a solution?

Thank you in advance,
Sandro

--
"Linux is like a wigwam: no windows, no gates ... apache inside!"

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature