When the SSL certificate was installed, the Nginx process was forcibly killed and never got up:
Restarting Nginx daemon:nginxcat:/usr/local/nginx/logs/nginx.pid:no such file or directoryKill:usage:kill [s Sigspec |-n signum |-sigspec] pid | Jobspec. or kill-l [Sigspec]Nginx
In Linux Nginx and PHP we are separate two different programs, unlike in Windows PHP is just a module of Apache only.So we let them integration can be, the principle is to submit the user's request by Nginx to an nginx, and then he then forwarded to PHP, PHP processing completed he will return the results to nginx ...F
We encounter a lot of problems when using thinkphp in Nginx, such as:No permissions, this is the benefit of Linux Rights Management, we give him permission.We give him permission to access the normal:Then we add a lists method for the Indexcontroller controller:Then we add a lists method, as follows:Save exit. To visit her.No ... Because Nginx does not support php behind the URL where there is a slash and f
The final effect is as follows:In fact, it is very simple, first create a test.php file in the HTML directory, as follows:Then use VI to open him, write a test source code, the source code is as follows:Then save exit, go to/usr/local/nginx/conf to find nginx.conf configuration file, modify it.In the 46 line to add the rules can be modified, white to play regular expression just, "$" is the NGINX reserved v
http://www.csdn.net/article/2014-11-28/28228581. Single-point account verification, do not need to read, but write, Redis, see if plus watch2. The ultimate purchase conflict of Rob Bao. Packaging is called "optimistic lock". The optimistic lock has a version number. Optimistic lock plus lock failed, rollback, or scroll to the next issue.Optimistic locks, such as Watch in Redis, are one of them. Through this implementation, we guarantee the security of the data. Study the Watch of Redishttp://ww
The reverse proxy diagram looks like this:From the visible, our server is actually divided into two, a dedicated to the source of PHP and other programs, and another is dedicated to store the image of the server, because the picture in server A does not exist, so it may lead to the following display:Not see this is quite normal, because server A does not have this picture, the picture under Server B:So we're going to change the configuration file for Server A:Then we start adding a reverse proxy
Clusters, such as buying a generation to push the server down and put a piece he's quite a cluster, and load balancing is to get this big bunch of servers to work on average. He is called load Balancer, as shown in:For example, I use 192.168.8.155 to act as a pic host 1 and PIC Host 2 with Server A, 192.168.8.166, and 192.168.8.177来 as follows:Then start modifying the nginx.conf file under Server A (192.168.8.155) Conf directory: upstream imgserver{ 192.168.8.166:80 weight=1 max_fails=
The KILL command is used to terminate the specified procedure (terminate a process) and is a common command for the unix/linux process. In general, when we need to terminate some or certain processes, we first apply the Ps/pidof/pstree/top and other objects to obtain the process PID, and then use the KILL command to kill the process. Another use of the
Turn from: How to find the zombie process and kill it, you can't kill it. To view the parent process and kill itFind zombie processes with PS and grep commands#ps-A-ostat,ppid,pid,cmd | Grep-e ' ^[zz] 'Command annotations:-A parameter lists all processes-O Custom output fields We set the Display field to stat (status), Ppid (process parent ID), PID (process id),
Find zombie processes with PS and grep commands#ps-A-ostat,ppid,pid,cmd | Grep-e ' ^[zz] 'Command annotations:-A parameter Lists all processes-O custom output fields We set the Display field to stat (state), PPID (process parent ID), PID (process id), cmd (command) These four parameters because the process of the state Z or Z for the zombie process, So we use grep to grab the stat state for the ZZ process to run the result reference as follows Z 12334 12339/path/cmd at this point, we can use
the old version with the newly compiled version of Nginx [[emailprotected] nginx-1.12.2]# mv/usr/local/nginx/sbin/nginx \ /usr/local/nginx/sbin/nginxold [[emailprotected] nginx-1.12.2]# CP objs/
Use the script kill process, Syntax: run script + process name, script kill
The script is attached below, and the permission must be attached to X for execution.
#! /Bin/sh # pid kill thread for chenglee # if fileformat = dos, update fileformat = unix # code: set fileformat = unix # check: set ff? If [$ #-lt 1] then echo "not procedure_name" exit 1fi PROCESS =
Tags: delete user name connect creating action query SSL how ATIHow do I check every 10 seconds to kill a query that exceeds 100 seconds for a specified user? Pt-kill--no-version-check--host 127.0.0.1--port 3306--user ' xxxxxx '--password ' xxxxxx '--charset UTF8--match-command Query--match-user The specified user name--busy-time--kill--victims all--interval--pri
system (you can use the tool or use alt+p)
Step two: Unzip the package.
Step three: Carry out configure. (The red part is the Nginx installation directory)
./configure \
--prefix=/usr/local/nginx \
--pid-path=/var/run/nginx/nginx.pid \
--lock-path=/var/lock/nginx.lock \
--error-log-path=/var/log/nginx/error.log \
--ht
Pt-kill Common Kill process parameters1. Press User Kill/usr/bin/pt-kill--busy-time--match-user= "dbUSER1 | DbUSER2,... "--victim all--interval 1--kill--daemonize--pid=/tmp/ptkill.pid--print--log=/home/pt-kill.logNote: Test by user to ki
Percona utility-Introduction to pt-kill, perconapt-kill
Pt-kill is an excellent tool for kill MySQL connection and is part of percona toolkit, when the maximum number of connections is exceeded due to a large number of idle connections and a problematic SQL statement causes a high mysql load, you must
Sometimes we can't kill a process using kill, but we can use kill-9, why?First look at the kill function, the man manual for Kill is described as follows:Kill (1) Linux User ' s Manual
This article mainly introduces the parameters of common pt-kill processes. if you need it, refer to pt-kill, which is an excellent tool for kill MySQL connection and part of percona toolkit, when the maximum number of connections is exceeded due to a large number of idle connections and a problematic SQL statement causes a high mysql load, you must
Introduction to common killing process parameters of pt-kill and parameters of pt-kill
Pt-kill is an excellent tool for kill MySQL connection and is part of percona toolkit, when the maximum number of connections is exceeded due to a large number of idle connections and a problematic SQL statement causes a high mysql l
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.