Skip to main content

/usr/lib64/sa/sa2 -A error

Comments

7 comments

  • cPanelLauren
    Hello @mvandemar That error is typically associated with the latest sysstat log file being corrupted. What happens when you run the following: sar -q |tail
    sar -q -f /var/log/sa/sa02 1>/dev/null
    sar -q -f /var/log/sa/sa03 1>/dev/null
    Thanks!
    0
  • mvandemar
    @cPanelLauren Thanks, this is the results: [root@vps3 ~]# sar -q | tail 01:10:01 PM 1 220 0.07 0.07 0.05 0 01:20:01 PM 2 228 0.14 0.11 0.06 0 01:30:01 PM 2 225 0.07 0.08 0.06 0 01:40:01 PM 2 224 0.07 0.08 0.07 0 01:50:01 PM 2 228 0.23 0.16 0.11 0 02:00:01 PM 4 226 0.08 0.08 0.10 0 02:10:01 PM 2 225 0.12 0.11 0.10 0 02:20:01 PM 2 227 0.04 0.08 0.10 0 02:30:01 PM 5 227 0.02 0.06 0.09 0 Average: 2 223 0.11 0.11 0.12 0 [root@vps3 ~]# sar -q -f /var/log/sa/sa02 1>/dev/null End of system activity file unexpected [root@vps3 ~]# sar -q -f /var/log/sa/sa03 1>/dev/null [root@vps3 ~]#
    -Michael
    0
  • cPanelLauren
    Hi @mvandemar So it was indeed yesterday's sysstat logs that were corrupt based on this: [root@vps3 ~]# sar -q -f /var/log/sa/sa02 1>/dev/null End of system activity file unexpected
    But today's logs look to be fine. I can't say specifically why it happened yesterday though. Did anything unusual happen on the server yesterday?
    0
  • mvandemar
    About 20 hours prior to getting that email my server ran out of space, but I fixed it right away. Do you think that could have impacted it? -Michael
    0
  • cPanelLauren
    Hi @mvandemar That would be exactly it. Nearly every time I've seen this issue the server had run out of space at the time, whether or not the issue had been resolved or not. Thanks!
    0
  • mvandemar
    Awesome, thanks! -Michael
    0
  • cPanelLauren
    Hi @mvandemar You're most welcome! I'm glad its working as expected now and I'm glad I could help. Thank you.
    0

Please sign in to leave a comment.