Description of problem: hylafax never start with systemctl start hylafax-hfaxd.service Version-Release number of selected component (if applicable): hylafax+-7.0.0-1.mga7 How reproducible: every time you want to start Steps to Reproduce: 1. install hylafax+-7.0.0-1.mga7 2. configure with faxconfig 3. enable hylafax-hfaxd.service 4. start hylafax with systemctl start hylafax-hfaxd.service Solution: edit /usr/lib/systemd/system/hylafax-hfaxd.service and set the right path in ConditionPathExists=/var/spool/fax/etc/setup.cache because this is wrong /var/spool/hylafax/etc/setup.cache edit /usr/lib/systemd/system/hylafax-faxq.service nd set the right path in ConditionPathExists=/var/spool/fax/etc/setup.cache because this is wrong /var/spool/hylafax/etc/setup.cache
Thank you for reporting the problem, and the reasons for it.
[Premature 'send' above]. No registered maintainer for this, so assigning globally. CC DavidG as the active committer.
Assignee: bugsquad => pkg-bugsCC: (none) => geiger.david68210
Please test with hylafax+-7.0.2-1.mga7 in core/Updates_testing repo!
Looks good with hylafax+-7.0.2-1.mga7 from core/updates systemctl restart hylafax-hfaxd.service OK hylafax-faxq.service Ok And after restart the machine hfaxd service comes up. Thank you.
Assigning to QA, Advisory: ======================== Current hylafax+ package fails to start the ylafax-hfaxd systemd service due to some wrong configurations. So this update fixes this issue. ======================== Packages in 7/core/updates_testing: ======================== hylafax+-7.0.2-1.mga7.i586.rpm hylafax+-client-7.0.2-1.mga7.i586.rpm libhylafax+7-7.0.2-1.mga7.i586.rpm libhylafax+-devel-7.0.2-1.mga7.i586.rpm hylafax+-7.0.2-1.mga7.x86_64.rpm hylafax+-client-7.0.2-1.mga7.x86_64.rpm lib64hylafax+7-7.0.2-1.mga7.x86_64.rpm lib64hylafax+-devel-7.0.2-1.mga7.x86_64.rpm Source RPM: ======================== hylafax+-7.0.2-1.mga7.src.rpm
Assignee: pkg-bugs => qa-bugs
MGA7-64 Plasma on Lenovo B50 No installation issues. I don't have such device, but I expect the service to run, right??? # systemctl -l status hylafax-hfaxd.service ● hylafax-hfaxd.service - HylaFAX hfaxd (client service) Loaded: loaded (/usr/lib/systemd/system/hylafax-hfaxd.service; disabled; vendor preset: disabled) Active: inactive (dead) Feb 27 15:48:38 mach5.hviaene.thuis systemd[1]: Condition check resulted in HylaFAX hfaxd (client service) being skipped. # systemctl enable hylafax-hfaxd.service Created symlink /etc/systemd/system/multi-user.target.wants/hylafax-hfaxd.service → /usr/lib/systemd/system/hylafax-hfaxd.service. # systemctl -l status hylafax-hfaxd.service ● hylafax-hfaxd.service - HylaFAX hfaxd (client service) Loaded: loaded (/usr/lib/systemd/system/hylafax-hfaxd.service; enabled; vendor preset: disabled) Active: inactive (dead) Feb 27 15:48:38 mach5.hviaene.thuis systemd[1]: Condition check resulted in HylaFAX hfaxd (client service) being skipped. # systemctl start hylafax-hfaxd.service # systemctl -l status hylafax-hfaxd.service ● hylafax-hfaxd.service - HylaFAX hfaxd (client service) Loaded: loaded (/usr/lib/systemd/system/hylafax-hfaxd.service; enabled; vendor preset: disabled) Active: inactive (dead) Condition: start condition failed at Thu 2020-02-27 15:50:53 CET; 2s ago └─ ConditionPathExists=/var/spool/fax/etc/setup.cache was not met Feb 27 15:48:38 mach5.hviaene.thuis systemd[1]: Condition check resulted in HylaFAX hfaxd (client service) being skipped. Feb 27 15:50:53 mach5.hviaene.thuis systemd[1]: Condition check resulted in HylaFAX hfaxd (client service) being skipped. journalctl doesnot give more info.
CC: (none) => herman.viaene
You have to run "/usr/sbin/faxsetup -server" to configure your fax server and so the setup.cache will be created. # systemctl -l status hylafax-hfaxd.service ● hylafax-hfaxd.service - HylaFAX hfaxd (client service) Loaded: loaded (/usr/lib/systemd/system/hylafax-hfaxd.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2020-02-28 07:14:27 CET; 4s ago Main PID: 2015 (hfaxd) Memory: 740.0K CGroup: /system.slice/hylafax-hfaxd.service └─2015 /usr/sbin/hfaxd -d -i hylafax févr. 28 07:14:27 david.david systemd[1]: Started HylaFAX hfaxd (client service). févr. 28 07:14:27 david.david HylaFAX[2015]: Listening to 0.0.0.0:4559 févr. 28 07:14:27 david.david HylaFAX[2015]: HylaFAX INET Protocol Server: restarted.
Confirm above, after running # /usr/sbin/faxsetup -server I get # systemctl -l status hylafax-hfaxd.service ● hylafax-hfaxd.service - HylaFAX hfaxd (client service) Loaded: loaded (/usr/lib/systemd/system/hylafax-hfaxd.service; disabled; vendor preset: disabled) Active: active (running) since Fri 2020-02-28 10:47:20 CET; 4min 26s ago Main PID: 29213 (hfaxd) Memory: 820.0K CGroup: /system.slice/hylafax-hfaxd.service └─29213 /usr/sbin/hfaxd -d -i hylafax Feb 28 10:47:20 mach5.hviaene.thuis systemd[1]: Started HylaFAX hfaxd (client service). Feb 28 10:47:20 mach5.hviaene.thuis HylaFAX[29213]: Listening to 0.0.0.0:4559 Feb 28 10:47:20 mach5.hviaene.thuis HylaFAX[29213]: HylaFAX INET Protocol Server: restarted. That's as far as I can go. Giving OK unless someone has a fax available to do a real test.
Whiteboard: (none) => MGA7-64-OK
Validating. Advisory in Comment 5.
Keywords: (none) => validated_updateCC: (none) => andrewsfarm, sysadmin-bugs
(In reply to Herman Viaene from comment #8) > That's as far as I can go. Giving OK unless someone has a fax available to > do a real test. I'm the reporter of the Bug, because in need this for real with fax modem. The Ok was on comment 4. It is working since i have installed the testing package.
Keywords: (none) => advisoryCC: (none) => tmb
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2020-0066.html
Status: NEW => RESOLVEDResolution: (none) => FIXED