Share

SQLgrey Postfix greylisting service

Tracker: Bugs

5 sqlgrey process problem - ID: 1965695
Last Update: Comment added ( nobody )

Hi,

I am having problem with sqlgrey where
/usr/bin/perl -w /usr/local/sbin/sqlgrey -d

not running after few mins. There is no error log generated. did anyone has
similar problem?

Thanks.


Nobody/Anonymous ( nobody ) - 2008-05-16 22:35

5

Closed

Invalid

Nobody/Anonymous

None

v1.0 (example)

Public


Comments ( 4 )




Date: 2008-09-10 11:10
Sender: nobody

I discovered the same problem with sqlgrey 1.6.8 and mysql 5.0.51 here.

kernel: [687872.658710] sqlgrey[3190]: segfault at 4 ip b7b84874 sp
bfdbae40 error 4 in libmysqlclient.so.15.0.0[b7b16000+1a4000]

The problem is caused by the mysqld connection timeout (wait_timeout
parameter).
If I'm getting this right, sqlgrey starts a connection to mysqld, the
first time sqlgrey is accessed by postfix. This connection is kept open by
sqlgrey all the time.
If there's no other connect within 8 hours (the default for wait_timeout)
or what ever wait_timeout is set to, sqlgrey will seqfault the next time it
gets a connection and tries to use it's (timeouted) mysqlconnection.

So the problem is, sqlgrey does not detect this timeout right and is not
able to reconnect to mysql.


Date: 2008-07-11 13:08
Sender: gyverProject Admin


Segfaults can't be caused by pure Perl programs like SQLgrey. This is
probably an hardware problem. Marking invalid.


Date: 2008-07-11 11:37
Sender: nobody

Logged In: NO

I also have a similar problem.
I run daemon sqlgrey 1.6.8 with Mysql DBMS. DB access is "sync", not
"async".

I have just installed it in test environment with no connection. I start
sqlgrey and it works fine. I make SMTP session: it's ok.
After a day, I made an smtp session: sqlgrey segfault! This is the only
log written:

kernel:<6>sqlgrey[9861]: segfault at 0000000000000008 rip 0000003d2ca489d5
rsp 00007fff031e68e0 error 4

Marco
<falon AT csi.it>



Date: 2008-05-16 22:41
Sender: gyverProject Admin


- Can you run it without detaching from terminal (ie: without -d) to get a
look at any error that may be printed when it crashes?
- Which version are you using?


Log in to comment.




Attached File

No Files Currently Attached

Changes ( 3 )

Field Old Value Date By
status_id Open 2008-07-11 13:08 gyver
resolution_id None 2008-07-11 13:08 gyver
close_date - 2008-07-11 13:08 gyver