Mailing List Archive: DBMail: users

Forced upgrade from 2.0 to 2.2

Index | Next | Previous | View Threaded

greminn at gmail

Mar 10, 2009, 4:44 PM

Post #1 of 12 (890 views)
Permalink

Forced upgrade from 2.0 to 2.2

Hi There,

Our dbmail 2.0 running on debian sarge was damaged last night.

We are currently building a new VM with debian etch and dbmail 2.2.
The innodb mysql database from the old server is just being recovered
onto the new server... once completed, is this just simply a matter of
running the migrate_from_2.0_to_2.2.mysql file, configuring dbmail for
our environment and starting it?

Thanks

Simon
_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

greminn at gmail

Mar 10, 2009, 4:46 PM

Post #2 of 12 (845 views)
Permalink

Re: Forced upgrade from 2.0 to 2.2 [In reply to]

On Wed, Mar 11, 2009 at 12:44 PM, Simon <greminn[at]gmail.com> wrote:
> Hi There,
>
> Our dbmail 2.0 running on debian sarge was damaged last night.
>
> We are currently building a new VM with debian etch and dbmail 2.2.
> The innodb mysql database from the old server is just being recovered
> onto the new server... once completed, is this just simply a matter of
> running the migrate_from_2.0_to_2.2.mysql file, configuring dbmail for
> our environment and starting it?

Oh.. i have read:

http://www.dbmail.org/dokuwiki/doku.php?id=upgrading_to_2.1

So i would need to perform a "dbmail-util -by" as well correct?

Thanks Again,

Simon
_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

aaron at serendipity

Mar 10, 2009, 5:07 PM

Post #3 of 12 (845 views)
Permalink

Re: Forced upgrade from 2.0 to 2.2 [In reply to]

On Wed, 11 Mar 2009 12:46:07 +1300, Simon <greminn[at]gmail.com> wrote:
> On Wed, Mar 11, 2009 at 12:44 PM, Simon <greminn[at]gmail.com> wrote:
>> Hi There,
>>
>> Our dbmail 2.0 running on debian sarge was damaged last night.
>>
>> We are currently building a new VM with debian etch and dbmail 2.2.
>> The innodb mysql database from the old server is just being recovered
>> onto the new server... once completed, is this just simply a matter of
>> running the migrate_from_2.0_to_2.2.mysql file, configuring dbmail for
>> our environment and starting it?

Yep.

> Oh.. i have read:
>
> http://www.dbmail.org/dokuwiki/doku.php?id=upgrading_to_2.1
>
> So i would need to perform a "dbmail-util -by" as well correct?

Correct.

Aaron
_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

greminn at gmail

Mar 10, 2009, 5:14 PM

Post #4 of 12 (845 views)
Permalink

Re: Forced upgrade from 2.0 to 2.2 [In reply to]

On Wed, Mar 11, 2009 at 1:07 PM, Aaron Stone <aaron[at]serendipity.cx> wrote:

>>> Our dbmail 2.0 running on debian sarge was damaged last night.
>>>
>>> We are currently building a new VM with debian etch and dbmail 2.2.
>>> The innodb mysql database from the old server is just being recovered
>>> onto the new server... once completed, is this just simply a matter of
>>> running the migrate_from_2.0_to_2.2.mysql file, configuring dbmail for
>>> our environment and starting it?
>
> Yep.
>
>> Oh.. i have read:
>>
>> http://www.dbmail.org/dokuwiki/doku.php?id=upgrading_to_2.1
>>
>> So i would need to perform a "dbmail-util -by" as well correct?
>
> Correct.

Thanks Aaron, The VM has 2 x E5310 Xeon Cores @ 1.6GHz... and the
ibdata1 file is approx 40GB.. so that upgrade script might take a
while huh?

Simon
_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

greminn at gmail

Mar 10, 2009, 5:23 PM

Post #5 of 12 (846 views)
Permalink

Re: Forced upgrade from 2.0 to 2.2 [In reply to]

On Wed, Mar 11, 2009 at 1:26 PM, Aaron Stone <aaron[at]serendipity.cx> wrote:

> I'm sure it will! Be sure to keep a backup of the restored database in
> pre-2.2 script state, just in case, of course. If you could report back to
> the list how long the two steps take (sql migration and dbmail-util) that
> would be great to know.

Any ideas rough approx time? 30mins, 30hours, 30 days?

