Hylafax Mailing List Archives

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

[hylafax-users] faxgetty <defunct> - 'Extra' FaxGetty



Admin  --  we may be signed up to the list as web@xxxxxxxxxxxxxxxxxxxxxxx.

 

 

Hello List!

 

Is this Problem I am seeing a ‘Wedge” or something else?

 

            Modem ttyS15 (***-****): Receiving from "Always the Same Sender"

            fpclinux2:/home/lxuser # ps -A | grep fax

            3760 ?        00:00:00 faxq

            3762 ?        00:00:00 hfaxd

            29366 ?        00:00:01 faxgetty

            29368 ?        00:00:14 faxgetty

à         4588 ?        00:00:00 faxgetty <defunct>

 

            Often we see “faxgetty <defunct>” when we arrive in the morning.  ALWAYS from the same sender.  This after we ‘Grep’ “Fax” I notice that there is a 3rd faxgetty (which is Defunct).

            We have ruled out this being line noise by switching the phone lines between the 2 modems (ttyS14 USED to do it) in the Box.  This is a send/receive error. 

            Sometimes we get errors, sometimes it will not give errors.  (Sender broadcasting multiple faxes overnight).  Sometimes it will happen on the 1st or 2nd fax, other times after the 10th.  Simply must be a send-receive issue.  Sender SAYS nothing has changed on their end w/ their fax-server and we have not changed anything on ours, yet, this happened kind of ‘out of the blue’

            Solution so far has been to kill the faxgetty instances and re-start them.  What could be causing these?

 

SYSTEM INFO

Hylafax 4.2.2  --  Would like to WAIT a little bit to make sure the Flurry of ‘updates’ is over if possible.

Suse 9.0 Linux box

Dual AMD T-Bird with plenty of RAM.

Modems – PCI Internal  MultiTech MT5634ZPX

This Fax-Server is used for Receiving, we do not use it to send (unless I am bored and decide to print to the Fax-Server).  Caller-ID has been turned off.

 

            Modem config + last ‘error’ below (Error we saw here was  “Failed to properly detect high-speed data carrier”)  

            HOWEVER, we have gotten this in the past from the SAME sender and STILL continued to receive a next fax (and more).  I do NOT think this is the ‘Cause’ of faxgetty becoming <Defunct>

 

 

 

Modem config

CountryCode:                1

AreaCode:                     406

FAXNumber:                  *-*

LongDistancePrefix:       1

InternationalPrefix:         011

DialStringRules: etc/dialrules

ServerTracing:                1

TracingMask:                 0x11

#SessionTracing:           11

SessionTracing:             0xFFF

RecvFileMode:               0644

LogFileMode:                 0644

DeviceMode:                  0644

RingsBeforeAnswer:       2

SpeakerVolume:                        off

GettyArgs:                    "-h %l dx_%s"

LocalIdentifier:   FRONTLINE

ClocalAsRoot:               no

PriorityScheduling:         yes

TagLineFont:                 etc/lutRS18.pcf

TagLineFormat:              "From %%l|%c|Page %%P of %%T"

PercentGoodLines:        0

MaxConsecutiveBadLines:          0

MaxRecvPages:             150

ModemType:                 Class1.0           # use this to supply a hint

ModemRate:                  57600               # must be at least as fast as the DCE-DCE communication

ModemFlowControl:       rtscts                # many firmwares have broken software flow control

#Class1TCFRecvHack:   yes                   # avoid +FCERROR before TCF

Class1EnableV34Cmd:   AT+F34=14,1,2  # 33600-2400 primary, 2400-1200 control

Class1TCFRecvHack:     yes                   # avoid +FCERROR before TCF

# Class1MsgRecvHackCmd:       AT+FRS=1        # avoid +FCERROR before image

Class1TMConnectDelay:            400                   # counteract quick CONNECT response

 

 

 

 

Last received log (truncated)

Jan 26 07:59:25.60: [ 6019]: SESSION BEGIN 000006393 14065857576

Jan 26 07:59:25.60: [ 6019]: HylaFAX (tm) Version 4.2.1

Jan 26 07:59:25.60: [ 6019]: <-- [4:ATA\r]

Jan 26 07:59:25.60: [ 6019]: <-- <3:41 54 41>

Jan 26 07:59:25.60: [ 6019]: <-- <1:0D>

Jan 26 07:59:37.80: [ 6019]: --> <11:0D 0A 43 4F 4E 4E 45 43 54 0D 0A>

Jan 26 07:59:37.80: [ 6019]: --> [7:CONNECT]

Jan 26 07:59:37.80: [ 6019]: STATE CHANGE: ANSWERING -> RECEIVING

Jan 26 07:59:37.80: [ 6019]: MODEM input buffering enabled

Jan 26 07:59:37.80: [ 6019]: RECV FAX: begin

Jan 26 07:59:37.86: [ 6019]: MODEM input buffering disabled

Jan 26 07:59:37.86: [ 6019]: <-- HDLC<32:FF C0 04 AD 00 55 12 9E 36 86 62 82 1A 04 14 2E B6 94 04 6A A6 4E CE 96 F6 76 04 2C 74 4C 74 8C>

Jan 26 07:59:37.86: [ 6019]: <-- data [32]

 

<<<SNIP>>>

 

