Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
coolnet560 Posted Friday at 09:42 AM Posted Friday at 09:42 AM I don't have much traffic at the moment it seems, and I am receiving this message. Any suggestions on how to fix this?
Marc Posted Friday at 09:46 AM Posted Friday at 09:46 AM I'm not sure what I can say to you other than what it saus in the message there. As it says, you should set up cron or web service coolnet560 1
Daniel F Posted Friday at 09:46 AM Posted Friday at 09:46 AM You could use cron jobs if you host supports it (most do!) or use a web service like easycron coolnet560 1
Gary Posted Saturday at 11:24 PM Posted Saturday at 11:24 PM Hi @coolnet560, This guide may shed some light on setting up a cron job successfully, but the description once 'Use cron (recommended)' is selected should be self explanatory and get you out of trouble. coolnet560 1
coolnet560 Posted Sunday at 07:17 AM Author Posted Sunday at 07:17 AM 7 hours ago, Gary said: Hi @coolnet560, This guide may shed some light on setting up a cron job successfully, but the description once 'Use cron (recommended)' is selected should be self explanatory and get you out of trouble. Thank you for your help. I had my hosting provider enable the cron job.
Gary Posted Sunday at 10:18 PM Posted Sunday at 10:18 PM Good to hear! Your community should run perfectly from now on. 😉
coolnet560 Posted Monday at 11:39 AM Author Posted Monday at 11:39 AM Unfortunately, it seems I am getting an error message. Sent in a ticket to them to fix it. /opt/alt/php81/usr/bin/php -d memory_limit=-1 -d max_execution_time=0 /home/therecom/forums.therecommunity.net/applications/core/interface/task/task.php 9ffd090fc92a79cd541bc9eeb89397c2 Marc 1
coolnet560 Posted Monday at 12:30 PM Author Posted Monday at 12:30 PM Here's what it looks like on the cpanel.
Marc Posted Monday at 12:36 PM Posted Monday at 12:36 PM Check the file itself can be executed by your system. Other than that though, it would be something your hosting company would need to look into
Donnie95 Posted Monday at 01:07 PM Posted Monday at 01:07 PM You may have forgotten to include the random number at the end of the cron command, or the path to your PHP executable and task.php file may be incorrect.
coolnet560 Posted Monday at 02:05 PM Author Posted Monday at 02:05 PM 1 hour ago, Marc said: Check the file itself can be executed by your system. Other than that though, it would be something your hosting company would need to look into 56 minutes ago, Donnie95 said: You may have forgotten to include the random number at the end of the cron command, or the path to your PHP executable and task.php file may be incorrect. I looked at the command settings and it seems that the * means every minute. I did change it to 01 and left the stars for the rest. See what happens tomorrow I guess. Have to be honest my hosting provider is clueless. 😂
Jim M Posted Monday at 02:08 PM Posted Monday at 02:08 PM 2 minutes ago, coolnet560 said: looked at the command settings and it seems that the * means every minute. Every minute is what you would want 🙂 . Changing that to 01 would just run it on the first minute of every hour.
coolnet560 Posted Monday at 02:13 PM Author Posted Monday at 02:13 PM (edited) 5 minutes ago, Jim M said: Every minute is what you would want 🙂 . Changing that to 01 would just run it on the first minute of every hour. If that's the case, any suggestions on the error? I see this in the email "Cron <therecom@webhosting2018> /opt/alt/php81/usr/bin/php -d memory_limit=-1 -d max_execution_time=0 /home/therecom/forums.therecommunity.net/applications/core/interface/task/task.php" Incorrect Key. How do I fix that? Edited Monday at 02:14 PM by coolnet560
teraßyte Posted Monday at 02:14 PM Posted Monday at 02:14 PM Based on your screenshot, you are missing the key at the end of the command: 9ffd090fc92a79cd541bc9eeb89397c2 Edit the cronjob and be sure to past the entire line of text in it. coolnet560 1
coolnet560 Posted Monday at 02:17 PM Author Posted Monday at 02:17 PM 2 minutes ago, teraßyte said: Based on your screenshot, you are missing the key at the end of the command: 9ffd090fc92a79cd541bc9eeb89397c2 Edit the cronjob and be sure to past the entire line of text in it. Thank you. Added that. I guess they forgot to add the key. teraßyte 1
Recommended Posts