Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
Scott Allen Posted January 30, 2021 Posted January 30, 2021 Hello I recently started investigating externally hosting some of our content (images, downloads etc) on soemthing like S3. I started small and it went well. I set the downloads folder to be stored on digital ocean spaces and to move files across. It seems to have moved some and is stuck on others. I now have a notification tell me that task queue has been running for too long and might be misconfigured. Background tasks are slowly building up and attempting to run them manually gets stuck on starting forever. It seems during this time that invisioncommunity software is trying to upload the files and failing. Unfortunately this has left this site in a bit of a weird state. Half the stuff has uploaded, but most of the links have transitioned to the new link, so a lot of things are broken. At this stage, I'd be happy to simply roll back to hosting everything locally and forget this idea. Maybe if I could somehow delete the queue job and set it back to locally. I see the below for various different files every second on system logs. Anyone have any ideas? ------ ------------------------------------ SOCKETS REQUEST: https://vgcdn.nyc3.digitaloceanspaces.com/uploads/monthly_2016_06/576a55f6eac23_FalconBMS4.33.1DeepStrikeTE_zip.64cf8f6d10288309efad9f2d83468e1d ------------------------------------ PUT /uploads/monthly_2016_06/576a55f6eac23_FalconBMS4.33.1DeepStrikeTE_zip.64cf8f6d10288309efad9f2d83468e1d HTTP/1.1 Host: vgcdn.nyc3.digitaloceanspaces.com User-Agent: Invision Community 4 Cache-Control: public, max-age=31536000 Content-Length: 27569 Content-MD5: <removed> Content-Type: application/x-unknown X-Amz-Acl: public-read X-Amz-Content-Sha256: 76c58b003032b80aece60e95e4240cb5a478e7715b9a69565e2015ca7c585505 X-Amz-Date: 20210130T060544Z Authorization: AWS4-HMAC-SHA256 Credential=<removed>,SignedHeaders=cache-control;content-length;content-md5;content-type;host;x-amz-acl;x-amz-content-sha256;x-amz-date,Signature=<removed> Connection: Close PK�������� #0 /var/www/veterans/system/Log/Log.php(176): IPS\_Log::log('\n\n-------------...', 'request') #1 /var/www/veterans/system/Http/Request/Sockets.php(267): IPS\_Log::debug('\n\n-------------...', 'request') #2 /var/www/veterans/system/File/Amazon.php(766): IPS\Http\Request\_Sockets->__call('PUT', Array) #3 /var/www/veterans/system/File/Amazon.php(304): IPS\File\_Amazon::makeRequest('monthly_2016_06...', 'put', Array, NULL, 'PK\x03\x04\x14\x00\x00\x00\x08\x00\xCDQ\xB9H\xEA...', NULL, false, false) #4 /var/www/veterans/system/File/File.php(1257): IPS\File\_Amazon->save() #5 /var/www/veterans/system/File/File.php(1180): IPS\_File->copy(4) #6 /var/www/veterans/system/File/FileSystem.php(220): IPS\_File->move(4) #7 /var/www/veterans/applications/downloads/extensions/core/FileStorage/Files.php(56): IPS\File\_FileSystem->move(4) #8 /var/www/veterans/applications/core/extensions/core/Queue/MoveFiles.php(56): IPS\downloads\extensions\core\FileStorage\_Files->move(16, 4, 1) #9 /var/www/veterans/system/Task/Task.php(47): IPS\core\extensions\core\Queue\_MoveFiles->run(Array, 16) #10 /var/www/veterans/applications/core/modules/admin/system/background.php(87): IPS\_Task::runQueue() #11 /var/www/veterans/system/Helpers/MultipleRedirect/MultipleRedirect.php(92): IPS\core\modules\admin\system\_background->IPS\core\modules\admin\system\{closure}(Array) #12 /var/www/veterans/applications/core/modules/admin/system/background.php(136): IPS\Helpers\_MultipleRedirect->__construct(Object(IPS\Http\Url\Internal), Object(Closure), Object(Closure)) #13 /var/www/veterans/system/Dispatcher/Controller.php(90): IPS\core\modules\admin\system\_background->process() #14 /var/www/veterans/applications/core/modules/admin/system/background.php(42): IPS\Dispatcher\_Controller->execute() #15 /var/www/veterans/system/Dispatcher/Dispatcher.php(152): IPS\core\modules\admin\system\_background->execute() #16 /var/www/veterans/admin/index.php(14): IPS\_Dispatcher->run() #17 {main}
Jimi Wikman Posted January 30, 2021 Posted January 30, 2021 Contact support. there is a table that you can clean up, but it is best if you let support check it. also check your data usage on s3 as it can add up a bit if this loop for a while.
Scott Allen Posted February 2, 2021 Author Posted February 2, 2021 Thank you for your reply Do you happen to know the table? Support are essentially refusing to get involved.
CoffeeCake Posted February 3, 2021 Posted February 3, 2021 Look for tasks in the table name, likely core_tasks.
Recommended Posts