Kolab 16: Problems after Update

[Bartosiak-Jentys, Chris]

Ah yes, cant believe I missed that! Thanks for the explanation Winfried.

On 2016-07-07 16:10, Winfried Ritsch wrote:
> Thanks,
> 
> Also fixed my Kolab16, CentOS7
> 
> the new table differs in data column:
> 
> | data          | blob        | YES  |     | NULL    |                |
> 
> see below.
> 
> mfg
>  winfried
> 
> Before:  MariaDB [kolab]> drop table policy_result;
> 
> +---------------+-------------+------+-----+---------+----------------+
> | Field         | Type        | Null | Key | Default | Extra          |
> +---------------+-------------+------+-----+---------+----------------+
> | id            | int(11)     | NO   | PRI | NULL    | auto_increment |
> | key           | varchar(16) | NO   | MUL | NULL    |                |
> | value         | tinyint(1)  | NO   |     | NULL    |                |
> | sender        | varchar(64) | NO   |     | NULL    |                |
> | recipient     | varchar(64) | NO   |     | NULL    |                |
> | sasl_username | varchar(64) | YES  |     | NULL    |                |
> | sasl_sender   | varchar(64) | YES  |     | NULL    |                |
> | created       | int(11)     | NO   |     | NULL    |                |
> +---------------+-------------+------+-----+---------+----------------+
> 
> After: sending an email via submission
> 
> +---------------+-------------+------+-----+---------+----------------+
> | Field         | Type        | Null | Key | Default | Extra          |
> +---------------+-------------+------+-----+---------+----------------+
> | id            | int(11)     | NO   | PRI | NULL    | auto_increment |
> | key           | varchar(16) | NO   | MUL | NULL    |                |
> | value         | tinyint(1)  | NO   |     | NULL    |                |
> | sender        | varchar(64) | YES  |     | NULL    |                |
> | recipient     | varchar(64) | NO   |     | NULL    |                |
> | sasl_username | varchar(64) | YES  |     | NULL    |                |
> | sasl_sender   | varchar(64) | YES  |     | NULL    |                |
> | created       | int(11)     | NO   |     | NULL    |                |
> | data          | blob        | YES  |     | NULL    |                |
> +---------------+-------------+------+-----+---------+----------------+
> 
> 
> On Thursday 07 July 2016 14:56:08 Bartosiak-Jentys, Chris wrote:
>> Thanks Jeroen,
>> 
>> Dropping the policy_results table seems to have fixed the problem on
>> both servers, thank you!
>> Seems its automatically regenerated on the next email I send.
>> 
>> Any idea what could have caused this issue? I did dump the kolab
>> database before dropping the table as a precaution but the dump just
>> contains the table schema, no data was in policy_result.
>> 
>> Thanks,
>> 
>> Chris Bartosiak-Jentys
>> 
>> On 2016-07-07 13:52, Jeroen van Meeuwen (Kolab Systems) wrote:
>> > On 2016-07-07 13:11, Bartosiak-Jentys, Chris wrote:
>> >> Hello everyone, I am also seeing this issue on 2 CentOS 7 Kolab16
>> >> servers since updating. Bellow is the output from my logs with
>> >> Jeroen's suggested debug logging turned on:
>> >>
>> >>
>> >> Jul  7 12:00:41 srv01 postfix/submission/smtpd[24317]: input attribute
>> >> name: 2016-07-07 12:00:41,674 pykolab.smtp_access_policy ERROR
>> >> Unhandled exception caught: OperationalError('(OperationalError)
>> >> (1054, "Unknown column \'policy_result.data\' in \'field list\'")',)
>> >
>> > There's the problem.
>> >
>> > Can you remove/drop the policy_result table from the kolab database?
>> >
>> > Kind regards,
>> >
>> > Jeroen van Meeuwen
>> 
>> _______________________________________________
>> users mailing list
>> users at lists.kolab.org
>> https://lists.kolab.org/mailman/listinfo/users