New answers tagged terminal
Depending on the cron version/type you are using, the output from the command usually gets sent via email to someone. In the traditional style you can put MAILTO=your.login or maybe even MAILTOfirstname.lastname@example.org and get the output from the script. In the worst case try 0 */3 * * * /usr/bin/php /var/acme/cron/api_update_db.php > ...
You may be getting some stderr\stdout output which might help identify the problem. Usually this ends up being mailed to yourself, but if not try adding specific redirection of all output to the end of your crontab entry to a file, e.g.: 0 */3 * * * /usr/bin/php /var/acme/cron/api_update_db.php &> /tmp/cron.output
crontab -u <username> -e The short answer, run the cron as a user with the appropriate credentials to the database. Source
Check the Security log when the Firewall is on and see if you can find any blocked entries from the IP that's connecting. Also, check the number of rules in the Firewall and consider disabling/deleting some extraneous ones if there are a lot; if there are too many rules it can actually slow down the response time because it has to process every rule.
Top 50 recent answers are included