Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

We have a virtual dedicated server with a fairly large amount of traffic. We use GoDaddy using CPanel. We have 10GIG of space of which about 80% is not our content but logs and server utilities.

Godaddy support is evasive and they are trying to encourage us to migrate to new service with 15GIG.

Reviewing the large files we found the following:

We have a ton old TMP files at this directory. /public_html/files/TMP/FILE_PERSISTANCE_PROVIDER: (no access)

some large files in these directories.

/usr/local/apache/logs/ - suphp_log (220M) - access_log (7M) - error_log (5M)

/usr/local/apache/domlogs/ (no access)

/usr/local/cpanel/ (no access)

/usr/local/cpanel-rollback

/tmp

Questions:

  1. What can we safely delete or truncate?
  2. How can we change permissions on files with no access to delete?
  3. Is there utility to monitor and clean up temp files
  4. Other files/programs that we can delete?

    thanks!

share|improve this question
    
i would say you should probably leave any files you aren't sure about alone. –  Jason Jul 16 '10 at 18:08
1  
Be firm with the support: tell them you payed for 10gb, and you want it. –  Tom H Jul 16 '10 at 18:11
    
Archived access logs could be located in the tmp folder. Access logs should be downloaded periodically - they could get huge. But, like Jason says, you need to be sure what is what. Your service provider should be able to tell you. (Just seen Vitor Py's comment (+1), and as if by magic there's an ad in the side panel!) –  w3d Jul 16 '10 at 18:13
    
Jason - that is why we are asking! Tom - there is obviously some overhead utility software and useful log and temp files that cuts down on contracted amount. –  TMP File guy Jul 16 '10 at 18:14
1  
possible duplicate of Our GoDaddy web server is drowning in temp files!! –  Warner Jul 16 '10 at 18:40

1 Answer 1

First, I would ask to see if you can run cron jobs on your server. If not, then there might not be any hope to really solve the issue, because what I believe you really need is a way to rotate your logs.

Second, the best way to clear out any files is to login in a shell (if you can), and pipe /dev/null into one of the files that we know is safe. The reason why we do this is so that we effectively clear out the disk space, even if there's a program that still has a "reference" on the file (even if you can delete the file normally through FTP or even by doing a "rm /path/to/file", if there's a program that is using that file, the file will still actually be on the hard disk until the program shuts down.)

Third, if I were to wager, suphp_log might be useless from your perspective; however, confirm with GoDaddy to see if that's a file that they are interested in.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.