军总，越来越频繁了，隔十个小时左右就502，lnmpa
日志在哪看，需要帖哪个目录哪个文件的日志上来？ lnmpa的502肯定是apache挂了你看看/usr/local/apache/logs/error_log 里是否有相关的信息
回复 2# 的帖子
这是什么问题呢 zend_mm_heap corrupted 貌似是个bug在php 5.4.35之后的版本中是修复了的
下面还有个提示，让你增加MaxClients的值
你的是vps什么配置的？ PHP版本（php_version）： 5.2.17p1
要怎么升呢？
内存1.5G MaxClients在哪设置呢，军哥的建议是设置多少 http://lnmp.org/faq/upgrade.html
回复 7# 的帖子
现在的是 5.2.17p1不知道可以升级到哪个版本，http://php.net/downloads.php
好像也没说哪些可以直接升吧
回复 8# 的帖子
看之前#4给你的回复回复 9# 的帖子
一直卡到这里了，郁闷死 为何升级成功了，探针显示的还是，也重启过了PHP版本（php_version）：5.2.17p1./upgrade_php.sh
完了，我是lnmpa的，输成了lnmp的命令了 root@debian:~# /etc/init.d/mysql start
Starting MySQL
.Manager of pid-file quit without updating file. ... failed!
启动不了MYSQL了 150420 22:47:07 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
150420 22:47:09 '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
150420 22:47:11InnoDB: Initializing buffer pool, size = 8.0M
150420 22:47:11InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
150420 22:47:11InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
150420 22:47:11InnoDB: Error: Write to file ./ibdata1 failed at offset 0 0.
InnoDB: 1048576 bytes should have been written, only -1 were written.
InnoDB: Operating system error number 28.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: Error number 28 means 'No space left on device'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html
InnoDB: Error in creating ./ibdata1: probably out of disk space
InnoDB: Could not open or create data files.
InnoDB: If you tried to add new data files, and it failed here,
InnoDB: you should now edit innodb_data_file_path in my.cnf back
InnoDB: to what it was, and remove the new ibdata files InnoDB created
InnoDB: in this failed attempt. InnoDB only wrote those files full of
InnoDB: zeros, but did not yet use them in any way. But be careful: do not
InnoDB: remove old data files which contain your precious data!
150420 22:47:11 Plugin 'InnoDB' init function returned error.
150420 22:47:11 Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
14:47:11 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133331 Kbytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x30000
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
150420 22:47:11 mysqld_safe mysqld from pid file /usr/local/mysql/var/debian.pid ended
150420 22:47:54 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
150420 22:47:54 '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
150420 22:47:54InnoDB: Initializing buffer pool, size = 8.0M
150420 22:47:54InnoDB: Completed initialization of buffer pool
InnoDB: Error: auto-extending data file ./ibdata1 is of a different size
InnoDB: 0 pages (rounded down to MB) than specified in the .cnf file:
InnoDB: initial 640 pages, max 0 (relevant if non-zero) pages!
InnoDB: Could not open or create data files.
InnoDB: If you tried to add new data files, and it failed here,
InnoDB: you should now edit innodb_data_file_path in my.cnf back
InnoDB: to what it was, and remove the new ibdata files InnoDB created
InnoDB: in this failed attempt. InnoDB only wrote those files full of
InnoDB: zeros, but did not yet use them in any way. But be careful: do not
InnoDB: remove old data files which contain your precious data!
150420 22:47:54 Plugin '150420 22:47:54 mysqld_safe mysqld from pid file /usr/local/mysql/var/debian.pid ended
页:
[1]