Bug 518274 - Unable to create inet socket for milter-greylist
Summary: Unable to create inet socket for milter-greylist
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: milter-greylist
Version: 11
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Enrico Scholz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-19 17:20 UTC by Eli Wapniarski
Modified: 2010-06-28 14:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-28 14:11:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Eli Wapniarski 2009-08-19 17:20:18 UTC
I've been using milter-greylist for a number of years. Up until Fedora 10 I've had no trouble using it through an inet socket. After installing Fedora 11 and starting milter-regex and then checking the status with

/etc/rc.d/init.d/milter-regex

reports that the process is dead but that the pid exists

The maillog reports:

Aug 19 18:22:27 gw sendmail[4512]: n7JFMR3P004512: Milter (greylist): local socket name /var/milter-greylist/milter-greylist.sock unsafe
Aug 19 18:22:27 gw sendmail[4512]: n7JFMR3P004512: Milter (greylist): to 


The reason that this is important that when using a unix socket milter-regex crashes at random time intervals and when it does, of course the mail is halted.

Please find below relevant information about my installation and configuration.

I appreciate you looking into this. If you need any more info from me please do not hesitate to ask.

Currently I have installed

milter-greylist-4.2.2-0.fc11.x86_64
sendmail-8.14.3-5.fc11.x86_64


relevant line in sendmail.mc
----------------------------------
INPUT_MAIL_FILTER(`greylist',`S=inet:3333@localhost')


relevant lines in greylist.conf
-------------------------------
pidfile "/var/run/milter-greylist.pid"
socket "inet:3333@localhost"
dumpfile "/var/lib/milter-greylist/db/greylist.db" 600
geoipdb "/usr/share/GeoIP/GeoIP.dat"
dumpfreq 1
user "grmilter"

Comment 1 Enrico Scholz 2009-08-19 19:32:19 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).

Comment 2 Eli Wapniarski 2009-08-19 20:12:49 UTC
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

Comment 3 Enrico Scholz 2009-08-19 20:57:07 UTC
Please try
http://koji.fedoraproject.org/koji/buildinfo?buildID=127939

Comment 4 Eli Wapniarski 2009-08-20 05:35:19 UTC
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?

Comment 5 Eli Wapniarski 2009-08-23 05:21:55 UTC
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.

Comment 6 Eli Wapniarski 2009-12-05 06:43:49 UTC
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

Comment 7 Fedora Update System 2010-01-12 23:43:32 UTC
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

Comment 8 Eli Wapniarski 2010-01-13 05:21:24 UTC
I've been using the update for a long time. Works great with inet socket

Comment 9 Bug Zapper 2010-04-28 09:50:23 UTC
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

Comment 10 Bug Zapper 2010-06-28 14:11:03 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.