josephs8

No errors are reported in the cronlog (and it is showing it is being executed every minute), the messages log, or the PHP log. I also was able to execute the command that crontab runs manually and it did not produce any errors. I've also set up a log on the cronjob output and checked for output errors from that and nothing. Finally, I also switched it to traffic based and it didn't seem to impact it.

We are using a cronjob and yes it is using the same version of php. We've always used a cronjob and it has not gotten any better just appears to be increasing.

I am not getting an error that scheduled tasks are not running, but I have a very large number of background tasks that appear on the widget on the dashboard. It shows I can run them manually, but I am afraid of what that could do to the board's performance with that many. What are my possible options here to fix this?

@Jim M thanks for the image. But I must still be doing something wrong. I search for Task click on the Tasks item that pops up. Then find the queue task (its usually at the top and running), I remove the running lock and then click run now and I get a 404 error not a 500 error. Are you doing anything differently? Or would you be able to provide a video of what you are doing as I feel like I am missing something here.

@Jim M I updated the credentials. Please let me know if those work or not. Thank you.

@Jim M you mean allowing it to talk with the internet from the server? If thats the case no we have no restrictions on outgoing traffic from the server.

@Jim M I am not seeing any 500 error. I do see an error, but it is not generating a 500 error in the logs and seems really unclear what it means. RuntimeException: (0) #0 /var/www/atrl.net/html/applications/core/tasks/queue.php(43): IPS\_Task::runQueue() #1 /var/www/atrl.net/html/system/Task/Task.php(375): IPS\core\tasks\_queue->IPS\core\tasks\{closure}() #2 /var/www/atrl.net/html/applications/core/tasks/queue.php(55): IPS\_Task->runUntilTimeout() #3 /var/www/atrl.net/html/system/Task/Task.php(274): IPS\core\tasks\_queue->execute() #4 /var/www/atrl.net/html/applications/core/modules/admin/settings/advanced.php(751): IPS\_Task->run() #5 /var/www/atrl.net/html/system/Dispatcher/Controller.php(107): IPS\core\modules\admin\settings\_advanced->runTask() #6 /var/www/atrl.net/html/applications/core/modules/admin/settings/advanced.php(38): IPS\Dispatcher\_Controller->execute() #7 /var/www/atrl.net/html/system/Dispatcher/Dispatcher.php(153): IPS\core\modules\admin\settings\_advanced->execute() #8 /var/www/atrl.net/html/admin/index.php(13): IPS\_Dispatcher->run() #9 {main}

When I try to access the Dashboard of the Admin CP it is timing out. I've checked my server logs and the only response I am getting is that the connection timed out. This happens after about 30 seconds. What would be causing this and how can I fix it? 2022/12/24 13:35:17 [error] 1288#1288: *228311 upstream timed out (110: Connection timed out) while reading response header from upstream, client: xxx.xx.xx.xxx, server: demo.com, request: "GET /admin/?app=core&module=overview&controller=dashboard HTTP/2.0", upstream: "fastcgi://unix:/run/php-fpm/www.sock", host: "demo.com", referrer: "https://demo.com/admin/?app=core&module=members&controller=members&do=view&id=36247

@Jim M We officially launched with our new server as I thought that may just be an issue on the test server as you mentioned but no such luck. The issue seems to still be there. I removed all the plugins/apps except 1 app and 2 plugins that failed to remove not sure if that is part of the issue or not and not sure how to get rid of those. Where do you find the 500 errors? I was looking through my NGINX logs and I do not see any 500 errors being reported so if you can tell me where to find them I may have a better idea what is causing them. Thanks for your assistance!

@Jim M this will be our new production site. So you are saying I have launch a website that is broken for you to be able to help with it?

@Jim M I re-added them. Also please make sure you read the notes as this is the test site that we are currently having issues with so if you are trying to login to our production site that will not work.

@Jim M I just updated those credentials earlier today. Can you please elaborate on what isn't working as I verified all the login information worked before I added it.

Yes, I am using cron. The crontask does point to /usr/bin/php but I've verified that as root the /usr/bin/php returns version 8.0.26 (which the con task runs as root) and PHP7 has never been installed on this server. Also other tasks appear to be running just fine, this is the only task that is stuck.

@Marc Stridgen thank you. I ended up playing around with this over the weekend and did do a manual from move bucket to bucket which saved a bunch of time so thank you. One other question I do have is when I move additional files that are not already in s3 do I just copy the contents of the upload directory directly to my S3 bucket thus leaving the folder structure exactly the same?

Hello, I am getting the following error in my community. I have looked over the server logs and did not see anything nor does clicking the view logs button product anything. I've tried unlocking the task and restarting, restarting the server, restarting nginx and php-fpm and none of those work. How can I get this issue resolved?

Currently I am storing most of my files in a AWS S3 bucket. However I want to change it to use a custom URL so I can take advantage of a CDN in front of my S3 bucket. My question is how will this impact my community when I make this change? Is it an instant change or will there be some time that it will take to update the URL's to use the new custom URL I have specified. This would obviously also change the S3 Bucket name as I will need to create a new S3 bucket that uses my the domain I chose for the CDN. During this I may also change the region the bucket is located in so the endpoint will change, though will this make a difference since I am using a custom URL? Thank you!

Thanks @Jim M one other question, if I do the manual upload to S3 myself do I need to worry about the directory structure at all? Since everything is stored in the file system uploads directory at the moment do I just upload that directly to the root of my S3 container?

Right now I have Theme Resources, Icons & Logos, and Image Proxy Cache already using AWS S3 instance. For the rest I am using a file share on the server "../uploads/". I did quick df of that folder and found that it is 28GB. In the settings for the files it does say that things will be moved in the background and it may break things in the process of this. My question is it possible to do this ahead of time. Could I manually upload all the files currently in the uploads directory to my S3 instance manually? If not is there anyway to check on the progress and determine how long this would take?

Hello, I found a bug I believe that is related to this when you have Dev Mode turned on and try to access the admin section I am getting the error attached below. I turned off all other customizations and was able to trace it back to this. I can provide more information if necessary.