Common Nginx logs and configuration methods in PHP
The content of this article is about common Nginx logs and setting methods. It has certain reference value. Friends in need can refer to it. I hope it will be helpful to you.
Preface
As a programmer, something a little more important than coding is log analysis and query. Common logs and setting methods are listed below.
Configuration file
nginx is divided into two logs: access_log and error_log
The settings need to be in nginx.conf, and the default is passed The source code package compilation and installation nginx directory should be in the
/usr/local/nginx
directory. If you install it through yum or other methods and do not know or do not know the specific nginx installation directory, you can use
find / -name nginx.conf
or
nginx -V | grep prefix ------------- nginx version: nginx/1.13.9 built by gcc 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) built with OpenSSL 1.0.2k-fips 26 Jan 2017 TLS SNI support enabled configure arguments: --prefix=/usr/local/nginx --with-http_ssl_module
Open access log
If your source code package is installed by default, open the path as follows
vim /usr/local/nginx/nginx.conf
Find the following content
http { include mime.types; default_type application/octet-stream; log_format main '$remote_addr - $remote_user [$time_local] "$request" ' '$status $body_bytes_sent "$http_referer" ' '"$http_user_agent" "$http_x_forwarded_for"'; access_log logs/access.log main; ... }
Change log_format Just open the comment of access_log. Log_format can define the log specifications of nginx.
log_format default specification parameter table
Name | Annotation |
---|---|
$remote_addr | Client/user IP address |
$time_local | Access time |
$request | Request method Request address |
$status | The request status code is consistent with the HTTP status code |
$body_bytes_sent | The requested address size is calculated in bytes format |
$http_referer | Request source, from what Local access |
$http_user_agent | User information (browser information) |
$http_x_forwarded_for | Forward IP address |
Enable error log
If your source code package is installed by default, open the path as follows
vim /usr/local/nginx/nginx.conf
Find the following content
error_log logs/error.log; #error_log logs/error.log notice; #error_log logs/error.log info;
Just delete the annotation. You can store different error types separately. For example,
error_log logs/error.log notice;
notice is an error type. If you don’t write it, it will be all.
Recommended related articles:
Nginx common log splitting methods nginx apache nginx php nginx rewrite
nginx common configurationThe above is the detailed content of Common Nginx logs and configuration methods in PHP. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



How to configure Nginx in Windows? Install Nginx and create a virtual host configuration. Modify the main configuration file and include the virtual host configuration. Start or reload Nginx. Test the configuration and view the website. Selectively enable SSL and configure SSL certificates. Selectively set the firewall to allow port 80 and 443 traffic.

In Linux, use the following command to check whether Nginx is started: systemctl status nginx judges based on the command output: If "Active: active (running)" is displayed, Nginx is started. If "Active: inactive (dead)" is displayed, Nginx is stopped.

Steps to start Nginx in Linux: Check whether Nginx is installed. Use systemctl start nginx to start the Nginx service. Use systemctl enable nginx to enable automatic startup of Nginx at system startup. Use systemctl status nginx to verify that the startup is successful. Visit http://localhost in a web browser to view the default welcome page.

The server does not have permission to access the requested resource, resulting in a nginx 403 error. Solutions include: Check file permissions. Check the .htaccess configuration. Check nginx configuration. Configure SELinux permissions. Check the firewall rules. Troubleshoot other causes such as browser problems, server failures, or other possible errors.

How to confirm whether Nginx is started: 1. Use the command line: systemctl status nginx (Linux/Unix), netstat -ano | findstr 80 (Windows); 2. Check whether port 80 is open; 3. Check the Nginx startup message in the system log; 4. Use third-party tools, such as Nagios, Zabbix, and Icinga.

There are two ways to solve the Nginx cross-domain problem: modify the cross-domain response header: add directives to allow cross-domain requests, specify allowed methods and headers, and set cache time. Use CORS modules: Enable modules and configure CORS rules that allow cross-domain requests, methods, headers, and cache times.

How to fix Nginx 403 Forbidden error? Check file or directory permissions; 2. Check .htaccess file; 3. Check Nginx configuration file; 4. Restart Nginx. Other possible causes include firewall rules, SELinux settings, or application issues.

Starting an Nginx server requires different steps according to different operating systems: Linux/Unix system: Install the Nginx package (for example, using apt-get or yum). Use systemctl to start an Nginx service (for example, sudo systemctl start nginx). Windows system: Download and install Windows binary files. Start Nginx using the nginx.exe executable (for example, nginx.exe -c conf\nginx.conf). No matter which operating system you use, you can access the server IP
