Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0033293Openbravo ERPA. Platformpublic2016-06-16 16:412022-02-01 08:05
shuehner 
Triage Platform Base 
highminorhave not tried
acknowledgedopen 
5
 
 
Core
No
0033293: LogCleanup Utility background job inside pi not working correctly in at least one case
Has been observed in a customer installation having 15Q2.

The ad_pinstance + _para tables are not cleanup up by that process as they should be.

process monitor shows the process being executed but ends in status 'ERR' on every execution.

Log for those process execution always looks similar:
2016-06-08 19:00:00.049 - Starting log clean up process for Client:CLIENT_NAME - Organization:*+|
2016-06-08 19:00:00.118 - Cleaning up entity ADSessionUsageAudit +|
2016-06-08 19:00:01.546 - Deleted 0 rows +|
2016-06-08 19:00:01.546 - Entity ADSessionUsageAudit cleaned up in 1428ms +|
2016-06-08 19:00:01.551 - Cleaning up entity ADParameter +|
                                                                                No excpetion is logged in catalina.out or openbravo.log or process monitor output which makes it hard to debug.

Checking the configuration table for this process shows that all config entries are duplicated and one set of the entries is missing value for ad_column_id.

http://wiki.openbravo.com/wiki/Logs_Clean_Up [^]
That maybe related to the Red warning in this document but unclear.
Unknown but from observed apparently wrong behavior in customer instance.
Access can be requested via SHU
Check and improve error logging to make it possible to debug.
Review failure and avoid if possible.
If double config to be cleanup manually is cause of the problem check if it is not possible to make user more aware of the issue
No tags attached.
related to defect 0034667 closed alostale incorrect log in LogCleanUpProcess if vacuum fails 
Issue History
2016-06-16 16:41shuehnerNew Issue
2016-06-16 16:41shuehnerAssigned To => platform
2016-06-16 16:41shuehnerModules => Core
2016-06-16 16:41shuehnerTriggers an Emergency Pack => No
2016-12-01 12:43alostaleStatusnew => acknowledged
2016-12-01 14:03alostalePrioritynormal => high
2016-12-01 15:37alostaleRelationship addedrelated to 0034667
2022-02-01 08:05alostaleAssigned Toplatform => Triage Platform Base

There are no notes attached to this issue.