version 2.8 problem

[Richard Thomas]

troxlinux <xserverlinux <at> gmail.com> writes:

> 
> Hi list , recently updated version of amavisd to 2.8, change the
> structure of the database but not working
> 
> Mar 22 14:45:13 mail dovecot: IMAP(raburto <at> prisma.com.ni): Connection
> closed bytes=421/3600
> Mar 22 14:45:14 mail amavis[16050]: (16050-02) (!)WARN
> save_info_final: sql exec: err=1054, S1000, DBD::mysql::st execute
> failed: Unknown column 'rseqnum' in 'field list' at (eval 103) line
> 172.
> Mar 22 14:45:14 mail amavis[16050]: (16050-02) sql_storage: retrying
> on final, 3 attempts remain
> Mar 22 14:45:15 mail amavis[16050]: (16050-02) (!)WARN
> save_info_final: sql exec: err=1054, S1000, DBD::mysql::st execute
> failed: Unknown column 'rseqnum' in 'field list' at (eval 103) line
> 172.
> Mar 22 14:45:15 mail amavis[16050]: (16050-02) sql_storage: retrying
> on final, 2 attempts remain
> Mar 22 14:45:16 mail amavis[16050]: (16050-02) (!)WARN
> save_info_final: sql exec: err=1054, S1000, DBD::mysql::st execute
> failed: Unknown column 'rseqnum' in 'field list' at (eval 103) line
> 172.
> Mar 22 14:45:16 mail amavis[16050]: (16050-02) sql_storage: retrying
> on final, 1 attempts remain
> Mar 22 14:45:17 mail amavis[16050]: (16050-02) (!)WARN
> save_info_final: sql exec: err=1054, S1000, DBD::mysql::st execute
> failed: Unknown column 'rseqnum' in 'field list' at (eval 103) line
> 172.
> Mar 22 14:45:17 mail amavis[16050]: (16050-02) (!!)ERROR sql_storage:
> too many retries on storing final, info not saved
> 
> any idea?
> 
> sldss
> 

Hi,

I've just hit the same problem upgrading to amavisd-new 2.8.0 on 
CentOS 5.9 (== RedHat Enterprise Linux 5.9). There is a database
update required for the upgrade to 2.7.0 (which I guess was missed 
by RedHat/CentOS), full details are in the README file for mysql 
under /usr/share/doc/amavisd-new-2.8.0. You need to add the following
4 columns:

  ALTER TABLE msgrcpt ADD rseqnum     integer  DEFAULT 0   NOT NULL;
  ALTER TABLE msgrcpt ADD content     char(1)  DEFAULT ' ' NOT NULL;
  ALTER TABLE msgrcpt ADD is_local    char(1)  DEFAULT ' ' NOT NULL;
  ALTER TABLE msgs    ADD originating char(1)  DEFAULT ' ' NOT NULL;

If you don't periodically clean out those tables the update will take 
ages, further down in the same README file you will find suggestions
for DELETE scripts that will remove old messages from the database.

I'm still in the process of purging old messages before I run the above 
ALTER TABLE statements, so I'll report back when it's done to confirm.

HTH,

Richard