[hylafax-users] FaxGetty[]: Can not deduce identity of UUCP

[David <david@xxxxxxxxxxxxxxxxxx>]

I've been unable to set up HylaFAX with any modem because I seem to constantly get this message in my logs whenever I run faxgetty or faxmodem:
Apr 18 02:14:47 mtrx FaxGetty[16376]: Can not deduce identity of UUCP
Apr 18 02:14:47 mtrx FaxGetty[16377]: Can not deduce identity of UUCP
Apr 18 02:14:47 mtrx FaxGetty[16378]: Can not deduce identity of UUCP
Apr 18 02:14:47 mtrx FaxGetty[16379]: Can not deduce identity of UUCP
Apr 18 02:14:47 mtrx FaxGetty[16380]: Can not deduce identity of UUCP
Apr 18 02:14:47 mtrx FaxGetty[16381]: Can not deduce identity of UUCP
Apr 18 02:14:47 mtrx FaxGetty[16382]: Can not deduce identity of UUCP
Apr 18 02:14:47 mtrx FaxGetty[16383]: Can not deduce identity of UUCP
Apr 18 02:14:47 mtrx FaxGetty[16384]: Can not deduce identity of UUCP
Apr 18 02:14:47 mtrx FaxGetty[16385]: Can not deduce identity of UUCP

uucp     16355  0.0  0.0   6620  1348 ?        Ss   12:14   0:00 faxq
uucp     16358  0.0  0.0   4240  1016 ?        Ss   12:14   0:00 hfaxd -i hylafax
Additionally, after running faxmodem, faxq dies and then I get "FIFO: open: No such device or address" on the terminal.

It's on a Fedora Core 5 machine I've been having all the problems. 
Linux mtrx 2.6.18-1.2239.fc5smp #1 SMP Fri Nov 10 13:22:44 EST 2006 i686 i686 i386 GNU/Linux.

These are the steps I have taken:

• I've tried installing different HylaFAX Versions from the RPM packages on Sourceforge:
  hylafax-4.3.0.12-1fc5.i386.rpm
  hylafax-4.3.3-1fc5.i386.rpm
  hylafax-4.4.2-1fc5.i386.rpm
  hylafax-5.2.3-1fc5.i386.rpm
  All install without any problems and the FaxSetup wizard completes without an issue everytime.
• I've tried removing then installing the different HylaFAX versions after deleting all /etc/hylafax and /var/spool/hylafax directories in the case where configuration might be a problem.
  
• I've tried changing the ServerTracing directive to 0xfff and others combinations across the config files /etc/hylafax/hfaxd.conf, /var/spool/hylafax/etc/config and /var/spool/hylafax/etc/config.ttyS1 and restarted the services, but it hasn't given any debug information around the error message above.
• I've tried copying the configuration files from the old working server to the new.
• I've tried comparing the permissions on all the HylaFAX files with the working server.
• I've tried swapping different modems and trying different configurations.

I have two "Diamond Voice 56K" external modems that I have been running on an older Fedora Core 2 machine, running HylaFAX version 4.2.1.
On the old machine, HylaFAX works with these modems without a single problem, so there isn't any issue with the modems.  Running Getty on the COM port and WvDial work and communicate without issues.
This is my HylaFAX config.ttyS1 file:
CountryCode:    61
AreaCode:       7
FAXNumber:      +61.7.41000000
LongDistancePrefix:     1
InternationalPrefix:    0015
DialStringRules:        etc/dialrules
ServerTracing:          0xfff
SessionTracing:         0xfff
RecvFileMode:           0600
LogFileMode:            0600
DeviceMode:             0600
RingsBeforeAnswer:      1
NoCarrierRetrys:        4
SpeakerVolume:  high
GettyArgs:              "-h %l dx_%s"
LocalIdentifier:        "Company Name"
TagLineFont:            etc/lutRS18.pcf
TagLineFormat:  "From %%l|%c|Page %%P of %%T"
MaxRecvPages:   175
Class1ExtendedRes:      yes
ModemType:              Class1          # use this to supply a hint
ModemRate:              19200           # rate for DCE-DTE communication
#ModemFlowControl:      rtscts          # default
ModemFlowControl:       xonxoff
ModemNoFlowCmd:         AT&K0           # setup no flow control
ModemHardFlowCmd:       AT&K3           # setup hardware flow control
ModemSoftFlowCmd:       AT&K4           # setup software flow control
ModemSetupDTRCmd:       AT&D2           # setup so DTR drop resets modem
ModemSetupDCDCmd:       AT&C1           # setup so DCD reflects carrier (or not)
ModemMfrQueryCmd:       !Rockwell
ModemModelQueryCmd:     !RC288DPi
ModemRevQueryCmd:       ATI3            # product information
ModemDialCmd:  ATDT%s@


In conclusion, I don't think there is a problem with the HylaFAX configuration, physical modems or communications to the devices.
What I haven't tried is swapping the serial ports the modem is on.  (COM Port 1 is already in use and has a lot of reliance on it).  I also haven't tried Building HylaFAX from the source.

Any information no-matter how important would be greatly appreciated as this is urgent.
Is there any way of getting more debug information for the "Can not deduce identity of UUCP" error message?
Does anyone know what this error message means?

Best regards,
David