Jan 26 08:00:10.92: [ 6019]: --> HDLC<154:FF C0 60 72 4E 03 F1 B1 B1 B1 B1 3B 8A FE D7 F4 5E 6B 46 EB D2 2F BF 34 07 2F B8 23 66 CE 56 BF 64 DC 29 0B 62 22 90 88 88 88 B4 0C B8 B0 87 B5 55 4E E6 8F F6 2B E0 D8 ED 63 8A 62 FE D8 6C 55 C6 68 D8 A6 2B F1 6C 20 84 44 7B 4D 34 D5 57 5E 43 6D 06 98 22 3A 0C FD 69 A0 C9 DA 9D C2 64 ED 6E D0 70 61 50 60 A8 EA 8D 7B B4 20 E3 C4 44 44 44 44 44 44 44 44 44 44 44 44 44 44 44 44 44 44 7F FC B5 08 5C 7F 2C F5 7C B7 D7 1E 3F FF E5 65 16 B9 67 11 F0 01 00 10 94 36>

Jan 26 08:00:10.92: [ 6019]: RECV received frame number 78

Jan 26 08:00:10.92: [ 6019]: RECV received RCP frame

Jan 26 08:00:10.92: [ 6019]: --> [10:NO CARRIER]

Jan 26 08:00:10.92: [ 6019]: MODEM input buffering disabled

Jan 26 08:00:10.92: [ 6019]: <-- [9:AT+FRH=3\r]

Jan 26 08:00:10.92: [ 6019]: <-- <8:41 54 2B 46 52 48 3D 33>

Jan 26 08:00:10.92: [ 6019]: <-- <1:0D>

Jan 26 08:00:11.00: [ 6019]: --> <11:0D 0A 43 4F 4E 4E 45 43 54 0D 0A>

Jan 26 08:00:11.00: [ 6019]: --> [7:CONNECT]

Jan 26 08:00:12.18: [ 6019]: --> <17:FF 13 BF 2F 01 00 4E 6C B4 10 03 0D 0A 4F 4B 0D 0A>

Jan 26 08:00:12.18: [ 6019]: --> HDLC<9:FF C8 FD F4 80 00 72 36 2D>

Jan 26 08:00:12.18: [ 6019]: --> [2:OK]

Jan 26 08:00:12.18: [ 6019]: RECV recv PPS (partial page signal)

Jan 26 08:00:12.18: [ 6019]: RECV recv EOP (no more pages or documents)

Jan 26 08:00:12.18: [ 6019]: RECV received 79 frames of block 1 of page 2

Jan 26 08:00:12.22: [ 6019]: RECV/CQ: Adjusting for EOFB at row 1040

Jan 26 08:00:12.22: [ 6019]: RECV: 20116 bytes of data, 1040 total lines

Jan 26 08:00:12.22: [ 6019]: MODEM input buffering disabled

Jan 26 08:00:12.22: [ 6019]: <-- [9:AT+FRS=7\r]

Jan 26 08:00:12.22: [ 6019]: <-- <8:41 54 2B 46 52 53 3D 37>

Jan 26 08:00:12.22: [ 6019]: <-- <1:0D>

Jan 26 08:00:12.38: [ 6019]: --> <6:0D 0A 4F 4B 0D 0A>

Jan 26 08:00:12.38: [ 6019]: --> [2:OK]

Jan 26 08:00:12.38: [ 6019]: <-- [9:AT+FTH=3\r]

Jan 26 08:00:12.38: [ 6019]: <-- <8:41 54 2B 46 54 48 3D 33>

Jan 26 08:00:12.38: [ 6019]: <-- <1:0D>

Jan 26 08:00:13.34: [ 6019]: --> <11:0D 0A 43 4F 4E 4E 45 43 54 0D 0A>

Jan 26 08:00:13.34: [ 6019]: --> [7:CONNECT]

Jan 26 08:00:13.34: [ 6019]: <-- HDLC<3:FF C8 31>

Jan 26 08:00:13.34: [ 6019]: <-- data [3]

Jan 26 08:00:13.34: [ 6019]: <-- <3:FF 13 8C>

Jan 26 08:00:13.34: [ 6019]: <-- data [2]

Jan 26 08:00:13.34: [ 6019]: <-- <2:10 03>

Jan 26 08:00:13.72: [ 6019]: --> <6:0D 0A 4F 4B 0D 0A>

Jan 26 08:00:13.72: [ 6019]: --> [2:OK]

Jan 26 08:00:13.72: [ 6019]: RECV send MCF (message confirmation)

Jan 26 08:00:13.72: [ 6019]: <-- [9:AT+FRH=3\r]

Jan 26 08:00:13.72: [ 6019]: <-- <8:41 54 2B 46 52 48 3D 33>

Jan 26 08:00:13.72: [ 6019]: <-- <1:0D>

Jan 26 08:00:14.49: [ 6019]: --> <11:0D 0A 43 4F 4E 4E 45 43 54 0D 0A>

Jan 26 08:00:14.49: [ 6019]: --> [7:CONNECT]

Jan 26 08:00:15.66: [ 6019]: --> <13:FF 13 FB 9A F6 10 03 0D 0A 4F 4B 0D 0A>

Jan 26 08:00:15.66: [ 6019]: --> HDLC<5:FF C8 DF 59 6F>

Jan 26 08:00:15.66: [ 6019]: --> [2:OK]

Jan 26 08:00:15.66: [ 6019]: MODEM input buffering enabled

Jan 26 08:00:15.66: [ 6019]: RECV FAX: end

Jan 26 08:00:15.66: [ 6019]: SESSION END

 

 

 

 

Hans Strickler

www.frontlineprocessing.com

hss@xxxxxxxxxxxxxxxxxxxxxxx

676 Ferguson Ave. Suite 5

Bozeman, Mt. 59718

866*651*3068

406*585*7576 (Fax)

 

 

GIF image



Home
Report any problems to webmaster@hylafax.org

HylaFAX is a trademark of Silicon Graphics Corporation.
Internet connectivity for hylafax.org is provided by:
VirtuALL Private Host Services