Re: [hylafax-users] "Waiting for modem to come ready" another
Lee Howard
> I am contacting you because I have problems with iaxmodem and hylafax.
>
> Sometimes it goes into some modem status "waiting to be ready" and does
> not change state. These same modem worked just before.
>
> The only solution I found for now is to reboot the service iaxmodem and
> hylafax.
>
> Looking at the logs, I perceived that the modem has a problem:
>
> "Unable to Pass The full buffer onto the Device queue. 1 bytes of 4094
> written: Resource temporarily unavailable"
>
> If anyone has an idea to help me.
>
> The version :
> iaxmodem-0.1.14-1
> hylafax-4.3.3-7rhel5
> Asterisk 1.4.24
I think that you should upgrade iaxmodem to 1.2.0. I suspect that your
old iaxmodem is crashing.
Thanks,
Lee.
____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-us...@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail sa...@ifax.com.*
Lee Howard
> Find the process number of the corresponding ttyIAX<num>
>
> # kill -9 <process number>
>
> This will kill the process for the corresponding wedged modem. If your system is set up properly, your modem will respawn automatically within seconds.
Modern versions of iaxmodem, when run in "daemon" mode will restart the
modems by sending SIGHUP to the modem. If you do a 'kill -9' to a modem
in daemon mode then it won't respawn.
Get the pid of the iaxmodem process:
lsof | grep `ls -l /dev/ttyIAX00 | sed 's/.* //'` | grep "^iaxmodem" |
sed -e 's/^iaxmodem *//' -e 's/ .*//'
Send it SIGHUP:
kill -HUP <pid>
Jonathan Recly
Le 19/11/2010 17:26, Alcorn, Brian C a écrit :
Jonathan,
This indicates that your modem is "wedged". There is a wedged script that can be edited to automate the recovery of said modem, however I haven't played with it much.
To manually recover without a reboot, I do the following:
# faxstat (this will display the modems and their states)
Identify the wedged modem, which will remain at "waiting for modem to come ready" or something of the like. Since you are using IAX, I believe your modems would be named as ttyIAX<num>. make note of which number modem is wedged.
# ps -aef | grep iaxmodem
Find the process number of the corresponding ttyIAX<num>
# kill -9 <process number>
This will kill the process for the corresponding wedged modem. If your system is set up properly, your modem will respawn automatically within seconds. Use the faxstat command to monitor and verify that the modem comes back up.
***Often there is no logical explanation for why a modem wedges. Spending time attempting to identify the root cause is largely futile; instead, having a proven recovery method is far better an approach. I hope this helps.
-Brian
I every Body
First, thanks for your help. :)
Lee : I tested the update iaxmodem. But the result was unsatisfactory. The modem could not send faxes.
Brian : I test your method. But I have a litle problem. Command ps -aef | grep iaxmodem return a list of process like /usr/sbin/iaxmodem .... and there are not difference betwen every process (except PID) ..... to script patch, it's not very easy :)
Lee Howard
> Le 27/11/2010 03:57, Lee Howard a écrit :
>>
>> Jonathan Recly wrote:
>> > Lee : I tested the update iaxmodem. But the result was unsatisfactory.
>> > The modem could not send faxes.
>>
>> work from.
>>
>> Thanks,
>>
>> Lee.
>>
>
> I Lee,
>
> The recipient tel me two bad result's messages :
>
> 1 width : RSRPEC error/got DCN; Giving up after 3 attempts to send
> same page
> Other message said : Failure to train remote modem at 2400 bps or
> minimum speed; Giving up after 3 attempts to send same page
>
> The physical fax explain that transmission isn't complete ....
>
> The same fax sent width old iaxmodem version is ok ....
Okay, so go back through the iaxmodem releases release-by-release and
find out which release was the last release that worked.