MySQL. ERROR! The server quit without updating PID file (/usr/local/mysql/var/VM
重启的时候报错lnmp restart
+-------------------------------------------+
| Manager for LNMP, Written by Licess |
+-------------------------------------------+
| http://lnmp.org |
+-------------------------------------------+
Stoping LNMP...
Stoping nginx...done
Shutting down MySQL.. SUCCESS!
Gracefully shutting down php-fpm . done
Starting LNMP...
Starting nginx...done
Starting MySQL. ERROR! The server quit without updating PID file (/usr/local/mysql/var/VM_100_217_centos.pid).
Starting php-fpmdone
因为我本机没有用Mysql，我可以不要Mysql吗？
然后只需要启动其他的，怎么启动呢？
/usr/local/nginx/sbin/nginx -s reload
/etc/init.d/php-fpm restart
=========================================================
错误信息/usr/local/mysql/var/主机名.err 的日志：
160323 21:56:44 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
160323 21:56:44 InnoDB: The InnoDB memory heap is disabled
160323 21:56:44 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160323 21:56:44 InnoDB: Compressed tables use zlib 1.2.3
160323 21:56:44 InnoDB: Initializing buffer pool, size = 16.0M
160323 21:56:44 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file /usr/local/mysql/var/ibdata1 did not exist:
InnoDB: a new database to be created!
160323 21:56:44InnoDB: Setting file /usr/local/mysql/var/ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
160323 21:56:44InnoDB: Log file /usr/local/mysql/var/ib_logfile0 did not exist: new to be created
InnoDB: Setting log file /usr/local/mysql/var/ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
160323 21:56:44InnoDB: Log file /usr/local/mysql/var/ib_logfile1 did not exist: new to be created
InnoDB: Setting log file /usr/local/mysql/var/ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
160323 21:56:44InnoDB: Waiting for the background threads to start
160323 21:56:45 InnoDB: 5.5.42 started; log sequence number 0
160323 21:56:45 Server hostname (bind-address): '0.0.0.0'; port: 3306
160323 21:56:45 - '0.0.0.0' resolves to '0.0.0.0';
160323 21:56:45 Server socket created on IP: '0.0.0.0'.
160323 21:56:45 Event Scheduler: Loaded 0 events
160323 21:56:45 /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.42-log'socket: '/tmp/mysql.sock'port: 3306Source distribution
160323 21:56:45 /usr/local/mysql/bin/mysqld: Normal shutdown
160323 21:56:45 Event Scheduler: Purging the queue. 0 events
160323 21:56:45InnoDB: Starting shutdown...
160323 21:56:47InnoDB: Shutdown completed; log sequence number 1595675
160323 21:56:47 /usr/local/mysql/bin/mysqld: Shutdown complete
160323 21:56:47 mysqld_safe mysqld from pid file /usr/local/mysql/var/VM_100_217_centos.pid ended
160323 21:56:48 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
160323 21:56:48 InnoDB: The InnoDB memory heap is disabled
160323 21:56:48 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160323 21:56:48 InnoDB: Compressed tables use zlib 1.2.3
160323 21:56:48 InnoDB: Initializing buffer pool, size = 16.0M
160323 21:56:48 InnoDB: Completed initialization of buffer pool
160323 21:56:48 InnoDB: highest supported file format is Barracuda.
160323 21:56:48InnoDB: Waiting for the background threads to start
160323 21:56:49 InnoDB: 5.5.42 started; log sequence number 1595675
160323 21:56:49 Server hostname (bind-address): '0.0.0.0'; port: 3306
160323 21:56:49 - '0.0.0.0' resolves to '0.0.0.0';
160323 21:56:49 Server socket created on IP: '0.0.0.0'.
160323 21:56:49 Event Scheduler: Loaded 0 events
160323 21:56:49 /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.42-log'socket: '/tmp/mysql.sock'port: 3306Source distribution
160323 21:56:49 /usr/local/mysql/bin/mysqld: Normal shutdown
160323 21:56:49 Event Scheduler: Purging the queue. 0 events
160323 21:56:50InnoDB: Starting shutdown...
"VM_100_217_centos.err" 348L, 22536C
[ 本帖最后由 gyrate360 于 2016-3-26 07:07 编辑 ] InnoDB: Database physically writes the file full: wait...
里面有当前磁盘或分区已满的提示，检查一下硬盘空间或当前分区 原帖由 licess 于 2016-3-26 10:20 发表 https://bbs.vpser.net/images/common/back.gif
InnoDB: Database physically writes the file full: wait...
里面有当前磁盘或分区已满的提示，检查一下硬盘空间或当前分区
我现在本机数据库是没有使用的，所以我想把MySQL卸载了或者启动lnmp的时候不要MySQL，怎么启动呢？
我现在每天早上起来lnmp都崩溃了
[ 本帖最后由 gyrate360 于 2016-3-27 11:43 编辑 ] centos：
chkconfig mysql off
chkconfig --del mysql
debian、Ubuntu：
update-rc.d -f mysql remove
这样就不开机启动了，lnmp脚本的话还需要修改，去掉/bin/lnmp 末尾mysql)判断的几行就行了
回复 4# 的帖子
好的，谢谢，我发现每天都要手动重启电脑下，就好了，不知道是什么问题。预防怕以后会迁移数据库到本机来，我想知道下类似这种启动：
/usr/local/nginx/sbin/nginx -s reload
/etc/init.d/php-fpm restart
#/etc/init.d/mysql restart
还有什么我就不清楚了
不带Mysql启动就行了。
[ 本帖最后由 gyrate360 于 2016-3-28 08:00 编辑 ]
回复 4# 的帖子
然后我查找日志 Too many open files in system，找到这个帖子后，没有重启电脑就可以了，虽然问题解决了，但不知道是什么原因Error 'su: /Bin/Bash: Too Many Open Files In System' When Switching to Non-root User on Enterprise Linux
Applies to:
Linux OS - Version: 4.4 and later
Linux x86-64
Symptoms
You get the following error when switching to non-root user by 'su':
su: /bin/bash: Too many open files in system
Cause
System-wide resource threshold file-max exceeded.
Solution
Increase the file-max value, e.g.
#echo "6553600" > /proc/sys/fs/file-max
You can add the following line in /etc/sysctl.conf to keep the setting cross reboot:
fs.file-max=6553600
[@more@]
[ 本帖最后由 gyrate360 于 2016-3-28 08:19 编辑 ]
页:
[1]