Re: Fresh install misses autostart of daemon and faxgetty

On 12/01/2018 05:43 AM, Carsten wrote:
> after having a lot of trouble with the outdated version of hylafax I
> now did a fresh install of version 5.6.1 from
> http://hylafax.sourceforge.net
>
> My old hylafax version 3:6.0.6-6+deb8u1 from the repository has been
> uninstalled and cleaned up by
> "...
> apt-get purge hylafax-server hylafax-client
> mv /var/log/hylafax /var/log/hylafax-old
> mv /var/spool/hylafax /var/spool/hylafax-old
> mv /etc/hylafax /etc/hylafax-old
> ..."

HylaFAX is highly configurable.=A0 Unless you take care to mimic the
configuration and build that was done in your package-based installation
there is a good chance that you'll find something is configured different=
ly.

To find out how the Debian packager did things you can dig through the
source files:

https://packages.debian.org/source/sid/hylafax

What you'll find is that the Debian packager has done a lot of tweaking
in order to cope with Debian packaging guidelines.=A0 A lot of that you
may not need or care about, and after you weed through it you'll find
the bits that you're looking for.=A0 It's a daunting task, but it's
necessary if you're trying to mimic what you had before with the
imposition of the packaging guidelines.

As I do that now I notice that Debian patched v6.0.6 rather than
updating to v6.0.7.=A0 So, if you're going to v5.6.1 in order to get the
security update there is no need.

> The Build of the new version went fine as far as I can see, just this
> message confuses me:
> "...
> You do not appear to be using faxgetty to notify the HylaFAX scheduler
> about new modems and/or their status.
> ..."

faxsetup will examine /etc/inittab for a specific pattern that it
believes identifies a configuration that is "using faxgetty".=A0 If that
assumption is not met, then you'll get this message.=A0 Many people will
run faxgetty differently from that assumption, so this message is common
to see.

What you'll want to take note of, however, is that faxsetup does not
create startup mechanisms for faxgetty.=A0 Normally configuration of
faxgetty startup was something left to the administrator of the system
to do "manually".=A0 However, some package installations (such as Debian)
did this for you.

> Remember, I have had a working send and receive configuration before,
> using a postfix transport and faxgetty.
>
> issues:
> ########################################
> ##
> ## #1 Transport not working anymore
> ##
> #########################################
>
> Error: cannot find /usr/bin/faxmail

I'm guessing that your configuration put it in /usr/local/bin/faxmail.=A0
mail2fax.sh is different from faxmail.

> ########################################
> ##
> ## #2 Fax are not send
> ##
> ########################################
>
> After the workaround transport was working, I found the jobs in the
> faxq folder, but they did not get send.
>
> I found neither faxgetty nor faxmodem seem to listen and as I could
> not get faxgetty to work, I did a
> faxmodem ttyIAX0
> and the queued jobs were starting to be delivered.
>
> How do i get faxgetty involved?

You'll need to start faxgetty for each modem somehow.=A0 Using
/etc/inittab was popular.=A0 In modern days with systemd you'll probably
want to create systemd "service" files.=A0 If you're really lazy then jus=
t
putting a faxgetty line for each modem in an rc.local file would work,
too, but it won't "respawn" them if they stop.

> ########################################
> ##
> ## #3 after reboot, hylafax does not come up automatically
> ##
> ########################################
>
> When restarting the system, I ended up w/o having a running hylafax
> server.
> Only a manual "service hylafax start" brings back the core, but still
> there is no "faxgetty" process.
>
> I found some advice about to add the service to init.rc and tried this:
> "...
> =A0update-rc.d hylafax defaults 80 10
> ..."
> Ending up with this:
> "...
> insserv: Max recursions depth 99 reached
> insserv: There is a loop at service hylafax if started
> insserv: There is a loop at service rc.local if started
> insserv:=A0 loop involving service hylafax at depth 1
> insserv: exiting now without changing boot order!
> update-rc.d: error: insserv rejected the script header
> ..."
>
> How do I get the configuration to start at boot (hylafax including
> faxgetty)

The lazy way to deal with this is to use rc.local to run "hylafax
start".=A0 But, the messages you're seeing there are because Debian
expects a script header on the "hylafax" script.=A0 Look for the
"hylafax-server.hylafax.init" file in the
"hylafax_6.0.6-8.1.debian.tar.xz" file.=A0 You'll see the parts that
Debian is expecting at the top of that script.

> ########################################
> ##
> ## #4 Delivery report returns rubbish Subject
> ##
> ########################################
>
> During the try and error from above I received some delivery reports.
> I have had copied the "old" FaxDispatch and FaxNotify to the
> /var/spool/hylafax/etc folder.
>
> Working with Thunderbird I receive a subject like this -not from the
> source code, it is displayed like this:
>
> "=3D?UTF-8?B?w4T[..manyChars...]O2?=3D to 069[..faxnumber..] completed"
>
> What do I need to tweak here?

It's possible that something in your FaxDispatch and FaxNotify scripts
are not working properly with the v5.6.1 faxrcvd and notify scripts.=A0
Without looking at your modifications I don't know what you'd need to twe=
ak.

All of this said, you seem fairly dependent upon the Debian packaging of
HylaFAX, and so I'm wondering why you're wanting to switch away from it. =
(?)

Thanks,

Lee.



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