Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
Bob Snow Posted April 3 Posted April 3 I created a cron per the error message I got from Invision. My provider, SiteGround, says it is running, cron. Invistion says it is not. This is the error: You should set the cron to run the following command every minute: /usr/local/php80/bin/php -d memory_limit=-1 -d max_execution_time=0 /home/customer/www/mySite/public_html/applications/core/interface/task/task.php 29eb6f039e43b68b4ae33156cb778ac2 I created the cron many months ago, second or third time. SiteGround says the cron is running. I would like to start running the site. I have had it for many years and still, I'm at the cron stage. What to do. Bob /usr/local/php80/bin/php -d memory_limit=-1 -d max_execution_time=0 /home/customer/www/home2000.com/public_html/applications/core/interface/task/task.php 29eb6f039e43b68b4ae33156cb778ac2tomer/www/home2000.com/public_html/applications/core/interface/task/task.php 29eb6f039e43b68b4ae33156cb778ac2
Randy Calvert Posted April 3 Posted April 3 If cron is not working correctly and you can’t get it working properly, you can either run it with your site traffic or use a third party to run it for you. Personally I would look at the cron log and see if it’s actually executing. You should be able to see a log of it executing every minute. If you can’t find that, I would ask them to help you find that log.
Marc Posted April 4 Posted April 4 As mentioned above, you need to look at any errors being returned. The above is not an error, it's the cron command itself
Nathan Explosion Posted April 4 Posted April 4 (edited) Are you definitely using PHP 8.0 for your site? Go to the support page in the ACP and confirm what version of PHP your site is running under, then come back and advise. Edited April 4 by Nathan Explosion
Bob Snow Posted April 4 Author Posted April 4 This is the response from my Provider. SiteGround Check Thank you for contacting our Help Desk! I checked the server logs and I can confirm that the cron command is being executed every 30 minutes. Here are the server logs that confirm that: 2024-04-03 19:30:01.000827 CMD: u1169-mijchxsppju3 /usr/local/php80/bin/php -d memory_limit=-1 -d max_execution_time=0 /home/customer/www/home2000.com/public_html/applications/core/interface/task/task.php 29eb6f039e43b68b4ae33156cb778ac2 2024-04-03 20:00:01.000751 CMD: u1169-mijchxsppju3 /usr/local/php80/bin/php -d memory_limit=-1 -d max_execution_time=0 /home/customer/www/home2000.com/public_html/applications/core/interface/task/task.php 29eb6f039e43b68b4ae33156cb778ac2 2024-04-03 20:30:01.000841 CMD: u1169-mijchxsppju3 /usr/local/php80/bin/php -d memory_limit=-1 -d max_execution_time=0 /home/customer/www/home2000.com/public_html/applications/core/interface/task/task.php 29eb6f039e43b68b4ae33156cb778ac2 2024-04-03 21:00:01.000328 CMD: u1169-mijchxsppju3 /usr/local/php80/bin/php -d memory_limit=-1 -d max_execution_time=0 /home/customer/www/home2000.com/public_html/applications/core/interface/task/task.php 29eb6f039e43b68b4ae33156cb778ac2 2024-04-03 21:30:01.000456 CMD: u1169-mijchxsppju3 /usr/local/php80/bin/php -d memory_limit=-1 -d max_execution_time=0 /home/customer/www/home2000.com/public_html/applications/core/interface/task/task.php 29eb6f039e43b68b4ae33156cb778ac2 2024-04-03 22:00:01.000134 CMD: u1169-mijchxsppju3 /usr/local/php80/bin/php -d memory_limit=-1 -d max_execution_time=0 /home/customer/www/home2000.com/public_html/applications/core/interface/task/task.php 29eb6f039e43b68b4ae33156cb778ac2 2024-04-03 22:30:01.000683 CMD: u1169-mijchxsppju3 /usr/local/php80/bin/php -d memory_limit=-1 -d max_execution_time=0 /home/customer/www/home2000.com/public_html/applications/core/interface/task/task.php 29eb6f039e43b68b4ae33156cb778ac support@gvam1233.siteground.biz:~$ date Wed Apr 3 22:35:50 UTC 2024 I then executed the command via SSH and this is the output: baseos | home2000.com | u1169-mijchxsppju3@gvam1233.siteground.biz:~/www/home2000.com/public_html$ /usr/local/php80/bin/php -d memory_limit=-1 -d max_execution_time=0 /home/customer/www/home2000.com/public_html/applications/core/interface/task/task.php 29eb6f039e43b68b4ae33156cb778ac2 Cache-Control: no-cache, no-store, must-revalidate, max-age=0, s-maxage=0 Expires: 0 Content-type: text/html; charset=UTF-8 Not at command line If this is not the expected result, consult with your developer and see whether the cron command needs to be adjusted. Best Regards Miroslav Rangelov Technical Support Team
Bob Snow Posted April 4 Author Posted April 4 >>Nathan Explosion<< Yes. Version PHP 8.0.30 My PHP VERSION IS SET MANUALLY (Not sure what that means). Bob
Adlago Posted April 4 Posted April 4 17 minutes ago, Bob Snow said: I checked the server logs and I can confirm that the cron command is being executed every 30 minutes. Cron command should be executed every 1 minute. Ask the host to edit from 30 to 1 minute. Jim M 1
Jim M Posted April 4 Posted April 4 9 minutes ago, Bob Snow said: Why am I getting the "Maintenance Task not Running"? If you are not running it per our recommendations, you will get this. As you are running it once every 30 min, that would not be enough. You need to run the task once per minute.
Bob Snow Posted April 6 Author Posted April 6 (edited) My cron is now running every minute. And my PHP is 8.1.27. But my MySQL is 5.7.44-48-log. SiteGround said that is the way it is for now. Where does that leave me with Invision Community software? Bob Edited April 6 by Bob Snow
Randy Calvert Posted April 6 Posted April 6 Ok… does your site work? Can you login and say for example post a topic?
beats23 Posted April 7 Posted April 7 21 hours ago, Bob Snow said: But my MySQL is 5.7.44-48-log. SiteGround said that is the way it is for now Same here. My hosting only has MySQL 5.7.44-48-log; will it still work with IPSv5?
Bob Snow Posted April 7 Author Posted April 7 >>beats23<< I just started to update to 4.7.16 And found this: MySQL Requirements MySQL version 5.7.44-48-log. Recommendations None of these items are required in order to continue with the upgrade right now. However, they may affect how your community works or be required in future upgrades. You should make a note of them and contact your hosting provider or system administrator after the upgrade to address them. You can re-run these checks later from the Support section of the Administrator Control Panel. You are running MySQL version 5.7.44-48-log. While this version is compatible, we recommend version 8.0.13 or above So it seems to me we are both OK. Bob
Bob Snow Posted April 7 Author Posted April 7 >>beats23<< After I completed the update to 4.7.16 I got the following Error: Server Requirements Your server does not meet our recommendations. This may prevent you from upgrading to future versions of Invision Community. -You are running MySQL version 5.7.44-48-log. While this version is compatible, future releases of our software will --require version 8.0.13 or above. You should contact your hosting provider or system administrator and ask them to resolve these issues. Bob
Rick Vasquez Posted April 7 Posted April 7 considering 5.7 is EOL, I would recommend upgrading to 8.0.x anyway. An inplace upgrade should be trivial since you have little/no data in the database.
Bob Snow Posted April 7 Author Posted April 7 >>Rick<< My forum has nothing of value. My Invision Community is as new as if I had installed it 10 minutes ago. When you're talking about MySQL 8.0 it is not PHP? The reason I ask is my PHP is 1.2.7 and MySQL would be jumping up to about the same version number. Are we talking about 2 different items or have I got it confused that we're talking about one item, PHP? In other words, MySQL and PHP are one of the same? It just doesn't make sense that SiteGround would be stuck at MySQL5.7.44-48-log. If this MySQL is EOL what takes its place? Bob
Marc Posted April 8 Posted April 8 I have to be honest here. If you are asking questions like the above, you really need someone to be managing this on your behalf. MySQL is not PHP no. They are 2 separate things. In answer to your question, if you end up on a version that is not supported by the platform, you will be unable to upgrade at that point
Recommended Posts