crontab issue

some of my cronjobs dont run . mostly the ones that are ever 15min to 1time a day etc . but the ones that run as often as possible work fine .

also does my crontab status look right ?

  • cron.service - Regular background program processing daemon
    Loaded: loaded (/lib/systemd/system/cron.service; enabled; vendor preset: enabled)
    Active: active (running) since Sun 2019-04-28 21:55:18 PDT; 3h 27min ago
    Docs: man:cron(8)
    Main PID: 344 (cron)
    CGroup: /system.slice/cron.service
    `-344 /usr/sbin/cron -f

Apr 29 01:20:01 xxxxxx CRON[8856]: (www-data) CMD (cd /var/www/suitecrm; php -f cron.php > /dev/null 2>&1)
Apr 29 01:20:01 xxxxxx CRON[8857]: (www-data) CMD (cd /var/www/suitecrm; php -f cron.php > /dev/null 2>&1 )
Apr 29 01:21:01 xxxxxx CRON[8875]: pam_unix(cron:session): session opened for user www-data by (uid=0)
Apr 29 01:21:01 xxxxxx CRON[8876]: pam_unix(cron:session): session opened for user www-data by (uid=0)
Apr 29 01:21:01 xxxxxx CRON[8877]: (www-data) CMD (cd /var/www/suitecrm; php -f cron.php > /dev/null 2>&1)
Apr 29 01:21:01 xxxxxx CRON[8878]: (www-data) CMD (cd /var/www/suitecrm; php -f cron.php > /dev/null 2>&1 )
Apr 29 01:22:01 xxxxxx CRON[8944]: pam_unix(cron:session): session opened for user www-data by (uid=0)
Apr 29 01:22:01 xxxxxxt CRON[8943]: pam_unix(cron:session): session opened for user www-data by (uid=0)
Apr 29 01:22:01 xxxxxx CRON[8945]: (www-data) CMD (cd /var/www/suitecrm; php -f cron.php > /dev/null 2>&1)
Apr 29 01:22:01 xxxxxx CRON[8946]: (www-data) CMD (cd /var/www/suitecrm; php -f cron.php > /dev/null 2>&1 )

The first step is to get the system crontab to run cron.php every minute. You can check this in your crontab file, and then in syslog.

Then this program will manage and execute the SuiteCRM jobs which you can check in Admin / Schedulers. When you enter a job you can see the “last ran successfully” time, and check if it is ran recently, and in the correct timezone (frequently people neglect to configure this for CLI PHP).

If specific jobs fail then you should check your logs to see why.