Package: hylafax-server
Version: 3:6.0.7-5
Followup-For: Bug #1031200

Dear Maintainer,

Experienced same issue and I'm not sure when it was introduced and what the exact cause ist but I
don't recall I experiencing it on the last reboot (probably several months ago)

But what I suspect the cause to be:

iaxmodem creates a link from /dev/ttyIAX to a dynamic /dev/pts device.

The faxgetty systemd script contains:

BindsTo=dev-%i.device
After=dev-%i.device

And if %i is a link and not a real device, udev never triggers an event and the device binding is never true.

Commenting out those two statements solved the issue for me for now.

-Benoit-

-- System Information:
Debian Release: 12.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_SOFTLOCKUP
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE=de_CH:de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages hylafax-server depends on:
ii adduser 3.134
ii bsd-mailx [mailx] 8.1.2-0.20220412cvs-1
ii debconf [debconf-2.0] 1.5.82
ii ghostscript 10.0.0~dfsg-11+deb12u3
ii hylafax-client 3:6.0.7-5
ii init-system-helpers 1.65.2
ii libc6 2.36-9+deb12u4
ii libcrypt1 1:4.4.33-2
ii libgcc-s1 12.2.0-14
ii libjbig0 2.1-6.1
ii libpam0g 1.5.2-6+deb12u1
ii libstdc++6 12.2.0-14
ii libtiff-tools 4.5.0-6+deb12u1
ii libtiff6 4.5.0-6+deb12u1
ii lsb-base 11.6
ii psmisc 23.6-1
ii sed 4.9-1
ii sendmail-bin [mail-transport-agent] 8.17.1.9-2
ii systemd 252.22-1~deb12u1
ii sysvinit-utils [lsb-base] 3.06-4
ii zlib1g 1:1.2.13.dfsg-1

hylafax-server recommends no packages.

Versions of packages hylafax-server suggests:
pn mgetty <none>
pn psrip <none>

-- Configuration Files:
/etc/hylafax/hosts.hfaxd changed:
localhost


-- debconf information:
hylafax-server/start_now: true
hylafax-server/setup_failed:

-- debsums errors found:
debsums: changed file /lib/systemd/system/faxgetty@.service (from hylafax-server package)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hello Benoit,
thank you for adding this information. The problem is indeed that one: udev
is not triggering any event when the IAX modem device is created. This lead
to a not existing dev-%i.device and hence, to a non activation of the
faxgetty by systemd.

The solution is to start the device manually. In your case, if the IAX modem are started at boot, you may just leave the changes you have done to the
unit, and enable it for starting at boot time.

I am looking for a different approach that could starts faxgetty when an IAX device is created, and stops it when it is removed. I do not have a solution yet.

Bye,
Giuseppe

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)