Kolab 16: Problems after Update

[Bartosiak-Jentys, Chris]

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