Re: [hylafax-users] frustrated... trying to run a faxserver

[Siri Vias Khalsa <sirivias.khalsa@xxxxxxxxxx>]

Title: [hylafax-users] frustrated... trying to run a faxserver

First - you need to have the right modem command settings in config.ttyS1. You can copy them from an appropriate file in config that matches your modem. What faxaddmodem does is try to detect and set that up for you. Cant tell you which one without knowing what modem you have.
Second - ensure that the modem you are using is on ttyS1 (you said treat you like a newbie) use minicom to make sure.
Third - make sure faxgetty is running in init. Cant tell you how to do that without knowing what distro you are using. you need to have init run "faxgetty ttyS0" and respawn when it quits. This is the actual program that talks to the modem and it sets up the FIFO.ttyS1 pipe. Searching the archives should tell you what you need here a few times over.

When all of the above are completed, running faxstat should show something like:
HylaFAX scheduler on xxx: Running
Modem ttyS1 (+1.xxx.xxx.xxxx): Running and idle

-Siri Vias


On Fri, 2009-01-30 at 10:47 -0600, jimmysubman@xxxxxxxxx wrote:
>     Hello guys, I am trying to setup a hylafax server for couple of days
>     now, but without any success. I will be very greatfull if someone
>     could explain/solve my problem. And please try to talk to me like to
>     4yo beginner linux user :)
>     First I had exactly the same problem as the guy who posted his thread here :
>     http://www.hylafax.org/archive/2001-04/msg00010.php
>     
>     same sympthoms. After manually copying the configuration file
>     config.ttyS1 to fax/etc and hylafax/etc directory something has
>     changed - faxsetup command is giving me following output:
>     
>     Setup program for HylaFAX (tm) 4.3.1.
>     
>     Created for i686-pc-linux-gnu on Sun Jan  7 09:32:03 CET 2007.
>     
>     Reading cached parameters from /var/spool/hylafax/etc/setup.cache.
>     
>     Checking system for proper server configuration.
>     
>     
>     Warning: /etc/hylafax/vgetty-link does not exist or is not an
>     executable program !
>     
>     The file:
>     
>        /etc/hylafax/vgetty-link
>     
>     does not exist or this file is not an executable program.  The
>     HylaFAX software optionally uses this program and the fact that
>     it does not exist on the system is not a fatal error.  If the
>     program resides in a different location and you do not want to
>     install a symbolic link for /etc/hylafax/vgetty-link that points to your program
>     then you must reconfigure and rebuild HylaFAX from source code.
>     
>     Make /var/spool/hylafax/bin/ps2fax a link to /var/spool/hylafax/bin/ps2fax.gs.
>     
>     
>     Make /var/spool/hylafax/bin/pdf2fax a link to /var/spool/hylafax/bin/pdf2fax.gs.
>     
>     Update /var/spool/hylafax/status/any.info.
>     
>            HylaFAX configuration parameters are:
>     
>            [1] Init script starts faxq:            yes
>            [2] Init script starts hfaxd            yes
>            [3] Start old protocol:                 no
>            [4] Start paging protocol:              no
>     Are these ok [yes]?
>     
>     Modem support functions written to /var/spool/hylafax/etc/setup.modem.
>     Configuration parameters written to /var/spool/hylafax/etc/setup.cache.
>     
>     Restarting HylaFAX server processes.
>     Should I restart the HylaFAX server processes [yes]?
>     
>     /etc/init.d/hylafax start
>     Not starting HylaFAX daemons since they are already running.
>     
>     You do not appear to be using faxgetty to notify the HylaFAX scheduler
>     about new modems and/or their status.  This means that you must use the
>     faxmodem program to inform the new faxq process about the modems you
>     want to have scheduled by HylaFAX.  Beware that if you have modems that
>     require non-default capabilities specified to faxmodem then you should
>     read faxmodem(8) manual page and do this work yourself (since this
>     script is not intelligent enough to automatically figure out the modem
>     capabilities and supply the appropriate arguments).
>     
>     Should I run faxmodem for each configured modem [yes]?
>     
>     Done verifying system setup.
>     Updating /etc/hylafax/setup.cache from /var/spool/hylafax/etc/setup.cache.
>     Updating /etc/hylafax/setup.modem from /var/spool/hylafax/etc/setup.modem.
>     /var/spool/hylafax
>     debian:/var/spool/hylafax/etc#
>     
>     
>     
>     
>     Earlier faxaddmodem was initialized by faxsetup, without any response
>     from the modem. But the modem was usable, i could ring to any number
>     from it using the cutecom or minicom.
>     When I try to send a fax, I am receiving the following message :
>     
>     460 Failed to submit job 5: Unable to open scheduler FIFO: No such
>     device or address.
>     
>     And similar message when trying to send a fax through windows hylafax client.
>     Here are some file listings on my machine:
>     
>     
>     
>     
>     debian:/var/spool/fax/config# ls
>     att-dataport                  gvc-288          rc32acl-1
>     att-dataport-2                gvc-288-2        rockwell-k56
>     att-dataport-2.0              hayes            rockwell-rc
>     att-dpexpress-2               i4l_class1       rockwell-rc (kopia)
>     cirrus                        i4l_class2       sierra
>     class1                        intel-400e       skel
>     class1.0                      lucent           telebit-qblazer
>     class2                        lucent-isa       telebit-t3000
>     class2.0                      lucent-mt-2      telebit-wb
>     class2.1                      lucent-mt-20     topic
>     davicom-2                     lucent-mt-21     tricom2842
>     digi                          moto-288         uds-fastalk
>     digi-2                        mt-1432          umc92144
>     digi-20                       nuvo-voyager     umc9624
>     dsi-scout+                    ppi-pm14400fxmt  usr-2.0
>     eicon                         ppi-pm14400fxsa  usr-rts
>     eicon-2                       prometheus       usr-xon
>     elsa-microlink-56k-basic-2.0  rc144ac          zyxel-1496e
>     etc                           rc144ac-1        zyxel-1496e-1
>     e-tech                        rc288dpi         zyxel-1496e-2.0
>     everex-2496d                  rc288dpi-1       zyxel-2864
>     exar                          rc32acl
>     debian:/var/spool/fax/config#
>     
>     
>     debian:/var/spool/fax/etc# ls
>     config        dialrules.europe  faxmail.ps  lutRS18.pcf  templates
>     config.ttyS1  dialrules.sf-ba   getty-link  pagesizes    typerules
>     cover.templ   egetty-link       hfaxd.conf  setup.cache  zipetc.tar
>     dialrules     faxcover.ps       hyla.conf   setup.modem
>     debian:/var/spool/fax/etc#
>     
>     
>     debian:/var/spool/hylafax# ls
>     archive  client  dev   doneq  FIFO  log    recvq  status
>     bin      config  docq  etc    info  pollq  sendq  tmp
>     debian:/var/spool/hylafax#
>     
>     
>     debian:/var/spool/hylafax/config# ls
>     agere-mp-2                    gvc-288          rc32acl
>     agere-mp-21                   gvc-288-2        rc32acl-1
>     att-dataport                  hayes            rockwell-k56
>     att-dataport-2                iaxmodem         rockwell-rc
>     att-dataport-2.0              intel-400e       sierra
>     att-dpexpress-2               linux-isdn-2     skel
>     cirrus                        lucent           t38modem
>     class1                        lucent-isa       telebit-qblazer
>     class1.0                      lucent-mt-10     telebit-t3000
>     class2                        lucent-mt-2      telebit-wb
>     class2.0                      lucent-mt-20     topic
>     class2.1                      lucent-mt-21     tricom2842
>     conexant-1.0                  Makefile         uds-fastalk
>     davicom-2                     Makefile.in      umc92144
>     digi                          moto-288         umc9624
>     digi-2                        mt-1432          usr-2.0
>     digi-20                       nuvo-voyager     usr-rts
>     dsi-scout+                    ppi-pm14400fxmt  usr-xon
>     eicon                         ppi-pm14400fxsa  zyxel-1496e
>     eicon-2                       prometheus       zyxel-1496e-1
>     elsa-microlink-56k-basic-2.0  rc144ac          zyxel-1496e-2.0
>     e-tech                        rc144ac-1        zyxel-2864
>     everex-2496d                  rc288dpi
>     exar                          rc288dpi-1
>     debian:/var/spool/hylafax/config#
>     
>     
>     debian:/var/spool/hylafax/etc# ls
>     config        dialrules.europe  faxmail.ps   hyla.conf    setup.modem
>     config.ttyS1  dialrules.sf-ba   getty-link   lutRS18.pcf  templates
>     cover.templ   egetty-link       hfaxd.conf   pagesizes    typerules
>     dialrules     faxcover.ps       hosts.hfaxd  setup.cache
>     debian:/var/spool/hylafax/et
>     
>     
>     Ask me if you need additional informaition. Thank you for any support.
>     Darek
>     
>     
>     ____________________ 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@xxxxxxxxx*
>     
>     
>     
>

-- 


-Siri Vias

Siri Vias Khalsa
Verifi, Inc.
Senior Systems Administrator
sirivias.khalsa@xxxxxxxxxx
323-655-5789 x125 office
310-498-3975 cell