Requests optimized but not pulled

  • Resolved szmigieldesign

    (@szmigieldesign)


    7 years ago

    Hello,

    it seems that most problems with communication between my sites and LiteSpeed Image Optimization Server were fixed either by my hosting company or by LiteSpeed with last updates.

    All of my sites seem to process the images and pull them ok.

    However, one site, with plenty of images is stalled. When I try to send the request I get an error:

    Failed to push to LiteSpeed server: Previous requests that optimized but not pulled: 8178

    The amount of images optimized is a lot, considering there are total of 480 image groups, so they should be downloaded from LS server.

    What can be done to import all the images? I’m stuck with optimized and waiting: 93 and optimized and pulled: 73.

    I have wp_cron disabled and running via regular cron via curl every 15 minutes for 15 minutes (limited with 1GB RAM).

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 18 total)
  • Plugin Support LiteSpeed Lisa

    (@lclarke)

    Are you still having a problem with this?

    Running wp-cron.php should solve the issue.

    If it’s still not working, please let us know!

    Plugin Support Hai Zheng?

    (@hailite)

    We will also add a new manual cron button to Image Optimization in this week’s release which will help you finish pulling.

    But you may need to check why cron didn’t do the pull task automatically.

    Thread Starter szmigieldesign

    (@szmigieldesign)

    Unfortunately still no luck.

    Failed to push to LiteSpeed server: Previous requests that optimized but not pulled: 8178

    My other sites on the same host work flawlessly and they all have default wp-cron disabled and it’s invoked with crontab every 15 minutes.

    Plugin Support Cold Egg

    (@eric780217)

    Hi szmigieldesign,

    LSCache v1.6.5 just released. This version provide pull button manually from Image optimize function. Could you update and try it?

    Let us know if it works to you.

    Best,
    Eric

    Thread Starter szmigieldesign

    (@szmigieldesign)

    Hello,

    unfortunately still no go. This time:

    ` Failed to push to LiteSpeed server: “Too many errors while fetching image source files for previous request.” ‘

    After I click Send Optimization Request.

    Requesting the pull with the new Pull Images button seems to initiate the pull as the timer increases whenever I click Update Reduction Status but it doesn’t pull anything. Spamming wp_cron.php doesn’t help either. It’s locked on 93 notified and 73 optimized and pulled.

    I’ve submitted the report if it’s helpful:

    Report number: CCGMCXJU
    Report date: 11/30/2017 22:43:47

    Plugin Support Hai Zheng?

    (@hailite)

    Cool. Thanks for the report number. With v1.6.5 it will be easier to track the issue.

    Will update once we figure it out.

    Plugin Support Hai Zheng?

    (@hailite)

    Please try now.

    Also you have some images not pulled yet. Please run cron or manual pull button to fetch them.

    Thread Starter szmigieldesign

    (@szmigieldesign)

    I no longer get an error when trying to push more images to process but it still doesn’t pull them back. I’m stuck with 94 notified and 73 optimized and pulled. Images failed to fetch is still 10.

    Plugin Support Hai Zheng?

    (@hailite)

    Please try redo notification button when you click update status.

    Thread Starter szmigieldesign

    (@szmigieldesign)

    I’ve clicked both – with no effect on pull.

    Right now, clicking “Send Optimization Request” does nothing (no confirmation or error).

    Are you getting any errors on your side? Can I produce some extra debug info? I’m happy to help.

    This is what I see now:
    Image

    Plugin Support Hai Zheng?

    (@hailite)

    When you don’t have enough credit for one image group, it will bypass submitting. We will add an error message to get it more clear in next release.

    I noticed you have a “pull image” button. Can you try it to pull all finished images first? This way you can get the credit back to request again.

    Thread Starter szmigieldesign

    (@szmigieldesign)

    It doesn’t pull the images. I’ve clicked it. There’s a cron job running for 15 minutes every 15 minutes on my server and images won’t pull. Spamming wp-cron.php doesn’t help either.

    Plugin Support Hai Zheng?

    (@hailite)

    Manually clicking that button can bypass cron job but directly call pull action.

    Can you turn on debug and give the snippet of the log when you click that button?

    Thread Starter szmigieldesign

    (@szmigieldesign)

    
12/05/17 16:06:13.732 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] GET HTTP/1.1 /wp-admin/admin.php
12/05/17 16:06:13.732 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] Query String: page=lscache-optimization&type=img_pull&LSCWP_CTRL=media&LSCWP_NONCE=1efb78f7b0
12/05/17 16:06:13.732 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] Cookie _lscache_vary: admin_bar:1;logged-in:1;role:99
12/05/17 16:06:13.819 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] X Cache_control -> private ( logged in user )
12/05/17 16:06:13.819 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] LSCWP_CTRL: media
12/05/17 16:06:13.819 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] LSCWP_CTRL verified: 'media'
12/05/17 16:06:13.819 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] Router parsed type: img_pull
12/05/17 16:06:13.820 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] Media: Manually running Cron pull_optimized_img
12/05/17 16:06:13.870 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] IAPI posting to : https://eu.wp.api.litespeedtech.com/client_pull
12/05/17 16:06:14.257 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] IAPI failed to decode post json: "took too many times"
12/05/17 16:06:14.257 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] Media: Failed to pull optimized img: --- '"took too many times"'
12/05/17 16:06:14.257 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] 301 from https://photography.szmigieldesign.pl/wp-admin/admin.php
12/05/17 16:06:14.258 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] 301 to https://photography.szmigieldesign.pl/wp-admin/admin.php?page=lscache-optimization&type=img_pull
12/05/17 16:06:14.258 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] X Cache_control -> no Cache ( 301 to same url )
12/05/17 16:06:14.258 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] not cacheable before ctrl finalize
12/05/17 16:06:14.258 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] X-LiteSpeed-Cache-Control: no-cache
12/05/17 16:06:14.258 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] Optimizer bypass: Not frontend HTML type
12/05/17 16:06:14.258 [2a02:a317:e141:8600:5dad:816a:3588:6917:26281 1 qaJ] End response
--------------------------------------------------------------------------------

12/05/17 16:06:14.347 [2a02:a317:e141:8600:5dad:816a:3588:6917:20673 1 xrC] GET HTTP/1.1 /wp-admin/admin.php
12/05/17 16:06:14.347 [2a02:a317:e141:8600:5dad:816a:3588:6917:20673 1 xrC] Query String: page=lscache-optimization&type=img_pull
12/05/17 16:06:14.347 [2a02:a317:e141:8600:5dad:816a:3588:6917:20673 1 xrC] Cookie _lscache_vary: admin_bar:1;logged-in:1;role:99
12/05/17 16:06:14.453 [2a02:a317:e141:8600:5dad:816a:3588:6917:20673 1 xrC] X Cache_control -> private ( logged in user )
12/05/17 16:06:14.521 [2a02:a317:e141:8600:5dad:816a:3588:6917:20673 1 xrC] X Cache_control -> no Cache ( Admin page )
12/05/17 16:06:14.623 [2a02:a317:e141:8600:5dad:816a:3588:6917:20673 1 xrC] not cacheable before ctrl finalize
12/05/17 16:06:14.623 [2a02:a317:e141:8600:5dad:816a:3588:6917:20673 1 xrC] X-LiteSpeed-Cache-Control: no-cache
12/05/17 16:06:14.624 [2a02:a317:e141:8600:5dad:816a:3588:6917:20673 1 xrC] Optimizer bypass: Not frontend HTML type
12/05/17 16:06:14.624 [2a02:a317:e141:8600:5dad:816a:3588:6917:20673 1 xrC] End response
--------------------------------------------------------------------------------
    Plugin Support Hai Zheng?

    (@hailite)

    "took too many times" happens because the file is pulled too many times. We increased the limit. Please try to pull again.

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘Requests optimized but not pulled’ is closed to new replies.

Tags