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

[Lee Howard <faxguy@deanox.com>]

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