I am Getting Error On WordPress When I Activate w3 Total Cache
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 196608 bytes) in /home/vika8467/public_html/blog/wp-content/plugins/w3-total-cache/lib/W3/ConfigKeys.php on line 1329
How do I fix this?
Related
I am getting the following error java.lang.IllegalArgumentException: Buffering capacity 2097152 exceeded in my local Wikidata installation. It happens when I run the runUpdater.sh
I don't see how I can set the buffer size in the config ?
I created a view to replace the user's page.
I want that when a user visits another user's account, he has a 403 error.
Here is its configuration :
When I go to the account of the current user, it works. But when I go to the account of another user, I have a 500 error in my browser :
HTTP ERROR 500
In the Drupal logs, I have a lot of errors but no details :
In the Apache logs I have the following error :
[Sun Nov 18 13:02:17.467832 2018] [proxy_fcgi:error] [pid 17384:tid 140440486577920] [client 185.228.231.100:63896] AH01071: Got error 'PHP message: PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /var/www/www-domaine-com/web/core/modules/views/src/Plugin/views/display/PathPluginBase.php on line 397\n'
I do not understand why the page does not work. How can I fix this ?
I increased the php memory to 256MB but there is the same error.
If I delete the contextual filter, it works. But you need the context filter for my view.
After I have moved GoDaddy to a different server VPC Wordpress shows
Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 72 bytes) in /home/rm/public_html/wp-includes/pomo/streams.php on line 110
When I try to log in as admin:
Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 78 bytes) in /home/rm/public_html/wp-includes/pomo/mo.php on line 297
What can I do to resolve this issue?
You need to paste this code in wp-config.php file.
define( 'WP_MEMORY_LIMIT', '256M' );
This code tells WordPress to increase the PHP memory limit to 256MB.
I hope this will help you.
How do I handle "Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 49152 bytes) in /home/ezzy0881/public_html/wp-includes/SimplePie/Item.php on line 662"?
You need to increase the amount of memory allocated to WP. In your wp-config.php file, add define( 'WP_MEMORY_LIMIT', '64M' );. wp-config.php should be editable within the admin. Otherwise, get FTP access and you'll find the config file in the root of you site.
I hope you can help me. I can not stand having to keep restarting my ec2 instance on Amazon.
I have two wordpress sites hosted there. My sites have always worked well until two months ago, one of them started having this problem. I tried all ways pack up, and the only solution was to reconfigure.
Now that all was right with the two. The second site started the same problem. I think Amazon is clowning me.
I am using a free micro instance. If anyone knows what the problem is, please help me!
Your issue will be the limited memory that is allocated to the T1 Micro instances in EC2. I'm assuming you are using ANI Linux in this case and if an alternate version of Linux is used then you may have different locations for your log and config files.
Make sure you are the root user.
Have a look at your MySQL logs in the following location:
/var/log/mysqld.log
If you see repeated instances of the following it's pretty certain that the 0.6GB of memory allocated to the micro instance is not cutting it.
150714 22:13:33 InnoDB: Initializing buffer pool, size = 12.0M
InnoDB: mmap(12877824 bytes) failed; errno 12
150714 22:13:33 InnoDB: Completed initialization of buffer pool
150714 22:13:33 InnoDB: Fatal error: cannot allocate memory for the buffer pool
150714 22:13:33 [ERROR] Plugin 'InnoDB' init function returned error.
150714 22:13:33 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
150714 22:13:33 [ERROR] Unknown/unsupported storage engine: InnoDB
150714 22:13:33 [ERROR] Aborting
You will notice in the log excerpt above that my buffer pool size is set to 12MB. This can be configured by adding the line innodb_buffer_pool_size = 12M to your MySQL config file /etc/my.cnf.
A pretty good way to deal with InnoDB chewing up your memory is to create a swap file.
Start by checking the status of your memory:
free -m
You will most probably see that your swap is not doing much:
total used free shared buffers cached
Mem: 592 574 17 0 15 235
-/+ buffers/cache: 323 268
Swap: 0 0 0
To start ensure you are logged in as the root user and run the following command:
dd if=/dev/zero of=/swapfile bs=1M count=1024
Wait for a bit as the command is not verbose but you should see the following response after about 15 seconds when the process is complete:
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 31.505 s, 34.1 MB/s
Next set up the swapspace with:
mkswap /swapfile
Now set up the swap event:
swapon /swapfile
If you get a permissions response you can ignore it or address the swap file by changing the permissions to 600 with the chmod command.
chmod 600 /swapfile
Now add the following line to /etc/fstab to create the swap spaces on server start:
/swapfile swap swap defaults 0 0
Restart your MySQL instance:
service mysqld restart
Finally check to see if your swap file is working correctly with the free -m command.
You should see something like:
total used free shared buffers cached
Mem: 592 575 16 0 16 235
-/+ buffers/cache: 323 269
Swap: 1023 0 1023
Hope this helps.