Cron jobs issue, fresh install

mindeswx · September 27, 2021, 11:26am

Your software - v2.16.5 (that’s what it says in the right bottom corner on the dashboard)

My PHP version is : 7.2.24-0ubuntu0.18.04.9
My MySQL/MariaDB version is (delete as applicable): MySQL/MariaDB version - mysqlnd 5.0.12

Updating/Installing Errors
I am (delete as applicable): Updating
Upgrading/installing via (delete as applicable) : Web

These errors are showing in the installer : none

These errors are showing in the Mautic log : none

Your problem
My problem is :
Only able to send emails immediately, queue is not working, it says the email has been sent, but I am not receiving it.

Steps I have tried to fix the problem :
I have followed the installation steps on your website for ubuntu 18.4, and after opening my dashboard it said update is available, so I clicked on that.

Now that I am unable to queue the emails I think it should be CRON jobs related, so I searched in the forum and looks like everyone has their console on -
/var/www/html/bin/console

but on my server it is on
/var/www/html/app/console for some reason. ( there is no bin folder)
Please help me troubleshoot it

This is the output of crontab -l

root@email1:/var/www/html# crontab -l
# Cron jobs for Mautic 2
#* * * * * php /var/www/html/app/console mautic:segments:update
#* * * * * php /var/www/html/app/console mautic:campaigns:update
#* * * * * php /var/www/html/app/console mautic:campaigns:trigger
#
# Cron jobs for Mautic 3
* * * * * php /var/www/html/bin/console mautic:segments:update
* * * * * php /var/www/html/bin/console mautic:campaigns:update
* * * * * php /var/www/html/bin/console mautic:campaigns:trigger

and this is the /etc/ctrontab


# /etc/crontab: system-wide crontab
# Unlike any other crontab you don't have to run the `crontab'
# command to install the new version when you edit this file
# and files in /etc/cron.d. These files also have username fields,
# that none of the other crontabs do.


SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

 m h dom mon dow user  command
17 *    * * *   root    cd / && run-parts --report /etc/cron.hourly
25 6    * * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
47 6    * * 7   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
52 6    1 * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
#




Thank you!!

mikew · September 27, 2021, 1:35pm

hi there

in the more recent versions of Mautic console is sitting in /mautic/bin/console

Also I do not see that you have a cronjob to send queued messages.
you will need something like this
*/2 * * * * php7.4 /var/www/mautic/bin/console mautic:emails:send > /dev/null
This will trigger a send every two minutes for example

mindeswx · September 27, 2021, 6:40pm

Thank you for your answer, that’s strange why I didn’t get the newest version when doing a fresh install, and did an update on the dashboard.
Anyways, will try to set up CRON jobs manually and let you know.

rcheesley · September 27, 2021, 6:49pm

Your PHP version is too low to get the newer version:

See Requirements - Mautic Community - this lists the minimum versions required.

There is a bug which means you won’t see newer versions:

github.com/mautic/mautic

Mautic shows it's running the latest version when new version requires higher PHP version

opened 01:26PM - 23 Sep 21 UTC

closed 03:32PM - 07 Jan 22 UTC

dennisameling

bug user-experience installation stale

### Mautic Version 3.0.0 and later (including Mautic 4) ### PHP version … 7.3.28 ### What browsers are you seeing the problem on? Not relevant ### What happened? When running Mautic 3.x and PHP 7.3, Mautic doesn't inform the user that Mautic 4 is available. This is because the minimum PHP version in Mautic 4 is 7.4, so the update logic simply marks Mautic 4 as "incompatible" and skips it. This way, users will never know that Mautic 4 is available, unless they upgrade to PHP 7.4. This problem is caused by the following code snippet: https://github.com/mautic/mautic/blob/bf37c06008a936fe9e2919b4baa2d3220cfb6ad1/app/bundles/CoreBundle/Helper/Update/Github/ReleaseParser.php#L54-L60 I'm considering to include a fix for this bug as part of the work in https://github.com/mautic/mautic/issues/9607. ### How can we reproduce this issue? Step 1: Install Mautic 3.2.0 or later on PHP 7.3 Step 2: Open the dashboard. No notification shows up that a new version is available. Step 3: To double-check, run this on the command line: ``` $ php bin/console mautic:update:find Great! You are running the current version of Mautic. ``` Step 4: Switch to PHP 7.4 Step 5: Re-run the CLI command above. Mautic now tells you that version 4 is available: ``` $ php bin/console mautic:update:find Version 4.0.0 of Mautic is available for download. Please visit https://github.com/mautic/mautic/releases/tag/4.0.0 for more information. To update, you can run 'php bin/console mautic:update:apply' from the command line. ``` ### Relevant log output _No response_ ### Code of Conduct - [X] I confirm that I have read and agree to follow this project's Code of Conduct

