ls -lla /etc/e-smith/templates/var/spool/hylafax/etc/
ls -lla /etc/e-smith/templates/var/spool/hylafax/etc/config/
I’m pretty sure that I didn’t touch this side…
NethServer templates seem to be ok, but verify with rpm -V nethserver-hylafax.
rpm -V nethserver-hylafax
additionally:
o.k. I’m doing a re-install. I removed hylafax.
rpm -qa fax
Still have an output from
config show hylafax
yum install nethserver-hylafax
ce-base: repo.uk.bigstepcloud.com
ce-extras: repo.uk.bigstepcloud.com
ce-sclo-rh: repo.uk.bigstepcloud.com
ce-sclo-sclo: repo.uk.bigstepcloud.com
ce-updates: repo.uk.bigstepcloud.com
epel: ftp.plusline.net
nethforge: mrmarkuz.goip.de
nethserver-base: mrmarkuz.goip.de
nethserver-updates: mrmarkuz.goip.de
Dependencies Resolved
===========================================================================================
Installing:
Transaction Summary
Install 1 Package (+9 Dependent packages)
Total download size: 3.7 M
Total 1.6 MB/s | 3.7 MB 00:00:02
Installed:
Dependency Installed:
Complete!
@filippo_carletti
Configuring now from the old server-manager results in
Task completed with errors
Template /var/spool/hylafax/etc/FaxWedged #11 (exit status 1)#12 (exit status 1)#15 (exit status 1)
and
HylaClient::send: client/22870: Cannot open FIFO: No such device or address
Event: nethserver-hylafax-save FAILED
ps -e | grep faxgetty
ps -aux | grep faxgetty
systemctl stop faxgetty
ls -la
I don’t get it, sorry.
edit:
faxstatxxx.de : Running
MUST be running and idle.
BTW in the new server-manager no service for faxgetty is shown.
@schulzstefan @filippo_carletti
Hi
Just looking over the entries, I get the impression that either the com port is not there (wrong permissions seem anyway the case - the user involved needs to be member of the “dialout” group to be able to access the com port.)
Is this device there? /dev/ttyS3
(Is that what you’re using for the Faxmodem?)
Please bear in mind that I have not used Hylafax in 4-5 years…
My 2 cents
Hi Andy,
com port is correct. I put a serial card in the server because I didn’t trust the onboard serial. Modem is under ttyS3 and worked til updating. Sending and receiving faxes is working.
What is the user used for Hylafax?
schulzstefan:
Task completed with errors
Template /var/spool/hylafax/etc/FaxWedged #11 (exit status 1)#12 (exit status 1)#15 (exit status 1)
and
HylaClient::send: client/22870: Cannot open FIFO: No such device or address
Event: nethserver-hylafax-save FAILED
ps -e | grep faxgetty
ps -aux | grep faxgetty
systemctl stop faxgetty
For me it looks like templates are the problem. Maybe the configuration in the old server-manager has not been ported to the last release.
drwxr-xr-x 20 uucp uucp 271 Jan 14 18:56 hylafax
inside the directory:
s -la
BTW: FIFO came from the last install-approach. It has to be FIFO.ttyS3.
I’d like to kill the faxgetty, but I can’t? Where does it come from?
Add in hylafax to the dialout group
Faxgetty:
kill -9 PID help?
2 Likes
Andy_Wismer:
Faxgetty:
kill -9 PID help?
No. It restarts instantly. Where is this process initiated?
Most likely from it’s profile…
IMVHO this could not be the problem. If I configure this manually, it works. I mean it’s a modem, just running. No need to touch the config for the last 8 years. All I want to have is a persistent configuration whisch survives the next updates from the OS. And the case that the config is lost after issuing updates indicates that something’s wrong with the templates.
Do you have the following in the folders?
These screenshots are from a NS 7.8.2003, where I - without updating - just installed Hylafax from the old NethServer GUI, aka Server-Manager…
Adding hylafax to dialout doesn’t cost anything, is also not a security issue, but if it helps…
1 Like
Basically. In dispatch there is a folder named /print.conf - it’s empty. The file 90print is there.
The modem works fine if it is configurated from scratch. It looses the config while updating NS. I can’t see that this depends on the group dialout. But I’ll try.
It’s also quickly removed if it’s NOT the problem…
Your templates folder look OK, but it does have problems “expanding” something, as per your post a bit earlier…
As I don’t have a modem - my old Proliant does have serial ports (!) - I can’t check the configuration part. I even have a free, unused analog line, but no modem to test…
