SOLVED /var/tmp disk warning for atop

[kwdamp]

Started getting a Disk Usage Warning for /var/tmp on one of our dedicated servers last week.

Digging into it today it looks like it's the atop.acct file in the atop.d folder that has gotten up to over 3gb. I wasn't even aware we were running atop reports on that machine (Cent Os7.9)

Is atop attached to one of the account management tools in cpanel/whm? Wondering if there is an easy way to manage what I assume are just log files it is creating.

Can't seem to find many answers on cursory searches of the web or here, so any help would be greatly appreciated.

 

[ServerHealers]

atop tool is 3rd party and don't have any connection with cPanel I'd say. You or your admins might have installed this tool manually to troubleshoot server performance, and may have terminated atop process incorrectly. If you terminate atop process incorrectly, then it has no chance to stop process accounting; as a result the accounting file may consume a lot of disk space after a while!!!

 

[kwdamp]

atop tool is 3rd party and don't have any connection with cPanel I'd say. You or your admins might have installed this tool manually to troubleshoot server performance, and may have terminated atop process incorrectly. If you terminate atop process incorrectly, then it has no chance to stop process accounting; as a result the accounting file may consume a lot of disk space after a while!!!

@cPRex can you confirm atop doesn't sit on top of any of the cpanel tools?

I have gone over the admin log and install logs for this dedicated server and we didn't install atop directly. So it is either integrated w/ cpanel or the hosting provider set it up by default for some reason.

Thanks

 

[cPRex]

Yes, we don't make or distribute atop on our end, so it must have been added by the host at some point.

 

[kwdamp]

Well, the mystery of how it got installed will remain. But the problem is solved.

In case anyone finds this thread with a similar problem in the future, the solution was a simple server reboot.

Apparently one small inadvertent risk of using kernelcare is reboots of the machines are no longer mandatory at intervals determined by security patch installations. Turns out this machine hadn't been rebooted in over 3 months, and I guess atop doesn't clean up its temp files until the machine reboots.