HylaFAX The world's most advanced open source fax server

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

[hylafax-users] Modem wedged / "initializing server" problem



Hello.

I run a hylafax server (used for receiving faxes only) that has been
running successfully for almost two months now.  When I came in this
morning, the logs show that we have not received any faxes for two days. 
The server has a 4-port internal modem, and there seems to be a problem
with the modem on port "a", shown by faxstat alternating between
"initializing server" and "waiting for modem to come ready."

A search of the archives showed that other people have had this "modem
wedged" problem, but I didn't find any clear answer as to what could be
causing this.  Many of the previous posts have suggested checking
configuration settings, but in my case, the server has been up and running
properly for a while now, so I can't think of any settings that would have
changed to cause this.

The details:

faxstat alternates between

HylaFAX scheduler on localhost.localdomain: Running
Modem ttyMU1a (+1.XXX.XXX.XXXX): Initializing server
Modem ttyMU1b (+1.XXX.XXX.XXXX): Running and idle
Modem ttyMU1c (+1.XXX.XXX.XXXX): Running and idle
Modem ttyMU1d (+1.XXX.XXX.XXXX): Running and idle

and

HylaFAX scheduler on localhost.localdomain: Running
Modem ttyMU1a (+1.XXX.XXX.XXXX): Waiting for modem to come ready
Modem ttyMU1b (+1.XXX.XXX.XXXX): Running and idle
Modem ttyMU1c (+1.XXX.XXX.XXXX): Running and idle
Modem ttyMU1d (+1.XXX.XXX.XXXX): Running and idle

Upon restarting the faxgetty processes (`killall faxgetty`),
/var/log/messages shows:
Nov  7 10:31:48 localhost FaxGetty[6299]: CAUGHT SIGNAL 15
Nov  7 10:31:48 localhost FaxGetty[6300]: CAUGHT SIGNAL 15
Nov  7 10:31:48 localhost FaxGetty[6299]: CLOSE /dev/ttyMU1c
Nov  7 10:31:48 localhost FaxGetty[6300]: CLOSE /dev/ttyMU1d
Nov  7 10:31:48 localhost FaxGetty[6301]: CAUGHT SIGNAL 15
Nov  7 10:31:48 localhost FaxGetty[6301]: CLOSE /dev/ttyMU1b
Nov  7 10:31:48 localhost FaxGetty[7221]: CAUGHT SIGNAL 15
Nov  7 10:31:48 localhost FaxGetty[7221]: CLOSE /dev/ttyMU1a
Nov  7 10:31:48 localhost FaxGetty[7753]: OPEN /dev/ttyMU1a  HylaFAX (tm)
Version 4.2.2
Nov  7 10:31:48 localhost FaxGetty[7753]: /dev/ttyMU1a: Can not lock device.
Nov  7 10:31:48 localhost FaxGetty[7759]: OPEN /dev/ttyMU1c  HylaFAX (tm)
Version 4.2.2
Nov  7 10:31:48 localhost FaxGetty[7758]: OPEN /dev/ttyMU1d  HylaFAX (tm)
Version 4.2.2
Nov  7 10:31:48 localhost FaxGetty[7760]: OPEN /dev/ttyMU1b  HylaFAX (tm)
Version 4.2.2
Nov  7 10:31:59 localhost FaxGetty[7759]: MODEM LT V.92 1.0 MT5634SMI-V92
DATA/FAX MODEM VERSION 1.32D LT V.92 1.0 MT5634SMI-V92 Data/Fax Modem
Version 1.32d/
Nov  7 10:31:59 localhost FaxGetty[7758]: MODEM LT V.92 1.0 MT5634SMI-V92
DATA/FAX MODEM VERSION 1.32D LT V.92 1.0 MT5634SMI-V92 Data/Fax Modem
Version 1.32d/
Nov  7 10:31:59 localhost FaxGetty[7760]: MODEM LT V.92 1.0 MT5634SMI-V92
DATA/FAX MODEM VERSION 1.32D LT V.92 1.0 MT5634SMI-V92 Data/Fax Modem
Version 1.32d/
Nov  7 10:32:18 localhost FaxGetty[7753]: Purge stale UUCP lock
/var/lock/LCK..ttyMU1a
Nov  7 10:33:27 localhost FaxGetty[7753]: /dev/ttyMU1a: Can not initialize
modem.
Nov  7 10:36:44 localhost FaxGetty[7753]: Unable to setup modem on
/dev/ttyMU1a; giving up after 2 attempts
Nov  7 10:36:44 localhost FaxGetty[7753]: CLOSE /dev/ttyMU1a
Nov  7 10:36:44 localhost FaxQueuer[6251]: MODEM /dev/ttyMU1a appears to
be wedged
Nov  7 10:36:44 localhost FaxQueuer[6251]: MODEM WEDGED: bin/wedged
"ttyMU1a" "/dev/ttyMU1a"
Nov  7 10:36:44 localhost FaxGetty[8345]: OPEN /dev/ttyMU1a  HylaFAX (tm)
Version 4.2.2
Nov  7 10:36:44 localhost FaxQueuer[6251]: NOTIFY exit status: 0 (8344)

Server details:
OS: Red Hat Linux 3.2.3-49
hylafax version: 4.2.2
modem: MultiTech 4-port ISI MultiModem

I have tried restarting the server with faxsetup and even restarting the
machine, all with no success.  Another suggestion I have seen is to run
minicom.  I can do this, but I'm not really sure what I'm looking for.

I'm at a loss as to why this would suddenly stop working.  If anyone has
any ideas or suggestions, I would appreciate it.  Please let me know if I
can provide more information that may be useful.

Thanks,
Jeff Cleary




____________________ 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*




Project hosted by iFAX Solutions