Re: [hylafax-users] sendfax sometimes hangs, can't identify protocol?

[Mark Hunting <mark@xxxxxxxxxx>]

Aidan Van Dyk wrote:
> Hm.. if sendfax and faxstat are the *only* clients you use, then the
> trigger bug doesn't sound likely.  Are there any faxq messages in syslog
> about "Bad fifo message" or something like that?
>   
Bingo. There is indeed some very usefull information in syslog (I 
think). Two sendfax processes I had to kill today were process ID's 
26875 (the example from my previous mail), and 8693. In syslog there are 
lots of FIFO errors, but what surprises me are these lines:

May  8 11:42:36 caracas FaxQueuer[3699]: HylaClient::send: /26876: 
Cannot open FIFO: No such file or directory
and
May  8 12:03:53 caracas FaxQueuer[3699]: HylaClient::send: t/8694: 
Cannot open FIFO: No such file or directory

The numbers here are the killed sendfax ID's + 1. The times are indeed 
the times on which the hanging sendfax processes were started. Do you 
know what this all means?
Here is the contect of the two lines:

cat /var/log/syslog|grep -i fifo|grep -v 'not found':
May  8 11:31:28 caracas FaxQueuer[3699]: Bad FIFO cmd '5' from client
May  8 11:36:03 caracas FaxQueuer[3699]: Bad FIFO cmd 'o' from client
May  8 11:36:51 caracas FaxQueuer[3699]: Bad FIFO cmd 'd' from client
May  8 11:40:40 caracas FaxQueuer[3699]: Bad FIFO cmd '4' from client
May  8 11:42:36 caracas FaxQueuer[3699]: Bad FIFO cmd 't' from client /26876
May  8 11:42:36 caracas FaxQueuer[3699]: HylaClient::send: /26876: 
Cannot open FIFO: No such file or directory
May  8 11:43:40 caracas FaxQueuer[3699]: Bad FIFO cmd '0' from client
May  8 11:44:35 caracas FaxQueuer[3699]: Bad FIFO cmd '5' from client 61
May  8 11:44:35 caracas FaxQueuer[3699]: HylaClient::send: 61: Cannot 
open FIFO: No such file or directory
May  8 11:45:55 caracas FaxQueuer[3699]: Bad FIFO cmd '3' from client
May  8 11:47:58 caracas FaxQueuer[3699]: Bad FIFO cmd 'o' from client
May  8 11:50:41 caracas FaxQueuer[3699]: Bad FIFO cmd 'c' from client
May  8 11:51:51 caracas FaxQueuer[3699]: Bad FIFO cmd '0' from client
May  8 11:53:39 caracas FaxQueuer[3699]: Bad FIFO cmd ':' from client
May  8 11:54:11 caracas FaxQueuer[3699]: Bad FIFO cmd '.' from client
May  8 11:57:50 caracas FaxQueuer[3699]: Bad FIFO cmd ',' from client
May  8 11:59:27 caracas FaxQueuer[3699]: Bad FIFO cmd '0' from client
May  8 11:59:27 caracas FaxQueuer[3699]: Bad FIFO cmd '5' from client 116
May  8 11:59:27 caracas FaxQueuer[3699]: HylaClient::send: 116: Cannot 
open FIFO: No such file or directory
May  8 12:00:48 caracas FaxQueuer[3699]: Bad FIFO cmd '9' from client
May  8 12:00:48 caracas FaxQueuer[3699]: Bad FIFO cmd ':' from client
May  8 12:02:02 caracas FaxQueuer[3699]: Bad FIFO cmd '.' from client
May  8 12:02:02 caracas FaxQueuer[3699]: Bad FIFO cmd '5' from client 208
May  8 12:02:02 caracas FaxQueuer[3699]: HylaClient::send: 208: Cannot 
open FIFO: No such file or directory
May  8 12:03:53 caracas FaxQueuer[3699]: Bad FIFO cmd 'n' from client t/8694
May  8 12:03:53 caracas FaxQueuer[3699]: HylaClient::send: t/8694: 
Cannot open FIFO: No such file or directory
May  8 12:04:44 caracas FaxQueuer[3699]: Bad FIFO cmd '7' from client
May  8 12:04:44 caracas FaxQueuer[3699]: Bad FIFO cmd ',' from client
May  8 12:06:20 caracas FaxQueuer[3699]: Bad FIFO cmd '0' from client
May  8 12:06:20 caracas FaxQueuer[3699]: Bad FIFO cmd '3' from client 5324
May  8 12:06:20 caracas FaxQueuer[3699]: HylaClient::send: 5324: Cannot 
open FIFO: No such file or directory
May  8 12:06:20 caracas FaxQueuer[3699]: Bad FIFO cmd '0' from client
May  8 12:07:41 caracas FaxQueuer[3699]: Bad FIFO cmd 'c' from client
May  8 12:07:41 caracas FaxQueuer[3699]: Bad FIFO cmd '5' from client 383

I had to do a grep -v 'not found' because my syslog file contains a huge 
amount of lines like

May  8 09:23:15 caracas FaxQueuer[3699]: FIFO: JOB 27891 not found for 
msg "D22,1,212029,000034734,"docq/doc27933.pdf;01""

I don't know what that means, but apparently it's not important. I never 
experience problems form them.
> Well, you're in luck.  You can build debian packages right from CVS:
> 	http://cvs.hylafax.org/HylaFAX/?p=HylaFAX;a=commit;h=909cfff8fd757586cfdcf5f47092e7afab7712ae
>   
Great!

____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*