/var/cache/yum/epel is 2GB big

[veronicabend]

I need to make room in the /var partition, which is 20GB big in total, and I found out that this folder /var/cache/yum/epel is 2GB big. Is it safe to remove its contents? I tried "yum clear all" as I found in some other post, but nothing happened.

Thanks.

 

[cPanelTristan]

Do you have epel repository enabled for yum? That isn't a default repo but one you would have added at a later date.

As for "yum clear all", you would instead run "yum clean all"

 

[veronicabend]

Thanks for your help.

I tried "yum clean all", but the folder is still 2.1GB big.

When I run it, though, this was the output:

Loading "security" plugin
Loading "rhnplugin" plugin


Repository epel is listed more than once in the configuration


What should I do? I have not manually done anything about an epel repository.


This seems to have something to do with sqlite. Files in the folder are like this:

-rw-r--r-- 1 root root 13791232 Mar 29 00:18 e96c973c914fbb660a3de02f1401820bbfb34feb-primary.sqlite
-rw-r--r-- 1 root root 13742080 Feb 21 01:19 ef2f2c13a7ff747dafc39c2e7005a48e78fcd108-primary.sqlite
-rw-r--r-- 1 root root 13575168 Nov 27 22:18 efb313b05aa69fc5830083512b560af1f9a68103-primary.sqlite
-rw-r--r-- 1 root root 13388800 Aug 24 2011 f49912e6acf9a488763b5431657aade164e49f1a-primary.sqlite
-rw-r--r-- 1 root root 13661184 Dec 28 22:18 f546d6bab8d07965d8c35bbf9e7bdc41f4728499-primary.sqlite
-rw-r--r-- 1 root root 13589504 Nov 24 19:18 f5b8ce49275383f576e8c12e9434b50e377ffa04-primary.sqlite
-rw-r--r-- 1 root root 13787136 Mar 16 02:28 f8089a317a988105a41684c8f92c0e16873c3502-primary.sqlite

Thanks again for your help.

 

[cPanelTristan]

epel is not a default repository, so someone added it to the machine. It doesn't come with the base installation of CentOS or RHEL. I cannot state what to do with the files, since those aren't the default files for the regular repos. If you choose to remove them, that is going to be up to you. I suggest asking your provider or datacenter, since any issues that occur due to these files being removed need to be the liability of someone who helps manage the server.