Re: [hylafax-users] After upgrade "No assignable modem located"

[Ross Boylan <RossBoylan@xxxxxxxxxxxxxxxxxx>]

On Thu, Oct 09, 2003 at 01:51:02PM -0700, Lee Howard wrote:
> On 2003.10.09 12:12 Ross Boylan wrote:
> >I just upgraded from 4.1.2 to 4.1.7 on Debian.  After the upgrade I'm
> >unable to send faxes, and I see the message "No assignable modem
> >located" in the log.
> 
> Just a guess, but you may have multiple faxqs running.  I've had to 
> killall faxq sometimes when upgrading.  These days I always make sure 
> to 'service hylafax stop' before upgrading.
> 
> >I also noticed a recommendation in the documentation to rerun
> >faxaddmodem after an upgrade, which sort of suggests upgrades always
> >knock out available modems.
> 
> No.  The reason for that recommendation is so that upgraders benefit 
> from any enhancements in the config template files.
> 
> Lee.
> 
I just tried again, and it worked, but I'm not sure why.  I only had a
single faxq process running, but two faxgettys.  I shut down the
services and restarted them, and the conditions were the same.

I'm still suspicious that having two faxgetty's running targetting the
same port is not good.  Is that OK?  One is clearly from the inittab,
and the other is clearly from the Debian hylafax startup script.  I
see various log messages that seem to indicate contention:

# my comments about what I *think* is going on

# shut down the services.  Note two pid's for FaxGetty
# the shutdown script does a killall faxgetty
Oct 10 21:09:02 wheat FaxGetty[901]: CAUGHT SIGNAL 15
Oct 10 21:09:02 wheat FaxGetty[4678]: CAUGHT SIGNAL 15
Oct 10 21:09:02 wheat FaxGetty[4678]: CLOSE /dev/ttyS2
Oct 10 21:09:02 wheat FaxGetty[901]: CLOSE /dev/ttyS2
# Next line is inittab respawn, I think
Oct 10 21:09:03 wheat FaxGetty[5577]: OPEN /dev/ttyS2  HylaFAX (tm) Version 4.1.7
# I was using the modem for other things, probably leading to next line
Oct 10 21:09:03 wheat FaxGetty[5577]: /dev/ttyS2: Can not lock device.
Oct 10 21:09:03 wheat FaxGetty[5577]: STATE CHANGE: BASE -> LOCKWAIT (timeout 30)
# I closed my dialup session, maybe leading to the next
Oct 10 21:09:39 wheat FaxGetty[5577]: CAUGHT SIGNAL 15
Oct 10 21:09:39 wheat FaxGetty[5577]: CLOSE /dev/ttyS2
# Not sure where the next process comes from
Oct 10 21:09:39 wheat FaxGetty[5581]: OPEN /dev/ttyS2  HylaFAX (tm) Version 4.1.7
Oct 10 21:09:39 wheat FaxGetty[5581]: /dev/ttyS2: Can not lock device.
Oct 10 21:09:39 wheat FaxGetty[5581]: STATE CHANGE: BASE -> LOCKWAIT (timeout 30)
# restarted hylafax services
Oct 10 21:10:13 wheat FaxQueuer[5587]: servertracing = 0xFFFF (line 7)
Oct 10 21:10:13 wheat FaxQueuer[5587]: HylaFAX (tm) Version 4.1.7
Oct 10 21:10:13 wheat FaxQueuer[5587]: Copyright (c) 1990-1996 Sam Leffler
Oct 10 21:10:13 wheat FaxQueuer[5587]: Copyright (c) 1991-1996 Silicon Graphics, Inc.
# start script launches faxgetty, presumably
Oct 10 21:10:13 wheat FaxGetty[5591]: OPEN /dev/ttyS2  HylaFAX (tm) Version 4.1.7
# note next error
Oct 10 21:10:13 wheat FaxGetty[5591]: /dev/ttyS2: Can not lock device.
Oct 10 21:10:13 wheat FaxGetty[5591]: STATE CHANGE: BASE -> LOCKWAIT (timeout 30)
Oct 10 21:10:13 wheat FaxQueuer[5587]: FIFO RECV "+ttyS2:N1 (415) 550-1062"
Oct 10 21:10:13 wheat FaxQueuer[5587]: MODEM ttyS2: NUMBER 1 (415) 550-1062
Oct 10 21:10:13 wheat HylaFAX[5589]: HylaFAX INET Protocol Server: restarted.
Oct 10 21:10:13 wheat HylaFAX[5589]: HylaFAX Old Protocol Server: restarted.
Oct 10 21:10:14 wheat HylaFAX[5589]: HylaFAX SNPP Protocol Server: restarted.
Oct 10 21:11:52 wheat FaxGetty[5581]: MODEM U.S. ROBOTICS 56K VOICE INT V4.9.1 5601/
Oct 10 21:11:52 wheat FaxGetty[5581]: STATE CHANGE: LOCKWAIT -> RUNNING (timeout 30)
Oct 10 21:11:52 wheat FaxQueuer[5587]: FIFO RECV "+ttyS2:RPc0f9c703:ff"
Oct 10 21:11:52 wheat FaxQueuer[5587]: MODEM ttyS2: READY, capabilities Pc0f9c703:ff
Oct 10 21:12:22 wheat FaxGetty[5581]: STATE CHANGE: RUNNING -> LOCKWAIT (timeout 30)
Oct 10 21:12:26 wheat FaxGetty[5591]: MODEM U.S. ROBOTICS 56K VOICE INT V4.9.1 5601/
Oct 10 21:12:26 wheat FaxGetty[5591]: STATE CHANGE: LOCKWAIT -> RUNNING (timeout 30)
Oct 10 21:12:26 wheat FaxQueuer[5587]: FIFO RECV "+ttyS2:RPc0f9c703:ff"
Oct 10 21:12:26 wheat FaxQueuer[5587]: MODEM ttyS2: READY, capabilities Pc0f9c703:ff
Oct 10 21:12:56 wheat FaxGetty[5591]: ANSWER: Can not lock modem device
Oct 10 21:12:56 wheat FaxGetty[5591]: STATE CHANGE: RUNNING -> LOCKWAIT (timeout 30)
Oct 10 21:12:56 wheat FaxQueuer[5587]: FIFO RECV "+ttyS2:U"
Oct 10 21:12:56 wheat FaxQueuer[5587]: MODEM ttyS2: BUSY
# still complaints

Then I sent the fax, producing many more entries.  I can provide them
if they would help.

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