Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: DBMail: users

imapd error

  

 
DBMail users RSS feed   Index | Next | Previous | View Threaded


jon at host-it

Nov 6, 2008, 3:14 AM

Post #1 of 10 (1577 views)
Permalink
imapd error
Hey guys,



(Apologise if this is a duplicate post - I don't see my first attempt at
time of writing and believe the attachment may have been too big)



After digging through logs for an unrelated problem i came across these
errors;



http://pure.noffle.net/~jduggan/error.out



Looking back through logs they go back atleast the last 7 days. Are they
anything to worry about?



TIA



Jon


paul at nfg

Nov 6, 2008, 3:35 AM

Post #2 of 10 (1507 views)
Permalink
Re: imapd error [In reply to]
Not good.

What version are you running?


Jon Duggan wrote:
> Hey guys,
>
>
>
> (Apologise if this is a duplicate post – I don’t see my first attempt at
> time of writing and believe the attachment may have been too big)
>
>
>
> After digging through logs for an unrelated problem i came across these
> errors;
>
>
>
> http://pure.noffle.net/~jduggan/error.out
>
>
>
> Looking back through logs they go back atleast the last 7 days. Are
> they anything to worry about?
>
>
>
> TIA
>
>
>
> Jon
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> DBmail mailing list
> DBmail [at] dbmail
> https://mailman.fastxs.nl/mailman/listinfo/dbmail


--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmail [at] dbmail
https://mailman.fastxs.nl/mailman/listinfo/dbmail


jon at host-it

Nov 6, 2008, 4:11 AM

Post #3 of 10 (1502 views)
Permalink
RE: imapd error [In reply to]
Hi Paul,

Thanks for the swift response.

This is DBMail version 2.2.10

I have had a few occasions where users say they have lost email, are these errors possibly related?

Just for extra information, it's a production system with about 6000 mail accounts, running on mysql (debian packages) on debian etch.

If you need any further information let me know.

TIA

Jon


-----Original Message-----
From: dbmail-bounces [at] dbmail [mailto:dbmail-bounces [at] dbmail] On Behalf Of Paul J Stevens
Sent: 06 November 2008 11:35
To: DBMail mailinglist
Subject: Re: [Dbmail] imapd error


Not good.

What version are you running?


Jon Duggan wrote:
> Hey guys,
>
>
>
> (Apologise if this is a duplicate post – I don’t see my first attempt at
> time of writing and believe the attachment may have been too big)
>
>
>
> After digging through logs for an unrelated problem i came across these
> errors;
>
>
>
> http://pure.noffle.net/~jduggan/error.out
>
>
>
> Looking back through logs they go back atleast the last 7 days. Are
> they anything to worry about?
>
>
>
> TIA
>
>
>
> Jon
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> DBmail mailing list
> DBmail [at] dbmail
> https://mailman.fastxs.nl/mailman/listinfo/dbmail


--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmail [at] dbmail
https://mailman.fastxs.nl/mailman/listinfo/dbmail

_______________________________________________
DBmail mailing list
DBmail [at] dbmail
https://mailman.fastxs.nl/mailman/listinfo/dbmail


paul at nfg

Nov 6, 2008, 6:08 AM

Post #4 of 10 (1507 views)
Permalink
Re: imapd error [In reply to]
Jon Duggan wrote:
> Hi Paul,
>
> Thanks for the swift response.
>
> This is DBMail version 2.2.10
>
> I have had a few occasions where users say they have lost email, are these errors possibly related?

That would be the first time, afaik. I can't tell if there's a relation.
The logs you sent contain insufficient information. I'd need to see the
query that triggered the error.

>
> Just for extra information, it's a production system with about 6000 mail accounts, running on mysql (debian packages) on debian etch.
>
> If you need any further information let me know.

Next time you see this error, try find out what query triggers the error.



--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmail [at] dbmail
https://mailman.fastxs.nl/mailman/listinfo/dbmail


jon at host-it

Nov 6, 2008, 7:04 AM

Post #5 of 10 (1501 views)
Permalink
RE: imapd error [In reply to]
>> I have had a few occasions where users say they have lost email, are these errors possibly related?
>
>That would be the first time, afaik. I can't tell if there's a relation.

This possibly isn’t dbmail related (could be our spam filtering)

>Next time you see this error, try find out what query triggers the error.

Full log level 5 for a session with such an error can be found here;

http://pure.noffle.net/~jduggan/debug5.imapd.out

If you need further information do let me know.

TIA

Jon

_______________________________________________
DBmail mailing list
DBmail [at] dbmail
https://mailman.fastxs.nl/mailman/listinfo/dbmail


paul at nfg

Nov 6, 2008, 7:43 AM

Post #6 of 10 (1500 views)
Permalink
Re: imapd error [In reply to]
Jon Duggan wrote:
>>> I have had a few occasions where users say they have lost email, are these errors possibly related?
>> That would be the first time, afaik. I can't tell if there's a relation.
>
> This possibly isn’t dbmail related (could be our spam filtering)
>
>> Next time you see this error, try find out what query triggers the error.
>
> Full log level 5 for a session with such an error can be found here;
>
> http://pure.noffle.net/~jduggan/debug5.imapd.out
>
> If you need further information do let me know.

