Bug 518274
| Summary: | Unable to create inet socket for milter-greylist | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Eli Wapniarski <eli> |
| Component: | milter-greylist | Assignee: | Enrico Scholz <rh-bugzilla> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 11 | CC: | rh-bugzilla |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-06-28 14:11:03 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Eli Wapniarski
2009-08-19 17:20:18 UTC
Are you sure that your report is correct? The logfile message | local socket name /var/milter-greylist/milter-greylist.sock unsafe can not be caused by the | INPUT_MAIL_FILTER(`greylist',`S=inet:3333@localhost') sendmail.mc configuration. For the crashes (?) it would be interesting to know whether they * are reproducibly (e.g. immediately after startup), or whether they * are happening randomly It would be nice when you could provide a backtrace (after installing the milter-greylist-debuginfo package). Oops sorry about that good eye Aug 19 23:10:55 gw sendmail[7706]: n7JKAtGP007706: Milter (greylist): error connecting to filter: Connection refused by localhost Aug 19 23:10:55 gw sendmail[7706]: n7JKAtGP007706: Milter (greylist): to error state Message about the pid file is correct There is a very old discussion on the milter-greylist mailing list which led me to the solution of using the inet socket. The url is http://tech.groups.yahoo.com/group/milter-greylist/messages/1643?threaded=1&m=e&var=1&tidx=1 K... the newer milter-greylist is running (using unix socket). I'm assuming that this should, hopefully, fix it from crashing with the unix socket. Do you want me to try to get it running with an inet socket? Or is the same issue that prevented me from creating it with the older version still relevant? milter-greylist crashed again utilizing a unix socket. When I tried to restart the milter I got the following error message in the logs Aug 23 08:10:58 gw milter-greylist: greylist: Unable to bind to port unix:/var/lib/milter-greylist/milter-greylist.sock: Address already in use Aug 23 08:10:58 gw milter-greylist: greylist: Unable to create listening socket on conn unix:/var/lib/milter-greylist/milter-greylist.sock Aug 23 08:10:58 gw milter-greylist: smfi_main() returned -1 Aug 23 08:10:58 gw milter-greylist: Final database dump: no change to dump Aug 23 08:10:58 gw sendmail[12561]: n7N5AwsQ012561: Milter (greylist): error connecting to filter: Connection refused by /var/lib/milter-greylist/milter-gre ylist.sock Some good news however, I tried to run milter-greylist through an inet socket and the socket was created and milter-greylist is running. I will let you know how things go. OK... Its been several months and the newer version seems to be working without a hitch. It would be great if you could push the version to 4.2.3 to the Updates repository for Fedora 11. I see that its already available for Fedora 12. Thanks milter-greylist-4.2.3-1.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update milter-greylist'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2010-0386 I've been using the update for a long time. Works great with inet socket This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. 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 WONTFIX if it remains open with a Fedora 'version' of '11'. 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 Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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. Thank you for reporting this bug and we are sorry it could not be fixed. |