Updated: 16 November 2026 · Applies to: CloudLinux OS servers that still have OptimumCache installed

If yum or dnf stops with a dependency error that names optimumcache (often when it tries to install or update tuned-profiles-cloudlinux), remove OptimumCache. CloudLinux no longer supports it: its documentation lists OptimumCache under deprecated components with the note "OptimumCache is no longer supported". Once the package is gone, the update that failed goes through normally.

What OptimumCache was

According to CloudLinux, OptimumCache was "a de-duplicating file cache optimized specifically for shared hosting": it kept one copy of files that many accounts share, such as WordPress and Joomla core files, in a ploop image. Nothing in a current CloudLinux setup depends on it, so removing it does not affect websites.

1. Check whether it is installed

rpm -q optimumcache

If the output says package optimumcache is not installed, the error comes from something else: read the package name in the error message again and check How to resolve Missing perl module during the packages update or How to Exclude or Skip a Package in yum and dnf Updates.

2. Remove OptimumCache (as root)

These are the steps from CloudLinux's own uninstall guide, run one at a time. First stop the service:

service optimumcache stop

Delete the ploop image that holds the cache:

occtl --delete-ploop

Empty the cache store file:

:>/var/share/optimumcache_store

Remove the package:

yum remove optimumcache

On CloudLinux 8 and later, yum is an alias for dnf, so the same command works there.

3. Reboot if you can

CloudLinux recommends a reboot after removal. According to its documentation, the pfcache= mount options that OptimumCache added disappear by themselves after the reboot. Versions 0.2-11 and later remove the ploop image during the uninstall; if the image could not be unmounted, the clean-up waits for the next reboot. On older versions, removing the RPM did not always delete the ploop image, and CloudLinux says to reboot and delete the leftover ploop files by hand if unmounting fails.

To check that nothing is left mounted after the reboot:

mount | grep pfcache

No output means the cache is fully gone.

4. Run the update again

yum update

The package that was blocked (for example tuned-profiles-cloudlinux) now installs without the dependency error.

If occtl --delete-ploop fails

If the command reports that it cannot unmount the ploop image, a process still has files open on it. CloudLinux's troubleshooting section covers this case; the simplest route is to reboot the server, then run the remaining steps. Uninstalling can also take a long time on a server with a large cache, so let it finish instead of interrupting it.

For other CloudLinux update problems, see If RPM or yum processes hangs on a CloudLinux Server. If you would rather have an engineer clean up the server, use server management or Hire an Expert.

Official documentation: CloudLinux, deprecated components (OptimumCache).

Related services

KVM VPS hosting

NVMe SSD and full root access, with Free Basic Managed Support.

Unmanaged dedicated servers

full root access and free IPMI KVM, with Free Basic Managed Support.

Managed dedicated servers

our engineers look after the server for you, from $135 a month.

Was this answer helpful?

Still stuck? Open a ticket