Bug 1985587

Summary:	spamd starts before resolv.conf setup, causing DNS resolution errors
Product:	[Fedora] Fedora	Reporter:	Jason Tibbitts <j>
Component:	spamassassin	Assignee:	Kevin Fenzi <kevin>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	34	CC:	jskarvad, kevin, michael, nb, olysonek-foss, pzhukov
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-08 06:24:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jason Tibbitts 2021-07-24 04:58:26 UTC

Description of problem:
It seems that spamd can start before the network or DNS resolution is fully configured, resulting in errors like the following:

check[880]: dns: sendto() to [::1]:53 failed: Connection refused, failing over to [127.0.0.1]:53
check[880]: dns: sendto() to [127.0.0.1]:53 failed: Connection refused, failing over to [::1]:53
check[880]: dns: bad dns reply: bgread: recv() failed: Connection refused at /usr/share/perl5/vendor_perl/Mail/SpamAssassin/DnsResolver.pm line 742

Simply running 'systemctl restart spamassassin' seems to be enough to fix this.

I'm seeing this on systems which have been updated many times from very old Fedora releases so I'm sure something about their configurations differs from a freshly installed system.  /etc/resolv.conf is a symlink to /var/run/NetworkManager/resolv.conf so I believe systemd-resolved isn't involved, but /var/run is on tmpfs so I suspect the problem is simply that there's a race between spamassassin startup and the resolv.conf creation.  This arrangement has been in place for a while so I can't explain why I haven't seen this problem before.

I suspect there is an appropriate After= line to use.  Probably just using network-online.target instead of network.target.  I tried that (with a quick systemctl edit) and it appears to work, but I've no idea if it's the right thing to do.  Maybe I should switch the symlink to use the systemd-resolved setup instead.


Version-Release number of selected component (if applicable):
spamassassin-3.4.6-1.fc34.x86_64

How reproducible:
Most, perhaps all fresh boots, but never after a post-boot restart of spamassassin.

Comment 1 Kevin Fenzi 2021-07-30 19:55:22 UTC

Yeah, I think we should switch to network-online.target. 

Here's a PR that does this: https://src.fedoraproject.org/rpms/spamassassin/pull-request/12

Comment 2 Ben Cotton 2022-05-12 16:52:55 UTC

This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Ben Cotton 2022-06-08 06:24:43 UTC

Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Michael Altizer 2022-09-27 18:42:08 UTC

Still present in Fedora 35 with spamassassin-3.4.6-3.fc35.x86_64.