Menu
▾
▴
sqlgrey-users
|
From: Beast <be...@i6...> - 2005-08-11 03:33:27
|
This morning I found that sqlgrey daemon dies. Aug 11 07:35:22 blowfish sqlgrey: fatal: Modification of a read-only value attempted at /usr/lib/perl5/5.8.5/i386-linux-thread-multi/Sys/Syslog.pm line 312. Aug 11 07:35:22 blowfish postfix/smtpd[4367]: warning: premature end-of-input on 127.0.0.1:2501 while reading input attribute name Aug 11 07:35:23 blowfish postfix/smtpd[4367]: warning: connect to 127.0.0.1:2501: Connection refused What could be the reason? sqlgrey ver. 1.5.7 -- --beast |
|
From: Ryan I. <iv...@gm...> - 2007-05-24 01:12:19
|
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 |
|
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. |
|
From: Matteo N. <mat...@st...> - 2007-05-24 14:26:18
|
Brian Wong ha scritto: > 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. Yes, there's a memory leak in DBI version < 1.5.2. After upgrade to 1.5.5 memory leak has been partialy solved. Now sqlgrey eat 1mbyte of ram per days, instead of 1MByte each 10 minutes :) |
|
From: Beast <be...@i6...> - 2005-08-11 05:18:24
|
Beast wrote: > > This morning I found that sqlgrey daemon dies. > > Aug 11 07:35:22 blowfish sqlgrey: fatal: Modification of a read-only > value attempted at > /usr/lib/perl5/5.8.5/i386-linux-thread-multi/Sys/Syslog.pm line 312. > Aug 11 07:35:22 blowfish postfix/smtpd[4367]: warning: premature > end-of-input on 127.0.0.1:2501 while reading input attribute name > Aug 11 07:35:23 blowfish postfix/smtpd[4367]: warning: connect to > 127.0.0.1:2501: Connection refused > > What could be the reason? > > sqlgrey ver. 1.5.7 > > > This is the first time after running smoothly for more than 2 months, today it dies 3 times. I think some mail could trigger it, but found nothing on the log file. [root@blowfish log]# grep fatal maillog Aug 11 07:35:22 blowfish sqlgrey: fatal: Modification of a read-only value attempted at /usr/lib/perl5/5.8.5/i386-linux-thread-multi/Sys/Syslog.pm line 312. Aug 11 10:38:12 blowfish sqlgrey: fatal: Modification of a read-only value attempted at /usr/lib/perl5/5.8.5/i386-linux-thread-multi/Sys/Syslog.pm line 312. Aug 11 12:09:51 blowfish sqlgrey: fatal: Modification of a read-only value attempted at /usr/lib/perl5/5.8.5/i386-linux-thread-multi/Sys/Syslog.pm line 312. I'm setting loglevel to 4 now and see what happen in the next few hours :-( -- --beast |
|
From: Beast <be...@i6...> - 2005-08-11 06:33:16
|
Beast wrote: > Beast wrote: > >> >> This morning I found that sqlgrey daemon dies. >> >> Aug 11 07:35:22 blowfish sqlgrey: fatal: Modification of a read-only >> value attempted at >> /usr/lib/perl5/5.8.5/i386-linux-thread-multi/Sys/Syslog.pm line 312. >> Aug 11 07:35:22 blowfish postfix/smtpd[4367]: warning: premature >> end-of-input on 127.0.0.1:2501 while reading input attribute name >> Aug 11 07:35:23 blowfish postfix/smtpd[4367]: warning: connect to >> 127.0.0.1:2501: Connection refused >> >> What could be the reason? >> >> sqlgrey ver. 1.5.7 >> >> >> > > This is the first time after running smoothly for more than 2 months, > today it dies 3 times. I think some mail could trigger it, but found > nothing on the log file. > > [root@blowfish log]# grep fatal maillog > Aug 11 07:35:22 blowfish sqlgrey: fatal: Modification of a read-only > value attempted at > /usr/lib/perl5/5.8.5/i386-linux-thread-multi/Sys/Syslog.pm line 312. > Aug 11 10:38:12 blowfish sqlgrey: fatal: Modification of a read-only > value attempted at > /usr/lib/perl5/5.8.5/i386-linux-thread-multi/Sys/Syslog.pm line 312. > Aug 11 12:09:51 blowfish sqlgrey: fatal: Modification of a read-only > value attempted at > /usr/lib/perl5/5.8.5/i386-linux-thread-multi/Sys/Syslog.pm line 312. > > I'm setting loglevel to 4 now and see what happen in the next few hours :-( > I think I've found the problem, it always dies whenever 061196164024.cidr.odn.ne.jp send an email. --- Aug 11 12:55:58 blowfish sqlgrey: optin: greylisting active for xx...@my... Aug 11 12:55:58 blowfish sqlgrey: grey: identified dynamic pattern (last IP byte): 061196164024.cidr.odn.ne.jp, 61.196.164.24: Using full IP. Aug 11 12:55:58 blowfish sqlgrey: fatal: Modification of a read-only value attempted at /usr/lib/perl5/5.8.5/i386-linux-thread-multi/Sys/Syslog.pm line 312. Aug 11 12:55:58 blowfish postfix/smtpd[5359]: warning: premature end-of-input on 127.0.0.1:2501 while reading input attribute name -- --beast |
|
From: Beast <be...@i6...> - 2005-08-11 06:46:33
|
Beast wrote: > > I think I've found the problem, it always dies whenever > 061196164024.cidr.odn.ne.jp send an email. > > --- > Aug 11 12:55:58 blowfish sqlgrey: optin: greylisting active for > xx...@my... > Aug 11 12:55:58 blowfish sqlgrey: grey: identified dynamic pattern (last > IP byte): 061196164024.cidr.odn.ne.jp, 61.196.164.24: Using full IP. > Aug 11 12:55:58 blowfish sqlgrey: fatal: Modification of a read-only > value attempted at > /usr/lib/perl5/5.8.5/i386-linux-thread-multi/Sys/Syslog.pm line 312. > Aug 11 12:55:58 blowfish postfix/smtpd[5359]: warning: premature > end-of-input on 127.0.0.1:2501 while reading input attribute name > It is because of mail from using "%". I have tried sending mail with this kind of address (from any host) and sqlgrey dies, probably because of unquote '%'. MAIL FROM: <LNGNOTES/LNGJAPAN%LNG...@ln...> -- --beast |
|
From: Lionel B. <lio...@bo...> - 2005-08-11 09:05:01
|
Beast wrote the following on 11.08.2005 08:45 : > [...] > It is because of mail from using "%". I have tried sending mail with > this kind of address (from any host) and sqlgrey dies, probably > because of unquote '%'. > > MAIL FROM: <LNGNOTES/LNGJAPAN%LNG...@ln...> > > This problem was fixed with the 1.6.2 release. Just install latest stable SQLgrey (1.6.5) and the problem will go away. Lionel |
|
From: Beast <be...@i6...> - 2005-08-11 09:57:26
|
Lionel Bouton wrote: > Beast wrote the following on 11.08.2005 08:45 : > >> [...] >> It is because of mail from using "%". I have tried sending mail with >> this kind of address (from any host) and sqlgrey dies, probably >> because of unquote '%'. >> >> MAIL FROM: <LNGNOTES/LNGJAPAN%LNG...@ln...> >> >> > > This problem was fixed with the 1.6.2 release. Just install latest > stable SQLgrey (1.6.5) and the problem will go away. > Tks. I've reject it on sender_access. -- --beast |
|
From: Beast <be...@i6...> - 2005-08-11 11:40:46
|
Lionel Bouton wrote: > Beast wrote the following on 11.08.2005 08:45 : > >> [...] >> It is because of mail from using "%". I have tried sending mail with >> this kind of address (from any host) and sqlgrey dies, probably >> because of unquote '%'. >> >> MAIL FROM: <LNGNOTES/LNGJAPAN%LNG...@ln...> >> >> > > This problem was fixed with the 1.6.2 release. Just install latest > stable SQLgrey (1.6.5) and the problem will go away. Do I need to recreate mysql table after upgrading? Tks. -- --beast |
|
From: Lionel B. <lio...@bo...> - 2005-08-11 11:53:00
|
Beast wrote the following on 11.08.2005 13:40 : > Lionel Bouton wrote: > >> [...] >> This problem was fixed with the 1.6.2 release. Just install latest >> stable SQLgrey (1.6.5) and the problem will go away. > > > Do I need to recreate mysql table after upgrading? > Tks. > No. SQLgrey upgrades never need database administration: tables are automatically converted to new formats and new tables are created by SQLgrey itself when needed. Lionel. |
|
From: Michael S. <Mic...@lr...> - 2005-08-11 11:55:04
|
On Thu, 11 Aug 2005, Beast wrote: > Lionel Bouton wrote: > > Beast wrote the following on 11.08.2005 08:45 : > > > >> [...] > >> It is because of mail from using "%". I have tried sending mail with > >> this kind of address (from any host) and sqlgrey dies, probably > >> because of unquote '%'. > >> > >> MAIL FROM: <LNGNOTES/LNGJAPAN%LNG...@ln...> > >> > >> > > > > This problem was fixed with the 1.6.2 release. Just install latest > > stable SQLgrey (1.6.5) and the problem will go away. > > Do I need to recreate mysql table after upgrading? > Tks. > You don't have to, sqlgrey handles necessary upgrades of the tables automatically. Michael Storz ------------------------------------------------- Leibniz-Rechenzentrum ! <mailto:St...@lr...> Barer Str. 21 ! Fax: +49 89 2809460 80333 Muenchen, Germany ! Tel: +49 89 289-28840 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X