Re: [hylafax-users] "job sent succesfully", while it was not

[Patrice Fournier <pfournier@loups.net>]

Quoting Giulio Orsero <giulioo@pobox.com>:

> 4.1.3
> 
> At about 2002-07-29 21:00 I updated the HylaFAX installation from
> 4.1.2cvs to 4.1.3. I checked that the job still resulted as "to be
> sent" after the upgrade and sent another test fax succesfully.

Should not matter.

> This morning there are some issues regarding this job:
> 1) user received confirmation email "job sent succesfully"

Not good :(

> 2) job is not visible with "faxstat"

That's because of #3

> 3) every faxstat invocation results in a message in the log
> doneq/q6536: line 52: Document has been rejected
> 
> Since user mistakenly scheduled job for 00:00 he may well had some
> problem in sending proper postscript to the server too.
> 
> The problem is that he received confirmation that all was ok. 
> Note that docq/<document> does not esist anymore while we retain those
> docs for 3 days, and previous jobs's docs are still there. We have a
> modified notify script that attach the sent fax as tif, and the
> confirmation email lacks the attachment (0 bytes).

docq/doc6559.ps.6536 does not exist?
How about docq/doc6559.ps?
 
> system log for this job:
> Jul 29 09:24:49 fax FaxQueuer[778]: SUBMIT JOB 6536
> Jul 30 00:00:11 fax FaxSend[5897]: SEND FAX: JOB 6536 DEST XXXXXXXXXXXX
> COMMID 00005768 DEVICE '/dev/ttyS2'
> Jul 30 00:00:59 fax FaxQueuer[4459]: NOTIFY: bin/notify "doneq/q6536"
> "done" "0:56"

Anything in the system log about docq/doc6559.ps?

> transmission log shows there was a problem:

Where are we in the log? right after NSF?

> Jul 30 00:00:55.42: [ 5897]: <-- [9:AT+FRH=3\r]
> Jul 30 00:00:55.44: [ 5897]: --> [7:CONNECT]
> Jul 30 00:00:55.71: [ 5897]: --> [2:OK]
> Jul 30 00:00:55.71: [ 5897]: REMOTE best rate 14400 bit/s
> Jul 30 00:00:55.71: [ 5897]: REMOTE max page width 1728 pixels in 215
> mm
> Jul 30 00:00:55.71: [ 5897]: REMOTE max unlimited page length
> Jul 30 00:00:55.71: [ 5897]: REMOTE best vres 7.7 line/mm
> Jul 30 00:00:55.71: [ 5897]: REMOTE best format 2-D MMR
> Jul 30 00:00:55.71: [ 5897]: REMOTE supports T.30 Annex A, ECM
> Jul 30 00:00:55.71: [ 5897]: REMOTE best 10 ms/scanline
> Jul 30 00:00:55.71: [ 5897]: USE 14400 bit/s
> Jul 30 00:00:55.71: [ 5897]: USE 10 ms/scanline

hmmm.. there's no SEND file line here... it looks like the job had no file
to send (and accepted this). It then proceeded to close the connection and
has the code is optimistic and defaults to success, the job was reported to
be sent successfully. Now, why it accepted to connect with no job to send
is what we should find out.

> Jul 30 00:00:55.71: [ 5897]: <-- [9:AT+FTH=3\r]
> Jul 30 00:00:55.76: [ 5897]: --> [7:CONNECT]
> Jul 30 00:00:55.76: [ 5897]: <-- data [3]
> Jul 30 00:00:55.76: [ 5897]: <-- data [2]
> Jul 30 00:00:57.09: [ 5897]: --> [2:OK]
> Jul 30 00:00:57.09: [ 5897]: <-- [14:AT+FCLASS=0H0\r]
> Jul 30 00:00:59.85: [ 5897]: --> [2:OK]
> Jul 30 00:00:59.85: [ 5897]: sched policy=0, priority=0
> Jul 30 00:00:59.85: [ 5897]: SESSION END
> 
> dataformat:2-D MMR       <===== MMR?

I've seen this often on job that didn't complete. Has it sent no page, how
do you know it didn't send it in 2-D MMR? :)

I'll try to reproduce this later and see if I can find out why/how it
happenned.

-- 
Patrice Fournier
pfournier@loups.net

____________________ 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@hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*