"송신 작업"상태에서 Hylafax 모뎀이 멈춤

Question

12 개의 모뎀이 내 HylaFax 서버에 연결되어 있는데 때로는 모뎀에서 회선 연결을 끊을 때까지 "작업 전송 중"상태로 고정되어있는 일부 모뎀이 나타납니다 일자리가 죽었어.

예고없이 영원히이 상태에 머물 수있는 모뎀, 여기에 내가 갇혀중인 작업에 대한 서버 추적에서 무엇을 얻을 :

내가 알고있는 것처럼

Jan 26 10:33:53.57: [29579]: SESSION BEGIN 000028267 79137356 
Jan 26 10:33:53.57: [29579]: HylaFAX (tm) Version 6.0.6 
Jan 26 10:33:53.57: [29579]: SEND FAX: JOB 5166 DEST 79137356 COMMID 000028267 DEVICE '/dev/ttyT38-23' FROM 'tuxfax <tuxfax@tuxfax.tux>' USER apache 
Jan 26 10:33:53.57: [29579]: STATE CHANGE: RUNNING -> SENDING 
Jan 26 10:33:53.57: [29579]: <-- [12:AT+FCLASS=1\r] 
Jan 26 10:33:53.57: [29579]: --> [2:OK] 
Jan 26 10:33:53.57: [29579]: DIAL 79137356 
Jan 26 10:33:53.57: [29579]: <-- [10:ATDT79137356\r] 
Jan 26 10:34:09.51: [29579]: --> [7:CONNECT] 
Jan 26 10:34:17.55: [29579]: --> HDLC<40:FF C0 04 FF FF FF FF 73 1D 01 01 88 A1 B0 BB 00 00 BB BB 00 00 BB BB 00 00 00 00 00 00 00 00 B7 44 0D 00 00 09 00 E1 4F> 
Jan 26 10:34:17.55: [29579]: --> [2:OK] 
Jan 26 10:34:17.55: [29579]: REMOTE NSF "FF FF FF FF CE B8 80 80 11 85 0D DD 00 00 DD DD 00 00 DD DD 00 00 00 00 00 00 00 00 ED 22 B0 00 00 90 00" 
Jan 26 10:34:17.55: [29579]: NSF remote fax equipment: unknown 
Jan 26 10:34:17.55: [29579]: <-- [9:AT+FRH=3\r] 
Jan 26 10:34:17.56: [29579]: --> [7:CONNECT] 
Jan 26 10:34:18.27: [29579]: --> HDLC<25:FF C0 02 CC 9C 4C AC 1C 4C 4C EC 04 04 04 04 04 04 04 04 04 04 04 04 8B C9> 
Jan 26 10:34:18.27: [29579]: --> [2:OK] 
Jan 26 10:34:18.27: [29579]: REMOTE CSI "77225292" 
Jan 26 10:34:18.27: [29579]: <-- [9:AT+FRH=3\r] 
Jan 26 10:34:18.28: [29579]: --> [7:CONNECT] 
Jan 26 10:34:18.61: [29579]: --> HDLC<11:FF C8 01 00 73 1D 01 01 88 03 AE> 
Jan 26 10:34:18.61: [29579]: --> [2:OK] 
Jan 26 10:34:18.61: [29579]: REMOTE best rate 9600 bit/s 
Jan 26 10:34:18.61: [29579]: REMOTE max A4 page width (215 mm) 
Jan 26 10:34:18.61: [29579]: REMOTE max unlimited page length 
Jan 26 10:34:18.61: [29579]: REMOTE best vres 15.4 line/mm 
Jan 26 10:34:18.61: [29579]: REMOTE format support: MH, MR 
Jan 26 10:34:18.61: [29579]: REMOTE best 20 ms, 10 ms/scanline 
Jan 26 10:34:18.61: [29579]: USE 9600 bit/s 
Jan 26 10:34:18.61: [29579]: SEND file "docq/doc5166.pdf;f0" 
Jan 26 10:34:18.61: [29579]: USE A4 page width (215 mm) 
Jan 26 10:34:18.61: [29579]: USE unlimited page length 
Jan 26 10:34:18.61: [29579]: USE 3.85 line/mm 
Jan 26 10:34:18.61: [29579]: USE 2-D MR 
Jan 26 10:34:18.61: [29579]: USE 20 ms/scanline 
Jan 26 10:34:18.61: [29579]: SEND training at v.29 9600 bit/s 
Jan 26 10:34:18.61: [29579]: <-- [9:AT+FRS=7\r] 
Jan 26 10:34:18.69: [29579]: --> [2:OK] 
Jan 26 10:34:18.69: [29579]: <-- [9:AT+FTH=3\r] 
Jan 26 10:34:18.69: [29579]: --> [7:CONNECT] 
Jan 26 10:34:18.69: [29579]: <-- HDLC<23:FF C0 C2 1C 1C 1C 0C 2C CC 8C EC F4 0C AC EC 4C CC 04 0A F2 C2 22 04> 
Jan 26 10:34:18.69: [29579]: <-- data [23] 
Jan 26 10:34:18.69: [29579]: <-- data [2] 
Jan 26 10:34:20.23: [29579]: --> [7:CONNECT] 
Jan 26 10:34:20.23: [29579]: <-- HDLC<6:FF C8 C1 00 61 10> 
Jan 26 10:34:20.23: [29579]: <-- data [6] 
Jan 26 10:34:20.23: [29579]: <-- data [2] 
Jan 26 10:34:20.53: [29579]: --> [2:OK] 
Jan 26 10:34:20.53: [29579]: <-- [9:AT+FTS=7\r] 
Jan 26 10:34:20.66: [29579]: --> [2:OK] 
Jan 26 10:34:20.66: [29579]: <-- [10:AT+FTM=96\r] 
Jan 26 10:34:20.66: [29579]: --> [7:CONNECT] 
Jan 26 10:34:20.66: [29579]: <-- data [1024] 
Jan 26 10:34:20.66: [29579]: <-- data [776] 
Jan 26 10:34:20.66: [29579]: <-- data [2] 
Jan 26 10:34:22.52: [29579]: --> [2:OK] 
Jan 26 10:34:22.52: [29579]: <-- [9:AT+FRH=3\r] 
Jan 26 10:34:23.47: [29579]: --> [7:CONNECT] 
Jan 26 10:34:24.51: [29579]: --> HDLC<5:FF C8 21 57 BE> 
Jan 26 10:34:24.51: [29579]: --> [2:OK] 
Jan 26 10:34:24.51: [29579]: TRAINING succeeded 
Jan 26 10:34:24.51: [29579]: <-- [9:AT+FRS=7\r] 
Jan 26 10:34:24.59: [29579]: --> [2:OK] 
Jan 26 10:34:24.59: [29579]: <-- [10:AT+FTM=96\r] 
Jan 26 10:34:24.59: [29579]: --> [7:CONNECT] 
Jan 26 10:34:24.59: [29579]: SEND begin page 
Jan 26 10:34:24.59: [29579]: Reading MMR-compressed image file 
Jan 26 10:34:24.60: [29579]: <-- data [1029] 
Jan 26 10:34:24.60: [29579]: <-- data [1024] 
Jan 26 10:34:24.60: [29579]: <-- data [1024] 
Jan 26 10:34:24.60: [29579]: <-- data [1024] 
Jan 26 10:34:24.60: [29579]: <-- data [1024] 
Jan 26 10:34:24.60: [29579]: <-- data [1026] 
Jan 26 10:34:24.60: [29579]: <-- data [1043] 
Jan 26 10:34:24.60: [29579]: <-- data [1039] 
Jan 26 10:34:24.60: [29579]: <-- data [1042] 
Jan 26 10:34:24.60: [29579]: <-- data [1034] 
Jan 26 10:34:24.60: [29579]: <-- data [1034] 
Jan 26 10:34:24.60: [29579]: <-- data [1036] 
Jan 26 10:34:24.60: [29579]: <-- data [1032] 
Jan 26 10:34:24.60: [29579]: <-- data [1028] 
Jan 26 10:34:24.60: [29579]: <-- data [1035] 
Jan 26 10:34:24.60: [29579]: <-- data [1033] 
Jan 26 10:34:24.60: [29579]: <-- data [1033] 
Jan 26 10:34:24.60: [29579]: <-- data [1030] 
Jan 26 10:34:24.60: [29579]: <-- data [1027] 
Jan 26 10:34:24.60: [29579]: <-- data [1026] 
Jan 26 10:34:24.60: [29579]: <-- data [1025] 
Jan 26 10:34:24.60: [29579]: <-- data [1035] 
Jan 26 10:34:24.60: [29579]: <-- data [1028] 
Jan 26 10:34:24.60: [29579]: <-- data [1024] 
Jan 26 10:34:24.60: [29579]: <-- data [1030] 
Jan 26 10:34:24.60: [29579]: <-- data [264] 
Jan 26 10:34:24.60: [29579]: SENT 25864 bytes of data 
Jan 26 10:34:24.60: [29579]: <-- data [1031] 
Jan 26 10:34:24.60: [29579]: <-- data [1038] 
Jan 26 10:34:24.60: [29579]: <-- data [1039] 
Jan 26 10:34:24.60: [29579]: <-- data [868] 
Jan 26 10:34:24.60: [29579]: SENT 3931 bytes of data 
Jan 26 10:34:24.60: [29579]: SEND 2D RTC 
Jan 26 10:34:24.60: [29579]: <-- data [30] 
Jan 26 10:34:24.60: [29579]: <-- data [2] 
Jan 26 10:34:24.60: [29579]: SEND end page 
Jan 26 10:34:49.80: [29579]: --> [2:OK] 
Jan 26 10:34:49.80: [29579]: <-- [9:AT+FTS=9\r] 
Jan 26 10:34:49.96: [29579]: --> [2:OK] 
Jan 26 10:34:49.96: [29579]: SEND send EOP (no more pages or documents) 
Jan 26 10:34:49.96: [29579]: <-- [9:AT+FTH=3\r] 
Jan 26 10:34:49.96: [29579]: --> [7:CONNECT] 
Jan 26 10:34:49.96: [29579]: <-- HDLC<3:FF C8 F4> 
Jan 26 10:34:49.96: [29579]: <-- data [3] 
Jan 26 10:34:49.96: [29579]: <-- data [2] 
Jan 26 10:34:51.00: [29579]: --> [2:OK] 
Jan 26 10:34:51.00: [29579]: <-- [9:AT+FRH=3\r] 
Jan 26 10:34:51.87: [29579]: --> [7:CONNECT] 
Jan 26 10:34:52.91: [29579]: --> HDLC<5:FF C8 5F C8 E7> 
Jan 26 10:34:52.91: [29579]: --> [2:OK] 
Jan 26 10:34:52.91: [29579]: SEND recv DCN (disconnect) 
Jan 26 10:34:52.91: [29579]: Remote fax disconnected prematurely 
Jan 26 10:34:52.91: [29579]: <-- [9:AT+FRS=7\r] 
Jan 26 10:34:52.98: [29579]: --> [2:OK] 
Jan 26 10:34:52.98: [29579]: <-- [9:AT+FTH=3\r] 
Jan 26 10:34:52.99: [29579]: --> [7:CONNECT] 
Jan 26 10:34:52.99: [29579]: <-- HDLC<3:FF C8 DF> 
Jan 26 10:34:52.99: [29579]: <-- data [3] 
Jan 26 10:34:52.99: [29579]: <-- data [2] 

