From: Brian W. <bw...@gm...> - 2007-05-24 14:05:49
|
On 5/23/07, Ryan Ivey <iv...@gm...> wrote: > SLES 10 > sqlgrey 1.6.7 > postfix > mailwatch > mailscanner > > I have sqlgrey setup and configured and all appears fine when starting > sqlgrey in daemon mode and it logs and writes to the mysql database and > greylists each incoming message for the default 6 minutes, but as soon > as the 6 minutes is up and it begins allowing messages, sqlgrey dies and > the default port of 2501 closes. I run 'socklist |grep 2501' and see > several sqlgrey processes and can telnet 127.0.0.1 2501 without any > problems during the initial 6 minutes, but all processes drop and the > connection is refused once sqlgrey dies. I cannot figure out why > sqlgrey is dying. I restart sqlgrey when I see it stop, but it quickly > dies again and I can restart postfix, but this too doesn't fully resolve > the problem, besides it seems somewhat barbaric to setup a cron job to > run every 5 or 6 minutes to restart everything. Before I switch to > using postfix greylisting, does anyone have any pointers? I don't have > a problem with syslog, as I've noticed in other posts, besides I believe > 1.6.7 resolved that issue. > > Thanks, > Ryan I have found my sqlgrey process to consume more and more memory until it dies. Previous posts to this list indicate that it is a memory leak in the DBI driver. Monitor your memory usage. Perhaps you are suffering from the same problem? I use PgSQL. I had to resort to restarting the sqlgrey process every night. I didnt want to do this but I couldnt find a good alternative for sqlgrey. Hopefully everything will be sorted out soon. |