Recent changes to support-requests

Error in log

Anonymous — Thu, 24 Feb 2011 09:57:26 -0000

Dear all,

i've found this three kind of error during normal work with sqlgrey:

First One:

Feb 23 03:15:28 [sqlgrey] dbaccess: error: couldn't get now() from DB: Too many connections_
Feb 23 03:15:28 [sqlgrey] dbaccess: error: couldn't access domain_awl table: Too many connections_
Feb 23 03:15:28 [sqlgrey] dbaccess: error: couldn't get now() from DB: Too many connections_
Feb 23 03:15:28 [sqlgrey] dbaccess: error: couldn't access domain_awl table: Too many connections_
Feb 23 03:15:28 [sqlgrey] dbaccess: error: couldn't get now() from DB: Too many connections_
Feb 23 03:15:28 [sqlgrey] dbaccess: error: couldn't access domain_awl table: Too many connections_

Second Warn:

Feb 23 02:25:12 [sqlgrey] dbaccess: warning: couldn't do query:_UPDATE domain_awl SET last_seen = NOW(), first_seen = first_seen WHERE sender_domain = NULL AND src = NULL:_Too many connections, reconnecting to DB_
Feb 23 02:25:12 [sqlgrey] dbaccess: warning: couldn't do query:_UPDATE domain_awl SET last_seen = NOW(), first_seen = first_seen WHERE sender_domain = NULL AND src = NULL:_Too many connections, reconnecting to DB_

Third:
Feb 23 21:07:49 [sqlgrey] dbaccess: warning: couldn't do query:_UPDATE from_awl SET last_seen = NOW(), first_seen = first_seen WHERE sender_name = 'maría073' AND sender_domain = '3016.jp' AND src = '79.163.190.114':_Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '=', reconnecting to DB_
Feb 23 21:07:50 [sqlgrey] dbaccess: warning: couldn't do query:_UPDATE from_awl SET last_seen = NOW(), first_seen = first_seen WHERE sender_name = 'maría073' AND sender_domain = '3016.jp' AND src = '79.163.190.114':_Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '=', reconnecting to DB_
Feb 23 21:07:50 [sqlgrey] dbaccess: warning: couldn't do query:_UPDATE from_awl SET last_seen = NOW(), first_seen = first_seen WHERE sender_name = 'maría073' AND sender_domain = '3016.jp' AND src = '79.163.190.114':_Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '=', reconnecting to DB_

It look strange because the db won't grow up, and stll on 200MB.

Any suggestions ?

Rgs
Maximilian

Problem with special chars in email

Anonymous — Mon, 14 Feb 2011 17:05:28 -0000

an email like bla_#.#@abc.com cannot be deleted from autowhite list

Problem with sqlgrey and mysql 5.1

Will McCown — Sun, 03 Jan 2010 22:51:15 -0000

The database initialization in sqlgrey failed with mysql 5.1.

After some effort the problem was traced to the following message:

Specified key was too long; max key length is 1000 bytes...

The cure was to modify the create table statements to add the the
qualifier "CHARACTER SET latin1" to several of the columns.

Details of the changes in the attached file.

I can't say for sure, but I would expect that this change would do no
harm on other installations.

Losing connection to MySQL

Nejc Škoberne — Tue, 31 May 2005 12:00:30 -0000

Hi,

I am constantly getting these with 1.4.5:

May 31 13:54:56 cygnus sqlgrey: failed to send mail: No
child processes
May 31 13:54:56 cygnus sqlgrey: Warning: couldn't do
query: INSERT INTO from_awl (sender_name,
sender_domain, host_ip, last_seen)
VALUES(NULL,'-undef-','202.108.255',NOW()): Column
'sender_name' cannot be null, reconnecting to DB
May 31 13:54:56 cygnus sqlgrey: failed to send mail: No
child processes

What's the solution?

Thanks.

Nejc

Fatal error

jean — Fri, 25 Feb 2005 08:49:00 -0000

postfix 2.1.5-3
sqlgrey 1.4.8 and 1.5.0
perl 5.8.3-18

Feb 23 09:27:43 mail sqlgrey:
fatal: Modification of a read-only value attempted
at /usr/lib/perl5/5.8.3/i386-linux-thread-
multi/Sys/Syslog.pm line 312.

I have the problem three times per day