El 2024-09-01 a las 15:21 +0200, Giuseppe Sacco escribió: > Thanks for your answers, Camaleón. I still have some: > > Il giorno dom, 01/09/2024 alle 12.41 +0200, Camaleón ha scritto: > [...] > > Debian 12 installation was performed completely fresh, a new system, not > > and update/upgrade from an older Debian version. > > OK > > > > But after OS install, I manually backed up / restore my old HylaFAX > > server configuration, which was plenty of data (faxes, logs...). > > Was the backup/restore of data done after hylafax packages were already > installed and configured? Or, was hylafax installed after che restore of the > data?
Data was restored AFTER HylaFAX package was installed and configured and NICELY running after hitting bug #1031200 and finally bypassed the faxgetty systemd problematic: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031200#75 > > Now, after the CRON JOB was run, all files seem to be gone despite I > > set the two variables to tell not to do so; and what is even worse, > > HylaFAX is NOT working :-/ > > So, you restored the data, you started hylafax, everything was working right, Well... kinda so, but yes (see #BTS 1031200). HylaFAX was FINE yesterday until TODAY when the cronjob run and hit this new bug. > maybe you sent or received some faxes, then the cron job was run and deleted > everything despite you changed FAXCRON_OPTS and FAXQCLEAN_OPTS in > /etc/default/hylafax? ^^^^^^^^^^^^^^^^^^^^ Not there ;-) Well, AFTER the cronjob routine was executed, I'm experiencing two (2) issues: 1. None of my fax users (normal user -sm02- and admin user) are able to operate as usual. Log NOW says: sep 01 10:23:26 stt005 HylaFAX[24873]: Unable to open the user access file /etc/hosts.hfaxd: No such file or directory sep 01 10:23:26 stt005 HylaFAX[24873]: pam_unix(hylafax:auth): conversation failed sep 01 10:23:26 stt005 HylaFAX[24873]: pam_unix(hylafax:auth): auth could not identify password for [sm02] sep 01 10:23:26 stt005 HylaFAX[24873]: pam_authenticate failed in pamCheck with 0x7: Authentication failure sep 01 10:24:02 stt005 HylaFAX[24874]: Unable to open the user access file /etc/hosts.hfaxd: No such file or directory sep 01 10:24:02 stt005 HylaFAX[24874]: pam_unix(hylafax:auth): conversation failed sep 01 10:24:02 stt005 HylaFAX[24874]: pam_unix(hylafax:auth): auth could not identify password for [sm02] sep 01 10:24:02 stt005 HylaFAX[24874]: pam_authenticate failed in pamCheck with 0x7: Authentication failure sep 01 17:01:59 stt005 HylaFAX[26348]: Unable to open the user access file /etc/hosts.hfaxd: No such file or directory sep 01 17:01:59 stt005 HylaFAX[26348]: pam_unix(hylafax:auth): conversation failed sep 01 17:01:59 stt005 HylaFAX[26348]: pam_unix(hylafax:auth): auth could not identify password for [sm02] sep 01 17:01:59 stt005 HylaFAX[26348]: pam_authenticate failed in pamCheck with 0x7: Authentication failure sep 01 17:02:05 stt005 HylaFAX[26349]: Unable to open the user access file /etc/hosts.hfaxd: No such file or directory sep 01 17:02:05 stt005 HylaFAX[26349]: pam_unix(hylafax:auth): conversation failed sep 01 17:02:05 stt005 HylaFAX[26349]: pam_unix(hylafax:auth): auth could not identify password for [sm02] sep 01 17:02:05 stt005 HylaFAX[26349]: pam_authenticate failed in pamCheck with 0x7: Authentication failure sep 01 17:02:05 stt005 HylaFAX[26349]: ADMIN failed from 192.168.0.8 [192.168.0.8], sm02 2. My old faxes and logs are also gone because of the faxqclean routine was run despite is was disabled. Removing these old files prevent HylaFAX server to operate normally, because of «seqf» files DOT NOT MATCH (these files hold a count number). root@stt005:/# cat /var/spool/hylafax/log/xferfaxlog 09/01/24 11:31 CALL 000009609 ttyS0 "" fax "+34 xx xxx xxxx" "" 0 0 0:00:49 0:00:49 "No sender protocol (T.30 T1 timeout)" "" "" "" "" "" > What were the values you gave to these variables? As I pointed out in my first comment on this bug, I set the variables in «/etc/hylafax/hfaxd.conf.systemd» and gave them a «null» (empty) value as instructed in README file: root@stt005:/var/spool# cat /etc/hylafax/hfaxd.systemd.conf | grep -i faxq FAXQCLEAN_OPTS="" FAXQCRON_OPTS="" In the meantime, how can I safely disable ANY cronjob related to HylaFAX? Cheers, -- Camaleón
