Re: [hylafax-users] Bad 1D/2D pixel counts and invalid code words UPDATE

["Dennis Fellows" <dennis@lamtop.com>]

Here's the log (below)... and when I run the command "fax2ps -S <filename>
2>/dev/null" it hangs on line 238. If you want that output I'll send it but
I don't want to bog you down with lots of text. Here's what I got when I
sent standard error to a file :
Fax3Decode2D: /var/spool/fax/recvq/fax00004.tif: Uncompressed data (not
supported) at scanline 27 (x1046).

Interestingly enough, I ran the tiff file through tiff2ps and it came out ok
(but with a signifigant amount of errors)

Again, THANKS for all your help!!!

You talked of removing "fax2ps -S <filename> 2>/dev/null" from faxrcvd but
it doesn't exist anywhere in that script.
In my faxrcvd, I added the following line "fax2ps -S $1 | lpr -P
<myfaxprinter>" to the standard script just before it begins the email
construction part (otherwise it's the generic script included with the rpm).
I don't having it handling any errors and it's still hanging....

Apr 12 14:05:43.55: [ 6035]: SESSION BEGIN 00000004 12626584152
Apr 12 14:05:43.55: [ 6035]: <-- [4:ATA\r]
Apr 12 14:05:50.14: [ 6035]: --> [74:+FHT:FF 03 40 32 35 31 34 49 50 4C 20
20 20
 20 20 20 20 20 20 20 20 20 20 ]
Apr 12 14:05:50.94: [ 6035]: --> [26:+FHT:FF 13 80 00 EE FA 02 ]
Apr 12 14:05:52.00: [ 6035]: --> [5:+FCON]
Apr 12 14:05:52.00: [ 6035]: ANSWER: FAX CONNECTION
Apr 12 14:05:52.00: [ 6035]: STATE CHANGE: ANSWERING -> RECEIVING
Apr 12 14:05:52.00: [ 6035]: MODEM input buffering enabled
Apr 12 14:05:52.00: [ 6035]: RECV FAX: begin
Apr 12 14:05:53.75: [ 6035]: --> [74:+FHR:FF 03 43 32 32 34 34 30 37 32 38
30 36
 20 20 20 20 20 20 20 20 20 20 ]
Apr 12 14:05:54.01: [ 6035]: --> [23:+FHR:FF 13 83 00 A2 28 ]
Apr 12 14:05:57.24: [ 6035]: --> [28:+FTSI:"          6082704422"]
Apr 12 14:05:57.24: [ 6035]: REMOTE TSI "6082704422"
Apr 12 14:05:57.24: [ 6035]: --> [21:+FDCS:0,5,0,2,1,0,0,3]
Apr 12 14:05:57.24: [ 6035]: REMOTE wants 14400 bit/s
Apr 12 14:05:57.24: [ 6035]: REMOTE wants page width 1728 pixels in 215 mm
Apr 12 14:05:57.24: [ 6035]: REMOTE wants unlimited page length
Apr 12 14:05:57.24: [ 6035]: REMOTE wants 3.85 line/mm
Apr 12 14:05:57.24: [ 6035]: REMOTE wants 2-D MR
Apr 12 14:05:57.24: [ 6035]: --> [2:OK]
Apr 12 14:05:57.24: [ 6035]: <-- [7:AT+FDR\r]
Apr 12 14:05:58.34: [ 6035]: --> [14:+FHT:FF 13 84 ]
Apr 12 14:05:58.63: [ 6035]: --> [5:+FCFR]
Apr 12 14:05:58.63: [ 6035]: --> [28:+FTSI:"          6082704422"]
Apr 12 14:05:58.63: [ 6035]: REMOTE TSI "6082704422"
Apr 12 14:05:58.63: [ 6035]: --> [21:+FDCS:0,5,0,2,1,0,0,3]
Apr 12 14:05:58.63: [ 6035]: REMOTE wants 14400 bit/s
Apr 12 14:05:58.63: [ 6035]: REMOTE wants page width 1728 pixels in 215 mm
Apr 12 14:05:58.63: [ 6035]: REMOTE wants unlimited page length
Apr 12 14:05:58.63: [ 6035]: REMOTE wants 3.85 line/mm
Apr 12 14:05:58.63: [ 6035]: REMOTE wants 2-D MR
Apr 12 14:06:00.13: [ 6035]: --> [7:CONNECT]
Apr 12 14:06:00.13: [ 6035]: RECV: begin page
Apr 12 14:06:00.13: [ 6035]: RECV: send trigger 022
Apr 12 14:06:00.13: [ 6035]: <-- data [1]
Apr 12 14:06:00.90: [ 6035]: RECV/CQ: Bad 2D pixel count, row 0, got 0,
expected
 1728
Apr 12 14:06:01.12: [ 6035]: RECV/CQ: Bad 1D pixel count, row 11, got 1732,
expe
cted 1728
Apr 12 14:06:01.41: [ 6035]: RECV/CQ: Invalid 2D code word, row 27, x 1046
Apr 12 14:06:01.41: [ 6035]: RECV/CQ: Bad 2D pixel count, row 27, got 1046,
expe
cted 1728
Apr 12 14:06:05.12: [ 6035]: RECV/CQ: Bad 1D pixel count, row 260, got 1705,
exp
ected 1728
Apr 12 14:06:05.12: [ 6035]: RECV/CQ: Bad 2D pixel count, row 261, got 1803,
exp
ected 1728
Apr 12 14:06:09.22: [ 6035]: RECV/CQ: Bad 1D pixel count, row 500, got 1730,
exp
ected 1728
Apr 12 14:06:14.87: [ 6035]: RECV/CQ: Invalid EOL code word, row 819, x 1364
Apr 12 14:06:14.87: [ 6035]: RECV/CQ: Bad 2D pixel count, row 819, got 1364,
exp
ected 1728
Apr 12 14:06:14.87: [ 6035]: RECV/CQ: Bad 2D pixel count, row 820, got 2092,
exp
ected 1728
Apr 12 14:06:14.87: [ 6035]: RECV/CQ: Bad 1D pixel count, row 821, got 2160,
exp
ected 1728
Apr 12 14:06:18.16: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1050, got 0,
expec
ted 1728
Apr 12 14:06:18.16: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1051, got 0,
expec
ted 1728
Apr 12 14:06:18.16: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1052, got 0,
expec
ted 1728

Apr 12 14:06:18.16: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1053, got 0,
expec
ted 1728
Apr 12 14:06:18.16: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1054, got 0,
expec
ted 1728
Apr 12 14:06:18.32: [ 6035]: RECV: 31208 bytes of data, 1055 total lines
Apr 12 14:06:18.32: [ 6035]: RECV/CQ: Adjusting for RTC found at row 1049
Apr 12 14:06:18.32: [ 6035]: --> [15:+FPTS:1,0,0,0,0]
Apr 12 14:06:19.60: [ 6035]: --> [14:+FHR:FF 13 4F ]
Apr 12 14:06:19.60: [ 6035]: --> [6:+FET:0]
Apr 12 14:06:19.60: [ 6035]: RECV recv MPS (more pages, same document)
Apr 12 14:06:19.60: [ 6035]: --> [2:OK]
Apr 12 14:06:19.60: [ 6035]: RECV send MCF (message confirmation)
Apr 12 14:06:19.60: [ 6035]: RECV FAX (00000004): from 6082704422, page 1 in
0:2
2, INF, 3.85 line/mm, 2-D MR, 14400 bit/s
Apr 12 14:06:19.60: [ 6035]: <-- [7:AT+FDR\r]
Apr 12 14:06:20.77: [ 6035]: --> [14:+FHT:FF 13 8C ]
Apr 12 14:06:22.55: [ 6035]: --> [7:CONNECT]
Apr 12 14:06:22.55: [ 6035]: RECV: begin page
Apr 12 14:06:22.55: [ 6035]: RECV: send trigger 022
Apr 12 14:06:22.55: [ 6035]: <-- data [1]
Apr 12 14:06:23.32: [ 6035]: RECV/CQ: Bad 2D pixel count, row 0, got 0,
expected
 1728
Apr 12 14:06:26.01: [ 6035]: RECV/CQ: Bad 2D pixel count, row 116, got 1913,
exp
ected 1728
Apr 12 14:06:26.88: [ 6035]: RECV/CQ: Invalid EOL code word, row 162, x 465

Apr 12 14:06:26.88: [ 6035]: RECV/CQ: Bad 2D pixel count, row 162, got 465,
expe
cted 1728
Apr 12 14:06:26.88: [ 6035]: RECV/CQ: Invalid BlackTable code word, row 163,
x 5
39
Apr 12 14:06:26.88: [ 6035]: RECV/CQ: Bad 1D pixel count, row 163, got 539,
expe
cted 1728
Apr 12 14:06:26.96: [ 6035]: RECV/CQ: Bad 2D pixel count, row 164, got 1730,
exp
ected 1728
Apr 12 14:06:27.32: [ 6035]: RECV/CQ: Invalid EOL code word, row 181, x 1618
Apr 12 14:06:27.32: [ 6035]: RECV/CQ: Bad 2D pixel count, row 181, got 1618,
exp
ected 1728
Apr 12 14:06:27.98: [ 6035]: RECV/CQ: Bad 1D pixel count, row 220, got 1773,
exp
ected 1728
Apr 12 14:06:27.98: [ 6035]: RECV/CQ: Bad 2D pixel count, row 221, got 1729,
exp
ected 1728
Apr 12 14:06:41.53: [ 6035]: RECV: 32751 bytes of data, 838 total lines
Apr 12 14:06:54.31: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1341, got 0,
expec
ted 1728
Apr 12 14:06:54.31: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1342, got 0,
expec
ted 1728
Apr 12 14:06:54.31: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1343, got 0,
expec
ted 1728
Apr 12 14:06:54.31: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1343, got 0,
expec
ted 1728
Apr 12 14:06:54.31: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1344, got 0, e
xpec
ted 1728
Apr 12 14:06:54.31: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1345, got 0,
expec
ted 1728
Apr 12 14:06:54.43: [ 6035]: RECV: 23119 bytes of data, 1346 total lines
Apr 12 14:06:54.43: [ 6035]: RECV/CQ: Adjusting for RTC found at row 1340
Apr 12 14:06:54.43: [ 6035]: --> [15:+FPTS:1,0,0,0,0]
Apr 12 14:06:55.72: [ 6035]: --> [14:+FHR:FF 13 2F ]
Apr 12 14:06:55.72: [ 6035]: --> [6:+FET:2]
Apr 12 14:06:55.72: [ 6035]: RECV recv EOP (no more pages or documents)
Apr 12 14:06:55.72: [ 6035]: --> [2:OK]
Apr 12 14:06:55.72: [ 6035]: RECV send MCF (message confirmation)
Apr 12 14:06:55.72: [ 6035]: RECV FAX (00000004): from 6082704422, page 2 in
0:3
6, INF, 3.85 line/mm, 2-D MR, 14400 bit/s
Apr 12 14:06:55.72: [ 6035]: RECV FAX (00000004): recvq/fax00004.tif from
608270
4422, route to <unspecified>, 2 pages in 1:03
Apr 12 14:06:55.72: [ 6035]: <-- [7:AT+FDR\r]
Apr 12 14:06:56.82: [ 6035]: --> [14:+FHT:FF 13 8C ]
Apr 12 14:06:56.82: [ 6035]: RECV FAX: bin/faxrcvd "recvq/fax00004.tif"
"ttyR0"
"00000004" ""
----- Original Message -----
From: "Lee Howard" <faxguy@deanox.com>
To: "Dennis Fellows" <dennis@lamtop.com>; <hylafax-users@hylafax.org>
Sent: Friday, April 13, 2001 10:49 AM
Subject: Re: [hylafax-users] Bad 1D/2D pixel counts and invalid code words
UPDATE


> At 10:15 AM 4/13/01 -0500, Dennis Fellows wrote:
> >I sent a few questions yesterday about some errors in my session log. I
was
> >told everything was normal but today I noticed that my faxgetty is hung
> >(again) and it occured on the very same transmission that I sent the logs
> >about.
> >
> >If you would like I can resend the logs (and modem config) or you could
> >reference message " Bad 1D/2D pixel counts and invalid code words".
> >
> >Here is some added info. I did a "ps ax | grep fax" and got...
> >5259 ?        S      0:00 faxq
> > 5269 ?        S      0:00 hfaxd -i hylafax
> > 6035 ?        S      0:00 /usr/sbin/faxgetty ttyR0
> > 6036 ?        S      0:00 /usr/sbin/faxgetty ttyR1
> > 6037 ?        S      0:00 /usr/sbin/faxgetty ttyR2
> > 6038 ?        S      0:00 /usr/sbin/faxgetty ttyR3
> > 6180 ?        S      0:00 sh bin/faxrcvd recvq/fax00004.tif ttyR0
00000004
> > 6182 ?        R    1123:26 /usr/bin/fax2ps -S recvq/fax00004.tif
> > 7019 pts/0    S      0:00 grep fax
> >
> >I did a faxstat and got...
> >HylaFAX scheduler on hpe60.lamtop.com: Running
> >Modem ttyR0 (1.262.658.4152): Receiving from "6082704422"
> >Modem ttyR1 (1.262.658.4184): Running and idle
> >Modem ttyR2 (1.262.658.4221): Running and idle
> >Modem ttyR3 (1.262.658.1463): Running and idle
> >
> >I am running Hylafax 4.1beta3 (binary rpm
hylafax-4.1beta3-1rh7.i386.rpm),
> >RH7.0, libtiff 3.5.5-7, Multitech 2834Zdx modem, and a Rocketport PCI
> >multi-I/O board (RJ45 Octacable)
> >
> >I probably shouldn't say that the faxgetty is hung because it seems to be
a
> >problem probably with libtiff, again. I say faxgetty is hung because my
> >modem won't answer the phone. I'm going to leave the system "as is"
(since
> >it's not a production machine yet) so someone (like Lee?) can get more
info
> >if needed.
>
> Here I am. :-)  It looks like fax2ps is hung, not faxgetty, but because
> faxrcvd hasn't returned anything to faxgetty... faxgetty hasn't changed
the
> "Receiving from..." message.
>
> I'd *still* like a look at your session log now that you've turned up
> SessionTracing to 0xFFF.  The log should be there without killing
faxgetty,
> fax2ps, or faxrcvd.
>
> fax2ps is a part of libtiff, not HylaFAX (although the origins of both are
> the same).  What would be ideal, though, is for you to re-create by hand
> and test the fax2ps command issued by faxrcvd which is causing the hang:
>
>  $FAX2PS $FILE 2>/dev/null
>
> I'd guess that you could remove this portion from your faxrcvd without any
> ill effects as I've never seen a postscript attachment with the receipt
> notifications.
>
> Lee.
>
>
>
>



____________________ HylaFAX(tm) Users Mailing List _______________________
 To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null