It looks like you're new here. If you want to get involved, click one of these buttons!
I have a new install of Sendy on a ubuntu stack from Bitnami installed on EC2. I have setup the cron job and the server syslog shows:
Jun 18 19:30:01 CRON[18548]: (root) CMD (php /opt/bitnami/apache2/htdocs/sendy/scheduled.php > /dev/null 2>&1)
Jun 18 19:35:01 CRON[18636]: (root) CMD (php /opt/bitnami/apache2/htdocs/sendy/scheduled.php > /dev/null 2>&1)
Jun 18 19:40:01 CRON[18714]: (root) CMD (php /opt/bitnami/apache2/htdocs/sendy/scheduled.php > /dev/null 2>&1)
Jun 18 19:45:01 CRON[18790]: (root) CMD (php /opt/bitnami/apache2/htdocs/sendy/scheduled.php > /dev/null 2>&1)
Jun 18 19:50:01 CRON[18868]: (root) CMD (php /opt/bitnami/apache2/htdocs/sendy/scheduled.php > /dev/null 2>&1)
Jun 18 19:55:01 CRON[18942]: (root) CMD (php /opt/bitnami/apache2/htdocs/sendy/scheduled.php > /dev/null 2>&1)
So I assume it is running. I set up a test message and it does not seem to be sending.
I following a previous forum thread and reset cron setup, created a new campaign and see the "Blue Cron setup modal" box.
Any tips on how to proceed?
I can run:
php /opt/bitnami/apache2/htdocs/sendy/scheduled.php
from command, so permissions seem fine.
Actually got it fixed!
I used the full PHP binary path in the cron entry: /opt/bitnami/php/bin/php