Jump to content

[PROBLEM] Smarty cache causes server RAM 100% usage.


SmartyLo

Recommended Posts

Good day!

This problem started few days ago - sometimes server just goes down. Once it happens at night (so it probably doesnt depends of visitors). My VPS server is pretty good, on dashboard on ISP panel there is no more 5-10% usage of RAM and other. But sometimes it becames up to 100%. 

I cant find the reason. Maybe somebody already faced with such problem.

 

Here's what I found in mysql.log file (the time is the exact time of server ram overflow)

So i decided that reason is smarty cache (but it's disabled, i'm using expressCache module). 

I tried to drop this table (according to ref. link advice), but there is no ps_smarty_cache table in phpmyadmin. 

 

Please, help. 

161215 17:11:29  InnoDB: Error: table 'prestashop/ps_smarty_cache'
InnoDB: in InnoDB data dictionary has tablespace id 815,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name ./prestashop/ps_smarty_cache.ibd and id 3089, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
InnoDB: Starting in background the rollback of uncommitted transactions
161215 17:11:29  InnoDB: Rolling back trx with id 103AC0F, 1 rows to undo
161215 17:11:29  InnoDB: Waiting for the background threads to start

InnoDB: Rolling back of trx id 103AC0F completed
161215 17:11:30  InnoDB: Rollback of non-prepared transactions completed
161215 17:11:30 InnoDB: 5.5.52 started; log sequence number 772964991
161215 17:11:30 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
161215 17:11:30 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
161215 17:11:30 [Note] Server socket created on IP: '127.0.0.1'.
161215 17:11:31 [Note] Event Scheduler: Loaded 0 events
161215 17:11:31 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.52-0+deb7u1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)
Killed
161215 17:50:52 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
161215 17:50:52 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
161215 17:50:52 [Note] /usr/sbin/mysqld (mysqld 5.5.52-0+deb7u1) starting as process 2821 ...
161215 17:50:52 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
161215 17:50:52 [Note] Plugin 'FEDERATED' is disabled.
161215 17:50:52 InnoDB: The InnoDB memory heap is disabled
161215 17:50:52 InnoDB: Mutexes and rw_locks use GCC atomic builtins
161215 17:50:52 InnoDB: Compressed tables use zlib 1.2.7
161215 17:50:52 InnoDB: Using Linux native AIO
161215 17:50:52 InnoDB: Initializing buffer pool, size = 128.0M
161215 17:50:52 InnoDB: Completed initialization of buffer pool
161215 17:50:52 InnoDB: highest supported file format is Barracuda.
Edited by SmartyLo (see edit history)
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...