Jump to content

upgrade to 1.4.8 Memcached Problems


Recommended Posts

Dear all.

 

Yesterday I updated to the latest version of Prestashop, from a1.4.7

 

At first it seems that everything went well, but after a few hours the CPU of the VPS was very hight with the Apache process consuming 100% of it.

 

In the Apache log it seems that the cause is the script of Memcached:

 

PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/prestashop/classes/MCached.php on line 89

 

PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/prestashop/classes/MCached.php on line 159

 

Well last night i deactivate Memcached and installed APC cache, but when i go to add some products to the Cart, an error occurs :

 

 

 


TECHNICAL ERROR: unable to add the product.

Details:
Error thrown: [object XMLHttpRequest]
Text status: parsererror


 

I searched the forum for this last error, and allways the solution is to install mbstring (that allready have it)

 

So right now i'm not ussing any Cache system.

 

Anyone having this issues with Memcached or ApcCache ?

 

Regards.

 

PD: sorry about my english.

Link to comment
Share on other sites

Hi to all.

 

Here we have strange behavior with memcache.

 

First i start it:

 

 /usr/bin/memcached -vv -m 128 -p 11211 -u nobody -l 127.0.0.1

 

Send some request to Apache, and CPU gets to 100%

 

After few minutes or seconds we can see this error :

 

Failed to write, and not due to blocking: Broken pipe
<33 connection closed.

 

And in /var/log/apache2/error.log we have this:

 

Sun May 20 10:08:58 2012] [error] [client XXXXXXX] PHP Notice: MemcachePool::set(): Server 127.0.0.1 (tcp 11211, udp 0) failed with: Network timeout (0) in /var/www/prestashop/classes/MCached.php on line 60,

 

That is the same problem as here :

 

http://oscarm.org/2008/8/troubleshooting-connection-problems-memcached

 

Mi iptables script allow this type of data travel (iptables -I INPUT -p tcp --dport 11211 -s 127.0.0.1 -j ACCEPT).

 

So i put another iptables rule to do not track this type of traffic :

 

 iptables -t raw -I OUTPUT -s 127.0.0.1 --protocol tcp --sport 11211 -j NOTRACK

 

And another time, the error appears

 


Failed to write, and not due to blocking: Broken pipe
<33 connection closed.


 

And i can see very high traffic statics within iptables rule:

 

 

Chain OUTPUT (policy ACCEPT 80897 packets, 309M bytes)
pkts bytes target prot opt in out source destination
37706 195M NOTRACK tcp -- * * 127.0.0.1 0.0.0.0/0 tcp spt:11211 

 

Is this a kernel related problem ?

 

I'm ussing OVH VPS with custom kernel, was running fine until i updated to 1.4.8

 

Anyone having this same problem ?

 

Regards.

Link to comment
Share on other sites

  • 1 year later...

Yo lo he resuelto cambiando el fichero php.ini en mi instancia Amazon EC2 que he migrado recientemente (ver blog)

 

max_execution_time = 360     
max_input_time = 120         
memory_limit = 128M         

 

Estoy con la versión 1.5.6.0 y al activar memcached he obtenido el error que indica este post.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...