LNMP installation FAQ and lnmp FAQ

LNMP installation FAQ and lnmp FAQ
1. ERROR: invalid PHP executable specified by TEST_PHP_EXECUTABLE =/usr/local/src/php-5.3.18/sapi/cli/phpCause: make php errors mean: Close the security mode is good, it is a fault caused by testing the safe mode. Latest php versionInstallThe safe Module is no longer in the package. Solution: Ignore this error and make install directly.
2. nginx: [emerg] getpwnam ("www") failedCase: when the test file is run after nginx is installed. Error message: An error occurred while obtaining the www user. Solution: In nginx. conf, remove the comment before "# user nobody;" and change it to "user www ;"
3. nginx: [error] open () "/usr/local/nginx/logs/nginx. pid" failed (2: No such file or directory)Appearance: JustInstallAn error is reported after nginx is restarted. No nginx. pid solution in the/usr/local/nginx/logs Directory: Run this statement,ProblemTo solve the problem "/usr/local/nginx/sbin/nginx-c/usr/local/nginx/conf/nginx. conf", specify the configuration file path for nginx./Usr/local/nginx/sbin/nginx-t to test whether the nginx configuration file is correct
4. nginx: [warn] conflicting server name "" on 0.0.0.0: 80, ignoredThis error occurs when you reload the nginx configuration file. Error Description: The nginx configuration file has a Domain Name Conflict. Solution: Check whether the configuration file has a conflicting domain name. If yes, delete it and reload it. In linux, use grep "blogguy.cn" in LINUX to search for it. This is generally caused by not paying attention to the modification. If the same duplicate is found, you can remove the duplicate domain name configuration.
5. nginx: [alert] kill (34719, 1) failed (3: No such process)Cause: After linux is restarted, Run "/usr/local/nginx/sbin/nginx-s reload" to report this error. It means that 34719 of processes killed at nginx startup fails, the reason is that this process does not exist. Solution: [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:00:29] ERROR: failed to load configuration file '/usr/local/php/etc/php-fpm.conf' [23-Jun-2013 21:00:29] ERROR: FPM initialization failed: Run"/Usr/local/php/sbin/php-fpm-t"It appears when testing the configuration file of php-fpm. Solution: [root @ mylinux 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 such file or directory (2) [23-Jun-2013 21:16:01] ERROR: failed to load configuration file '/usr/local/php/etc/php-fpm.conf' [23-Jun-2013 21:16:01] ERROR: FPM initialization failed: this problem occurs when you start php-fpm. 6. It is actually the same problem. Solution: [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 ).Case: Run"Service mysqld start "or"/etc/init. d/mysqld start"An error occurs when the mysqld daemon is started. It means that the mysql instance fails to be restarted. The cause is that no solution is found. The error indicates that no specific problem is found, only [root @ mylinux/] # cd/usr/local/mysql/data [root @ mylinux data] # tail-f-n 20 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 = large At 16:34:53 InnoDB: Completed initialization of buffer poolInnoDB: Unable to lock. /ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld processInnoDB: using the same InnoDB data or log files. innoDB: Unable to lock. /ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld processInnoDB: using the same InnoDB data or log files. innoDB: Unable to lock. /ibd Ata1, error: 11 InnoDB: Check that you do not already have another mysqld processInnoDB: using the same InnoDB data or log files. innoDB: Unable to lock. /ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld processInnoDB: using the same InnoDB data or log files. innoDB: Unable to lock. /ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld processInn ODB: using the same InnoDB data or log files. innoDB: Unable to lock. /ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld processInnoDB: using the same InnoDB data or log files. innoDB: Unable to lock. /ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld processInnoDB: using the same InnoDB data or log files. innoDB: Unable to lock. /ibdata1, erro R: 11 InnoDB: Check that you do not already have another mysqld processInnoDB: using the same InnoDB data or log files. innoDB: Unable to lock. /ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld processInnoDB: using the same InnoDB data or log files. innoDB: Unable to lock. /ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld processInnoDB: using The same InnoDB data or log files. innoDB: Unable to lock. /ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld processInnoDB: using the same InnoDB data or log files. innoDB: Unable to lock. /ibdata1, error: 11 InnoDB: Check that you do not already have 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 11 in a file operation. innoDB: Error number 11 means 'Resource temporarily unavailable '. innoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html130623 16:36:33 InnoDB: cocould 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 shoshould now edit innodb_data_file_path in my. cnf back130623 16:36:33 InnoDB: to what it was, 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 did not yet use them in any way. but be caref Ul: 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' registry 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
Cause:Check the preceding log.InnoDB: Check that you do not already have another mysqld processIt indicates that the mysqld process is already running, so mysql cannot be started.Solution:[Root @ mylinux etc] # ps-ef | grep mysqld [root @ mylinux etc] # kill-9 process no. [root @ mylinux etc] # service mysqld start this is a mysql report. I restarted the CentOS server, and then restarted mysqld. The problem was solved by myself, probably because of the LVM disk management software.
There are many possible causes for this problem at google. The best way is to check the Error Log First:

1. It may be that the/usr/local/mysql/data/rekfan. pid file has no write permission.
Solution: grant permissions, execute "chown-R mysql: mysql/var/data" "chmod-R 755/usr/local/mysql/data", and then restart mysqld!

2. the mysql process may already exist in the process.
Solution: Run "ps-ef | grep mysqld" to check whether the mysqld process exists. If the "kill-9 process number" is used to kill the process and restart mysqld!

3. It may be the second time that mysql is installed on the machine. Residual data affects service startup.
Solution: Go to the mysql data DIRECTORY/data to see, if there is a mysql-bin.index, just remove it, it is the culprit. I am using the third solution! Http://blog.rekfan.com /? P = 186

4. mysql uses/etc/my when the configuration file is not specified at startup. cnf configuration file. Open this file to check whether the data directory (datadir) is specified in [mysqld ).
Solution: Set this line in [mysqld]: datadir =/usr/local/mysql/data

5. skip-federated Field Problems
Solution: Check whether the skip-federated field has been commented out in the/etc/my. cnf file. If so, comment out the field immediately.

6. The error log directory does not exist.
Solution: use the "chown" "chmod" command to grant the mysql owner and permissions.

7. selinux. If it is a centos system, selinux is enabled by default.
Solution: Close it, open/etc/selinux/config, change SELINUX = enforcing to SELINUX = disabled, and then save the disk and restart the machine.

8. the disk space attached to the data directory of mysql is used up.

Solution: df-h: Check the disk usage. The disk is full, because the system default partition is used at that time. I don't know why I cannot automatically resize the disk and then clean up the excess data. I will study it later. Start mysql. started successfully!