Very slow working, sleep queries to MySQL

Home Forums Legacy Support Support queries Setup issues Very slow working, sleep queries to MySQL

Viewing 15 posts - 1 through 15 (of 24 total)
  • Author
    Posts
  • #242747
    shynkaryk
    Participant
    Hello! Since yesterday my website works VERY slowly, I have frequent 503 errors. I have tried to deactivate different plugins but it doesn’t help. Support of my hosting told me that promlem is in Sleep queries to MySQL server to the data base.
    | 18328644 | dyskursn_wp449 | localhost | dyskursn_wp449 | Sleep | 2720 | | | 0.000 | | 18330254 | dyskursn_wp449 | localhost | dyskursn_wp449 | Sleep | 2656 | | | 0.000 | | 18399127 | dyskursn_wp449 | localhost | dyskursn_wp449 | Sleep | 44 | | | 0.000 | | 18399265 | dyskursn_wp449 | localhost | dyskursn_wp449 | Sleep | 36 | | | 0.000 | | 18399818 | dyskursn_wp449 | localhost | dyskursn_wp449 | Sleep | 10 | | | 0.000 |

    | 18399846 | dyskursn_wp449 | localhost | dyskursn_wp449 | Sleep | 9 | |

    When they are forcibly terminated, the site immediately loads. Please, help me because my students are angry. In another post, I provide access to the site.
    #242748
    shynkaryk
    Participant
    This reply has been marked as private.
    #242776
    shynkaryk
    Participant
    This reply has been marked as private.
    #242820
    MrVibe
    Keymaster
    Checking site...
    • unable to connect
    trying again.
    #242821
    shynkaryk
    Participant
    Thank You! Yes, the website is opening VERY slowly, up to some minutes...
    #242826
    MrVibe
    Keymaster
    I resolved the slowest query issue https://prnt.sc/r3heh0
    #242834
    shynkaryk
    Participant
    Sorry, but the website still openes during more than a minute, You can see it in statistiscs of the Query Monitor: https://prnt.sc/r3ikpd Our hosting provider told that this is error of the website, not hosting. On Saturday everything was fine with the site, we did not make any changes, just updated Elementor and Vibe Course Module. Please, help with this, this is critical problem for us.
    #242868
    shynkaryk
    Participant
    Errors on the course category page, 78 seconds: https://prnt.sc/r3lrox Errors on home page, 47 seconds: https://prnt.sc/r3ltmo Course status page is opening during 2 minutes: https://prnt.sc/r3lz12 It is terrible! Please, check and resolve these issues!
    #242907
    shynkaryk
    Participant
    I have updated Vibe Custom Types to 3.9.8.2. There are no such errors, but website is still VERY slow. Site Health Status: 2 critical issues The REST API request failed due to an error. Error: [] cURL error 28: Operation timed out after 10000 milliseconds with 0 bytes received The loopback request to your site failed, this means features relying on them are not currently working as expected. Error: [] cURL error 28: Operation timed out after 10001 milliseconds with 0 bytes received
    #242910
    Anshuman Sahu
    Keymaster
    This is purely a server issue. The recent update of vibe customtypes was to fix the issue with the latest version of elementor. Please try to deactivate these plugins : BadgeOs, BadgeOs community addon, Eventon, Mycred, wplms badgeOs addon, wplms mycred addon , and check if it site speed increase plus you can also take a clone of your website and set it on localhost to check the load speed issue is really a theme issue or server issue . OR you can also check it using another theme with buddypress and woocommerce both enabled .
    #242917
    shynkaryk
    Participant
    My hoster replied me that this is not server issue. Hoster told me: We see that a considerable amount of time is spent by your website on receiving information from a server having the IP address 37.252.11.207. Please consult the developers of your site about the purpose of these calls to a third-party server and the possibility of changing the site, to exclude requests to external resources. Plugins BadgeOs, BadgeOs community addon, Eventon, Mycred, wplms badgeOs addon, wplms mycred addon were inactive all the time. You have access to the admin panel and ftp and can check it.
    #242922
    shynkaryk
    Participant
    One more reply of my hoster:

    We can clearly demonstrate that the site opens for a very long time due to calls to the IP address 37.252.11.207 on the 80th port and timeouts for these calls:

    connect(5, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("37.252.11.207")}, 16) = -1 EINPROGRESS (Operation now in progress) clock_gettime(CLOCK_MONOTONIC, {18516188, 959540725}) = 0 clock_gettime(CLOCK_MONOTONIC, {18516188, 959565676}) = 0 clock_gettime(CLOCK_MONOTONIC, {18516188, 959592113}) = 0 clock_gettime(CLOCK_MONOTONIC, {18516188, 959618422}) = 0 poll([{fd=5, events=POLLOUT|POLLWRNORM}], 1, 0) = 0 (Timeout) clock_gettime(CLOCK_MONOTONIC, {18516188, 959676064}) = 0 rt_sigaction(SIGPIPE, {SIG_IGN, [PIPE], SA_RESTORER|SA_RESTART, 0x2ab42210f570}, NULL, 8) = 0 clock_gettime(CLOCK_MONOTONIC, {18516188, 959729467}) = 0 clock_gettime(CLOCK_MONOTONIC, {18516188, 959753972}) = 0 poll([{fd=5, events=POLLOUT}], 1, 200) = 0 (Timeout) clock_gettime(CLOCK_MONOTONIC, {18516189, 160094220}) = 0 clock_gettime(CLOCK_MONOTONIC, {18516189, 160143954}) = 0 rt_sigaction(SIGPIPE, NULL, {SIG_IGN, [PIPE], SA_RESTORER|SA_RESTART, 0x2ab42210f570}, 8) = 0 rt_sigaction(SIGPIPE, {SIG_IGN, [PIPE], SA_RESTORER|SA_RESTART, 0x2ab42210f570}, NULL, 8) = 0 clock_gettime(CLOCK_MONOTONIC, {18516189, 160276941}) = 0 poll([{fd=5, events=POLLOUT|POLLWRNORM}], 1, 0) = 0 (Timeout) clock_gettime(CLOCK_MONOTONIC, {18516189, 160363285}) = 0 rt_sigaction(SIGPIPE, {SIG_IGN, [PIPE], SA_RESTORER|SA_RESTART, 0x2ab42210f570}, NULL, 8) = 0 clock_gettime(CLOCK_MONOTONIC, {18516189, 160455705}) = 0 poll([{fd=5, events=POLLOUT}], 1, 1000) = 0 (Timeout) clock_gettime(CLOCK_MONOTONIC, {18516190, 161473010}) = 0 rt_sigaction(SIGPIPE, NULL, {SIG_IGN, [PIPE], SA_RESTORER|SA_RESTART, 0x2ab42210f570}, 8) = 0 rt_sigaction(SIGPIPE, {SIG_IGN, [PIPE], SA_RESTORER|SA_RESTART, 0x2ab42210f570}, NULL, 8) = 0 clock_gettime(CLOCK_MONOTONIC, {18516190, 161565415}) = 0 poll([{fd=5, events=POLLOUT|POLLWRNORM}], 1, 0) = 0 (Timeout) clock_gettime(CLOCK_MONOTONIC, {18516190, 161619664}) = 0 rt_sigaction(SIGPIPE, {SIG_IGN, [PIPE], SA_RESTORER|SA_RESTART, 0x2ab42210f570}, NULL, 8) = 0 clock_gettime(CLOCK_MONOTONIC, {18516190, 161672217}) = 0 poll([{fd=5, events=POLLOUT}], 1, 1000) = 0 (Timeout) clock_gettime(CLOCK_MONOTONIC, {18516191, 162499348}) = 0 rt_sigaction(SIGPIPE, NULL, {SIG_IGN, [PIPE], SA_RESTORER|SA_RESTART, 0x2ab42210f570}, 8) = 0 rt_sigaction(SIGPIPE, {SIG_IGN, [PIPE], SA_RESTORER|SA_RESTART, 0x2ab42210f570}, NULL, 8) = 0 clock_gettime(CLOCK_MONOTONIC, {18516191, 162634912}) = 0

    poll([{fd=5, events=POLLOUT|POLLWRNORM}], 1, 0) = 0 (Timeout)

    #242982
    shynkaryk
    Participant
    I don't know what happened, but the site is already working fine. Thank you!
    #243017
    shynkaryk
    Participant
    I don't understand: the site was working fine and now there is a problem with page load speed again. Site Health Status: 2 critical issues The REST API request failed due to an error. Error: [] cURL error 28: Operation timed out after 10000 milliseconds with 0 bytes received The loopback request to your site failed, this means features relying on them are not currently working as expected. Error: [] cURL error 28: Operation timed out after 10001 milliseconds with 0 bytes received What could be the reason for this? This problem was gone when I wrote the previous comment...
    #243051
    MrVibe
    Keymaster
    I checked the server config. You're using LightSpeed server with mysql 10.1 both of which are not tested with WPLMS. https://prnt.sc/r4cg3l Did your web host made this change recently ? We're already doing some tests in this regard, so, we need some time to test this configuration. Can you ask your web host to switch to apache from lightspeed and check if this speeds up things ? This is because Lightspeed builts its own cache in runtime and it might need configuration and we're yet to test it.
Viewing 15 posts - 1 through 15 (of 24 total)
  • The topic ‘Very slow working, sleep queries to MySQL’ is closed to new replies.