Excessive CPU usage

  • Resolved comunicazion

    (@comunicazion)


    4 years, 1 month ago

    Hello, I observe in my Linux VPS, every day an excessive use of the CPU with this data that I attach. Do you know what it could be?

    It repeats a lot and makes the cpu resources go up, until we kill the process. I change the name of the domain path to XXX. I do not attach the entire trace as it is very long. Thanks

    strace: Process 8324 attached
    sendto(5, “[\0\0\0\3SELECT event_id FROM wp_em_”…, 95, MSG_DONTWAIT, NULL, 0) = 95
    poll([{fd=5, events=POLLIN|POLLERR|POLLHUP}], 1, 86400000) = 1 ([{fd=5, revents=POLLIN}])
    recvfrom(5, “\1\0\0\1\1]\0\0\2\3def\37xxx_aragonmus”…, 32768, MSG_DONTWAIT, NULL, NULL) = 129
    access(“/home/XXX/public_html/wp-content/themes/sahifa/plugins/events-manager/templates/ical.php”, F_OK) = -1 ENOENT (No such file or directory)
    access(“/home/XXX/public_html/wp-content/themes/sahifa/plugins/events-manager/templates/ical.php”, F_OK) = -1 ENOENT (No such file or directory)
    access(“/home/XXX/public_html/wp-includes/theme-compat/plugins/events-manager/templates/ical.php”, F_OK) = -1 ENOENT (No such file or directory)
    access(“/home/XXX/public_html/wp-content/plugins/events-manager/templates/templates/ical.php”, F_OK) = 0
    access(“/home/XXX/public_html/wp-content/plugins/events-manager/templates/templates/ical.php”, R_OK) = 0
    sendto(5, “\277\1\0\0\3\r\nSELECT DISTINCT SQL_CALC_”…, 451, MSG_DONTWAIT, NULL, 0) = 451
    poll([{fd=5, events=POLLIN|POLLERR|POLLHUP}], 1, 86400000) = 1 ([{fd=5, revents=POLLIN}])
    recvfrom(5, “\1\0\0\1\1[\0\0\2\3def\37xxx_aragonmus”…, 32768, MSG_DONTWAIT, NULL, NULL) = 128
    sendto(5, “\24\0\0\0\3SELECT FOUND_ROWS()”, 24, MSG_DONTWAIT, NULL, 0) = 24
    poll([{fd=5, events=POLLIN|POLLERR|POLLHUP}], 1, 86400000) = 1 ([{fd=5, revents=POLLIN}])
    recvfrom(5, “\1\0\0\1\1\”\0\0\2\3def\0\0\0\fFOUND_ROWS()\0\f?”…, 32768, MSG_DONTWAIT, NULL, NULL) = 67
    sendto(5, “[\0\0\0\3SELECT event_id FROM wp_em_”…, 95, MSG_DONTWAIT, NULL, 0) = 95
    poll([{fd=5, events=POLLIN|POLLERR|POLLHUP}], 1, 86400000) = 1 ([{fd=5, revents=POLLIN}])
    recvfrom(5, “\1\0\0\1\1]\0\0\2\3def\37xxx_aragonmus”…, 32768, MSG_DONTWAIT, NULL, NULL) = 129
    access(“/home/XXX/public_html/wp-content/themes/sahifa/plugins/events-manager/templates/ical.php”, F_OK) = -1 ENOENT (No such file or directory)
    access(“/home/XXX/public_html/wp-content/themes/sahifa/plugins/events-manager/templates/ical.php”, F_OK) = -1 ENOENT (No such file or directory)
    access(“/home/XXX/public_html/wp-includes/theme-compat/plugins/events-manager/templates/ical.php”, F_OK) = -1 ENOENT (No such file or directory)
    access(“/home/XXX/public_html/wp-content/plugins/events-manager/templates/templates/ical.php”, F_OK) = 0
    access(“/home/XXX/public_html/wp-content/plugins/events-manager/templates/templates/ical.php”, R_OK) = 0

Viewing 3 replies - 1 through 3 (of 3 total)
  • timrv

    (@timrv)

    Hello,

    Sorry for the very late response regarding this issue. From the report logs that you mentioned, It seems like it’s an EM template from your theme. Does the same logs appear when you try and change the theme?

    If the logs is gone after changing the theme, Then the issue is probably on the customizations made from your theme/template

    Thread Starter comunicazion

    (@comunicazion)

    Hello, we have not tried to change the theme, although if we have managed to correct it, we believe that by removing some of the plugins (we have done many tests). We also now have the problem that, when publishing a post, many times after a short time, the VPS temporarily crashes. As long as nothing is published, the web admits thousands of visitors without problem.

    timrv

    (@timrv)

    Hello,

    I’m glad that you have managed to fix the issue. If perhaps the issue still happens, I would suggest making a Staging Site and try changing the theme and check again for error logs if it would still show.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Excessive CPU usage’ is closed to new replies.