@realmranshuman
Please add this code in theme => functions.php and run it once, then remove it.
!class_exists('\LiteSpeed\Cloud') || \LiteSpeed\Cloud::save_summary(['disabled_node' => [], 'err_domains' => []]);
Clear cache and try connecting to QC. If this is not working please tell me.
-
This reply was modified 6 months, 4 weeks ago by
litetim.
@litetim I added the code to the functions.php file> loaded a page > Sent Optimization Request > Removed the code from the functions.php > Toolbox > Purge All …..> Waited few minutes > Sent Optimization Request > The problem still exists. Tried multiple combinations of the steps.
The count of the images pulled remained the same. Clean Up Finished Data numbers diminished and disappeared way too quick as shown in the attached video.
https://ibb.co/fYKk2Sw0
@realmranshuman
I see you wrote about logs. Can you share logs about image otpimization PULL action?
@litetim Well, for starters, the Pull Images button is disabled/greyed out. The cron isn’t pulling the images either. On top of that, the credits are getting spent with each “Send Optimization Request”. So, no.. I am not able to share the pull action log, as I am not able to pull the images in any capacity. I can’t even “Destroy all optimization data” because 59099 images have been optimized before using paid credits, and it will go to waste.
But, here’s the log for the “Send Optimization Request”.
Logs
@realmranshuman I will ask colleagues from QC and see what happens.
Until then:
is your quota being used?
I see 10k left, yesterday were 6k+.
-
This reply was modified 6 months, 4 weeks ago by
litetim.
@litetim Yes, the quota is being used. All the images before this problem began, are optimized and their optimized and backup versions exist on the disk.
For some reason, LiteSpeed cache plugin stopped recognizing the last 20-25% images as optimized.. even though the optimized versions of the files exist on the disk.
And now when it sends the request> uses the quota> finds that there is no need to pull the images as the images exist on the disk> doesn’t pull the images > increases the id counter (images pulled counter remains unchanged)> The percentage circle increases (over several hours just a percent.. we have lot of images)
My hypothesis based on what I can read in the logs: it is just building the part of the database that it doesn’t recognize any longer at the expense of QUIC Cloud credits. There are thousands of images that are optimized, and their files exist on the disk, but the litespeed tables/rows all of a sudden lost the data, or aren’t able to recognize the data for those last 20-25% of images.
So how do I fix this? I can’t possibly destroy all the optimization data… there are over 100K images, and it will cost Quic Cloud credits. Not to mention that it will take weeks worth of time.
@litetim any updates for the codeblock that can fix this? Since it can take time on your end, we are letting the cron run at the cost of credits so altleast the images that already have their optimized files on the disk, can get served.
Plugin Support
qtwrk
(@qtwrk)
please try this
go to toolbox -> debug setting -> set debug log to ON , debug level to advance
set log size to 30 M
add litespeed_type=new_req , and notify_img and litespeed_type=imgoptm into Debug Include URI
then go to log view, clean up existing log if any
then go to image optm summary page , click “clean up unfinished data” if you have any
then send request again
wait for 10 minutes
go back to log view again ,copy paste and share the log