We are fixing this so that you get alerted about a release being available but informing you about the PHP version being unsupported with this PR:

github.com/mautic/mautic

Add additional checks to installation + update process

mautic:4.x ← dennisameling:installer-improvements

opened 01:34PM - 21 Sep 21 UTC

dennisameling

+1228 -516

~⚠️ **This PR needs #10481 to be merged first** ⚠️~ Done ✅ | Q … | A | -------------------------------------- | --- | Branch? | 4.x | Bug fix? | no | New feature? | yes | Deprecations? | no | BC breaks? | no | Automated tests included? | yes | Related user documentation PR URL | mautic/mautic-documentation#... | Related developer documentation PR URL | mautic/developer-documentation#... | Issue(s) addressed | Related to #9607, fixes #10472   #### Description: As described in https://github.com/mautic/mautic/issues/9607, we wanted to have additional checks in the Mautic installation and update process, like PHP version, database driver/version, etc. This PR lays the foundation for pre-update checks. Those checks are executed both in the UI and CLI update processes. This looks as follows (ignore the actual versions shown in the screenshots): **Pre-update checks in the UI** ![image](https://user-images.githubusercontent.com/17739158/134695440-db341cca-3585-4e6e-aa2c-52d808c85133.png) **Pre-update checks in the CLI** ![image](https://user-images.githubusercontent.com/17739158/134695545-451b009e-18be-4210-867d-e80a04520255.png) New pre-update checks can be added easily by creating a new check in `app/bundles/CoreBundle/Helper/Update/PreUpdateChecks`, then tagging it with `mautic.update_check` in the bundle's `config.php`. Then it will be picked up as a pre-update check. This PR adds the following checks as a starting point: - Database driver (MariaDB or MySQL) - Database version (MySQL 5.7.14+ or MariaDB 10.2.7+) --> these can now be configured dynamically in `app/release_metadata.json`) - PHP version (`minimum_php_version` and `maximum_php_version` in `app/release_metadata.json`) **Other fixes/changes in this PR** - Fixes #10472 where the user wasn't informed at all if a newer Mautic version was available, but the user's PHP version was too low. The user now sees that a new Mautic version is available, but the update will fail at the pre-update check step, telling the user that their PHP version is too old. - Don't run `upload-release-asset` GitHub action on forks (created a test release for this PR at https://github.com/dennisameling/mautic/releases/tag/4.9.99-alpha so ran into this issue there) - Remove a bunch of legacy code in `upgrade.php` that's no longer used - Fixed bug where the CLI installation defaults to pdo_mysql (`db_driver`) if a database driver is set in `app/config/local.php` but not in the CLI options. The same goes for `db_backup_tables` and `db_backup_prefix`. - Now leverages more [PHP typed properties](https://stitcher.io/blog/typed-properties-in-php-74) (this is possible since we require PHP 7.4 as of Mautic 4)  #### Steps to test this PR: 1. Checkout this PR locally: `gh pr checkout 10459` 2. For the remainder of the steps, we assume that you're using DDEV for local development. This allows you to easily change your PHP/database versions 3. **Before testing each scenario below**, please ensure you have a clean state where Mautic is not installed: `ddev delete --omit-snapshot --yes && rm -rf var/cache && rm app/config/local.php` 4. Before every test run you do, set the correct PHP/database versions in the DDEV config: - Open `.ddev/config.yaml` - Change `php_version` (don't forget to update the version in `webimage_extra_packages` as well), `mariadb_version`, `mysql_version` as needed. NOTE: you can only have EITHER a `mariadb_version` OR a `mysql_version` active, not both! 5. Run `ddev restart` so that the appropriate PHP/database versions will be activated. For testing the **CLI installation**, please run `ddev exec php bin/console mautic:install https://mautic.ddev.site --db_driver=pdo_mysql --db_host=db --db_user=db --db_name=db --db_password=db --db_port=3306 --admin_password=mautic --admin_email="demo@ddev.local"` - you can change the database driver by changing `db_driver` accordingly in this command. **Here's the text matrix for the installation process - all scenarios below have to be tested.** | Action | PHP version | Database driver | Database version | Expected outcome |--|--|--|--|--| | Install using UI | 7.3.x | pdo_mysql | 10.3.x | ❌ on PHP version | Install using CLI | 7.3.x | pdo_mysql | 10.3.x | ❌ on PHP version | Install using CLI | 7.4.x | pdo_sqlite | 10.3.x | ❌ on database driver | Install using UI | 7.4.x | pdo_mysql | MariaDB 10.1.x | ❌ on database version | Install using CLI | 7.4.x | pdo_mysql | MariaDB 10.1.x | ❌ on database version | Install using UI | 7.4.x | pdo_mysql | MySQL 5.6.x | ❌ on database version | Install using CLI | 7.4.x | pdo_mysql | MySQL 5.6.x | ❌ on database version | Install using UI | 7.4.x | pdo_mysql | MariaDB 10.3.x | ✅ | Install using CLI | 7.4.x | pdo_mysql | MariaDB 10.3.x | ✅ | Install using UI | 7.4.x | pdo_mysql | MySQL 5.7.x | ✅ | Install using CLI | 7.4.x | pdo_mysql | MySQL 5.7.x | ✅ Once you have a working Mautic installation, we can start testing the update scenario as well. **Before you start testing the update scenario, please head over to `app/config/local.php` and add the following lines at the bottom**: ``` 'system_update_url' => 'https://api.github.com/repos/dennisameling/mautic/releases', 'update_stability' => 'alpha', ``` Then run `rm -rf var/cache` to remove the cache and `ddev exec "php bin/console mautic:update:find"` to check for updates. Please only proceed if you see "Version 4.9.99-alpha of Mautic is available for download". I bumped the minimum PHP version to 8.0.0, MySQL version to 8.0.0 and MariaDB version to 10.5.0 so that you can see the update errors show up. - You can try the **CLI** update by running `ddev exec "php bin/console mautic:update:apply"`. - You can try the **UI** update by going to https://mautic.ddev.site/index_dev.php/s/update in your browser (it's important you use the dev version as the production assets will only be generated when we release a new Mautic version) | Action | PHP version | Database driver | Database version | Expected outcome |--|--|--|--|--| | Update using UI | 7.4.x | pdo_mysql | 10.3.x | ❌ on PHP version and database version | Update using CLI | 7.4.x | pdo_mysql | 10.3.x | ❌ on PHP version and database version  <a href="https://gitpod.io/#https://github.com/mautic/mautic/pull/10459"><img src="https://gitpod.io/button/open-in-gitpod.svg"/></a>

