Venv python bin path is not right in crontab when launched with mod_wgsi

[pbordron]

Describe the bug

When launched with mod_wsgi, the crontab is populated as follow (you need to access the website once to populate the crontab - lazy loading from apache):

$ sudo crontab -l -u dgenies

0 1 * * * /usr/bin/python3 /usr/local/venv/dgenies/lib/python3.6/site-packages/dgenies/bin/clean_jobs.py > /home/dgenies/clean.log 2>&1 # dgenies
* * * * * /usr/lib/python3.6/site-packages/dgenies/bin/start_local_scheduler.sh /usr/local/venv/dgenies/lib/python3.6/site-packages/dgenies /usr/local/venv/dgenies/bin/python3 /home/dgenies/.local_scheduler_pid /home/dgenies/logs/local_scheduler.log > /dev/null 2>&1 & # dgenies

This problem doesn't exists when running dgenies with flask:

# We clear the crontab
sudo -u dgenies /usr/local/venv/dgenies/bin/dgenies clear -c

# We run dgenies with flask
sudo -u dgenies /usr/local/venv/dgenies/bin/dgenies run -m webserver --no-browser -o 0.0.0.0

It will produce following crontab:

$ sudo crontab -l -u dgenies

0 1 * * * /usr/local/venv/dgenies/bin/python3 /usr/local/venv/dgenies/lib/python3.6/site-packages/dgenies/bin/clean_jobs.py > /home/dgenies/clean.log 2>&1 # dgenies
* * * * * /usr/local/venv/dgenies/lib/python3.6/site-packages/dgenies/bin/start_local_scheduler.sh /usr/local/venv/dgenies/lib/python3.6/site-packages/dgenies /usr/local/venv/dgenies/bin/python3 /home/dgenies/.local_scheduler_pid /home/dgenies/logs/local_scheduler.log > /dev/null 2>&1 & # dgenies

Computer (please complete the following information):

• OS: CentOS 7 + epel repository
• packages:
  • httpd
  • python3-mod_wsgi
  • dgenies in a venv /usr/local/venv/dgenies