Re: flexfax: Modem is wedged and HylaFAX is stuck

[Matthias.Apitz@SOFTCON.de]

Phil Watkinson wrote:

[NB: Cc: ist set to hylafax-testers@sisis.de]
    
    
    Hi,
    
    After a year of reliable service with v4.0pl1 and ReHat 4.0, on
    Friday afternoon,(the worst possible time) on day 2 of the new beta,
    the modem was reported as wedged. I have :

Please do not discuss issues of new beta code in the public
mailing list for HylaFAX.
    
     * Read the documentation and checked the archives
     * Bumped up the ServerTracing & SessionTracing values to 32779 in
       the config.cua1 file.
     * Soft reboot of the system
     * Ensured that the modem was responding and working with PPP
     * Did a total power-off reboot of the system, and rechecked modem
    
    and HylaFAX (faxq?) seems unwilling to process any jobs. Faxstat says:
    
    	HylaFAX scheduler on derrick.elgro.co.uk: Running
    	Modem cua1 (722304): Running and idle
    
    and yet all the send queue jobs have a status of W (waiting).
    
    The important part of the wedged man page is as follows :
        The wedged script sends electronic mail to the FaxMaster alias
        and attempts to disable any getty processes spawned by the
        init(8C) process.  In addition the faxq(8C) process  auto-
        matically disables use of the modem for servicing outbound jobs.
    
    The script tries to comment out the faxgetty line in the inittab file,
    which I've checked and it is running okay. My question is how does
    faxq disable the modem? And how do I re-enable it again?
    
    I've tried the 'faxstate -s ready cua1' several times without luck;
    and I'm beginning to wonder if I am missing the obvious. The few entries
    in the 'messages' file (nothing in the log directory) seems to show
    that HylaFAX (or a part of HylaFAX?) cannot find the modem :-
    
    Dec 15 09:19:07 derrick FaxQueuer[220]: 
    	JOB 19 (ready dest +04401205725015 pri 127 tts 0:00 
    	killtime 2:29:35): Unable to assign modem cua1 (cannot lock)
    Dec 15 09:19:07 derrick FaxQueuer[220]: 
    	JOB 19 (ready dest +04401205725015 pri 127 tts 0:00 
    	killtime 2:29:35): No assignable modem located
	....

Please check the source and try to find out why faxq(1M) can't lock
the device.

	matthias