Well, adding negative karma to a rawhide update when you rebuilt and tested on f37 isn't too valid.
That said, I would expect it to work. Can you file a bug and we can debug it there?
For help debugging failed Fedora CI tests (fedora-ci.*), contact the Fedora CI team.
For help debugging failed Fedora CoreOS tests (coreos.*), contact the Fedora CoreOS team.
For help debugging failed openQA tests (update.*), contact the Fedora Quality team, who will usually investigate and diagnose all failures within 24 hours.
This update was automatically created
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
so far, so good on both rawhide & f37
Rebuilt src rpm for Fedora 37, edited the v3.x.x.pre files and restarted:
bdm@peterson SPECS]$ sudo systemctl status spamassassin × spamassassin.service - Spamassassin daemon Loaded: loaded (/usr/lib/systemd/system/spamassassin.service; enabled; preset: disabled) Active: failed (Result: exit-code) since Wed 2022-12-21 18:13:00 GMT; 3min 27s ago Duration: 502ms Main PID: 13217 (code=exited, status=64) CPU: 495ms
Dec 21 18:13:00 peterson.fenrir.org.uk systemd[1]: spamassassin.service: Scheduled restart job, restart counter is at 5. Dec 21 18:13:00 peterson.fenrir.org.uk systemd[1]: Stopped spamassassin.service - Spamassassin daemon. Dec 21 18:13:00 peterson.fenrir.org.uk systemd[1]: spamassassin.service: Start request repeated too quickly. Dec 21 18:13:00 peterson.fenrir.org.uk systemd[1]: spamassassin.service: Failed with result 'exit-code'. Dec 21 18:13:00 peterson.fenrir.org.uk systemd[1]: Failed to start spamassassin.service - Spamassassin daemon.
Downgrade back to 3.4.6 and everything works normally again:
[bdm@peterson SPECS]$ sudo systemctl status spamassassin ● spamassassin.service - Spamassassin daemon Loaded: loaded (/usr/lib/systemd/system/spamassassin.service; enabled; preset: disabled) Active: active (running) since Wed 2022-12-21 18:16:37 GMT; 3s ago Main PID: 14204 (spamd) Tasks: 1 (limit: 9387) Memory: 109.0M CPU: 2.787s CGroup: /system.slice/spamassassin.service └─14204 /usr/bin/perl "-T -w" /usr/bin/spamd -c -m5 -H -x -u mail --virtual-config-dir=/etc/mail/spamassassin/%u --socketpath=/opt/spamd/spamd_socket --razor-home-dir=/var/lib/razor/ --razor-log-file=sys-sys>
Dec 21 18:16:37 peterson.fenrir.org.uk systemd[1]: Started spamassassin.service - Spamassassin daemon. Dec 21 18:16:39 peterson.fenrir.org.uk spamd[14204]: zoom: able to use 388/388 'body_0' compiled rules (100%) Dec 21 18:16:40 peterson.fenrir.org.uk spamd[14208]: util: setuid: ruid=0 euid=0 rgid=0 egid=0 Dec 21 18:16:40 peterson.fenrir.org.uk check[14204]: [ 2] [bootup] Logging initiated LogDebugLevel=3 to sys-syslog
Tried running sa-update and sa-compile as root, no improvement.
Looks like the status=64 is referring to command line errors for arguments passed to spamd
Those listed above have been working for years if not decades here.
Can't see why it would break.
Well, adding negative karma to a rawhide update when you rebuilt and tested on f37 isn't too valid. That said, I would expect it to work. Can you file a bug and we can debug it there?
Ah, I think I can duplicate it... will look at a fix.
OK, seems to be the razor arguments passed to spamd, I have deleted them from /etc/sysconfig/spamassassin and it's working now.
Sorry about the feedback mistake, didn't quite know how to proceed.
I'm building/testing a fix to the razor arguments now. ;) Thanks for the testing.
This update has been obsoleted by spamassassin-4.0.0-2.fc38.