![]() |
I do indeed have libtiff 3.5.4 on the machine. Going to the URL mentioned below now. I will post the results if only to indicate success when I'm done. Thanks Bernd Proissl for the info! Tuesday, June 06, 2000 On Tuesday, June 06, 2000 sometime around 6:30:06 AM Bernd quoth: BP> a bug in hylafax leads to faxq eating up all CPU time: BP> hylafax is incompatible with libtiff 3.5.x. BP> Do you have 3.5.x installed on your system? BP> see BP> http://www.hylafax.org/patches/tiff-3.5-interfaces.patch BP> or downgrade to libtiff 3.4 BP> search the archives. BP> The password problem should be resolved by the mentioned etc/host (or BP> etc/host.conf) or BP> similar, search the archives also. BP> bernd >> -----Original Message----- >> From: hylafax-users-bounce@hylafax.org >> [mailto:hylafax-users-bounce@hylafax.org]On Behalf Of ben @ >> instantemail.net >> Sent: Tuesday, June 06, 2000 12:12 PM >> To: Damian Ivereigh >> Cc: hylafax-users@hylafax.org >> Subject: [hylafax-users] Re[2]: sendfax not sending faxes >> >> >> Umm, no. It used to work sending faxes from mx1 to members. Back >> around the first of the month mx1 began getting a password prompt for >> unknown reasons and failing because this all happens in a perl >> program and there's no way to enter a password non-interactively. At >> management's request I removed HylaFAX from the members machine and >> reinstalled it. This changed nothing about the problems HylaFAX is >> having. After some more logging configuration and investigation I have >> found `sendfax -n -v -d <localfaxnumber> <text_file>` hangs at >> (indented for legibility) >> Apply DisplayNumber rules to "<localfaxnumber>" >> --> return result "<localfaxnumber>" >> and at the end of the log is: >> Jun 6 09:59:47 members HylaFAX[16468]: <--- 213 CHOPTHRESHOLD >> set to 3. >> Jun 6 09:59:47 members HylaFAX[16468]: command: JPARM >> DOCUMENT /tmp/doc5.ps >> Jun 6 09:59:47 members HylaFAX[16468]: <--- 200 Added >> document /tmp/doc5.ps as docq/doc5.ps.13. >> Jun 6 09:59:47 members HylaFAX[16468]: command: JSUBM >> >> This all deals with operation on a single host. I'll play with the >> password problem coming from another host after I get the faxhost >> fixed. What should my next step be in "debugging" this? >> >> Tuesday, June 06, 2000 >> On Tuesday, June 06, 2000 sometime around 3:59:40 AM Damian quoth: >> >> DI> So let me get this straight. Everything works find when you >> run sendfax on members. If you run sendfax on mx1 (pointed at >> members via the hylafax protocol) then you get the password prompt. The >> DI> password prompt is your problem. >> >> DI> I have never tried to utilise the hylafax protocol between >> machines, so I am not sure I can give you much advice, however >> from what I know there is a file called /var/spool/fax/etc/hosts which >> DI> controls this. The man page for it is hosts(5F) (run 'man 5f hosts'). >> >> DI> I am hoping this will help you figure out what to do. >> >> DI> Damian >> >> DI> "ben @ instantemail.net" wrote: >> >> >> >> 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 >> BP> ____________________ HylaFAX(tm) Users Mailing List _______________________ BP> 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