THanks

Simon

PS: WIll do on the reports.
_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

aaron at serendipity

Mar 10, 2009, 5:26 PM

Post #6 of 12 (845 views)
Permalink

Re: Forced upgrade from 2.0 to 2.2 [In reply to]

On Wed, 11 Mar 2009 13:14:58 +1300, Simon <greminn[at]gmail.com> wrote:
> On Wed, Mar 11, 2009 at 1:07 PM, Aaron Stone <aaron[at]serendipity.cx>
wrote:
>
>>>> Our dbmail 2.0 running on debian sarge was damaged last night.
>>>>
>>>> We are currently building a new VM with debian etch and dbmail 2.2.
>>>> The innodb mysql database from the old server is just being recovered
>>>> onto the new server... once completed, is this just simply a matter of
>>>> running the migrate_from_2.0_to_2.2.mysql file, configuring dbmail for
>>>> our environment and starting it?
>>
>> Yep.
>>
>>> Oh.. i have read:
>>>
>>> http://www.dbmail.org/dokuwiki/doku.php?id=upgrading_to_2.1
>>>
>>> So i would need to perform a "dbmail-util -by" as well correct?
>>
>> Correct.
>
> Thanks Aaron, The VM has 2 x E5310 Xeon Cores @ 1.6GHz... and the
> ibdata1 file is approx 40GB.. so that upgrade script might take a
> while huh?

I'm sure it will! Be sure to keep a backup of the restored database in
pre-2.2 script state, just in case, of course. If you could report back to
the list how long the two steps take (sql migration and dbmail-util) that
would be great to know.

Aaron
_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

greminn at gmail

Mar 10, 2009, 6:33 PM

Post #7 of 12 (845 views)
Permalink

Re: Forced upgrade from 2.0 to 2.2 [In reply to]

On Wed, Mar 11, 2009 at 1:26 PM, Aaron Stone <aaron[at]serendipity.cx> wrote:

>> Thanks Aaron, The VM has 2 x E5310 Xeon Cores @ 1.6GHz... and the
>> ibdata1 file is approx 40GB.. so that upgrade script might take a
>> while huh?
>
> I'm sure it will! Be sure to keep a backup of the restored database in
> pre-2.2 script state, just in case, of course. If you could report back to
> the list how long the two steps take (sql migration and dbmail-util) that
> would be great to know.

Hi Aaron (or others). The mysql script has completed (im guessing it
took approx on the 40GB innodb file). I went to run the dbmail-util
-by command and got this:

# dbmail-util -by
Mar 11 14:06:48 mail-store1 dbmail-util[10266]: Error:[sql]
dbmysql.c,db_mysql_check_collations(+138): collation mismatch, your
MySQL configuration specifies a different charset than the data
currently in your DBMail database.
Failed. An error occured. Please check log.

I have read various things, but it would be good to get the correct
thing todo here please?

Thanks

Simon
_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

aleksander at krediidiinfo

Mar 11, 2009, 2:37 AM

Post #8 of 12 (835 views)
Permalink

Re: Forced upgrade from 2.0 to 2.2 [In reply to]

Simon wrote:

> I have read various things, but it would be good to get the correct
> thing todo here please?

First check your database settings. Default collation was latin/swedish
for mysql I think. Compare your old and new my.cnf files. Check the
client as well as the mysql subsections. Has anything changed? Obviously
they have to match.

IIRC you can use show create table_name to see the encoding/collation.

Also, you're not using mysql 5.1 by any chance. It's not recommended
yet. Stick to 5.0.

HTH,

--

Aleksander Kamenik
System Administrator
Krediidiinfo AS
an Experian Company
Phone: +372 665 9649
Email: aleksander[at]krediidiinfo.ee

http://www.krediidiinfo.ee/
http://www.experiangroup.com/
_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

paul at nfg

Mar 11, 2009, 11:27 AM

Post #9 of 12 (819 views)
Permalink

Re: Forced upgrade from 2.0 to 2.2 [In reply to]

Aleksander Kamenik wrote:
> Simon wrote:
>
>> I have read various things, but it would be good to get the correct
>> thing todo here please?
>
> First check your database settings. Default collation was latin/swedish
> for mysql I think. Compare your old and new my.cnf files. Check the
> client as well as the mysql subsections. Has anything changed? Obviously
> they have to match.

