Skip Navigation

Home › Support › English Support › [Closed] Fatal Error: WPML consuming a lot of memory

[Closed] Fatal Error: WPML consuming a lot of memory

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 7:00 – 15:00 7:00 – 15:00 7:00 – 15:00 7:00 – 15:00 7:00 – 15:00 -
- - - - - - -

Supporter timezone: Pacific/Easter (GMT-05:00)

Tagged: 

This topic contains 62 replies, has 3 voices.

Last updated by Ilyes 4 months, 1 week ago.

Assisted by: Ilyes.

Author Posts
June 18, 2024 at 10:52 am #15748549

arildB

Hi
Just checking if you are finish with the migration to Cloudways?

Cheers
Arild
June 18, 2024 at 12:20 pm #15748910

Ilyes
Supporter

Languages: English (English ) French (Français )

Timezone: Pacific/Easter (GMT-05:00)

Hello,

Unfortunately, there is a fatal error and I don't have access to CW to fix it myself, I'm waiting for our team to check if they can disable this plugin : 

Fatal error: Uncaught Uncanny_Automator\Automator_Error: Too few arguments to function Uncanny_Automator\BDB_Universal_Token::__construct(), 0 passed in /mnt/BLOCKSTORAGE/home/214261.cloudwaysapps.com/hbvenppkkb/public_html/wp-content/plugins/uncanny-automator/src/core/classes/class-set-up-automator.php on line 388 and exactly 2 expected in /mnt/BLOCKSTORAGE/home/214261.cloudwaysapps.com/hbvenppkkb/public_html/wp-content/plugins/uncanny-automator/src/core/classes/class-initialize-automator.php:141

However, I had this conversation with our 2nd tier and this is what they suggested :

Redis connection error should not happen if you just added the non-persistent group cache code, and it could indicate other issues.
The error that you initially pasted, may indicate a possible loop happening somewhere as it is not normal to exhaust 4294967296 bytes.
I suggest testing in minimal first and activating one by one the extensions of the user.

Perhaps a good idea is to disable WPFUsion logs and depend on the built-in WordPress error logging instead, as that plugin and the logging capabilities may be the sole reason for the issue.

I will keep you updated if I have more updates on this,

June 18, 2024 at 12:45 pm #15749080

arildB

Hi again
I have disabled Uncanny Automator now.

Cheers
Arild
June 18, 2024 at 12:47 pm #15749085

arildB

I have also disabled the Wpfusion logs
June 18, 2024 at 1:16 pm #15749277

Ilyes
Supporter

Languages: English (English ) French (Français )

Timezone: Pacific/Easter (GMT-05:00)

Thanks, I will run another migration soon,

June 18, 2024 at 4:48 pm #15750299

arildB

Will you please send me a msg when the migration is finished?

Cheers
Arild

June 18, 2024 at 5:18 pm #15750457

Ilyes
Supporter

Languages: English (English ) French (Français )

Timezone: Pacific/Easter (GMT-05:00)

Please give us a couple more minutes as the migration have just started,

June 18, 2024 at 6:30 pm #15750617

Ilyes
Supporter

Languages: English (English ) French (Français )

Timezone: Pacific/Easter (GMT-05:00)

Migration completed, I will get back to you.
June 19, 2024 at 4:24 pm #15757391

Ilyes
Supporter

Languages: English (English ) French (Français )

Timezone: Pacific/Easter (GMT-05:00)

Hello again,

We need to test the following configuration on your site, however, please take a backup of your site and database and test this on time that doesn't have much traffic in case of errors :

1- Enable debug log :

To enable WP debug log, open your wp-config.php file and look for:

define('WP_DEBUG', false);

And change it to:

define('WP_DEBUG', true);

// Enable Debug logging to the /wp-content/debug.log file

define('WP_DEBUG_LOG', true);

// Disable display of errors and warnings which is recommended on a live site.

define('WP_DEBUG_DISPLAY', false);

@ini_set('display_errors',0);

2- Disable WPFUsion logs

3- Replace the current Redis configuration udner WP-config

Look for this code : 

define( 'WP_REDIS_CONFIG', [
   'token' => "e279430effe043b8c17d3f3c751c4c0846bc70c97f0eaaea766b4079001c",
   'host' => '127.0.0.1',
   'port' => 6379,
   'database' => 5513, 
   'timeout' => 2.5,
   'read_timeout' => 2.5,
   'split_alloptions' => true,
   'async_flush' => true,
   'client' => 'phpredis', 
   'compression' => 'zstd', 
   'serializer' => 'igbinary', 
   'prefetch' => true, 
   'debug' => false,
   'save_commands' => false,
   'prefix' => DB_NAME,  
   ] );

And replace it with :

