Frappe:frappe-worker & workerbeat Constantly Restarting

ERPNext
1

Hi Guys,

Recently I noticed outgoing email has stopped again. I don’t think anything was modified within the system…all else is still working.

The issue we cannot send any Quotes, Sales Invoices etc. I think the Daily Digest was still working though that has now stopped working also.

I checked the Workers using command : sudo supervisorctl status
Output:

frappe:frappe-web RUNNING pid 15591, uptime 0:03:00
frappe:frappe-worker STARTING
frappe:frappe-workerbeat STARTING
redis-cache RUNNING pid 15593, uptime 0:03:00

frappe:frappe-web RUNNING pid 15591, uptime 0:03:08
frappe:frappe-worker RUNNING pid 16733, uptime 0:00:02
frappe:frappe-workerbeat RUNNING pid 16734, uptime 0:00:02
redis-cache RUNNING pid 15593, uptime 0:03:08

frappe:frappe-web RUNNING pid 15591, uptime 0:03:15
frappe:frappe-worker STARTING
frappe:frappe-workerbeat BACKOFF Exited too quickly (process log may have details)
redis-cache RUNNING pid 15593, uptime 0:03:15

frappe:frappe-web RUNNING pid 15591, uptime 0:03:21
frappe:frappe-worker STARTING
frappe:frappe-workerbeat STARTING
redis-cache RUNNING pid 15593, uptime 0:03:21

So it seems as though the Worker & WorkerBeat are constantly Restarting. Where would one begin to investigate this issue?

Appreciate your assistance guys!

Kind regards,

Mark | reCIPHER Group

2

Seems worker exhausted,

sudo supervisorctl stop all
sudo supervisorctl reread
sudo supervisorctl start all
3

Thanks for the reply mate. I tried the commands however still have the same results…in fact now it appears the two worker processes are FATAL:

frappe:frappe-web RUNNING pid 13680, uptime 0:01:17
frappe:frappe-worker FATAL Exited too quickly (process log may have details)
frappe:frappe-workerbeat FATAL Exited too quickly (process log may have details)
redis-cache RUNNING pid 13690, uptime 0:01:17

Any ideas how I can review the process logs for more info?

Could it possibly be a conflict?