Operational considerations and common error resolution

Operational considerations and common error resolution

1. Configuration name such as virtual host and so on, remember to standardize

2. Do not test the online server, pressure measurement is done before the launch, after-line call attack

3. Can not compile without compiling, distribution difficulties, even if the compilation is to do a dedicated RPM package

4.chrome F12 Pull-up request interface

5. Three types of trusted Yum warehouses

CD Official Warehouse EPEL

6. To deal with problems to total, first look at each part of the general, and then in the overall view, first piecemeal, in from 0 to the whole

7. Install do not overwrite, link, in case of error can be rolled back

8. Set iptables, before setting, do a recurring plan crontab, each time to clear the rules and the default action for the accept, once you have been refused to go into, then wait a while.

9.ssh generally do not use the default port, because this is your own remote connection control, the default port too many attacks

10. Any custom name for operation and maintenance should be standardized, operating system standardization, application version standardization,

Hardware standardization, File path standardization, which is able to complete the task based on script assurance, and so on, remember to obsessive-compulsive disorder, should be consistent

Mysql:

1.cant Open and Lock Privilege tables:table ' mysql.host ' doesnt exists

Workaround: Run mysql_install_db initialization

2. [Mysqld]

Innodb_file_per_table=on

Skip_name_reslve=on Skip name resolution but only 5.2 or higher is supported

HTTP

1.Permission denied:httpd:could not open error log File/httpdtest/logs/log2/error_log

SELinux is not turned off, Setenforce 0 is off.

2.amp deployed to three hosts, remember that both httpd and PHP-FPM hosts have WordPress and PMA

3.PMA Web page appears red error, generally php-fpm www.conf file of the bottom of the session out of the problem, the two lines comment off the good

Php

1. Acceptable c * ERROR occurs because there is no C language, yum installation gcc is good

2. Install XCache execute phpize will not appear configure, failure

Cannot find autoconf. Please check your autoconf installation and the $PHP _autoconf environment variable. Then, rerun the this script.

You can get Yum M4 and autoconf first.

Compiling the installation

1.error:c++ compiler cannot create executables

Yum Install gcc gcc-c++ gcc-g77

2. Errors are usually the beginning of an error

Nginx

1.nginx: [Emerg] bind () to 0.0.0.0:80 failed (98:address already on use)

Nginx: [Emerg] bind () to 0.0.0.0:80 failed (98:address already on use)

Nginx: [Emerg] bind () to 0.0.0.0:80 failed (98:address already on use)

Nginx: [Emerg] bind () to 0.0.0.0:80 failed (98:address already on use)

Nginx: [Emerg] bind () to 0.0.0.0:80 failed (98:address already on use)

Nginx: [Emerg] still could not bind ()

80 ports are occupied, 80 ports are lifted.

2.nginx: [Emerg] mkdir () "/var/cache/nginx/client_temp" failed (2:no such file or directory)

Unable to create a file, help to create it.

Deep Learning:

Constantly challenge yourself, set yourself a higher goal, challenge your limits, but not too high

Piecemeal, one to conquer the small problem

Repetitive training

Hold on for 10,000 hours

Interview:

Iptables optimization rules, port numbers

The status of Nginx

LVS cluster: Used to be small, interview will ask

This article from "Blog Work First Edition" blog, declined reprint!

Operational considerations and common error resolution