How do i set the cleanup to stop running

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • murugappan
    Active Community Member
    • Aug 2017
    • 540

    #1

    How do i set the cleanup to stop running

    Currently we are using Version 7.4. We know it is very old and we working on a migration options to the latest. I the mean time we have a problem. The CRM system seems to timeout very often, very slow and sometimes is unable to allocate PHP Memory chunks. We have conducted an analysis on the performance and identified corrective and fine tuning steps. One of the contributed we found appears to be the cleanup job. I have set the scheduled "clean up" to June and December. I also want to selective skip cleanup of certain parts. What is the setting to skip/stop. Currently the setting in config is:

    'cleanupJobPeriod' => '1 month',
    'cleanupActionHistoryPeriod' => '15 days',
    'cleanupDeletedRecordsPeriod' => '1 day',
    'cleanupAuthTokenPeriod' => '1 month',
    'noteDeleteThresholdPeriod' => '1 month',
    'noteEditThresholdPeriod' => '7 days',

    ​​nth',


  • yuri
    EspoCRM product developer
    • Mar 2014
    • 9884

    #2
    Hi,

    There are no more parameters other than ones that are listed in the docs: https://docs.espocrm.com/administrat...rams/#clean-up

    If I remember correctly, the cleanup performance was improved in v8.0 or later.


    Comment


    • murugappan
      murugappan commented
      Editing a comment
      Thank you for the response. Unfortunately we are still in version 7.4. What value can i put to prevent the cleanup? We normally do not delete records in Entities, especially emails due to audit requirements.
  • yuri
    EspoCRM product developer
    • Mar 2014
    • 9884

    #3
    There was a performance problem (fixed in v9.0) with jobs cleanup.

    There's no parameter to disable jobs cleanup. The only option is to inactivate the Cleanup scheduled job completely (set the status field to Inactive).

    I see that cleanup memory usage problem was fixed in v7.3, hence I'm not sure what exactly causes your problem. PHP not being able to allocate memory looks like the same problem that was fixed in v7.3.

    Comment


    • murugappan
      murugappan commented
      Editing a comment
      yuri, thank you for the update. We located the performance issue. It was caused by "stream" setting in the Email entity. This caused the processing backlogs in the DB as the volume of emails are high. Thank you for the help.
  • murugappan
    Active Community Member
    • Aug 2017
    • 540

    #4
    yuri I have another error in the log which occurs frequently on a daily basis, Need your help on this message:

    [2026-06-23 22:41:24] ERROR: (403) GET /emascrm/; line: 86, file: /home/crmemast/public_html/emascrm/application/Espo/EntryPoints/Attachment.php [] []
    Last edited by murugappan; Today, 01:22 AM.

    Comment

    • yuri
      EspoCRM product developer
      • Mar 2014
      • 9884

      #5
      This error is originated from code base of v7.2, not v7.4. Maybe you don't have all files from the v7.4 for some reason. You can replace files manually, from the package. Just replace (by overriding) the 'application' and 'vendor' folders.

      This error occurred when some user tried to access an attachment they don't have access to. It could be that the user had a link to the attachment but didn't have access to it in the CRM. In v7.4 this error would have been logged with more details. In more recent versions, it would have been logged as a NOTICE I believe.

      Comment

      Working...