If you can run both mysql and dbmail with utf8 encoding.

>
> IIRC you can use show create table_name to see the encoding/collation.

Correct.

> Also, you're not using mysql 5.1 by any chance. It's not recommended
> yet. Stick to 5.0.

Actually, 5.1.32 was released last week which was pitched as production
quality. Personally, I'll stick with Monty's advice: avoid 5.1:

http://monty-says.blogspot.com/2008/11/oops-we-did-it-again-mysql-51-released.html

--
________________________________________________________________
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.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

greminn at gmail

Mar 11, 2009, 12:22 PM

Post #10 of 12 (820 views)
Permalink

Re: Forced upgrade from 2.0 to 2.2 [In reply to]

On Thu, Mar 12, 2009 at 7:27 AM, Paul J Stevens <paul[at]nfg.nl> wrote:
> Aleksander Kamenik wrote:
>> Simon wrote:
>>
>>> I have read various things, but it would be good to get the correct
>>> thing todo here please?
>>
>> First check your database settings. Default collation was latin/swedish
>> for mysql I think. Compare your old and new my.cnf files. Check the
>> client as well as the mysql subsections. Has anything changed? Obviously
>> they have to match.
>
> If you can run both mysql and dbmail with utf8 encoding.
>
>>
>> IIRC you can use show create table_name to see the encoding/collation.
>
> Correct.
>
>> Also, you're not using mysql 5.1 by any chance. It's not recommended
>> yet. Stick to 5.0.
>
> Actually, 5.1.32 was released last week which was pitched as production
> quality. Personally, I'll stick with Monty's advice: avoid 5.1:
>
>
> http://monty-says.blogspot.com/2008/11/oops-we-did-it-again-mysql-51-released.html\

I think i need to change the encoding/collation:

show create table dbmail_messageblks;
+--------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Table | Create Table

|
+--------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| dbmail_messageblks | CREATE TABLE `dbmail_messageblks` (
`messageblk_idnr` bigint(21) NOT NULL auto_increment,
`physmessage_id` bigint(21) NOT NULL default '0',
`messageblk` longblob NOT NULL,
`blocksize` bigint(21) NOT NULL default '0',
`is_header` tinyint(1) NOT NULL default '0',
PRIMARY KEY (`messageblk_idnr`),
KEY `physmessage_id_index` (`physmessage_id`),
KEY `physmessage_id_is_header_index` (`physmessage_id`,`is_header`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 |
+--------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

If this is so... can someone post the steps here please?
_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

jake at vapourforge

Mar 11, 2009, 6:13 PM

Post #11 of 12 (822 views)
Permalink

Re: Forced upgrade from 2.0 to 2.2 [In reply to]

Paul J Stevens wrote:
>
> Actually, 5.1.32 was released last week which was pitched as production
> quality. Personally, I'll stick with Monty's advice: avoid 5.1:
>
>
> http://monty-says.blogspot.com/2008/11/oops-we-did-it-again-mysql-51-released.html
>
>

Has anybody compared the performance of dbmail when running on the 3
backends?

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

josh at worldhosting

Mar 11, 2009, 6:32 PM

Post #12 of 12 (816 views)
Permalink

Re: Performance Comparison WAS Forced upgrade from 2.0 to 2.2 [In reply to]

Hi,

> Has anybody compared the performance of dbmail when running on the 3
> backends?

A while back I compared performance of dbmail with MySQL 5.0 and
Postgres 8.1 (my installation was going to be too large for sqlite) and
the performance differences are minimal.

A lot of people get hung up on which database has a higher performance.
There are many more factors that should influence your decision on which
to choose, such as ease of recovery, high-availability and backup
solutions.

What I suggest is that you go for the RDBMS that you are more
comfortable with administering, as a 1 or 2 % performance gain is not
worth working on a database system you're less experienced with.
Somewhere down the line you will have to do some kind of recovery.

The MySQL vs Postgres debate is long from over and I'm just glad that
dbmail gives us the choice.

For those interested, I ended up going for MySQL 5.0 with two masters
(but only one being used at a time, using ucarp to arbitrate a virtual
IP address) and one slave I can start and stop to do backups on. The
reason I chose MySQL was that I am more confident with it when in a
pressured situation or when I'm half awake, working on it in the middle
of the night.

Regards,
Josh.

P.S. I'm not going to tell you which RDBMS was the faster of the two ;)

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

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com