0 Members and 4 Guests are viewing this topic.
Job for amavisd.service failed because a timeout was exceeded.See "systemctl status amavisd.service" and "journalctl -xeu amavisd.service" for details.The job identifier is 170783.Aug 05 11:10:49 vps.domain.net amavis[66859]: starting. /usr/sbin/amavisd at vps.domain.net amavis-2.13.1 (20240304), Unicode aware, LANG="en_US.UTF-8"Aug 05 11:10:49 vps.domain.net amavis[66859]: perl=5.032001, user=, EUID: 986 (986); group=(), EGID: 983 983 (983 983)Aug 05 11:10:50 vps.domain.net amavis[66864]: (!)Net::Server: 2024/08/05-11:10:50 Can't connect to TCP port 10024 on ::1 [Cannot assign requested address]\n at line 64 in file /usr/share/perl5/vendor_perl/Net/Server/Proto/TCP.pmAug 05 11:10:50 vps.domain.net systemd[1]: amavisd.service: Can't open PID file /run/amavisd/amavisd.pid (yet?) after start: Operation not permitted
dnf install spamassassin amavissystemctl enable spamassassinsystemctl start spamassassinsystemctl enable amavisdsystemctl start amavisd
Job for amavisd.service failed because a timeout was exceeded.See "systemctl status amavisd.service" and "journalctl -xeu amavisd.service" for details.
I'm still getting the following errors although I did a reinstall with Startburst suggestions; Code: [Select]Job for amavisd.service failed because a timeout was exceeded.See "systemctl status amavisd.service" and "journalctl -xeu amavisd.service" for details.
Been out of the game for awhile but (referring to first post) it appears to be related to amavisd trying to bond to IP6.the "fix" appears to be to add $inet_socket_bind = '127.0.0.1'; /etc/amavisd/amavisd.confBUT I'm no CWP guru and others may advise against that as there is probably a better way to fix the issue.EDIT: In hindsight that probably a non fatal issue.