Resolved There was an issue with updating system packages and third-party components. pum is called with arguments: ['--list', '--repo-info', '--json']

[trialotto]

@PeopleInside and @GerdSchrewe

Gentlemen!

In a sense, you are both right.

The problem here is that there might be workarounds for a solution that does not exist ...... and "setting cronjobs at different times", "waiting for new updates", "ignoring error messages from Plesk package manager" and so on ........ are all reasonable workarounds, in the absence of a viable solution!

Somethings might not be changed by Plesk admins, like errors in the apt sources lists - they are frequently and consistently present : one can solve this, until a new update or some other administrative action overrides the (manual) adjustments.

Something might be change by Plesk admins - for instance, removing Imunify will (more than) halve the error messages of Plesk package manager.


In summary, we are forced to work with the workaround we individually prefer, due to the lack of viable solutions.

This particular thread has added value, given the fact that most of the issues with Plesk package manager can be resolved by Plesk.

So, please do not stop the discussion - just post and report the issues that you encounter with updates!


Kind regards....

 

[greedysoul]

I see the same for a week now. There is no problem updating with apt-get. Also when I run the repo list I get the json data and no errors.

 

[PeopleInside]

Hi greedysoul,
I'm no more using Plesk currently, however when I had this issue the solution was try a different Plesk cron time.

Resolved - There was an issue with updating system packages and third-party components. pum is called with arguments: ['--list', '--repo-info', '--json']

Hi, I hope this message finds you well. Since different days I'm getting an email from Plesk that indicate issues on updating third-party components. The email say: There was an issue with updating system packages and third-party components Reason: 2025-08-02 06:26:21 INFO: pum is called with...

talk.plesk.com

Plesk guide here

 

[greedysoul]

Thanks, I'll try that and see if it helps.

 

[trialotto]

Thanks, I'll try that and see if it helps.

@greedysoul

The workaround suggested by @PeopleInside should work, but it still is not a solution - it is a mere workaround of an issue.

An alternative workaround is to set your system time one hour later or earlier : this barely has impact on your system, but it will resolve the PUM issue in a more stable and reliable way, without the need to mess with cron jobs or cron settings.

After all, the disadvantage of changing cron jobs / cron settings is that you essentially "customize" config and that might become an issue in the future.

System time can simply be checked and switched in Plesk GUI.


Nevertheless, despite of all workarounds imagineable, one cannot solve PUM issues that are related to repository failures.

In most cases, PUM issues arise with a temporary failure of a remote repository - these issues are often resolved with 1 or 2 days : have patience!

In some cases, PUM issues arise due to notorious repositories, like that of Imunify, or the PUM issues are related to badly coded extensions (again, Imunify).

Most workarounds will not work if PUM issues are related to notorious repositories or badly coded extensions.

In the latter case, just report a bug......... and keep your fingers crossed that the issue will be resolved quickly.


In essence, if the repository maintainer or (not so good) code developer is in denial, one can do nothing about those PUM related issues.

However, in most cases, PUM notifications might suggest that there is an issue, but there actually is not : updates work fine, with 1 or 2 exceptions.

The latter is nothing to worry about .......... it is only something "to check" : if you see "other packages" being updated, all is fine.


Kind regards....