{"id":31600,"date":"2017-07-21T03:01:35","date_gmt":"2017-07-20T17:01:35","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=31600"},"modified":"2017-10-08T09:43:51","modified_gmt":"2017-10-07T23:43:51","slug":"linux-disk-usage-cpanel-heads-up-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/linux-disk-usage-cpanel-heads-up-tutorial\/","title":{"rendered":"Linux Disk Usage cPanel Heads Up Tutorial"},"content":{"rendered":"
\"Linux<\/a>

Linux Disk Usage cPanel Heads Up Tutorial<\/p><\/div>\n

What’s important, and what’s not? Leave you with that. See you tomorrow.<\/p>\n

Not a very good blog posting is it? Let’s say, instead …<\/p>\n


\n\"What's important, and what's not, regarding Linux CentOS WHM Apache\/PHP\/MySQL cPanel, when it presents one of its very rare error messages?\"
\n<\/code><\/p>\n

… and say, from today’s experience, take the time to “follow up on it” and “follow up on it now”. Guess the lesson, in life, here, too, is that in order to appreciate the “quiet achieving things in life” to the utmost “give them their due” if they ever do, as ever, not be wasting your time, and are displaying or showing something unusual to (really) tell you (something important).<\/p>\n

So what was our case today? The Linux CentOS WHM cPanel system is a very clever one, and in default usage, tends to want to keep your cPanel software up to date, like you might be familiar with Windows doing, though cPanel, by default, one of the best “quiet achieving things in life” (not that Windows isn’t, by the way) tends to do this updating quite surreptitiously. Today, though, going into cPanel we got the top right scenario of today’s tutorial picture<\/a>, featuring a yellow error box, the first one I’d ever seen cPanel present, with the wording …<\/p>\n


\nThe last attempt to update cPanel and WHM was blocked. Details<\/u>.
\n<\/code><\/p>\n

Now the word “blocked” is interesting these days (and all the other days, as well). The more sensationally minded of us think “catastrophe”, and think malware, hacking, and other catastrophic things, but am here to tell you that “blocked” can be a thing that happens for a good “protective” reason, cPanel being such a benign and useful tool, it is infinitely better to click on Details<\/u> and not “bury your head in the sand”, as I find out.<\/p>\n

So, what panned out to be the “blocking” reason? Lack of disk space to perform one of cPanel’s surreptitious upgrades, that’s the reason. And gasp, yes, “ssh”ing onto the web server and going “du -k \/” showing 99% usage. Ugh!<\/p>\n

And as bad as all this is, there is a focussing of the mind, and problem, but only<\/b><\/i> if you don’t bury your head in the sand.<\/p>\n

Which brings us onto the previous Linux Disk Usage Statistics Primer Tutorial<\/a> where we discussed tactics for just this issue, “ssh”ing to the web server and typing …<\/p>\n

$ du -a [DocumentRoot] 2> \/dev\/null | sort -n -r | head -10<\/code><\/p>\n

… where [DocumentRoot]<\/i> is where HTTP:\/\/www.rjmprogramming.com.au\/<\/i> points to, directory (ie. folder) wise (in regard to the web server system disk).<\/p>\n

And the resultant report made us realize “back in the day” when we presented Joomla Categories and Articles and Menus Primer Tutorial<\/a> a new Joomla website became necessary with an upgrade of PHP, I think it was, and at the time, while the new Joomla website was being bedded in, didn’t want to delete the files of the old Joomla. However, that decision, in particular, had come home to … well, you know the expression?! And here is another thing about Apache\/PHP\/MySQL web servers, and I dare say other web server architectures, that the individual website directories (ie. folders) each pointing to not subdomains exactly<\/i> but individual websites, as with our blogs and CMS and eCommerce website “products” here at RJM Programming each have the potential to build up huge error_log<\/i> files not controlled in a rotational sense like the log files of \/var\/log<\/i> for instance, by cPanel or some other overseer, and given no scrutiny by the web server manager to write some script to check on this, sometimes these “error_log” files can become huge, and I mean “huge”. Take a look<\/b> at, factoring in the kB units …<\/p>\n


\n$ du -a [DocumentRoot] 2> \/dev\/null | sort -n -r | head -10
\n20082532\t[DocumentRoot]
\n11666800\t[DocumentRoot]\/myfavourites
\n6184280\t[DocumentRoot]\/myfavourites\/administrator
\n6176472\t[DocumentRoot]\/myfavourites\/administrator\/error_log
\n5413304\t[DocumentRoot]\/myfavourites\/error_log<\/b>
\n864352\t[DocumentRoot]\/Mac
\n641408\t[DocumentRoot]\/PHP
\n593124\t[DocumentRoot]\/mycustomerportal
\n515244\t[DocumentRoot]\/mycustomerportal\/error_log
\n392912\t[DocumentRoot]\/HTMLCSS
\n<\/code><\/p>\n

… ugh! All obsolete now, as long as we just leave the (one) old redirecting Joomla index.php<\/a> (file) pointing to new Joomla<\/a> and so we could “ssh” to the web server and use an “rm” command, but for file removal “chunks” like this, especially ones where you want to leave just “one file standing” we prefer, believe it or not, to use the “(s)ftp” tool we use, which, these days, is FileZilla<\/a> (see also FileZilla Secure ftp Primer Tutorial<\/a>) and use its “GUI feel” to supervise, what we want to be deliberately trepidatious regarding, the “removal of web server files” “in bulk”.<\/p>\n

\n

Previous relevant Linux Disk Usage Statistics Primer Tutorial<\/a> is shown below.<\/p>\n

\"Linux<\/a>

Linux Disk Usage Statistics Primer Tutorial<\/p><\/div>\n

There are occasions when using a Linux or Unix operating system when it is gobsmacking how a two letter command can do so much. And so it is the case with our use of the “du”<\/a> to display disk usage statistics via the incarnation …<\/p>\n

$ du -a \/<\/code><\/p>\n

… to display a whole disk from its root directory ( \/ ) and up, reporting on the disk usage for all the files it encounters.<\/p>\n

Putting this in context for how it could be useful to track down, perhaps, major inode usage (ie. lots of files being created) somewhere. In this scenario we say that we might want to narrow the search to the top 15 files (which are perhaps directories, as you might know from your Unix and\/or Linux training) via …<\/p>\n

$ du -a \/ 2> \/dev\/null | sort -n -r | head -15<\/code><\/p>\n

… and on our local MAMP web server (of a MacBook Pro) we got<\/p>\n

$ du -a \/ 2> \/dev\/null | sort -n -r | head -15
\n463218232\t\/
\n183397888\t\/Users
\n183393240\t\/Users\/user
\n173735704\t\/Library
\n155636160\t\/Library\/pgAgent
\n139676416\t\/Users\/user\/Desktop
\n139661920\t\/Users\/user\/Desktop\/NS15148
\n109587848\t\/Users\/user\/Desktop\/NS15148\/robertmetcalfe
\n66994504\t\/Library\/pgAgent\/Downloads
\n48401968\t\/Applications
\n44435304\t\/Library\/pgAgent\/Library
\n27955056\t\/Users\/user\/Desktop\/NS15148\/robertmetcalfe\/Downloads
\n27639928\t\/opt
\n26857192\t\/opt\/local
\n26839216\t\/Library\/pgAgent\/VirtualBox VMs
\n<\/code><\/p>\n

… and just to put a little intelligence into this have a look at the “file”<\/a> command as a means to show a file type, and the marvellous “awk”<\/a> integration of all this via its “system()” method …<\/p>\n

$ du -a \/ 2> \/dev\/null | sort -n -r | head -15 | awk -F\"\\t\" '{ print $1, FS, system(\"file \\\"\" $2 $3 $4 $5 \"\\\"\"); }' | grep -v '^[0| ]' | sed '\/:\/s\/\/ ... is a\/g'
\n463218232 \t \/ ... is a directory
\n183397888 \t \/Users ... is a directory
\n183393240 \t \/Users\/user ... is a directory
\n173735704 \t \/Library ... is a directory
\n155636160 \t \/Library\/pgAgent ... is a directory
\n139676416 \t \/Users\/user\/Desktop ... is a directory
\n139661920 \t \/Users\/user\/Desktop\/NS15148 ... is a directory
\n109587848 \t \/Users\/user\/Desktop\/NS15148\/robertmetcalfe ... is a directory
\n66994504 \t \/Library\/pgAgent\/Downloads ... is a directory
\n48401968 \t \/Applications ... is a directory
\n44435304 \t \/Library\/pgAgent\/Library ... is a directory
\n27955056 \t \/Users\/user\/Desktop\/NS15148\/robertmetcalfe\/Downloads ... is a directory
\n27639928 \t \/opt ... is a directory
\n26857192 \t \/opt\/local ... is a directory
\n26839216 \t \/Library\/pgAgent\/VirtualBox VMs ... is a directory
\n<\/code><\/p>\n

If this was interesting you may be interested in this<\/a> too.<\/p>\n