define('WP_REDIS_CONFIG', [
    'token' => 'e279430effe043b8c17d3f3c751c4c0846bc70c97f0eaaea766b4079001c',
    'host' => '127.0.0.1',
    'port' => 6379,
    'database' => 5513,
    'timeout' => 2.5,
    'read_timeout' => 2.5,
    'split_alloptions' => true,
    'async_flush' => true,
    'client' => 'phpredis',
    'compression' => 'zstd',
    'serializer' => 'igbinary',
    'prefetch' => true,
    'debug' => false,
    'save_commands' => false,
    'prefix' => DB_NAME,
    'non_persistent_groups' => [
        'counts',
        'plugins',
        'themes',
        'bp_pages',
    ],
]);

4- Monitor if any errors are recorded under WP-content > Debug log related to Redis or Memory exhaust

Looking forward to the results,

June 20, 2024 at 9:41 am #15762541

arildB

Hi again
The Redis settings in our wp-config looks slightly different:

define( 'WP_REDIS_CONFIG', [
'token' => '79fb1487477c0a555d76e3249e1a1d2b975715293174f50afb456171301f',
'host' => 'https://cdn.wpml.org/var/run/redis/redis.sock',
'port' => 0,
'database' => 0,
'prefix' => 'db0:',
'client' => 'relay',
'timeout' => 0.5,
'read_timeout' => 0.5,
'retry_interval' => 10,
'retries' => 3,
'backoff' => 'smart',
'compression' => 'zstd',
'serializer' => 'igbinary',
'async_flush' => true,
'split_alloptions' => true,
'prefetch' => false,
'shared' => true,
'debug' => false,
] );
define( 'WP_REDIS_DISABLED', getenv('WP_REDIS_DISABLED') ?: false );

Not sure if that makes any difference?

June 20, 2024 at 8:14 pm #15766907

Ilyes
Supporter

Languages: English (English ) French (Français )

Timezone: Pacific/Easter (GMT-05:00)

Hello,

Yes it does make a difference, good catch, in that case this is your code : 

define( 'WP_REDIS_CONFIG', [
'token' => '79fb1487477c0a555d76e3249e1a1d2b975715293174f50afb456171301f',
'host' => 'https://cdn.wpml.org/var/run/redis/redis.sock',
'port' => 0,
'database' => 0,
'prefix' => 'db0:',
'client' => 'relay',
'timeout' => 0.5,
'read_timeout' => 0.5,
'retry_interval' => 10,
'retries' => 3,
'backoff' => 'smart',
'compression' => 'zstd',
'serializer' => 'igbinary',
'async_flush' => true,
'split_alloptions' => true,
'prefetch' => false,
'shared' => true,
'debug' => false,
] );
define( 'WP_REDIS_DISABLED', getenv('WP_REDIS_DISABLED') ?: false );

Then change it to : 

define( 'WP_REDIS_CONFIG', [
'token' => '79fb1487477c0a555d76e3249e1a1d2b975715293174f50afb456171301f',
'host' => 'https://cdn.wpml.org/var/run/redis/redis.sock',
'port' => 0,
'database' => 0,
'prefix' => 'db0:',
'client' => 'relay',
'timeout' => 0.5,
'read_timeout' => 0.5,
'retry_interval' => 10,
'retries' => 3,
'backoff' => 'smart',
'compression' => 'zstd',
'serializer' => 'igbinary',
'async_flush' => true,
'split_alloptions' => true,
'prefetch' => false,
'shared' => true,
'debug' => false,
'non_persistent_groups' => [
        'counts',
        'plugins',
        'themes',
        'bp_pages',
    ],
] );

define( 'WP_REDIS_DISABLED', getenv('WP_REDIS_DISABLED') ?: false );

Best,
June 21, 2024 at 10:18 am #15773855

arildB

Hi again
Have tested, and it broke the server. Have replaced it with the old settings, and it now working again
June 21, 2024 at 2:38 pm #15776216

Ilyes
Supporter

Languages: English (English ) French (Français )

Timezone: Pacific/Easter (GMT-05:00)

Hello again,

Is it possible to ask Redis team on how to add the proper code to ignore those non-persistant groups?

We need to add this snippet to your redis configuration : 

'non_persistent_groups' => [
        'counts',
        'plugins',
        'themes',
        'bp_pages',
    ],

But it keeps disconnecting the Redis connection and no errors are logged in debuglog, they should have a better idea on how to implement this correctly,

I have also notified our 2nd tier about this,

July 2, 2024 at 9:47 am #15873987

arildB

Hi again Ilyes
Your group exclusion seemed a bit heavy-handed, so we added some more. Please see the attached photo.
As expected the server has been stable since this was done on Friday. So I guess the next step is to figure out what group(s) are creating the error.

436592344_1594880694578074_8026809194671761396_n.png
July 2, 2024 at 12:52 pm #15875368

arildB

Hi again
Another interesting observation. When the site goes down, it does not go down completely. It's only the main domain (pulskuren.no) that stops working. The translated language (thepulsecure.com) is still working.
Hope that information helps.

Cheers
Arild

The topic ‘[Closed] Fatal Error: WPML consuming a lot of memory’ is closed to new replies.