HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
Re: [hylafax-users] multiple faxsend on the same serial
* francesco messineo <francesco.messineo@xxxxxxxxx> [070426 10:14]:
> I don't stop and restart faxq regularly, should I?
No...
> here are loglines:
>
> Apr 26 10:28:29 fax FaxSend[31299]: Error parsing "+FTM" query response: "OK"
> Apr 26 10:28:29 fax FaxSend[31299]: /dev/ttyM14: Can not initialize modem.
> Apr 26 10:28:33 fax FaxSend[31288]: /dev/ttyM14: Can not initialize modem.
> Apr 26 10:27:35 fax FaxSend[31071]: Error parsing "+FRM" query response: "OK"
> Apr 26 10:27:35 fax FaxSend[31071]: /dev/ttyM14: Can not initialize modem.
>
> (oddly enough, pid 31071 log only these two lines...)
>
> Apr 26 10:28:42 fax FaxSend[30859]: SEND FAX: JOB 45662 DEST
> +39-081-8635585 COMMID 000066690 DEVICE '/dev/ttyM14' FROM 'assistenza
> <assistenza@xxxxxxxxxx>' USER rsync
>
> Apr 26 10:29:11 fax FaxSend[31299]: MODEM V2.400B-V90_2M_DLS MT5600ZDX/
> Apr 26 10:29:12 fax FaxSend[31299]: SEND FAX: JOB 45393 DEST +39-0755-22801 COMMID 000066698 DEVICE '/dev/ttyM14' FROM 'assistenza <assistenza@xxxxxxxxxx>' USER rsync
>
> Apr 26 10:29:12 fax FaxSend[31288]: MODEM V2.400B-V90_2M_DLS MT5600ZDX/
> Apr 26 10:29:12 fax FaxSend[31288]: SEND FAX: JOB 45676 DEST +39-081-8783933 COMMID 000066699 DEVICE '/dev/ttyM14' FROM 'assistenza <assistenza@xxxxxxxxxx>' USER rsync
You'll have to increase logging levels. Make sure ServerTracing is set
to somethign like 0xFFFFF in $SPOOL/etc/config.
And I want logs of 'FaxQueuer', not of FaxSend from syslog. It should
have entries like (more than this, but at least this for each job):
Apr 26 10:20:05 espresso FaxQueuer[23332]: SUBMIT JOB 58
Apr 26 10:20:05 espresso FaxQueuer[23332]: JOB 58 (suspended dest pri 127 tts 0:00 killtime 2:59:00): CREATE
Apr 26 10:20:06 espresso FaxQueuer[23332]: JOB 58 (ready dest x8238 pri 127 tts 0:00 killtime 2:58:59): READY
Apr 26 10:20:07 espresso FaxQueuer[23332]: JOB 58 (ready dest x8238 pri 127 tts 0:00 killtime 2:58:58): PROCESS
Apr 26 10:20:07 espresso FaxQueuer[23332]: JOB 58 (ready dest x8238 pri 127 tts 0:00 killtime 2:58:58): No assignable modem located
Apr 26 10:20:20 espresso FaxQueuer[23332]: JOB 58 (ready dest x8238 pri 127 tts 0:00 killtime 2:58:45): PROCESS
Apr 26 10:20:20 espresso FaxQueuer[23332]: JOB 58 (ready dest x8238 pri 127 tts 0:00 killtime 2:58:45): No assignable modem located
Apr 26 10:20:25 espresso FaxQueuer[23332]: JOB 58 (ready dest x8238 pri 127 tts 0:00 killtime 2:58:40): PROCESS
Apr 26 10:20:25 espresso FaxQueuer[23332]: JOB 58 (active dest x8238 pri 127 tts 0:00 killtime 2:58:40): ACTIVE
Apr 26 10:20:25 espresso FaxQueuer[23332]: JOB 58 (active dest x8238 pri 127 tts 0:00 killtime 2:58:40): PREPARE START
Apr 26 10:20:25 espresso FaxQueuer[24320]: JOB 58 (active dest x8238 pri 127 tts 0:00 killtime 2:58:40): CONVERT DOCUMENT: bin/ps2fax -o docq/doc50.ps;f0 -r 98 -w 1728 -l 280 -m 4294967295 -U -3 docq/doc50.ps.58
Apr 26 10:20:26 espresso FaxQueuer[23332]: JOB 58 (active dest x8238 pri 127 tts 0:00 killtime 2:58:39): PREPARE DONE
Apr 26 10:20:26 espresso FaxQueuer[23332]: JOB 58 (active dest x8238 pri 127 tts 0:00 killtime 2:58:39): CMD START /usr/sbin/faxsend -m ttyds03 sendq/q58 (PID 24327)
Apr 26 10:21:18 espresso FaxQueuer[23332]: JOB 58 (active dest x8238 pri 127 tts 0:00 killtime 2:57:47): CMD DONE: exit status 0x200
Apr 26 10:21:18 espresso FaxQueuer[23332]: JOB 58 (done dest x8238 pri 127 tts 0:00 killtime 2:57:47): SEND DONE: 0:52
Apr 26 10:21:18 espresso FaxQueuer[23332]: JOB 58 (done dest x8238 pri 127 tts 0:00 killtime 2:57:47): DEAD
Apr 26 10:21:18 espresso FaxQueuer[23332]: JOB 58 (done dest x8238 pri 127 tts 0:00 killtime 2:57:47): DELETE
I'ld like to see the faxq logs that show it sending different jobs on
the same modem at the same time. All of the log. If it's really huge,
send it directly.
> I see the default value is 30 seconds. I don't really understand how
> should I tune it, maybe to allow a closer poll? Any hint here?
> As I wrote in another post, I see that this kind of errors always
> begin with a conversion problem of one or more pdf fax, but I don't
> get how this is related to what I observe.
The shorter the time, the more often faxgetty try's to take the lock
back (the one that faxq will hold if a job is sending). The larget the
time, the longer the wait between tries.
--
Aidan Van Dyk aidan@xxxxxxxx
Senior Software Developer +1 215 825-8700 x8103
iFAX Solutions, Inc. http://www.ifax.com/
____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
*To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*