1, error:invalid PHP executable specified by test_php_executable =/usr/local/src/php-5.3.18/sapi/cli/phpThe situation arises:Make PHP errors in the processwrong meaning: It's okay to turn off safe mode.The Safe Mode test is a curse. The latest version of PHP
installationThere is no safe module in the package.Workaround: This error can be ignored by direct make install OK.
2, Nginx: [Emerg] Getpwnam ("www") failedWhat happens: Just after the nginx is loaded, run the test file. Error meaning: Access to www user failed. Solution: In the nginx.conf "#user nobody;" The previous # comment is removed and changed to "user www www;"
3, Nginx: [ERROR] Open () "/usr/local/nginx/logs/nginx.pid" failed (2:no such file or directory)What happens: Restart the times when you have just
installed nginx. wrong meaning:In/usr/local/nginx/logsThere is no nginx.pid in the directoryWorkaround: run this sentence and solve the
problem "/usr/local/nginx/sbin/nginx-c/usr/local/nginx/conf/nginx.conf "The meaning of this sentence for nginx specifies the configuration file path.
/usr/local/nginx/sbin/nginx-t Test nginx configuration file is correct
4, Nginx: [warn] Conflicting server name "" On 0.0.0.0:80, ignoredThe situation arises:after configuring the Nginx configuration file, this error occurs when the reload is completed. Wrong meaning: Nginx'sThere is a domain name conflict in the configuration fileWorkaround: Check whether the configuration file has conflicting domain names, if any, delete and reload. Linux with the use of the Linux grep "blogguy.cn" search, generally because the changes are not paid attention to cause. Search to have the same repetition, remove the duplicate domain name configuration is possible.
5.nginx: [Alert] Kill (34719, 1) failed (3:no such process)What happens: After restarting the Linux system, run "/usr/local/nginx/sbin/nginx-s Reload" to report this errorerror Meaning: The Nginx kill process 34719 failed when booting, because there is no this process. Workaround:[Root@mylinux~]#/usr/local/nginx/sbin/nginx-c/usr/local/nginx/conf/nginx.conf[root@mylinux~]#/usr/local/nginx/sbin/nginx-s Reload Specify the Nginx configuration file and restart it.
6, [root@mylinux logs]#/usr/local/php/sbin/php-fpm-t[23-jun-2013 21:00:29] error:failed to open configuration file '/usr/local/php/etc/php-fpm.conf ': No such file or directory (2) [23-jun-2013 21:0 0:29] error:failed to load configuration file '/usr/local/php/etc/php-fpm.conf ' [23-jun-2013 21:00:29] error:fpm Initial Ization failedWhat's happening : Run "
/usr/local/php/sbin/php-fpm-t"occurs when you test the PHP-FPM configuration file. wrong meaning: not found php-fpm.conf file (php-fpm configuration file) Workaround: [email protected] init.d]# cd/usr/local/php/etc [Root@mylinux etc]# cp php-fpm.conf.default php-fpm.conf[Root@mylinux etc]#/usr/local/php/sbin/php-fpm-t[23-jun-2013 21:04:00] notice:configuration file/usr/local/php/etc/php-fpm.conf test is successful
7. [Root@mylinux init.d]#/etc/init.d/php-fpm start or service php-fpm startStarting PHP-FPM [23-jun-2013 21:16:01] error:failed to open configuration file '/usr/local/php/etc/php-fpm.conf ': No suc h file or directory (2) [23-jun-2013 21:16:01] error:failed to load configuration file '/usr/local/php/etc/php-fpm.conf ' [2 3-jun-2013 21:16:01] ERROR:FPM initialization failed failedWhat happens: When you start php-fpm, the problem and problem 6, is the same problem. wrong meaning: I can't find them .php-fpm.conf file (php-fpm configuration file)Workaround: [Root@mylinux init.d]# cd/usr/local/php/etc[Root@mylinux etc]# cp php-fpm.conf.default php-fpm.conf[Root@mylinux etc]# service php-fpm startstarting php-fpm done
8. Starting MySQL. error! The server quit without updating PID file (/usr/local/mysql/data/mylinux.pid).What's happening : Run "
service mysqld Start "or"/etc/init.d/mysqld start "When you start the mysqld daemonError: Failed to restart MySQL because it could not be found Workaround:From the error point of view, can not see the specific problem, only to see the log[Root@mylinux /]# cd/usr/local/mysql/data[Root@mylinux data]# tail-f-N mylinux.err
130623 16:34:53 Mysqld_safe starting mysqld daemon with databases From/usr/local/mysql/data130623 16:34:53 [Note] Plugin ' federated ' is disabled. 130623 16:34:53 innodb:the InnoDB memory heap is disabled 130623 16:34:53 innodb:mutexes and rw_locks use GCC atomic builtins130623 16:34:53 innodb:compressed tables use zlib 1.2.3 130623 16:34:53 innodb:initializing buffer pool, size = 128.0M130623 16:34:53 innodb:completed initialization of buffer poolinnodb:unable to lock./ibdata1, Error:11 Innodb:check that already has another mysqld processinnodb:using the same InnoDB data or log files. innodb:unable to lock./ibdata1, Error:11 Innodb:check that already has another mysqld processinnodb:using the same InnoDB data or log files. innodb:unable to lock./ibdata1, Error:11 Innodb:check that already has another mysqld processinnodb:using the same InnoDB data or log files. innodb:unable to lock./ibdata1, Error:11 Innodb:check that already has another mysqld processinnodb:using the same InnoDB data or log files. innodb:unable to lock./ibdata1, Error:11 Innodb:check that already has another mysqld processinnodb:using the same InnoDB data or log files. innodb:unable to lock./ibdata1, Error:11 Innodb:check that already has another mysqld processinnodb:using the same InnoDB data or log files. innodb:unable to lock./ibdata1, Error:11 Innodb:check that already has another mysqld processinnodb:using the same InnoDB data or log files. innodb:unable to lock./ibdata1, Error:11 Innodb:check that already has another mysqld processinnodb:using the same InnoDB data or log files. innodb:unable to lock./ibdata1, Error:11 Innodb:check that already has another mysqld processinnodb:using the same InnoDB data or log files. innodb:unable to lock./ibdata1, Error:11 Innodb:check that already has another mysqld processinnodb:using the same InnoDB data or log files. innodb:unable to lock./ibdata1, Error:11 Innodb:check that already has another mysqld processinnodb:using the same InnoDB data or log files. innodb:unable to lock./ibdata1, Error:11 Innodb:check that already has another mysqld processinnodb:using the same InnoDB data or log files. 130623 16:36:33 innodb:unable to open the first data file Innodb:error in opening./ibdata1 130623 16:36:33 innodb:operating system error number one in a file operation.innodb:error number one means ' Resource temporarily unavailable '.innodb:some Operating system error numbers is described at innodb:http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html130623 16:36:33 innodb:could not open or create data files. 130623 16:36:33 Innodb:if You tried to add new data files, and it failed here,130623 16:36:33 innodb:you should now edit Innodb_data_file_path in my.cnf back130623 16:36:33 innodb:to What it is, and remove the new ibdata files InnoDB created130623 16:36:33 innodb:in this failed attempt. InnoDB only wrote those files full of130623 16:36:33 Innodb:zeros, but does not yet use them in any the. but being careful:do not130623 16:36:33 innodb:remove old data files which contain your precious data!130623 16:36:33 [ERROR] Plugin ' InnoDB ' init function returned ERROR.130623 16:36:33 [ERROR] Plugin ' InnoDB ' registration as a STORAGE ENGINE failed.130623 16:36:33 [ERROR] unknown/unsupported storage Engine:innodb130623 16:36:33 [ERROR] aborting 130623 16:36:33 [Note]/usr/local/mysql/bin/mysqld:shutdown complete130623 16:36:33 mysqld_safe mysqld from PID File/usr/local/mysql/data/mylinux.pid ended
The
situation arises:View the above log is clearly a sentence
Innodb:check that already has another mysqld processindicates that there are already mysqld processes running, so starting MySQL failed.
Workaround: [Root@mylinux etc]#Ps-ef|grep mysqld[Root@mylinux etc]#kill-9 Process Number[Root@mylinux etc]#Service mysqld Start This is the specific error that started the MySQL report. I restarted the CentOS server and restarted the mysqld, and the problem solved itself, probably because of the LVM Disk Management software.
Google, there are many possible reasons for this problem, the best way is to look at the following error log:
1. may be/usr/local/mysql/data/rekfan.pid file does not have permission to write
WORKAROUND: Give permission to execute "chown -R mysql:mysql /var/ Data " " Chmod-r 755/usr/local/mysql/data "and then restart the mysqld!
2. The MySQL process may already exist in the process
WORKAROUND: Use the command "Ps-ef|grep mysqld" to see if there is a mysqld process, kill with "kill-9 process number" and then restart mysqld!
3. It may be the second time that MySQL is installed on the machine, with residual data affecting the start of the service.
workaround: Go to MySQL data directory/data See, if there is mysql-bin.index, quickly delete it, it is the culprit. I am using the third method to solve! http://blog.rekfan.com/?p=186
4.mysql The/ETC/MY.CNF profile is used when the configuration file is not specified at startup, please open this file to see if there is a specified data directory (DATADIR) under the [Mysqld] section.
WORKAROUND: Please set this line under [mysqld]: DataDir =/usr/local/mysql/data
5.skip-federated Field Issues
Workaround: Check the/etc/my.cnf file for any skip-federated fields that have not been commented out, and if so, comment them out immediately.
6. Error log directory does not exist
Workaround: Use "Chown" "chmod" command to give MySQL owner and permissions
7.selinux, if it is a CentOS system, the default is to turn on SELinux
Workaround: Turn it off, open the/etc/selinux/config, change the selinux=enforcing to selinux=disabled, and then save the restart machine and try again.
8.mysql of data directory mounted disk space is exhausted
Workaround: df-h View disk usage, Sure enough the disk is full, because the partition using the system default, do not know why not automatic expansion then clean up the excess data and study it later. Start MySQL and start successfully!
LNMP Installation FAQ Collection
