Hi Juan, > Just tested also 2.0.11, happens with this version also. > > Found the error, finally, is within the table quotas_tracking structure. > > The default structure for the field quotas_tracking.Counter (tested in > mysql) is decimal(10,4). > > Since the MessageCumulative size limit in the quota module is in bytes > this is easy to overflow, and the value stored in database ends being > 999999.9999, which is roughly almost 1 MB only > > The quota update tries to setup for example a 5 MB quota usage, but the > counter field get stalled at 1MB, that why it looked that the Counter > field reset. > > By resetting the database structure in the field quotas_tracking.Counter > to decimal(15,4) that gives a maximum of 99999999999.9999, or 93GB. > > And solved the problem
We are currently investigating and will have a patch available to try as soon as possible. Thank you for the detailed report. Robert _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
