Re: faxgetty exited on signal 6

Ryan Noll <[email protected]> Tue, 29 Mar 2016 16:45:36 -0700
Newsgroups gmane.comp.telephony.fax.hylafax.user
Message-ID <CAGzpdJAsMY9ZXrR8V3A9x7TPojRhB8aCROuvDcpQOBM-M5FKbw@mail.gmail.com>
Thank you, Mr. Howard.

The assertion that failed when running faxgetty interactively is

Assertion failed: (x == lastx), function _TIFFFax3fillruns, file
tif_fax3.c, line 452.
Abort

Now that was completely different then where I thought the abort would
occur. This would lead me to think that the problem may lay in the
version of libtiff that is installed. The version I have installed is
4.04. I vaguely remember seeing some previous posts where HylaFax was
not compatible with some versions of libtiff. Did I read that
correctly? Does HylaFax+ have this same incompatibility?

Thanks again,
Ryan


On Tue, Mar 29, 2016 at 10:21 AM, Lee Howard <[email protected]> wrote:
> On 03/28/2016 10:36 PM, Ryan Noll wrote:
>>
>> I am running HylaFax 6.0.6 on FreeBSD 10.2-RELEASE-p7. HylaFax is
>
> ....
>>
>> Mar 28 21:00:14.55: [21287]: <-- [11:AT+FRM=146\r]
>> Mar 28 21:00:15.17: [21287]: --> [7:CONNECT]
>> Mar 28 21:00:15.17: [21287]: RECV: begin page
>>
>> Right after RECV: begin page, faxgetty exits with
>>
>> Mar 28 21:00:16 freeswitch kernel: pid 21287 (faxgetty), uid 66:
>> exited on signal 6
>>
>> Does anyone have any ideas of what could cause this problem?
>
>
> Signal 6 is SIGABRT, so faxgetty is calling abort() for some reason.  Thus,
> there is a bug in HylaFAX when running on your platform.  As there aren't a
> lot of FreeBSD users running HylaFAX (at least that I know of), this is not
> terribly surprising.
>
> It's not logging the reason, which is frustrating, but it is probably giving
> the reason on stderr (wherever you have that directed).
>
> So, what I would suggest that you do is twofold:
>
> 1) Find the reason that faxgetty is giving.  You have faxgetty started under
> /etc/ttys.  See where stderr goes from there.  If you still can't find it
> then run faxgetty without "-D" from the command-line and look for the error
> message on the terminal when it aborts.  This message probably won't give us
> the smoking gun that is needed to fix things, but it would be a good place
> to start looking.
>
> 2) Try using HylaFAX+ 5.5.8 (http://hylafax.sourceforge.net).  There are
> some BSD-related changes in HylaFAX+ that are not in the hylafax.org
> releases that may be applicable...
>
> https://sourceforge.net/p/hylafax/HylaFAX+/2334/
> https://sourceforge.net/p/hylafax/HylaFAX+/2336/
> https://sourceforge.net/p/hylafax/HylaFAX+/2337/
> https://sourceforge.net/p/hylafax/HylaFAX+/2339/
>
> Thanks,
>
> Lee.


____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe [email protected] < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail [email protected].*