You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a function that works fine manually, but in DjangoQ it returns ERROR reincarnated worker Process-1:534 after death over and over again without giving me any specifics of what the error was?
So my question is, in what case will DjangoQ just destory the worker and not specify what error caused it?
More context, I run Django-Q in an AWS EC2, and my only suspicion is that my EC2 runs out of memory or resources during this task, and DjangoQ has no chance to explain what the error was.
Can anyone confirm? is running out of memory a reason DjangoQ will just quit like above without showing any exceptions?
The text was updated successfully, but these errors were encountered:
Yes, this happens when the instance runs out of memory. It just shuts down the process without any explicit errors. Make sure you keep the functions efficient and below the MAX memory usage.
I have a function that works fine manually, but in DjangoQ it returns
ERROR reincarnated worker Process-1:534 after death
over and over again without giving me any specifics of what the error was?So my question is, in what case will DjangoQ just destory the worker and not specify what error caused it?
More context, I run Django-Q in an AWS EC2, and my only suspicion is that my EC2 runs out of memory or resources during this task, and DjangoQ has no chance to explain what the error was.
Can anyone confirm? is running out of memory a reason DjangoQ will just quit like above without showing any exceptions?
The text was updated successfully, but these errors were encountered: