I have a series of Mautic builds self-hosted in side-by-side subdirectories. All working versions were either version 1.3 or 1.4. I decided to make my next build 2.0.1 which required a bit of server gymnastics including updating to php 5.6 from 5.5. Of course all my existing cron jobs stopped working because the path to php changed slightly plus the new 2.0.1 build has new cron job syntax entirely. My problem is that, after php (path) update to 5.6, I have Mautic 1.3 and 1.4 cron jobs working properly again (so I know the paths are correct) but I can’t get the new 2.0.1 cron jobs to work.
These cron jobs work properly for 1.4
/opt/php56/bin/php /home/server/public_html/marketing/account_name/app/console mautic:leadlists:update --env=prod
/opt/php56/bin/php /home/server/public_html/marketing/account_name/app/console mautic:campaigns:update --env=prod
/opt/php56/bin/php /home/server/public_html/marketing/account_name/app/console mautic:campaigns:trigger --env=prod
/opt/php56/bin/php /home/server/public_html/marketing/account_name/app/console mautic:email:process --env=prod
These DO NOT work properly for 2.0.1
/opt/php56/bin/php /home/server/public_html/marketing/account_name2/app/console mautic:segments:update
/opt/php56/bin/php /home/server/public_html/marketing/account_name2/app/console mautic:campaigns:rebuild
/opt/php56/bin/php /home/server/public_html/marketing/account_name2/app/console mautic:campaigns:trigger
/opt/php56/bin/php /home/server/public_html/marketing/account_name2/app/console mautic:emails:send
/opt/php56/bin/php /home/server/public_html/marketing/account_name2/app/console mautic:social:monitoring
I’m pulling my hair out! What am I doing wrong?!?
I have a series of Mautic builds self-hosted in side-by-side subdirectories. All working versions were either version 1.3 or 1.4. I decided to make my next build 2.0.1 which required a bit of server gymnastics including updating to php 5.6 from 5.5. Of course all my existing cron jobs stopped working because the path to php changed slightly plus the new 2.0.1 build has new cron job syntax entirely. My problem is that, after php (path) update to 5.6, I have Mautic 1.3 and 1.4 cron jobs working properly again (so I know the paths are correct) but I can’t get the new 2.0.1 cron jobs to work.
These cron jobs work properly for 1.4
/opt/php56/bin/php /home/server/public_html/marketing/account_name/app/console mautic:leadlists:update --env=prod
/opt/php56/bin/php /home/server/public_html/marketing/account_name/app/console mautic:campaigns:update --env=prod
/opt/php56/bin/php /home/server/public_html/marketing/account_name/app/console mautic:campaigns:trigger --env=prod
/opt/php56/bin/php /home/server/public_html/marketing/account_name/app/console mautic:email:process --env=prod
These DO NOT work properly for 2.0.1
/opt/php56/bin/php /home/server/public_html/marketing/account_name2/app/console mautic:segments:update
/opt/php56/bin/php /home/server/public_html/marketing/account_name2/app/console mautic:campaigns:rebuild
/opt/php56/bin/php /home/server/public_html/marketing/account_name2/app/console mautic:campaigns:trigger
/opt/php56/bin/php /home/server/public_html/marketing/account_name2/app/console mautic:emails:send
/opt/php56/bin/php /home/server/public_html/marketing/account_name2/app/console mautic:social:monitoring
I’m pulling my hair out! What am I doing wrong?!?
I’m getting these errors. Anybody have a solution?
Could not open input file: /home/server/public_html/marketing/account_name2/app/console mautic:segments:update
Could not open input file: /home/server/public_html/marketing/account_name2/app/console mautic:campaigns:rebuild
Could not open input file: /home/server/public_html/marketing/account_name2/app/console mautic:campaigns:trigger
Could not open input file: /home/server/public_html/marketing/account_name2/app/console mautic:emails:send