For site?[ redundant link deleted ]
/home/server/public_html/litepack.ch/wp-content/plugins/updraftplus/backup.phpAlso wanted to ask following error message, do I need this cPstrict on my server?
Would be very glad for a feedback.
Good bless you,Best regards, Jonas
Can’t locate cPstrict.pm in?@inc?(you may need to install the cPstrict module) (@INC contains: /usr/local/cpanel /usr/local/cpanel /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/x86_64-linux /usr/local/cpanel/3rdparty/perl/536/cpanel-lib /usr/local/cpanel/3rdparty/perl/536/lib/x86_64-linux /usr/local/cpanel/3rdparty/perl/536/lib /opt/cpanel/perl5/536/site_lib/x86_64-linux /opt/cpanel/perl5/536/site_lib) at /usr/local/cpanel/Cpanel/Math/Bytes.pm line 8.
BEGIN failed–compilation aborted at /usr/local/cpanel/Cpanel/Math/Bytes.pm line 8.
Compilation failed in require at /usr/local/cpanel/Cpanel/Quota.pm line 18.
BEGIN failed–compilation aborted at /usr/local/cpanel/Cpanel/Quota.pm line 18.
Compilation failed in require at /home/server/public_html/litepack.ch/wp-content/plugins/updraftplus/includes/get-cpanel-quota-usage.pl line 9.
BEGIN failed–compilation aborted at /home/aniasher/public_html/litepack.ch/wp-content/plugins/updraftplus/includes/get-cpanel-quota-usage.pl line 9.
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 18497504 bytes) in /home/server/public_html/litepack.ch/wp-content/plugins/updraftplus/backup.php?on line 2752
[13-Nov-2024 19:17:34 UTC] PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 20480 bytes) in /home/newcast1/public_html/consultantquotes/wp-includes/functions.php on line 650
[13-Nov-2024 19:17:34 UTC] PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 20480 bytes) in /home/newcast1/public_html/consultantquotes/wp-includes/functions.php on line 4264
[13-Nov-2024 19:17:34 UTC] PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 20480 bytes) in /home/newcast1/public_html/consultantquotes/wp-content/plugins/awesome-support/vendor/ericmann/sessionz/php/Manager.php on line 88
we are working on a site and we have been getting the out of memory message several times.
[STDERR] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 48558080 bytes) in /home/runcloud/webapps/XXXXX/YYYYY/wp-content/plugins/litespeed-cache/src/object.lib.php on line 736
Any advice?
PHP.ini memory limit was 256M (right now is 512M to solve the problem, but we’d like to return to 256M)
Our report number: DCNGFOCN
Thank You!
]]>Se ha producido un error del tipo E_ERROR en la línea 138 del archivo […]/wp-content/plugins/code-snippets/php/front-end/class-frontend.php. Mensaje de error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 134291136 bytes)
]]>Even in the backend when plugin is enable the related form submissions are not displayed.
This is happened only when your plugin is active
How can we solve it?
I am not using any wp rss aggregator add-ons, including post to feed. Why would some sources go over the memory limit, and why are others taking so long? I have inserted the sources as as shortcodes:
$shortcode = sprintf('[wp-rss-aggregator feeds="%1$s" template="sidebar" limit="5"]', $feed_title);
echo do_shortcode( $shortcode );Any and all guidance or responses are welcome. Thank you.
]]>I tried deactivating All-In-One Security (AIOS), then everything returned to its place instantly. After that, any plugins were being deleted and installed. Then I turned on AIOS again, but a critical error occurred, and my WordPress admin panel stopped working. This was fixed only by renaming the plugin folder through the hosting panel.
The same thing happened with the Rank Math SEO plugin. When it is disabled, All-In-One Security works fine, and other plugins are deleted and installed. But as soon as they start working together, a critical error occurs.
This error is present even when absolutely all AIOS settings are disabled, and absolutely all Rank Math SEO settings are disabled.
I am using:
In the logs, I found such a critical memory exhaustion error:
[08-Apr-2023 16:01:16 UTC] PHP Fatal error:
Allowed memory size of 67108864 bytes exhausted
(tried to allocate 32768 bytes)
in /public_html/wp-content/plugins/
seo-by-rank-math/vendor/woocommerce/
action-scheduler/classes/abstracts/
ActionScheduler_Lock.php on line 1Yes, I know that this can be fixed by increasing the memory through adding this line to wp-config.php file:
define( 'WP_MEMORY_LIMIT', '128M' );But unfortunately, my hosting provider does not provide more PHP memory on the current plan. And I would like to fix this in another way.
I see that this error is caused by the WooCommerce Rank Math module, but I am not using WooCommerce. Is there any way to disable this script that causes this critical memory exhaustion error?
Thank you
]]>I updated my site to WordPress 6.2 today and received a critical error. I have followed some guides online to troubleshoot this, but nothing I have tried has worked so far. Here’s a list of what I’ve done with some other relevant info:
I haven’t received an email with more info (pretty sure admin email is set correctly so this may be an unrelated problem), and I enabled debug mode by adding some lines to wp-config but couldn’t see a debug file.
Thanks in advance for any assistance!
]]>A simple “heartbeat” when the time comes can cause the error (no matter if the memory limit is 128,256,512), but obviously any other page load will do the same.
I managed to track the queries in that specific moment and i saw some “not-so-optimized” query IMHO, i’m focusing on these two that happen one right after the other:
SELECT wp_users.ID FROM wp_users WHERE 1=1 ORDER BY user_login ASC
SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE user_id IN ( $WTF ) ORDER BY umeta_id ASC
(with $WTF being the explicit list of all 14000+ users ids minus 1 – i guess the current one)
I think that comes from wp-includes/pluggable.php and the function
/**
* Retrieves info for user lists to prevent multiple queries by get_userdata().
*
* @since 3.0.0
*
* @global wpdb $wpdb WordPress database abstraction object.
*
* @param int[] $user_ids User ID numbers list
*/
function cache_users( $user_ids ) {
global $wpdb;
update_meta_cache( 'user', $user_ids );
$clean = _get_non_cached_ids( $user_ids, 'users' );
if ( empty( $clean ) ) {
return;
}
$list = implode( ',', $clean );
$users = $wpdb->get_results( "SELECT * FROM $wpdb->users WHERE ID IN ($list)" );
foreach ( $users as $user ) {
update_user_caches( $user );
}
}or the included update_meta_cache() function from meta.php
My db takes some seconds (like 5) to answer the latter query, but i’m pretty sure the php memory while looping over the results to cache the users, is going to be pretty frustrated and in fact the reason of my recurrent memory exhaustion.
I did some research and WP 6.0.0 (i’m on 6.1.1) promised to increase performances for large user amount’s sites:
But i think there’s still something to do..
Do someone have any advice on how speeding up or lighten this user cache updating process for large users sites?
]]>Recently we started having a problem whereby Shop Managers would get errors such as:
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 598016 bytes) in /homepages/**/*******/htdocs/public_html/wp-includes/functions.php on line 5275 or “buffer” errors (don’t remember the exact message) when they clicked on an order in the order list to look at order details. This only occurred when their site interface language was French. What is odd is that this is only on the backend (where nothing is translated with Transposh) and the site’s main language is French. If the user changed their site interface to English the problem did not occur. Administrators don’t have the problem (regardless of the language of their interface).
I submitted a support forum post to the WooCommerce plugin support. They asked if I had a translation plugin on the site. I said, “yes, Transposh”. They asked me to deactivate it and I did and the problem went away.
So now I’m asking you what could I do to confirm whether the problem is Transposh and especially what I could do to avoid any WooCommerce/Transposh conflicts in the WordPress admin?
Many thanks for your help!
]]>