which is still in progress but we hope will ship with 4.1.

dennisameling · September 27, 2021, 7:03pm

In addition to what was mentioned by others, could you please tell us where you got the installation instructions from? In your post I saw:

I have followed the installation steps on your website for ubuntu 18.4

I’m curious where exactly you found those instructions Mautic 2.16 is rather old, as we’re already at Mautic 4. I have a feeling you got instructions from an older source (article or blog post) that we might need to update. Thanks in advance!

mindeswx · September 27, 2021, 7:07pm

I followed this guide - Secure Mautic Installation on a VPS in 2020 | Mauteam.org
and yes, it’s in fact quite old already… By any chance you have a newer guide I could follow on a fresh VPS?
Thanks for the help!

dennisameling · September 27, 2021, 7:27pm

Ah, thanks for sharing! @Yosu_Cadilla would you mind updating that article for Mautic 4?

For now @mindeswx, you can follow this article: Mautic 3 Installation on Ubuntu 20.04 with PHP 7.3 and MySQL 5.7 - that one is slightly newer, but also not updated for Mautic’s latest version. You can basically follow that article but with the following changes:

Install PHP 7.4 instead of 7.3 (replace php7.3 with php7.4 everywhere)
Install Mautic 4 instead of Mautic 3, so instead of wget https://github.com/mautic/mautic/releases/download/3.2.5/3.2.5.zip you can do wget https://github.com/mautic/mautic/releases/download/4.0.0/4.0.0.zip

Then you will be on the latest version right away Hope this helps! We’re working on making this process smoother for the future, but for now you should be able to get started with these steps.

