Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

An error was reported when executing the sar command due to the change in the number of CPU: Invalid system activity file: / var/log/sa/saxx

2025-04-05 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

Shulou(Shulou.com)06/02 Report--

After adjusting the number of CPUs (2-> 8) on a Linux redhat 6 VM (virtual machine) at 9: 00 a.m. on the 29th, it was found that sar reported an error when checking the CPU loading of the day:

[root@vswhInd4DBt ~] # sar

Invalid system activity file: / var/log/sa/sa29

Check the official website of SYSSTAT

Http://sebastien.godard.pagesperso-orange.fr/faq.html

Mainly, it may be due to the change of sysstat version and the change of saxx file (/ var/log/sa/sa29) format, and the incompatibility leads to unreadable sarxx file.

Invalid system activity file:...

You are trying to use a file which is not a system activity file, or whose format is no longer compatible with that of files created by current version of sar.

If you were trying to use the standard system activity files located in the / var/log/sa directory then the solution is easy: Just log in as root and remove by hand all the files located in the / var/log/sa directory:

# rm / var/log/sa/sa??

If you are using sysstat 11.1.1 and later, you can also use the sadf command to convert an old system activity binary datafile (version 9.1.6 and later) to current up-to-date format. Use the following syntax:

$sadf-c old_datafile > new_datafile

Note: Starting with sysstat version 8.1.1 and later, it is possible to know which version of sar or sadc has been used to create a data file. Just enter the following command:

$sadf-H / your/datafile | grep sysstat

File created using sar/sadc from sysstat version 8.1.7

Back in my environment, the sysstat version hasn't changed.

It is suspected that the change of CPU number leads to the change of saxx file record and operation, which makes the saxx file write failure sar unreadable.

I'm going to wait until the 30th to see if it's normal, and sure enough, the order shows normal:

[root@vswhInd4DBt ~] # sar

Linux 2.6.32-504.el6.x86_64 (vswhInd4DBt) 07 Universe 30 CPU 2018 _ x86 pound 648

12:00:01 AM CPU user nice system iowait steal idle

12:10:01 AM all 0.48 0.00 0.11 0.12 0.00 99.29

12:20:01 AM all 0.27 0.00 0.10 0.06 0.00 99.57

12:30:02 AM all 0.21 0.00 0.08 0.02 0.00 99.68

...

Of course, after adjusting rm-rf / var/log/sa/sa29 to CPU on the 29th, the sar command should also show the adjusted information.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Servers

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report