Recent content by PeopleInside

For me the discussion with you ends here. Its a good idea to wait a little before install updates but the intent of this discussion was searching for help. Your replies did not helped me at all. Have a nice day. Fortunately I shared what was working and if you don't agree that it's a good...

At 6 AM Ubuntu run his cronjob to update the system. Plesk run his update too early after this time and uldate may still be in progress then cause the error. Move the Plesk maintenance cronjob to a later time works just for that. I monitored the server resource usage and it's not currently an...

@trialotto for me this problem lasted for weeks, for almost every day. Was starting to be stressful have a server that inform of error every days. What I shared finally here is the result of the investigation and suggestion from Plesk support and seems it worked so, change the Plesk scheduled...

At the end what seems helped is move the cronjob to 6 AM to 14 PM Plesk guide here In the Plesk guide I need select the Ubuntu tab: " (For Debian-based Linux operating systems (Debian, Ubuntu, etc.) "

It's terrible and seems there is not a real solution. For now I'm trying to change the update time but even the support seems unable to find a log that motivate the issue. Seems like a network temporary issue that still disturb me by email ... many different days... sometimes yes, sometimes no.

Unfortunately if I want help and resolve this issue seems I'm forced to contact the Plesk support.

If I run /usr/local/psa/admin/sbin/pum --list --repo-info --json right now no errors on SSH but is two days that in the morning at 6 AM I get a Plesk email of failed update. This is very annoying. On my opinion this is not managed well. I don't see any fix I can apply to resolve this. Maybe...

As I cannot get in touch with Plesk support because it require to me to pay to access the support, as also the Plesk guide here seems have the same error but not the same cause, as... I looked into the /var/log/plesk/install/autoinstaller3.log, I was able to find some row related to the 13...

Hi, the issue start to be again present since different days (2). var/log/plesk/systemupdatestool.log 2025-08-13 06:26:04 INFO: pum completed successfully 2025-08-13 06:26:05 INFO: pum is called with arguments: ['--check'] 2025-08-13 06:26:09 INFO: pum is called with arguments: ['--list'...

Hi Sebahat, thank you for your kind reply and for your time. I hope your day is going well! I will try and see, for now the error has been stopped but can happen again in the future as maybe Plesk run some update when is running other update. Thank you!

After this error I run: ps aux | grep -E 'pum|plesk' to check if some process was locking the update. AI helped to understand the result and no process was locking the update. I checked also for zombie process sudo lsof /var/lib/dpkg/lock-frontend sudo lsof /var/lib/apt/lists/lock sudo lsof...

The error can be reproduced using the command: /usr/local/psa/admin/sbin/pum --list --repo-info --json Result: 2025-08-02 11:00:20 INFO: pum is called with arguments: ['--list', '--repo-info', '--json'] 2025-08-02 11:00:20 ERROR: Update operation was locked by another update process (Plesk...

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: I searched on the Internet for a solution but I was unable to fix and find a solution. Could you please help me? IF I run apt-get...

Maybe I found this: #su pleskusername # echo "alias php='/opt/plesk/php/8.4/bin/php'" >> ~/.bashrc then exit and login again by ssh. php -v seems now works also for the plesk user