starred/healthchecks

Fork 0

mirror of https://github.com/healthchecks/healthchecks.git synced 2026-04-25 23:15:49 +03:00

[GH-ISSUE #441] ModuleNotFoundError: No module named 'cron_descriptor' #328

New issue

Closed

opened 2026-02-25 23:42:03 +03:00 by kerem · 12 comments

kerem commented

2026-02-25 23:42:03 +03:00

Owner

Originally created by @blade1989 on GitHub (Oct 20, 2020).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/441

I keep getting this error, but when I try to install it, I get Requirement already satisfied: message.

Originally created by @blade1989 on GitHub (Oct 20, 2020). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/441 I keep getting this error, but when I try to install it, I get `Requirement already satisfied:` message.

kerem closed this issue

2026-02-25 23:42:03 +03:00

kerem commented

2026-02-25 23:42:04 +03:00

Author

Owner

@cuu508 commented on GitHub (Oct 20, 2020):

I would first check if there's any issue with virtualenv. Perhaps the package is installed in a different virtualenv, or is installed globally, or something along these lines.

are you using virtualenv?
when you install cron-descriptor, do you do it from an activated virtualenv?
when/how do you get the error? while running manage.py runserver? Is it running inside an activated virtualenv?

@cuu508 commented on GitHub (Oct 20, 2020): I would first check if there's any issue with virtualenv. Perhaps the package is installed in a different virtualenv, or is installed globally, or something along these lines. * are you using virtualenv? * when you install cron-descriptor, do you do it from an activated virtualenv? * when/how do you get the error? while running `manage.py runserver`? Is it running inside an activated virtualenv?

kerem commented

2026-02-25 23:42:04 +03:00

Author

Owner

@blade1989 commented on GitHub (Oct 20, 2020):

I installed it in multiple ways, via virtualenv:

source hc-venv/bin/activate
pip install pretty-cron

Also via root terminal I executed pip install pretty-cron.

After the update, I executed pip install -r requirements.txt, But, no luck. the same error is present

I am using gunicorn with nginx to excecute the healthchecks

@blade1989 commented on GitHub (Oct 20, 2020): I installed it in multiple ways, via virtualenv: ``` source hc-venv/bin/activate pip install pretty-cron ``` Also via root terminal I executed `pip install pretty-cron`. After the update, I executed `pip install -r requirements.txt`, But, no luck. the same error is present I am using gunicorn with nginx to excecute the healthchecks

kerem commented

2026-02-25 23:42:04 +03:00

Author

Owner

@blade1989 commented on GitHub (Oct 20, 2020):

@cuu508 my apologize, wrong button

@blade1989 commented on GitHub (Oct 20, 2020): @cuu508 my apologize, wrong button

kerem commented

2026-02-25 23:42:04 +03:00

Author

Owner

@cuu508 commented on GitHub (Oct 20, 2020):

When/how do you get the error? while running manage.py runserver? Is it running inside an activated virtualenv?

Can you check if cron-descriptor shows up in the output of pip freeze when the virtualenv is active?

@cuu508 commented on GitHub (Oct 20, 2020): When/how do you get the error? while running manage.py runserver? Is it running inside an activated virtualenv? Can you check if `cron-descriptor` shows up in the output of `pip freeze` when the virtualenv is active?

kerem commented

2026-02-25 23:42:04 +03:00

Author

Owner

@blade1989 commented on GitHub (Oct 20, 2020):

Yes, I can clearly see cron-descriptor==1.2.24 in the output of pip freeze.

I just edited my previous comment, added: I am using gunicorn with nginx to excecute the healthchecks. In case you missed that

@blade1989 commented on GitHub (Oct 20, 2020): Yes, I can clearly see `cron-descriptor==1.2.24` in the output of `pip freeze`. I just edited my previous comment, added: `I am using gunicorn with nginx to excecute the healthchecks`. In case you missed that

kerem commented

2026-02-25 23:42:04 +03:00

Author

Owner

@cuu508 commented on GitHub (Oct 20, 2020):

How do you launch gunicorn? Is it installed in the virtualenv or globally?

@cuu508 commented on GitHub (Oct 20, 2020): How do you launch gunicorn? Is it installed in the virtualenv or globally?

kerem commented

2026-02-25 23:42:04 +03:00

Author

Owner

@blade1989 commented on GitHub (Oct 20, 2020):

When/how do you get the error?

While visiting healthchecks via browser

while running manage.py runserver? Is it running inside an activated virtualenv?

I excecute it via gunicorn hc.wsgi -w 4. I don't know if the virtualenv is being used. I think its globally? 🤔

@blade1989 commented on GitHub (Oct 20, 2020): > When/how do you get the error? While visiting healthchecks via browser > while running manage.py runserver? Is it running inside an activated virtualenv? I excecute it via `gunicorn hc.wsgi -w 4`. I don't know if the virtualenv is being used. I think its globally? :thinking:

kerem commented

2026-02-25 23:42:04 +03:00

Author

Owner

@cuu508 commented on GitHub (Oct 20, 2020):

My hunch would be that you have every dependency except cron-descriptor also installed globally, and gunicorn is not using the virtualenv.

@cuu508 commented on GitHub (Oct 20, 2020): My hunch would be that you have every dependency except cron-descriptor also installed globally, and gunicorn is not using the virtualenv.

kerem commented

2026-02-25 23:42:04 +03:00

Author

Owner

@blade1989 commented on GitHub (Oct 20, 2020):

I also get the error from executing ./manage.py migrate

@blade1989 commented on GitHub (Oct 20, 2020): I also get the error from executing `./manage.py migrate`

kerem commented

2026-02-25 23:42:04 +03:00

Author

Owner

@blade1989 commented on GitHub (Oct 20, 2020):

How do I make gunicorn use the virtualenv?

@blade1989 commented on GitHub (Oct 20, 2020): How do I make gunicorn use the virtualenv?

kerem commented

2026-02-25 23:42:04 +03:00

Author

Owner

@cuu508 commented on GitHub (Oct 20, 2020):

One way to do that is to install gunicorn inside the virtualenv. And then run hc-venv/bin/gunicorn instead of /usr/local/bin/gunicron (or wherever it gets installed globally)

@cuu508 commented on GitHub (Oct 20, 2020): One way to do that is to install gunicorn inside the virtualenv. And then run hc-venv/bin/gunicorn instead of /usr/local/bin/gunicron (or wherever it gets installed globally)

kerem commented

2026-02-25 23:42:04 +03:00

Author

Owner

@cuu508 commented on GitHub (Oct 21, 2020):

Hey @blade1989, did you find out what the issue was?

@cuu508 commented on GitHub (Oct 21, 2020): Hey @blade1989, did you find out what the issue was?

kerem referenced this issue

2026-02-25 23:44:11 +03:00

[PR #328] [MERGED] Bump django from 3.0.1 to 3.0.3 #930