는, 모뎀 (영원히) 기다리고에 대한 응답 할 원격 팩스.

서버 구성은 다음과 같습니다 HylaFax 6.0.6/CentOS는 6.3

질문은 다음과 같습니다

1. Hylafax 동결의이 종류를 피하기 위해 모든 구성 매개 변수가 있습니까?
2. 빠른 해결 방법으로, 나는 작업을 보내는 것을 모니터하고 "보내기 작업"에서 지속되는 작업을 죽일 수 있지만 실행중인 작업 (대기중인 작업이 아님)을 죽일 수는 없습니다.

Answer 1

휴대 전화 개발과 관련하여 팩스에 약간의 노출이 있었지만 팩스는 "테스트, 테스트, 테스트"문제였습니다 (GSM을 통해 팩스 코드를 실행할 때 불가능한 타이밍 문제로 인해 예상되는 상황에 대한 응답을 보내야하는 경우도있었습니다). 그리고 사양에 따라 모든 것을 구현하더라도 일이 보장되는 것은 아닙니다. 대부분의 (모든?) 모바일 네트워크와 전화가 오늘날 팩스 지원을 중단 한 이유가 있습니다.

저는 모뎀이 원격 팩스가 응답하기를 (영원히) 기다리고 있다고 생각합니다.

이 경우가있을 수 있으며 원격 팩스기 나 hylafax를 둘 책임이 없음을 이해할 수 있습니다. 일부 모니터링 서비스를 구현하는 것이 현명하고 신뢰할 수있는 방법입니다.