mindeswx · September 29, 2021, 11:53am

Thank you very much, I have followed these installation steps on the new server, and now I am running Mautic 4 , unfortunately the queue still isn’t working with the provided CRON jobs
( https://mauteam.org/wp-content/uploads/2019/10/cron-jobs.txt)

However, now I can trigger the email to be sent with this command -
php7.4 /var/www/html/bin/console mautic:emails:send

Could someone please share what are the correct CRON jobs for mautic 4?

Thank you.

mikew · September 29, 2021, 5:38pm

in the link you sent the cronjob is missing the one you are running manually

Cron jobs for Mautic 3

- - - - php /var/www/html/bin/console mautic:segments:update
- - - - php /var/www/html/bin/console mautic:campaigns:update
- - - - php /var/www/html/bin/console mautic:campaigns:trigger
        just add
        */3 * * * * php7.4 /var/www/html/bin/console mautic:emails:send
        or whatever frequency you want it to fire at.

Take note that the way the cronjob are set up above can be very heavy on the system as they are running every minute and not sure this is necessary.

Check out Crontab.guru - The cron schedule expression editor/1_** to understanding the intervals you may want

mindeswx · September 30, 2021, 9:55am

Thank you @mikew , added that line to the CRON jobs and it’s working now.
However, I have noticed one strange thing, when sending messages immediately I am able to use “from” as my domain - xxx@pinkcreators.com
but when using the queue method I get the following error -
The from address does not match a verified Sender Identity. Mail cannot be sent until this error is resolved. Visit https://sendgrid.com/docs/for-developers/sending-email/sender-identity/ to see the Sender Identity requirements

Using the domain that is verified on sendgrid (em2922.pinkcreators.com) solves this error.
Not a big deal, just a bit strange.

EDIT
I am still only able to trigger the queue manually, even though I can verify the CRON job is running
result of tail -f /var/log/syslog

Sep 30 11:02:01 email2 CRON[110654]: (root) CMD (php /var/www/html/bin/console mautic:campaigns:trigger^M)
Sep 30 11:02:01 email2 CRON[110655]: (root) CMD (php /var/www/html/bin/console mautic:segments:update^M)
Sep 30 11:02:01 email2 CRON[110656]: (root) CMD (php /var/www/html/bin/console mautic:emails:send^M)
Sep 30 11:02:01 email2 CRON[110657]: (root) CMD (php /var/www/html/bin/console mautic:campaigns:update^M)

But the emails are not sent, just after running
php /var/www/html/bin/console mautic:emails:send manually they are sent out. There are no errors when running the command.
Please help troubleshooting this… Thank you

mindeswx · September 30, 2021, 4:18pm

Finally fixed it… Spent half of the day bashing my head to the table for this…
It was my mistake using nano as crontab editor, because it has added the ^M symbol to the end of lines.

I have installed postfix, and all CRON job errors appeared in /var/spool/mail/root.

eleinbra · September 16, 2022, 1:08pm

@mindeswx what you do for remove the ‘^M’?

Edited

why you are with this same doubt.
I activated the master admin:
Preformatted text # sudo su

Update and Install ‘dos2unix’:
Preformatted text # apt update & apt upgrade -y
Preformatted text # apt install dos2unix

Go to the crontab folder:
Preformatted text # cd /var/spool/cron/crontabs/

Convert the crontab file with this command:
Preformatted text # dos2unix archive*
replace the 'archive’ by the name of your crontab archive.

I hope help us!

joeyk · September 16, 2022, 1:51pm

Hi, I wouldn’t run all the crons at the same time, but rather sequentually.
If you are running your segment update every minute and it takes 2 minutes to run, then you’ll have a problem in 2-3 days or you will produce long error logs.
Joey

Topic		Replies	Views
Campaign Problems, Cron Jobs Product Support community , discussion	7	586	October 6, 2020
Basic Question About CRON jobs Product Support mautic-3	15	991	September 22, 2021
Current Error Log: email send out, but not real successfully, not one received Product Support mautic-4	3	1411	October 9, 2022
Cannot schedule emails (cron job problem?) Product Support	2	368	February 15, 2021
Cron Job Error Messages Product Support mautic-4	3	265	September 14, 2023

Cron jobs issue, fresh install

Cron jobs for Mautic 3

Edited

Related topics