HylaFAX The world's most advanced open source fax server

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

[hylafax-users] Re[2]: sendfax not sending faxes



In the end yes the faxes will originate (as far as hylafax is
concerned) on MX1, but the sendfax problem currently (which I want to
get fixed before I tackle the PASS problem) is on 'localhost'
(members). If I try to originate a fax from MX1 and have it sent to
members (via the hylafax protocol) it prompts for a password and I
don't have any idea what may have caused that change. Currently on
members I have this:

members: faxstat -s
HylaFAX scheduler on localhost: Running
Modem cuaa0 (+1.828.258.3944): Waiting for modem to come free
Modem cuaa1 (+1.828.258.3944): Running and idle

JID  Pri S  Owner Number       Pages Dials     TTS Status
8    127 R    ben 2583944       0:0   0:12
10   127 B    ben 2583944       0:0   0:12         Blocked by concurrent job

members: ps ax | grep "[f]ax"
19889  ??  Is     0:00.02 /usr/local/sbin/faxq
19895  ??  R    149:18.18 /usr/local/sbin/faxq
19917  ??  S      0:00.42 /usr/local/sbin/faxgetty /dev/cuaa0 cuaa0
19920  ??  I      0:00.04 /usr/local/sbin/faxgetty /dev/cuaa1 cuaa1
49562  ??  Is     0:00.04 hfaxd -s 444 -i 4559

: cat /var/spool/lock/LCK..cuaa0
     19889

   Thus the faxq process running at PID 19889 (without over 50 days
worth of processing time) has the modem locked as if it's about to
send a fax, but nary a peep doth issue from said cuaa0 and I can't
find any trace of communications with the modem. Both of these jobs
were generated with sendfax -n [-v] -d AAABBBB <some_text_file>. 


The sendpage command actually dials the pager number, but it's just a
plain old numeric pager so it complains about "no carrier" which is
fine for now.
Also...
members: cat /var/spool/fax/etc/hosts
localhost
127.0.0.1
*.mydom1$
*.mydom2$
*.mydom3$

There are 3 domains on the local subnet and I will eventually want all
three of them to be able to send faxes.


                                                 Monday, June 05, 2000
On Monday, June 05, 2000 sometime around 9:38:13 PM Damian quoth:

DI> Do the faxes originate on "mx1" and then get sent to machine "members". How do they get there? Are you using rsh or something like that?

DI> Damian

DI> "ben @ instantemail.net" wrote:
>> 
>> hylafax-users,                 Monday, June 05, 2000
>> 
>>   I work for a company that uses hylafax to deliver faxes (hmm who
>> woulda thought?) and recently (last week) the hylafax process on a
>> machine called members began prompting the machine called MX1 for a
>> password where it never did before. I don't have any idea why this
>> happened and I could use some pointers.
>>    In an attempt to "fix" the situation I removed hylafax from the
>> members machine and reinstalled it to no avail. Currently sendfax
>> appears to complete normally but the document never makes it to the
>> modem so I'm thinking something is awry in the document preparation
>> process. The jobs get sent to the docq directory and I have noticed
>> that two faxq processes exist at some points (until I kill the all the
>> faxq/hfaxd servers and restart them) with one of the faxq processes
>> chewing up some serious resources.
>>    I've never used hylafax or ghostscript (or any other postscript
>> application) before so this is all a learning process. I looked around
>> on the website but I can't find help there for my problem.
>>    The machines are FreeBSD 3.4-RELEASE i386's and are running hylafax
>> v4.0pl2. The modems are MultiTech 28.8 Data/FAX modems. Can someone
>> shed some light on this problem (and hopefully offer some guidance)
>> for me?
>> 
>> --Ben
>> mailto:ben@instantemail.net
>> 
>> ____________________ HylaFAX(tm) Users Mailing List _______________________
>>  To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null




--Ben
mailto:ben@instantemail.net




____________________ HylaFAX(tm) Users Mailing List _______________________
 To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null




Project hosted by iFAX Solutions