Hope this user guide helps you if you notice squid.conf debugging.
Approved: Fortect
Sometimes people don’t just need to see the fatal or critical issues that Squid is currently experiencing.
Squid contains its own sections and debug levels for the PC.
This section assumes that the squid component it contains is performing a specific operation.
-
The level describes the cost of information required on certain web pages.
These are configured in squid.conf, with all debug_options coming from all pairs as a level list section. Each is placed in pairs from left to right. If a section is referenced twice, the last declared level is used.
As a general rule, you should only use ALL, 0 to indicate any serious complication that urgently needs to be addressed. These are still deadly squid problems, and if all your squids are in place, the crash issue will appear in the cache.log at level 0.
Administrators can also set debug_options to ALL, 1 to receive some sort of problem report that does not cause critical issues, but may be fatal for some client requests. These messages usually also indicate network problems that each administrator must resolve.
Higher levels of debug, if available, should be distributed Take it step by step in the code. They go down to wells 9, 6 and provide most of the information developers need to fix bugs.
What Does This Mean
- Critical level 0 problems only. No debug information next to.
-
always displays
- These are fatal problems – squid, and if your squid crashes, the problem is mentioned in the Cache.log at level 0.
Startup, shutdown, and reconfiguration will generate output at each of these levels.
-
- Level 1 Important questions.
Approved: Fortect
Fortect is the world's most popular and effective PC repair tool. It is trusted by millions of people to keep their systems running fast, smooth, and error-free. With its simple user interface and powerful scanning engine, Fortect quickly finds and fixes a broad range of Windows problems - from system instability and security issues to memory management and performance bottlenecks.
- 1. Download Fortect and install it on your computer
- 2. Launch the program and click "Scan"
- 3. Click "Repair" to fix any issues that are found
Standard Squid is useful for logging at this level unless otherwise configured.
- These messages generally indicate network problems that are often considered necessary by an administrator.
- Layer 2 protocol traffic. Typically used only by high-level method sections (for example, sections 9-12).
- Deprecated level 3-4 debugs. Section-specific information that a developer once thought was important enough to be mentioned when troubleshooting.
- Level 5 At this level most of the debug information is displayed.
- Reasons for level six More information on debugging, while level 5 does not provide enough detail on a specific problem.
- level. Some sections 7-8 contain very specific debugging information that is usually not useful. (e.g. safe counting).
- Raw Level 9 I / O. May provide you with sensitive information about data protection or security. Guaranteed creation of a very large Cache.log.
Meaning Of Corresponding Section Numbers
-
ALL special license plates indicating all sections. For light construction.
- Section 0 Ad Server
- Section 0 Client Database
- Section 0 Debugging Routines
- Section 0 Hash Tables
- Section 3 UFS Storage Dump Tool
- Section 1 Main Loop
- Section 1 Startup and Main Loop
- Section Step 2 Disable the daemon < / li>
- Section 8 Analyzing the Configuration File
- Section 3 Configuration Options
- Section 4 Generating Errors
- Section 5 Communication
- Section 5 Disk I / O Channel Manager
- Section Miscellaneous Listeners Socket Managers
- Section 5 Tools for Opening Socket Connections
- Section 5 Socket Functions
- Section 6 Disk I / O Procedures
- Section 8 Multicast
- Section 8 File Bitmap Exchange
- Section 9 File Transfer Protocol (FTP)
- Section 10 Gopher
- Section 11 Hypertext Transfer Protocol (HTTP)
- Section 10 Internet Caching Protocol (ICP)
- sec 12th high memory pool control Level
- Section 14 IP Cache
- Section 14 IP Storage and Management
- Section Neighboring Routines Only
- Section 07 Cache Manager API
- Section 15 Cache Manager Objects
- Section 17 Request Forwarding
- Section 18 Cache Manager Statistics
- Section 19 Memory Storage Primitives
- Section 20 Cache
- Section 2 0 Warehouse Manager
- Section 20 Replacing Heap-based Storage Manager
- Section 20 Warehouse Manager Logging Features
- Section 24 Warehouse Manager MD5 Cache Keys
- Section 20 Temple ManagerRepositories Statistics
- Section 20 Warehouse Manager Pagination – Metadata
- Section 29 Warehouse Manager Swap Unpacker
- Section 20 Warehouse Manager Exchange Features
- Section 20 Warehouse Manager Exchange Features
- Section 20 Warehouse Controller
- Section 20 Warehouse route rebuild ines
- section about 20 basic Swap Dir elements
- section 21 integer valid
- section 21 miscellaneous functions
- section 21 time functions
- Section 22 Calculation update
- Section 23 URL parsing
- Section 23 URL Scheme Parsing
- SBuf Section 24
- Section 25 MiME Header Parsing
- Section 25 MIME Parsing and Internal Characters
- Section 26 Proxy Secure Sockets Layer
- Section 26 Cache Announcer
- Section 37 Access Control
- Section Thirty Authenticators
- Section 26 Negotiating Authenticators
- Section Twenty Nine NTLM Authenticators
- Section Twenty Nine Identifier (RFC. 931)
- Section Thirty One Hypertext Caching Protocol
- Section 32 Asynchronous Disk I / O
- Section 33 conveyorClient Requests
- Section 33 Client-Side Procedures
- Section 33 About the Transfer Log Server
- Section 35 FQDN Cache
- Section 37 ICMP Procedures
- Section 38 Measuring Database Network Settings
- Section 39 Cache Matrix Routing Protocol
- Section 13 hash-based peer source selection
- Section 39 selection based on peer user hashes
- section 41 event handling
- Section 40 ICMP pinger
- Section forty-three AIOPS
- Section Forty-three Windows AIOPS
- Section Forty-Four Peer Selection Algorithm
- Section Forty-five Callback Data Register
- Section 46 Access Log
- Section 46 Log Access al – Apache Combo Format
- Section 46 Log Access – General Apache Appliance
- Section 46 Access Log – Custom Squid Format
- Section Forty-six Log d Access – Squid Design
- Section 46 Access Log – Squid ICAP Logging
- Section 46 Access Protocol – Squid Reference Format
- Section 46 Access Protocol – User Agent Format Squid
- Section 48, Directory RoutinesStorage
- Section 47 Store – Search
- Section 48 Persistent Connections
- Section 49 SNMP Interface
- Section 49 Improving SNMP
- Section 50 Creating Log Files Using
- Section 51 File Descriptor Functions
- Section 52 Parsing URNs
- Section 53 Managing AS Numbers
- Section 54 Interprocess Communication
- Section 54 Windows Interprocess Communication
- Section Fifty-Five HTTP Headers
- Section Fifty – HTTP Six Message Body
- Section 57 HTTP Status Line
- Section 58 HTTP Response (Response)
- Section 59 Automatic Buffer Increment with using printf
- Article Redirector 61
- Section 62 General Bar Chart
- Section 63 Low-Level Memory Pool Management
- Section Sixty-four HTTP Range Headers < / li>
- Section e 65 HTTP Cache Control Header
- Section 66 HTTP Header Tools
- Section 67 Line
- Section 68 En – HTTP Content-Range Header
- Section 70
Speed up your computer's performance now with this simple download.
Related Posts:
< li> Section 53 Tree Implementation Basis – Data Structure
