ip bd - week
0 0 * * 0 /usr/local/bin/php /home/your/public_html/marketing/app/console mautic:iplookup:download --env=prod >/home/your/public_html/marketing/loguiala/mauticiplookupdownload.log 2>&1
leadlist update
*/3 * * * * /usr/local/bin/php /home/your/public_html/marketing/app/console mautic:leadlists:update --env=prod >/home/your/public_html/marketing/loguiala/leadlistsupdate.log 2>&1
campains update
*/3 * * * * /usr/local/bin/php /home/your/public_html/marketing/app/console mautic:campaigns:update --env=prod >/home/your/public_html/marketing/loguiala/campaignsupdate.log 2>&1
campains trigger
*/3 * * * * /usr/local/bin/php /home/your/public_html/marketing/app/console mautic:campaigns:trigger --env=prod >/home/your/public_html/marketing/loguiala/campaignstrigger.log 2>&1
email process
*/3 * * * * /usr/local/bin/php /home/your/public_html/marketing/app/console mautic:email:process --env=prod >/home/your/public_html/marketing/loguiala/emailprocess.log 2>&1
segments update
*/3 * * * * /usr/local/bin/php /home/your/public_html/marketing/app/console mautic:segments:update --env=prod >/home/your/public_html/marketing/loguiala/segmentsupdate.log 2>&1
emails send
*/3 * * * * /usr/local/bin/php /home/your/public_html/marketing/app/console mautic:send:emails --env=prod >/home/your/public_html/marketing/loguiala/sendemails.log 2>&1
fetch - aka bounce
*/3 * * * * /usr/local/bin/php /home/your/public_html/marketing/app/console mautic:fetch:email --env=prod >/home/your/public_html/marketing/loguiala/fetchemail.log 2>&1
It works fine, but sometimes gives some crashes mostly at the moment of big imports - 50.000 records with tag set.
The 3 minute cron, one after another is an excess, i think, but the speed at which the sistem keeps record is important.
In just 10 minutes the soft/hardware created more than 30.000 emails waiting to be sent. The smtp is another issue
What others thing about this.
I’m doing something dumb?
ip bd - week
0 0 * * 0 /usr/local/bin/php /home/your/public_html/marketing/app/console mautic:iplookup:download --env=prod >/home/your/public_html/marketing/loguiala/mauticiplookupdownload.log 2>&1
leadlist update
*/3 * * * * /usr/local/bin/php /home/your/public_html/marketing/app/console mautic:leadlists:update --env=prod >/home/your/public_html/marketing/loguiala/leadlistsupdate.log 2>&1
campains update
*/3 * * * * /usr/local/bin/php /home/your/public_html/marketing/app/console mautic:campaigns:update --env=prod >/home/your/public_html/marketing/loguiala/campaignsupdate.log 2>&1
campains trigger
*/3 * * * * /usr/local/bin/php /home/your/public_html/marketing/app/console mautic:campaigns:trigger --env=prod >/home/your/public_html/marketing/loguiala/campaignstrigger.log 2>&1
email process
*/3 * * * * /usr/local/bin/php /home/your/public_html/marketing/app/console mautic:email:process --env=prod >/home/your/public_html/marketing/loguiala/emailprocess.log 2>&1
segments update
*/3 * * * * /usr/local/bin/php /home/your/public_html/marketing/app/console mautic:segments:update --env=prod >/home/your/public_html/marketing/loguiala/segmentsupdate.log 2>&1
emails send
*/3 * * * * /usr/local/bin/php /home/your/public_html/marketing/app/console mautic:send:emails --env=prod >/home/your/public_html/marketing/loguiala/sendemails.log 2>&1
fetch - aka bounce
*/3 * * * * /usr/local/bin/php /home/your/public_html/marketing/app/console mautic:fetch:email --env=prod >/home/your/public_html/marketing/loguiala/fetchemail.log 2>&1
It works fine, but sometimes gives some crashes mostly at the moment of big imports - 50.000 records with tag set.
The 3 minute cron, one after another is an excess, i think, but the speed at which the sistem keeps record is important.
In just 10 minutes the soft/hardware created more than 30.000 emails waiting to be sent. The smtp is another issue
What others thing about this.
I’m doing something dumb?