It looks like the "celery worker" process is maxing out both CPUs on our MHN server. I haven't the first clue as to why and would appreciate assistance in figuring it out. I'd like to stay in the good graces of my virtualization team.Gracias!
--
You received this message because you are subscribed to the Google Groups "Modern Honey Network" group.
To unsubscribe from this group and stop receiving emails from it, send an email to modern-honey-net...@googlegroups.com.
To post to this group, send email to modern-hon...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/modern-honey-network/fd997f0c-3edd-4065-996d-bfd4d15985aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command
www-data 20 0 348M 249M 3148 R 99.7 6.3 942h /opt/mhn/env/bin/python /opt/mhn/env/bin/celery worker -A mhn.tasks --loglevel=INFO
The celery worker does 2 things1. Handles password resets2. Downloads signature files from emerging threats and stores them in MHNs DBIf you don't care about these you can disable it by callingsudo supervisorctl stop mhn-celery-worker
On Tuesday, February 16, 2016, Nicholas Tripp <nichola...@duke.edu> wrote:It looks like the "celery worker" process is maxing out both CPUs on our MHN server. I haven't the first clue as to why and would appreciate assistance in figuring it out. I'd like to stay in the good graces of my virtualization team.Gracias!
--