Thanks for you quick response Nick.
This is the first time configuration for HylaFAX. I can talk to the modem via minicom. I am able to do atdt 3055417209 and I hear the modem requesting a tone.
This is a partial on messages:
Nov 20 10:18:12 Hermes FaxQueuer[4924]: HylaFAX (tm) Version 4.4.4
Nov 20 10:18:12 Hermes FaxQueuer[4924]: Copyright (c) 1990-1996 Sam Leffler
Nov 20 10:18:12 Hermes FaxQueuer[4924]: Copyright (c) 1991-1996 Silicon Graphics, Inc.
Nov 20 10:18:13 Hermes HylaFAX[4927]: HylaFAX INET: bind (port 4559): Address already in use
Nov 20 10:18:13 Hermes HylaFAX[4927]: HylaFAX INET: Unable to init server, trying again in 5 seconds.
Nov 20 10:18:18 Hermes HylaFAX[4927]: HylaFAX INET: bind (port 4559): Address already in use
Nov 20 10:18:18 Hermes HylaFAX[4927]: HylaFAX INET: Unable to init server, trying again in 10 seconds.
Nov 20 10:18:28 Hermes HylaFAX[4927]: HylaFAX INET: bind (port 4559): Address already in use
Nov 20 10:18:28 Hermes HylaFAX[4927]: HylaFAX INET: Unable to init server, trying again in 15 seconds.
Nov 20 10:18:43 Hermes HylaFAX[4927]: HylaFAX INET: bind (port 4559): Address already in use
Nov 20 10:18:43 Hermes HylaFAX[4927]: HylaFAX INET: Unable to init server, trying again in 20 seconds.
Nov 20 10:19:03 Hermes HylaFAX[4927]: HylaFAX INET: bind (port 4559): Address already in use
Nov 20 10:19:03 Hermes HylaFAX[4927]: HylaFAX INET: Unable to init server, trying again in 25 seconds.
Nov 20 10:19:04 Hermes FaxGetty[4948]: usage: faxgetty [-c config-item] [-q queue-dir] [-Dpx] modem-device
Nov 20 10:19:28 Hermes HylaFAX[4927]: HylaFAX INET: bind (port 4559): Address already in use
Nov 20 10:19:28 Hermes HylaFAX[4927]: HylaFAX INET: Unable to init server, trying again in 30 seconds.
Nov 20 10:19:58 Hermes HylaFAX[4927]: HylaFAX INET: bind (port 4559): Address already in use
Nov 20 10:19:58 Hermes HylaFAX[4927]: HylaFAX INET: Unable to init server, trying again in 35 seconds.
Nov 20 10:20:33 Hermes HylaFAX[4927]: HylaFAX INET: bind (port 4559): Address already in use
Nov 20 10:20:33 Hermes HylaFAX[4927]: HylaFAX INET: Unable to init server, trying again in 40 seconds.
Nov 20 10:21:13 Hermes HylaFAX[4927]: HylaFAX INET: bind (port 4559): Address already in use
Nov 20 10:21:13 Hermes HylaFAX[4927]: HylaFAX INET: Unable to init server, trying again in 45 seconds.
Nov 20 10:21:58 Hermes HylaFAX[4927]: HylaFAX INET: bind (port 4559): Address already in use
Nov 20 10:21:58 Hermes HylaFAX[4927]: HylaFAX INET: Unable to init server, giving up after 10 tries.
Nov 20 10:29:38 Hermes FaxGetty[4975]: usage: faxgetty [-c config-item] [-q queue-dir] [-Dpx] modem-device
Nov 20 11:13:08 Hermes gconfd (root-5049): starting (version 2.22.0), pid 5049 user 'root'
Nov 20 11:13:08 Hermes gconfd (root-5049): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Nov 20 11:13:08 Hermes gconfd (root-5049): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1
Nov 20 11:13:08 Hermes gconfd (root-5049): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Nov 20 11:47:19 Hermes FaxGetty[5229]: OPEN /dev/ttys.modem HylaFAX (tm) Version 4.4.4
Nov 20 11:47:19 Hermes FaxGetty[5229]: /dev/ttys.modem: Can not open modem (No such file or directory)
Nov 20 11:47:49 Hermes FaxGetty[5229]: CAUGHT SIGNAL 2
Nov 20 11:47:49 Hermes FaxGetty[5229]: CLOSE /dev/ttys.modem
Nov 20 11:47:59 Hermes FaxGetty[5231]: OPEN /dev/ttysACM0 HylaFAX (tm) Version 4.4.4
Nov 20 11:47:59 Hermes FaxGetty[5231]: /dev/ttysACM0: Can not open modem (No such file or directory)
Nov 20 11:48:29 Hermes FaxGetty[5231]: /dev/ttysACM0: Can not open modem (No such file or directory)
Nov 20 11:48:59 Hermes FaxGetty[5231]: /dev/ttysACM0: Can not open modem (No such file or directory)
Nov 20 11:48:59 Hermes FaxGetty[5231]: Unable to setup modem on /dev/ttysACM0; giving up after 2 attempts
Nov 20 11:48:59 Hermes FaxQueuer[4924]: MODEM /dev/ttysACM0 appears to be wedged
Nov 20 11:48:59 Hermes FaxQueuer[4924]: MODEM WEDGED: bin/wedged "ttysACM0" "/dev/ttysACM0"
Nov 20 11:48:59 Hermes FaxGetty[5231]: CLOSE /dev/ttysACM0
Nov 20 11:49:00 Hermes FaxQueuer[4924]: NOTIFY exit status: 0 (5232)
Nov 20 12:19:16 Hermes yum: Updated: libxml2-2.7.2-2.fc9.i386
Nov 20 12:19:19 Hermes yum: Updated: libxml2-python-2.7.2-2.fc9.i386
Nov 20 12:19:30 Hermes yum: Updated: libxml2-devel-2.7.2-2.fc9.i386
Nov 20 12:26:04 Hermes kernel: usb 1-1: USB disconnect, address 2
Nov 20 12:26:06 Hermes kernel: usb 1-1: new full speed USB device using ohci_hcd and address 3
Nov 20 12:26:07 Hermes kernel: usb 1-1: configuration #1 chosen from 1 choice
Nov 20 12:26:07 Hermes kernel: cdc_acm 1-1:1.0: ttyACM0: USB ACM device
Nov 20 12:26:07 Hermes kernel: usb 1-1: New USB device found, idVendor=0baf, idProduct=0303
Nov 20 12:26:07 Hermes kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 20 12:26:07 Hermes kernel: usb 1-1: Product: USB Modem
Nov 20 12:26:07 Hermes kernel: usb 1-1: Manufacturer: U.S.Robotics
Nov 20 12:26:07 Hermes kernel: usb 1-1: SerialNumber: 0000002
Nov 20 14:13:07 Hermes FaxGetty[5648]: OPEN /dev/ttyACM0 HylaFAX (tm) Version 4.4.4
Nov 20 14:13:25 Hermes FaxGetty[5648]: /dev/ttyACM0: Can not initialize modem.
Nov 20 14:14:59 Hermes FaxGetty[5648]: Unable to setup modem on /dev/ttyACM0; giving up after 2 attempts
Nov 20 14:14:59 Hermes FaxQueuer[4924]: MODEM /dev/ttyACM0 appears to be wedged
Nov 20 14:14:59 Hermes FaxQueuer[4924]: MODEM WEDGED: bin/wedged "ttyACM0" "/dev/ttyACM0"
Nov 20 14:14:59 Hermes FaxGetty[5648]: CLOSE /dev/ttyACM0
Nov 20 14:14:59 Hermes FaxQueuer[4924]: NOTIFY exit status: 0 (5651)
[root@Hermes log]#
I did a netstat and found that port 4559 is not being used. This ios the only thing I see that could be causing this but I don't know since I very new to this
HylaFAX and Fedora.
Nov 20 11:47:19 Hermes FaxGetty[5229]: /dev/ttys.modem: Can not open modem (No such file or directory)
If this were to be the cause how can I have the system create this?
Thanks,
Ramon
From: Nick Couchman [mailto:Nick.Couchman@xxxxxxxxx]
Sent: Thursday, November 20, 2008 3:00 PM
To: rfm@xxxxxxxxxxxxxxxxxx
Cc: hylafax-users@xxxxxxxxxxx
Subject: Re: [hylafax-users] How to un-wedge a modem
You need to figure out why it is wedged, first. I use a VM and a modem attached via a Serial-over-IP (Digi) device, and mine gets wedged occasionally when there are network problems or the Digi device has a problem. Also, when I first boot the VM, I have to reconfigure the devices a little bit as the way Digi configures them doesn't agree with Hylafax. So, I get that message and I just have to examine things in the "Serial-over-IP chain" to make sure everything is functioning properly.
Some things to check are:
- Does another process have the modem open? lsof can help you here...
- Is the modem functioning properly, or does it need to be reset? Minicom can be useful for figuring this out, after shutting down the faxgetty process.
- Go to the messages file and check and see if there is anything being reported in there as to why the modem is wedged - is it responding with an error code, not responding at all, etc.?
- Are permissions correctly on the /dev/ttyACM0 device such that the user running faxgetty (uucp on my system) can read and write to the device?
I assume this has been working for you before, but has recently stopped working? Have you rebooted, yet? If you have an internal modem this may be the only way to get a reset on it - I have to power cycle my external modem occasionally.
-Nick
-----Original Message-----
From: Ramon F. McDougall <rfm@xxxxxxxxxxxxxxxxxx>
To: 'Hylafax Users' <hylafax-users@xxxxxxxxxxx>
Subject: Re: [hylafax-users] How to un-wedge a modem
Date: Thu, 20 Nov 2008 14:47:34 -0500
Good Afternoon,
Does anyone know ho to un-wedge a modem. I am getting this from HylaFAX:
To: FaxMaster@xxxxxxxxxxxxxxxxxxxxx
From: The HylaFAX Receive Agent <fax@xxxxxxxxxxxxxxxxxxxxx>
Subject: modem on /dev/ttyACM0 appears wedged
Thanks in advance,
Ramon
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.
HylaFAX The world's
most advanced open source fax server