Re: Migration of Data from 2.2.17 to 3.0.2 (dbmail-util coredumping)

Resending as it does not appear to have arrived!

On 24/05/2012 10:32, Alan Hicks wrote:
> On 24/05/2012 08:52, Paul J Stevens wrote:
>> On 05/22/2012 01:17 PM, Daniel Schütze wrote:
>>> Can anyone suggest to me what might be going wrong, or if there is
>>> anything useful I can examine? So far this has happened 7 times up to
>>> physmessage_id 612844 (out of the 900k or so) so it is infrequent but
>>> being a coredump it does mean it halts the migration which is
>>> inconvenient. I am running MySQL 5.1.55, on freebsd 8.2 for general
>>> information.
> Apologies I only just picked up on fbsd. I'm preparing an upgrade to
> gmime and will hopefully have this later today, the port is unmaintained
> so unless anyone else is interested I'll look after it.
Submitted as http://www.freebsd.org/cgi/query-pr.cgi?pr=168308

>
> I'm aware of issues with ldap and the latest git appears to fix those so
> they maybe related, it's been a low priority for me recently, guess this
> bumps it up.
>>
>> Did you run the full schema migration successfully first?
>>
>>> Also, and separately, the migration is pretty slow overall which is an
>>> issue for the downtime it will cause. Looking at the test box (4 core
>>> Xeon, 4gig ram, standard hdd) during the conversion the processor load
>>> is low (20% overall i.e. 1 processor at under 100%), the disk utility is
>>> low (normally under 50%) and innodb pool is set to 500meg which is
>>> obviously full, so can someone suggest what is rate limiting the
>>> conversion?
>>

Re: Migration of Data from 2.2.17 to 3.0.2 (dbmail-util coredumping)

>Did you run the full schema migration successfully first?

Yes I ran it without error (took 24 hrs on the test box mind you!).

>Running dbmail-util -M is not required and does not require downtime.
>The data-store is backward compatible - only body searches will not work
>on messageblks.

I hadn't appreciated that at the time, though it is clearly laid out in the
docs which I saw when I re-read them.  I will want to migrate the messages
in due course to free up space of course.

>That said: I haven't seen this problem yet.

>Since the core dump seems to originate from gmime, I would advise you to
>upgrade to the latest gmime-2.4. I see rfc2047 related bugfixes at least
>in 2.4.30, and probably later ones as well.

I am using the freebsd ports and the latest version available is 2.4.24

Given the whole run is a test anyway I've started from scratch after making
some adjustments esp. as I want to see the system in action above rebuilding
the headers but before the message migration, then I'll try the migration
and see if that gives rise to the same issue.

Daniel Schütze

Re: switch to GMime-2.6 for development

Am 23.05.2012 18:27, schrieb Jorge Bastos:
>>> checking GMime version >= 2.6.0... configure: error: At least GMime
>> version 2.6.0 is required.
>>> error: Bad exit status from /var/tmp/rpm-tmp.5SAUE0 (%build)
>>
>> http://koji.fedoraproject.org/koji/packageinfo?packageID=325
>> Fedora 17 (released in two weeks is the first one with 2.6)
>>
>> i do not like to upgrade to F17 until it is hardly needed because
>> currently are too much php-pecl extensions still not supporting PHP 5.4
>> (the most important suhosin)
>>
>> please do not require gmime 2.6 too soon because Fedora is bleeding
>> edge and other distributions are behind
> 
> Go Debian :)
> 
> Works fine for me, and 2.6 is only for the master not the stable 3.x

no, thanks 

no .deb after 10 years Redhat
no back to sysv after all the pain with systemd at begin

and no replacement of > 20 virtual servers with a internal
build/update/test-infrastructure and not after 7 successfull
dist-upgrades in this environment from F9 to F16 since 2008

not for one package and running the mailsevrer another

switch to GMime-2.6 for development

Hi

> http://git.dbmail.eu/paul/dbmail/commit/?id=4e057f0741328a8c510cc4546555406c7415c140
> switch to GMime-2.6 for development

i am fine with this

but

> checking GMime version >= 2.6.0... configure: error: At least GMime version 2.6.0 is required.
> error: Bad exit status from /var/tmp/rpm-tmp.5SAUE0 (%build)

http://koji.fedoraproject.org/koji/packageinfo?packageID=325
Fedora 17 (released in two weeks is the first one with 2.6)

