Content and Operation of Server Patrol Inspection in Linux system

This article introduces the "Linux system server inspection content and operation" related knowledge, in the actual case of the operation process, many people will encounter such a dilemma, then let the editor lead you to learn how to deal with these situations! I hope you can read it carefully and be able to achieve something!

The specific contents of the inspection are explained here:

1. CPU occupancy rate

Check script: top shift+m c

The parameter to be recorded here is?% us. It is recommended to wait a few seconds to see the dynamic changes before recording.

Cpu occupancy rate

2. Memory utilization

Check script: free-m / free- g

Memory utilization

The key thing to look at here is whether the swap memory is used. What you need to record is the second one in the second line. The ratio of it to the total memory is the memory usage. Whether to use-m or-g depends on the memory size of the server.

3. Hard disk utilization

Check script: df

Hard disk utilization

Disk utilization depends on the disk utilization itself. Here, if the application under the server uses the mounted disk separately, you also need to check the utilization of the mounted disk separately.

4. Igamo is idle

Check script: iostat-xm

I am idle

The value that needs to be recorded is the red box in the picture,?% idle, and this is Imax O idle. Here you can use iostat-xm 1 to dynamically view multiple values and then take a more average one.

5. Application health status

Check to see if the page of the application is normal and whether the user is using it properly.

6. Application service status

Check script:. / Application Service status

Check to see if the service status is running.

7. Whether there is any error in the application service operation log

Check script: cat Application Service running Log | grep ERR

Visually check whether there are any errors in the log of the application service. You can also directly open it here to check:

Vim Application Service run Log

Then use "/ ERR" to check the error report

8. Whether there is any error in the application content log

Check script: cat application content logging grep ERR

9. Data file size

First, open the directory where the application data file is located, and then run: du-sh *

Here you can see the size of all the files in this directory.

10. Archive file status

This is a special function of the application I am responsible for, which can be archived, and all of you can ignore this requirement.

11. Backup implementation

Check the backup directory to see if the latest date of the backup is recent.

This is the end of the content of server inspection and operation of Linux system. Thank you for your reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!