NoneType object has no attribute run_sack in Plesk error causing trouble? Read to find out how to resolve the issue. 

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Service.

Let’s take a look at how our Support Team recently helped out a customer with the error: NoneType object has no attribute run_sack in Plesk.

How to resolve “NoneType object has no attribute run_sack” in Plesk

If your Plesk Updates Manager is failing on the RHEL-based OS of version 8.5, you have come to the right place. This specific error prevents updating system packages via Plesk > Tools & Settings > Update Settings > Available Updates. Furthermore, we may also receive this corresponding email:

'NoneType' object has no attribute 'run_sack'

Interestingly, the issue does not turn up on the RHEL-based OS of version 8.4.

According to our Support Team, the error is due to issue number #PPPM-13304. It results in the “Plesk Update Manager no longer fails with the “‘NoneType’ object has no attribute ‘run_sack’” error.

Our Support Team has been helping customers with this error on Plesk Obsidian 18.0.39 Update 1 on CentOS 8.5, RHEL 8.5, AlmaLinux OS 8.5, as well as on CloudLinux OS 8.5. One way around the error is to update the server.

However, if that doesn’t work, do not worry, our Support Team has a workaround solution.

Fortunately, the solution to the issue on hand is very simple as long as follow these steps:

1. First, we have to connect to the server through SSH.
2. Next, we will take a backup of the existing /usr/local/psa/admin/sbin/pum_worker file with the following command:

   # cp -a /usr/local/psa/admin/sbin/pum_worker{,.bak}
3. Next, we have to download the pum_worker file on the server. 

   # wget https://plesk.zendesk.com/hc/article_attachments/4410169516946/pum_worker
4. After that, we will replace the old one with the file from the previous step:

   # yes | cp -f pum_worker /usr/local/psa/admin/sbin/pum_worker && chmod 750 /usr/local/psa/admin/sbin/pum_worker

[Looking for a solution to another query? We are just a click away.]

Conclusion

In brief, the skilled Support Engineers at Bobcares demonstrated how to resolve the NoneType object has no attribute run_sack error.