Personal tools
HylaFAX The world's most advanced open source fax server

Handbook:Server Operation:Troubleshooting

When troubleshooting problems, it is important to take a look at the logs. See hylafax-log(5F) for specific error message information. It may also be prudent to turn up ServerTracing or SessionTracing in the config file. For SessionTracing, 0xFFF would be the normal debugging value.

There exists an incompatibility between some versions of HylaFAX with some versions of libtiff. It cannot be overstated that unpatched HylaFAX versions 4.1beta2 and earlier will only work with libtiff versions 3.4 and earlier. The symptoms of this incompatibility problem are varied and widespread throughout HylaFAX functions and can be misleading. HylaFAX versions 4.1beta3 and later support both libtiff versions 3.4 and 3.5 when compiled from source. Keep in mind that HylaFAX binaries (RedHat RPMs, for example) of CVS versions between 4.1beta2 and 4.1beta3 are compatible only with libtiff 3.4 or 3.5, depending on the release. In general, follow the dependency requirements. Libtiff 3.5.5 has significant improvements, including some that are of particular interest to fax page layout, and it is recommended that libtiff-3.5.5 or newer be used when possible.

The libtiff 3.6.1 release contained a serious flaw with respect to writing CCITT G3 and G4 TIFF (fax) image formats. Unpatched (see: http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=500), this version of libtiff cannot be used for fax use.

Installation Errors

A common question arising during faxsetup is in relation to these messages: 

Warning: /bin/vgetty does not exist or is not an executable program!
Warning: /bin/egetty does not exist or is not an executable program!

Simply put, don't worry about them. Both of these programs have to do with data and voice call handling, and for the purposes of faxing, their presence is unnecessary.

Server Status Errors

If faxstat says, Running and idle but no fax in the send-queue is faxed, then likely:

  • faxgetty is not running
  • the modem config file is wrong
  • your libtiff version doesn't agree with your HylaFAX version

If '/usr/local/sbin/hylafax start' results in: 

HylaFAX: not started (script disabled by configure).

Then your system is not likely configured for SysV init scripts such as this hylafax script, and the most straight-forward method of getting hfaxd and faxq running is to start them in an rc.local startup script "manually".

Faxing Errors

If you're using mail-to-fax gateway and mails remain in /var/spool/mqeue and get continuously re-sent, then you're probably experiencing an old HylaFAX and sendmail bug that has been fixed. Update to current versions of both.

If sendfax errors with "localhost: unknown host", make sure that your /etc/hosts file is configured properly for the loopback. It should have a line like this:

127.0.0.1 localhost loopback

Even under the best circumstances, faxing errors may never get fewer than about 1% unless the recipient fax machine types are fixed. Some fax machines have peculiar methods of communication. However, it is the goal of HylaFAX development to make HylaFAX flexible enough to communicate with any sane fax machine, and so such problems could rightly be considered HylaFAX bugs. For the sake of working around this problem, you may want to try using a different faxmodem or different faxmodem configuration settings. In particular, it can be useful to shift your faxmodem from functioning in Class 2/2.0 to Class 1 or vice-versa. To do this, re-run faxaddmodem.

Some of these types of errors will appear in the logs as:

  • Unspecified Transmit Phase B error
  • No response to MPS repeated 3 times
  • RSPREC error/got DCN
  • No answer (T.30 T1 timeout)
  • DCS sent 3 times without response
  • Client does not support...

If you can reproduce an error such as this, it would be a good idea to report it along with a portion of your session log to the hylafax-users mailing list for analysis.

HylaFAX Status Codes

See: HylaFAX_Status_Codes

Development & Reporting Bugs - Bugzilla

HylaFAX development is controlled by CVS, and code development is the major topic on the hylafax-devel mailing list. CVS read-access is open to all, however, write access is not. Unless you're doing a large amount of coding, it is suggested that you post proposed patches and explanations of them on the hylafax-devel mailing list for average development work. See http://www.hylafax.org/cvs.html for better HylaFAX CVS information.

If you are confident that a problem you are experiencing is a HylaFAX bug you may want to report it on the hylafax-users or hylafax-devel mailing list to confirm this. Reveiwing the archives would also be advisable. HylaFAX development and bug control is also handled by Bugzilla. You can also submit bug reports and patches there: http://bugs.hylafax.org/bugzilla/.

Selected Mailing List Posts

Chances are good that if you're having trouble with something in HylaFAX that somebody else has already had that problem. And chances are also good that the issue has been discussed on one of the mailing lists or at some other place. Here are a number of commonly referred-to and useful mailing-list archives and web-links. Be aware that some of this information may refer to specific HylaFAX versions; context is important; watch the dates!

Some Common Problems and Solutions

Retrieved from "https://legacy.hylafax.org/index.php?title=Handbook:Server_Operation:Troubleshooting&oldid=4193"

This page was last edited on 12 November 2012, at 19:31.
Powered by MediaWiki
Attribution-ShareAlike 2.5
Project hosted by iFAX Solutions