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。實施一些監測服務似乎是處理這一問題的唯一明智而可靠的方法。