i do not like to upgrade to F17 until it is hardly needed because
currently are too much php-pecl extensions still not supporting
PHP 5.4 (the most important suhosin)

please do not require gmime 2.6 too soon because Fedora
is bleeding edge and other distributions are behind

_______________________________________________
DBmail mailing list
DBmail <at> dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

Sieve script vacation not working

I am using dbmail 3.0 and while sieve scripts work fine, I can't use the
vacation script. I tried a very simple one like:

require ["vacation"];
   if header :matches "subject" "*" {
       vacation :subject "Automatic response"
                "I'm away -- send mail to foo in my absence";
   }

But it doesn't work. I get the following error in the debug log:

May 22 17:24:37 dbmail32 dbmail-lmtpd[4512]: [0x9bc3fb8] Debug:[sort]
sort_debugtrace(+625): sieve: [sv_interface,script.c,libsieve_eval:
[VACATION aborted: no match found in script.]

Any idea? Can you provide me your sieve script for example?

Leandro

Re: Migration of Data from 2.2.17 to 3.0.2 (dbmail-util coredumping)

Actually it's now gotten to the point where dbmail-util -My doesn’t run for
more than a couple of seconds before I get the errors I'm encountering.  I'm
not getting so many core dumps as just simple aborts to the command line:

	May 22 13:56:22 dbm3 dbmail-util[14952]: [0x80220b040] Error:[db]
db_exec(+319): 	SQLException: Cannot add or update a child row: a foreign
key constraint fails 	(`dbmail`.`dbmail_partlists`, CONSTRAINT
`dbmail_partlists_ibfk_1` FOREIGN KEY 	(`physmessage_id`) REFERENCES
`dbmail_physmessage` (`id`) ON DELETE CASCADE ON UPDATE 	CASCADE)
	May 22 13:56:22 dbm3 dbmail-util[14952]: [0x80220b040] Error:[db]
db_exec(+320): failed 	query [INSERT INTO dbmail_partlists (physmessage_id,
is_header, part_key, part_depth, 	part_order, part_id) VALUES
(657895,1,1,0,0,27)]
	migrating physmessage_id: 657895
	failed

From the messages (phymessage_id) affected it is clear that the frequency is
getting worse and high enough that the conversion exercise now seems futile.

Clearly I'll need to know/figure out what is causing this to try and
proceed.

Daniel Schütze

Migration of Data from 2.2.17 to 3.0.2 (dbmail-util coredumping)

_______________________________________________
DBmail mailing list
DBmail <at> dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

innodb tweaks

Hi,

Has anybody done any performance and storage tests for innodb with regard to dbmail 3.0. Like using
compression and partitioning on the email data tables?

https://dev.mysql.com/doc/refman/5.5/en/innodb-compression.html
https://dev.mysql.com/doc/refman/5.5/en/partitioning.html

Also, any recommendations on setting the various innodb buffer sizes, that deviate from the standard
recommendations? Maybe someone can simply share their experiences with tweaking innodb on a dbmail install.

Regards,

Aleksander Kamenik

Housekeeping dbmail_headervalue

Hello,
am I wrong or there is no dbmail-util procedure to delete headervalues
no more connected to messages?

After deleting some users directly from the dbmail_database and running
the dbmail-util -ay housekeeping utility, I noticed the
dbmail_headervalue table size remains pretty the same.

If I run manually the query:

select count(*) from dbmail_headervalue where id not in ( select
headervalue_id from dbmail_header );

I discovered a large number of no more connected header values.

Almost the same if I check the headernames with the query:

select count(*) from dbmail_headername where id not in ( select
headername_id from dbmail_header );

Leandro

sort in roundcubemail broken again

hi

http://git.dbmail.eu/paul/dbmail/commit/?h=dbmail_3_0&id=9e2f272541621d898d9485bfbf43818d7dce708c

in 2da7411789e03a9b51f2e286ea1ea6cc4f3e4303 this seems to be broken again
as long i reset user-preferences and do not touch sort all is fine
but from the moment you are sorting for anything it gets broken

_______________________________________________
DBmail mailing list
DBmail <at> dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

Clearing mailbox

Hello,

I'm trying to clear the inbox for an user. To do it i execute:

#dbmail-export -u TheUserId -m INBOX -d -o /tmp/in.mbox
#dbmail-util -dpy

/tmp/in.mbox is created but the inbox is not cleared.

¿What is the correct way?

I'm using dbmail 2.2.11 with PostgreSQL

Thanks

--

-- 
Oswaldo