Crop cycle timing out


We created a crop in Agriculture with 820 tasks. While creating a new crop cycle, the system used to time out. After searching in the forum for possible problems, we accordingly increased the http_timeout to 6000. After making his change the change and restarting, we did not see any timeout on the screen, but the project is not being created either. The mysql timeouts (connect_timeout and wait_timeout) in the my.cnf file are 600 each.

We are running this on a self-hosted platform on AWS. We started with a very underpowered instance. We have since increased the size of the instances to t3.large (2vcpu, 8gb RAM and 1gb swap space). We are watching the CPU and memory usage and both seem within range.

The worker error log does not show any major issues, and we believe that the project table is being updated. However, we have no way of knowing if the job is being executed well and if we will get the result back.

06:46:30 short: frappe.utils.background_jobs.execute_job(event=u’all’, is_async=True, job_name=u’erpnext.projects.doctype.project.project.project_status_update_reminder’, kwargs={}, method=u’erpnext.projects.doctype.project.project.project_status_update_reminder’, site=u’site1.local’, user=u’Administrator’) (69a34ec8-fbc5-45b6-88fe-989f71762b5a)
06:46:31 short: Job OK (69a34ec8-fbc5-45b6-88fe-989f71762b5a)
06:46:31 Result is kept for 500 seconds

Could you please suggest if we are loading the system arbitrarily? Are there any other ways to debug the issue at hand?

Thanks in advance. We would appreciate any help in this matter.

warm regards,

Did you try to restart everything?