[Sqlgrey-users] sqlgrey stops after a while

[Michael Z. <zi...@ve...>]

Dear list,

after running a while sqlgrey stops working. 
The logs show, that it restarted, but it's
port is closed after the restart.

Running it with log-level 4 showed:

optin: greylisting active for zi...@ve...
grey: identified dynamic pattern (last IP byte): 
12-226-48-61.client.mchsi.com, 12.226.48.61: Using full IP.
grey: reconnect ok: 12.226.48.61(12.226.48.61), jo...@pi... -> 
zi...@ve... (00:05:05)
grey: from awl: 12.226.48.61, jo...@pi... added
request: ccert_fingerprint= ccert_issuer= ccert_subject= 
client_address=12.226.48.61 client_name=12-226-48-61.client.mchsi.com 
helo_name=friend instance=472.456e1830.0 protocol_name=ESMTP 
protocol_state=RCPT queue_id= recipient=zi...@ve... 
request=smtpd_access_policy sasl_method= sasl_sender= sasl_username= 
sender=jo...@pi... size=0 action=PREPEND X-Greylist: delayed 
00:05:05 by SQLgrey-1.7.4
2006/11/30-00:32:06 Server closing!
2006/11/30-00:32:06 HUP'ing server
2006/11/30-00:32:07 sqlgrey (type Net::Server::Multiplex) starting! 
pid(30268)
Use of uninitialized value in unlink at /usr/sbin/sqlgrey line 2577.
Binding open file descriptors
Binding to TCP port 2501 on host localhost
Setting gid to "66 66"
other: Initial cleanup
perf: spent 0s cleaning: from_awl (0) domain_awl (0) connect (0)
-- after that sqlgrey's port is closed --

As the lines before the final stop + (unsuccessful) restart don't have
a timestamp, I am not sure, that the last action did really occur just
before the shutdown+restart. Hence the reason for the shutdown could
well be something, which is not connected with the input (but perhaps
with a timeout on the postfix side?).


The sqlgrey is just started manually via a   

    # nohup sqlgrey &

or am I wrong about that, and the sqlgrey needs to be entered into the
master.cf to be started as a postfix-service?


Thanks for your ideas about that situation
Michael