Description of problem: I have a CentOS 6.6 server running Postfix 2.6.6 with amavisd-new 2.9.1 managing email scanning with Clam-AV and SpamAssassin in a 'typical' setup. Amavisd-new and its dependencies are installed from the EPEL repo and CentOS base/updates only. The server had installed perl-Net-Server 0.97-7 from EPEL. Yesterday this package was updated to 2.007-2 from the EPEL repo. Following this update, amavis stopped working, preventing Postfix from receiving new mail. The output of 'service amavisd status' shows "amavisd dead but subsys locked". I removed the lock file and started the service, which reports OK but, in fact, is not running (status returns dead). The following error is reported in the maillog: amavis[4160]: (!)Net::Server: 2014/12/02-12:43:37 Can't connect to TCP port 10024 on ::1 [Cannot assign requested address]\n at line 68 in file /usr/share/perl5/vendor_perl/Net/Server/Proto/TCP.pm Running 'netstat -lntup | grep 10024' returns nothing. It should be listening on 127.0.0.1 Unable to find any solution to this I downgraded perl-Net-Server back to 0.97-7 EPEL package. Amavis service now starts properly. Output of netstat shows "tcp 0 0 127.0.0.1:10024 0.0.0.0:* LISTEN 7286/amavisd (master" Version-Release number of selected component (if applicable): 2.007-2 How reproducible: Always Steps to Reproduce: 1. Install amavisd-new with perl-Net-Server 0.97-7 and test that it starts 2. Upgrade perl-Net-Server to version 2.007-2 3. Observe that the amavis service will not run Actual results: perl-Net-Server version 2.007-2 prevents amavis from running Expected results: Updating perl-Net-Server should not break amavis Additional info: 1. I do not use IPv6 (and don't want it!) 2. I was fortunate to find a copy of the perl-Net-Server-0.97-7.el6.noarch rpm as EPEL had already thoughtfully removed it from their server!
I had the same problem. Adding: $inet_socket_bind = '127.0.0.1'; # if only inet available to amavisd.conf appears to resolve the issue.
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our 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 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 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 EPEL 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. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.