thammaneni opened a new issue #9317: Celery worker is failing during schedule execution. URL: https://github.com/apache/incubator-superset/issues/9317 A clear and concise description of what the bug is. I have scheduled around 20 emails. using redis as celery broker url and backend result storage. i am getting error in logs saying **logfile:** requests.exceptions.ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) [2020-03-17 08:01:13,569: ERROR/MainProcess] Process 'ForkPoolWorker-7069' pid:7551 exited with 'signal 9 (SIGKILL)' [2020-03-17 08:05:01,442: ERROR/MainProcess] Process 'ForkPoolWorker-7072' pid:7566 exited with 'signal 9 (SIGKILL)' [2020-03-17 08:05:01,453: ERROR/MainProcess] Task handler raised error: WorkerLostError('Worker exited prematurely: signal 9 (SIGKILL).') Traceback (most recent call last): File "/usr/local/python3.7/lib/python3.7/site-packages/billiard/pool.py", line 1223, in mark_as_worker_lost human_status(exitcode)), billiard.exceptions.WorkerLostError: Worker exited prematurely: signal 9 (SIGKILL). [2020-03-17 08:05:01,774: ERROR/MainProcess] Process 'ForkPoolWorker-7067' pid:7540 exited with 'signal 9 (SIGKILL)' [2020-03-17 08:05:01,785: ERROR/MainProcess] Task handler raised error: WorkerLostError('Worker exited prematurely: signal 9 (SIGKILL).') Traceback (most recent call last): File "/usr/local/python3.7/lib/python3.7/site-packages/billiard/pool.py", line 1223, in mark_as_worker_lost human_status(exitcode)), billiard.exceptions.WorkerLostError: Worker exited prematurely: signal 9 (SIGKILL). [2020-03-17 08:05:02,507: ERROR/MainProcess] Process 'ForkPoolWorker-4165' pid:4478 exited with 'signal 9 (SIGKILL)' [2020-03-17 08:05:02,561: ERROR/MainProcess] Task handler raised error: WorkerLostError('Worker exited prematurely: signal 9 (SIGKILL).') Traceback (most recent call last): File "/usr/local/python3.7/lib/python3.7/site-packages/billiard/pool.py", line 1223, in mark_as_worker_lost human_status(exitcode)), billiard.exceptions.WorkerLostError: Worker exited prematurely: signal 9 (SIGKILL). [2020-03-17 08:05:03,164: ERROR/MainProcess] Process 'ForkPoolWorker-7071' pid:7561 exited with 'signal 9 (SIGKILL)' [2020-03-17 08:05:03,875: ERROR/MainProcess] Process 'ForkPoolWorker-7074' pid:7570 exited with 'signal 9 (SIGKILL)' ### Expected results what you expected to happen. ### Actual results what actually happens. #### Screenshots  If applicable, add screenshots to help explain your problem. #### How to reproduce the bug 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error ### Environment (please complete the following information): superset version: superset version 0.33.10402 python version: python --version Flask 1.0.2 Python 3.7.3 (default, Sep 24 2019, 07:16:25) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)] - node.js version: `node -v` - npm version: `npm -v` ### Checklist Make sure these boxes are checked before submitting your issue - thank you! - [ ] I have checked the superset logs for python stacktraces and included it here as text if there are any. - [ ] I have reproduced the issue with at least the latest released version of superset. - [ ] I have checked the issue tracker for the same issue and I haven't found one similar. ### Additional context Add any other context about the problem here.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
