Platform:
Bitnami/Ubuntu/64bit/Wordpress 3.4.1
Amazon SMALL Instance
Issue:
Server page requests are spiking CPU to 70%+ levels and hanging on database queries causing new httpd processes to spawn on subsequent requests. The Wordpress installation is fresh and has 1600 'Pages' (not posts) imported into it. The site receives no traffic and is running on a fresh instance directly through an Amazon issued hostname. The latency issues occur only after the Pages are imported.
Eventually, the database crashes and apache begins returning: "Error establishing a database connection"
MYSQL Error Log:
Version: '5.5.21-log' socket: '/opt/bitnami/mysql/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
Killed
120711 22:15:26 mysqld_safe Number of processes running now: 0
120711 22:15:26 mysqld_safe mysqld restarted
120711 22:15:30 [Warning] The syntax '--log-slow-queries' is deprecated and will be removed in a future release. Please use '--slow-query-log'/'--slow-query-log-file' instead.
120711 22:15:30 [Note] Plugin 'FEDERATED' is disabled.
120711 22:15:30 InnoDB: The InnoDB memory heap is disabled
120711 22:15:30 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120711 22:15:30 InnoDB: Compressed tables use zlib 1.2.3
120711 22:15:30 InnoDB: Using Linux native AIO
120711 22:15:31 InnoDB: Initializing buffer pool, size = 256.0M
InnoDB: mmap(274726912 bytes) failed; errno 12
120711 22:15:31 InnoDB: Completed initialization of buffer pool
120711 22:15:31 InnoDB: Fatal error: cannot allocate memory for the buffer pool
120711 22:15:31 [ERROR] Plugin 'InnoDB' init function returned error.
120711 22:15:31 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
120711 22:15:32 [ERROR] Unknown/unsupported storage engine: InnoDB
120711 22:15:32 [ERROR] Aborting
120711 22:15:32 [Note] /opt/bitnami/mysql/bin/mysqld.bin: Shutdown complete
120711 22:15:33 mysqld_safe mysqld from pid file /opt/bitnami/mysql/data/ip-10-12-103-60.pid ended
Apache Error Log:
[Wed Jul 11 22:15:07 2012] [error] server reached MaxClients setting, consider raising the MaxClients setting
Tried:
Raising the number of MaxClients, but didn't matter as it appears database is bottleneck
Launching a fresh instance in AWS; the problem persisted
Thoughts:
I've never seen limitations on number of Pages in Wordpress, this couldn't be the issue could it?
Do we need a larger instance than a SMALL? We've run much larger sites on a SMALL with no issues in the past.
Thanks in advance! Patrick