Ok, nothing to worry about. The \Recent flag on messages will be
incorrect, but no information is lost.

The culprit:

Nov 6 14:38:58 mail4-core-2 dbmail/imap4d[15280]: Debug:[sql]
dbmysql.c,db_query(+287): query [UPDATE dbmail_messages SET recent_flag
= 0 WHERE message_idnr IN
(111121490,111119585,111119583,111118476,111115033,111114577,111114513,111114435,111113252,111110017,111109091,111108924,111108856,111107547,111104702,111098668,111096873,111095754,111093348,111092274,111090584,111089386,111088908,111088902,111088896,111088358,111085966,111074995,111074979,111068531,111065104,111065075,111058877,111056716,111051771,111046856,111043290,111042377,111040034,111039521,111039373,111037608,111034241,111007526,111006402,111006400,110997376,110997368,110997362,110994745,110994430,110992837,110991077,110990770,110989845,110987452,110954508,110946557,110945055,110942293,110941632,110940259,110938366,110932182,110931854,110928380,110927388,110926762,110924874,110923621,110923571,110923160,110922104,110920849,110920621,110919293,110918052,110917877,110917392,110916931,110916283,110915045,110913165,110909253,110908379,110907732,110907730



Apparently the line is too long for mysql to handle.

Try tweaking dbmail-imapsession.c, line 2088:

topslices = g_list_slices(recent,100);

setting it to someting like

topslices = g_list_slices(recent,50);

because that determines the number of message_idnrs in the IN(...) part
of the query.

But you may want to verify this by using TRACE_STDERR=5 rather than
syslog. For stderr logging the query will not be truncated so you can
capture it, and test it manually. Perhaps your max_allowed_packet in
my.cnf is too small. Check that first.



--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmail [at] dbmail
https://mailman.fastxs.nl/mailman/listinfo/dbmail


vulture at netvulture

Nov 6, 2008, 7:57 AM

Post #7 of 10 (1503 views)
Permalink
Re: imapd error [In reply to]
It looks like you have either a db schema issue, or database server problem.

Please do a show create table dbmail_messages;
You should have a recent_flag field.
If you are missing that field (unlikely) do a alter table
dbmail_messages add column `recent_flag` tinyint(1) NOT NULL DEFAULT '0';

You should also check the output for other fields that are missing
against the create_tables.mysql file in the dist.

Also, what version of MySQL are you running?

-Jon

Jon Duggan wrote:
>>> I have had a few occasions where users say they have lost email, are these errors possibly related?
>>>
>> That would be the first time, afaik. I can't tell if there's a relation.
>>
>
> This possibly isn’t dbmail related (could be our spam filtering)
>
>
>> Next time you see this error, try find out what query triggers the error.
>>
>
> Full log level 5 for a session with such an error can be found here;
>
> http://pure.noffle.net/~jduggan/debug5.imapd.out
>
> If you need further information do let me know.
>
> TIA
>
> Jon
>
> _______________________________________________
> DBmail mailing list
> DBmail [at] dbmail
> https://mailman.fastxs.nl/mailman/listinfo/dbmail
>
>


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

_______________________________________________
DBmail mailing list
DBmail [at] dbmail
https://mailman.fastxs.nl/mailman/listinfo/dbmail


jon at host-it

Nov 6, 2008, 9:04 AM

Post #8 of 10 (1507 views)
Permalink
RE: imapd error [In reply to]
>It looks like you have either a db schema issue, or database server problem.
>
>Please do a show create table dbmail_messages;
>You should have a recent_flag field.
>If you are missing that field (unlikely) do a alter table
>dbmail_messages add column `recent_flag` tinyint(1) NOT NULL DEFAULT '0';
>
>You should also check the output for other fields that are missing
>against the create_tables.mysql file in the dist.


My show create table doesn’t show the indexes or the foreign key restraints, though show indexes from dbmail_messages does show the following (apologise if it gets wrapped and distorted);

+-----------------+------------+----------------+--------------+----------------+-----------+-------------+----------+--------+------+------------+---------+
| Table | Non_unique | Key_name | Seq_in_index | Column_name | Collation | Cardinality | Sub_part | Packed | Null | Index_type | Comment |
+-----------------+------------+----------------+--------------+----------------+-----------+-------------+----------+--------+------+------------+---------+
| dbmail_messages | 0 | PRIMARY | 1 | message_idnr | A | 1675868 | NULL | NULL | | BTREE | |
| dbmail_messages | 1 | physmessage_id | 1 | physmessage_id | A | 1675868 | NULL | NULL | | BTREE | |
| dbmail_messages | 1 | mailbox_idnr | 1 | mailbox_idnr | A | 12506 | NULL | NULL | | BTREE | |
| dbmail_messages | 1 | seen_flag | 1 | seen_flag | A | 20 | NULL | NULL | | BTREE | |
| dbmail_messages | 1 | unique_id | 1 | unique_id | A | 1675868 | NULL | NULL | | BTREE | |
| dbmail_messages | 1 | status | 1 | status | A | 20 | NULL | NULL | | BTREE | |
+-----------------+------------+----------------+--------------+----------------+-----------+-------------+----------+--------+------+------------+---------+


We upgraded from 2.0.11 about 16months ago so possibly the upgrade missed some out?

The following is the output of my show create table...


| dbmail_messages | CREATE TABLE `dbmail_messages` (
`message_idnr` bigint(21) NOT NULL auto_increment,
`mailbox_idnr` bigint(21) NOT NULL default '0',
`physmessage_id` bigint(21) NOT NULL default '0',
`seen_flag` tinyint(1) NOT NULL default '0',
`answered_flag` tinyint(1) NOT NULL default '0',
`deleted_flag` tinyint(1) NOT NULL default '0',
`flagged_flag` tinyint(1) NOT NULL default '0',
`recent_flag` tinyint(1) NOT NULL default '0',
`draft_flag` tinyint(1) NOT NULL default '0',
`unique_id` varchar(70) NOT NULL default '',
`status` tinyint(3) unsigned zerofill NOT NULL default '000',
PRIMARY KEY (`message_idnr`),
KEY `physmessage_id` (`physmessage_id`),
KEY `mailbox_idnr` (`mailbox_idnr`),
KEY `seen_flag` (`seen_flag`),
KEY `unique_id` (`unique_id`),
KEY `status` (`status`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 |

>Also, what version of MySQL are you running?

We're running 5.0.32 (debian etch release). Do you need any more info?

TIA

Jon


_______________________________________________
DBmail mailing list
DBmail [at] dbmail
https://mailman.fastxs.nl/mailman/listinfo/dbmail


dbmail at tech

Nov 10, 2008, 3:03 AM

Post #9 of 10 (1486 views)
Permalink
Re: imapd error [In reply to]
>
> Ok, nothing to worry about. The \Recent flag on messages will be
> incorrect, but no information is lost.
>
> The culprit:
>
> Nov 6 14:38:58 mail4-core-2 dbmail/imap4d[15280]: Debug:[sql]
> dbmysql.c,db_query(+287): query [UPDATE dbmail_messages SET recent_flag
> = 0 WHERE message_idnr IN
> (111121490,111119585,111119583,111118476,111115033,111114577,111114513,111114435,111113252,111110017,111109091,111108924,111108856,111107547,111104702,111098668,111096873,111095754,111093348,111092274,111090584,111089386,111088908,111088902,111088896,111088358,111085966,111074995,111074979,111068531,111065104,111065075,111058877,111056716,111051771,111046856,111043290,111042377,111040034,111039521,111039373,111037608,111034241,111007526,111006402,111006400,110997376,110997368,110997362,110994745,110994430,110992837,110991077,110990770,110989845,110987452,110954508,110946557,110945055,110942293,110941632,110940259,110938366,110932182,110931854,110928380,110927388,110926762,110924874,110923621,110923571,110923160,110922104,110920849,110920621,110919293,110918052,110917877,110917392,110916931,110916283,110915045,110913165,110909253,110908379,110907732,110907730
>
>
>
> Apparently the line is too long for mysql to handle.
>
> Try tweaking dbmail-imapsession.c, line 2088:
>
> topslices = g_list_slices(recent,100);
>
> setting it to someting like
>
> topslices = g_list_slices(recent,50);
>
> because that determines the number of message_idnrs in the IN(...) part
> of the query.
>
> But you may want to verify this by using TRACE_STDERR=5 rather than
> syslog. For stderr logging the query will not be truncated so you can
> capture it, and test it manually. Perhaps your max_allowed_packet in
> my.cnf is too small. Check that first.
>
We're also occasionally receiving the same: Error:[imap]
imap4.c,IMAPClientHandler(+307): command return with error [idle]

We're on 2.2.11-rc2 installed via source on mysql 5.0.51a (deb) with
40gig dbmail db.

The default packet is 16mb, I doubt 100 items would exceed 1mb let alone
16 - on our other web reporting platform we have people doing where in
on thousands of rows with a16meg default packet - its probably another
strange mysql bug :o(

I'll change to 2.2.11.rc-3, trace_stderr=5 and topslices =
g_list_slices(recent,50); as suggested during our next maintenance
window and let you know.

S


paul at nfg

Nov 10, 2008, 4:58 AM

Post #10 of 10 (1481 views)
Permalink
Re: imapd error [In reply to]
Simon Gray wrote:
> We're also occasionally receiving the same: Error:[imap]
> imap4.c,IMAPClientHandler(+307): command return with error [idle]

You can ignore those. Could be a client hanging up without logging out,
or issuing a valid 'DONE' response.

> I'll change to 2.2.11.rc-3, trace_stderr=5 and topslices =
> g_list_slices(recent,50); as suggested during our next maintenance
> window and let you know.

If all you see is the IDLE error, this won't make any difference.


--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmail [at] dbmail
https://mailman.fastxs.nl/mailman/listinfo/dbmail

DBMail users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.