![]() |
Hello, all... I haven't fixed the problem I posted earlier, because I've got a worse one... Situation: HylaFAX 4.0pl1 (and pl0), Solaris 2.4, gcc 2.7.2, Multitech 2834ZDX 28.8 fax modem. Everything was working -- I could send and receive faxes, although faxes sent from the server had repeated and squished pages. Then, last weekend, something happened, but I don't know what. Now, the fax server times out when trying to talk to the modem. A faxstat gets me this, all the time: HylaFAX scheduler on main.techiesinc.com: Running Modem cua/a (+1.610.398.2910): Initializing server It never gets past initialization, and the server log looks like it's timing out trying to talk to the modem: Mar 4 18:02:41 main FaxQueuer[10472]: HylaFAX (tm) Version 4.0pl0 Mar 4 18:02:41 main FaxQueuer[10472]: HylaFAX (tm) Version 4.0pl0 Mar 4 18:02:41 main FaxQueuer[10472]: Copyright (c) 1990-1996 Sam Leffler Mar 4 18:02:41 main FaxQueuer[10472]: Copyright (c) 1990-1996 Sam Leffler Mar 4 18:02:41 main FaxQueuer[10472]: Copyright (c) 1991-1996 Silicon Graphics, Inc. Mar 4 18:02:41 main FaxQueuer[10472]: Copyright (c) 1991-1996 Silicon Graphics, Inc. Mar 4 18:03:16 main FaxGetty[10485]: OPEN /dev/cua/a Mar 4 18:03:16 main FaxGetty[10485]: OPEN /dev/cua/a Mar 4 18:03:17 main FaxGetty[10485]: Purge stale UUCP lock /var/spool/locks/LK.032.029.131072 Mar 4 18:03:17 main FaxGetty[10485]: Purge stale UUCP lock /var/spool/locks/LK.032.029.131072 Mar 4 18:03:17 main FaxGetty[10485]: DELAY 2600 ms Mar 4 18:03:17 main FaxGetty[10485]: DELAY 2600 ms Mar 4 18:03:20 main FaxGetty[10485]: <-- [15:ATE0V1Q0S0=0H0\r] Mar 4 18:03:20 main FaxGetty[10485]: <-- [15:ATE0V1Q0S0=0H0\r] Mar 4 18:03:25 main FaxGetty[10485]: MODEM <Timeout> Mar 4 18:03:25 main FaxGetty[10485]: MODEM <Timeout> Mar 4 18:03:25 main FaxGetty[10485]: DELAY 2600 ms Mar 4 18:03:25 main FaxGetty[10485]: DELAY 2600 ms Mar 4 18:03:38 main FaxQueuer[10472]: QUIT Mar 4 18:03:38 main FaxQueuer[10472]: QUIT This behavior persists through a reboot, a reinstall, installation of patch01 to HylaFAX, and repeated restarts of the server. I even blew away /var/spool/fax and reinstalled it, to make sure it wasn't some flag that I couldn't find somewhere. I've also checked modem cabling and power-cycled the modem several times. So, I thought it was the modem, but I can tip out to it with no problems, as long as faxgetty isn't running. Isn't faxgetty supposed to get out of the way if I want to tip out? It doesn't matter if it isn't, since I don't plan to use this modem for anything but fax, but I'm looking for clues here. When I try to do a faxaddmodem on that port, I get the following message: Sorry, the device is currently in use by another program. But, God help me, I can't see what other program (faxgetty is not running, nor do I have a ttymon running on that port). This problem seems to have started when a voice call came through on the fax line (I think -- it might have been a failed fax call; I wasn't here at the time). The server went into a "receiving facsimile" status and stayed there for over a day. Ever since then, it's been unable to talk to the modem. I saw in the troubleshooting guide that losing track of its FIFO special file could make faxq confused. I may have removed FIFO.cua_a while trying to debug this problem without stopping the server first. But would that problem survive a reboot and an fsck?? I've been tearing my hair out over this one for several days now, not to mention poring over the FAQ and the mailing list archive, but I can't make any headway here. Someone please help! Thanks in advance, oh, and please reply directly to me -- I don't subscribe to the list, I just read the archives. I could include more information in this e-mail, but it's long enough already... Leslie Dreyer Kalra Techies, Inc. lbd@techiesinc.com