When running cron jobs, env vars are not available to cron job script. This is caused by the fact, that /tmp/cron.env does not include ENV vars available to mautic_web or mautic_worker.
Because of that mautic_worker has no access to e.g. DB username or DB password, if they are set via ENV vars - therefore cron commands fail.
The solution to that is adding those vars to tmp/cron.env inside entrypoint_mautic_cron.sh.
"Quick fix" for me is custom dockerfile with additional step:
RUN sed -i '/declare -p | grep '\''PHP_INI_VALUE_'\'' > \/tmp\/cron.env/a env | grep MAUTIC | awk '\''{print "declare -x " $0}'\'' >> /tmp/cron.env' /entrypoint_mautic_cron.sh
O-Mutt
commented
2 months ago
Hi,
When running cron jobs, env vars are not available to cron job script. This is caused by the fact, that /tmp/cron.env does not include ENV vars available to mautic_web or mautic_worker.
Because of that mautic_worker has no access to e.g. DB username or DB password, if they are set via ENV vars - therefore cron commands fail.
The solution to that is adding those vars to tmp/cron.env inside entrypoint_mautic_cron.sh.
"Quick fix" for me is custom dockerfile with additional step:
RUN sed -i '/declare -p | grep '\''PHP_INI_VALUE_'\'' > \/tmp\/cron.env/a env | grep MAUTIC | awk '\''{print "declare -x " $0}'\'' >> /tmp/cron.env' /entrypoint_mautic_cron.sh