Issue run-parts: /etc/cron.daily/pleskupdate exited with return code 1

[mitches]

Server operating system version

Ubuntu 22.04.3 LTS

Plesk version and microupdate number

Plesk Obsidian 18.0.58

Hi

after updating to Plesk Obsidian 18.0.58 on Ubuntu 22.04.3 LTS I get the error message during a cronjob:
run-parts: /etc/cron.daily/pleskupdate exited with return code 1

I have no idea what the cause of this is - but it only occurs after the update. Does anyone know how to fix this?

Micha

 

[Peter Debik]

Please check /var/log/plesk/install/autoinstaller3.log for errors that occured during the previous update. It may not have completed as expected.

 

[mitches]

Hi Peter,

uh, this log is huge,

but i can see this tonight:

autoinstaller: read output of apt-cache policy
[2024-01-16 00:34:13.631754] Warning: not connected 'multiverse' repository section
[2024-01-16 00:34:13.631840] repository: Get brief packages info for all sources
[2024-01-16 00:34:13.631864] Checking for installed in extension catalog packages
[2024-01-16 00:34:13.631950] autoinstaller: read output of /usr/local/psa/bin/extension --list
[2024-01-16 00:34:13.854129] Detected installed extensions: 'composer' 'firewall' 'git' 'laravel' 'letsencrypt' 'nodejs' 'sslit'
[2024-01-16 00:34:13.854336] DebianAPTConfigurator:repareAvailablePackagesList()
[2024-01-16 00:34:14.850369] Detecting installed product components.
[2024-01-16 00:34:14.850514] (update package names cache)
[2024-01-16 00:34:14.851103] Component plesk/panel: mode up2date, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.851181] Component plesk/bind: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.851545] Component plesk/postgresql: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.851662] Component plesk/fail2ban: mode up2date, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.851740] Component plesk/l10n: mode up2date, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.851825] Component plesk/git: mode up2date, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.851895] Component plesk/resctrl: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.851959] Component plesk/pmm: mode error, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.852040] Component plesk/sitebuilder: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.852132] Component plesk/proftpd: mode up2date, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.852206] Component plesk/webalizer: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.852321] Component plesk/awstats: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.852469] Component plesk/modsecurity: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.852630] Component plesk/passenger: mode up2date, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.852700] Component plesk/ruby: mode error, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.852764] Component plesk/nodejs: mode up2date, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.853115] Component plesk/gems-pre: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.853225] Component plesk/mod_fcgid: mode up2date, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.853295] Component plesk/mod_perl: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.853367] Component plesk/mod_python: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.853464] Component plesk/apache: mode up2date, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.853784] Component plesk/php8.3: mode up2date, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.854098] Component plesk/php8.2: mode up2date, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.854174] Component plesk/php8.1: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.854264] Component plesk/php8.0: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.854339] Component plesk/php7.4: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.854451] Component plesk/php5: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.854538] Component plesk/nginx: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.854734] Component plesk/horde: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.854812] Component plesk/roundcube: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.854879] Component plesk/kav: mode error, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.854944] Component plesk/drweb: mode error, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.855021] Component plesk/spamassassin: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.855129] Component plesk/postfix: mode up2date, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.855272] Component plesk/qmail: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.855365] Component plesk/msmtp: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.855544] Component plesk/dovecot: mode up2date, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.855719] Component plesk/courier: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.855817] Component plesk/mysql-sys: mode up2date, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.855901] Component plesk/config-troubleshooter: mode install, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.855973] Component plesk/psa-firewall: mode up2date, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.856042] Component plesk/wp-toolkit: mode error, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.856110] Component plesk/advisor: mode error, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.856180] Component plesk/xovi: mode error, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.856258] Component plesk/imunifyav: mode error, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.856329] Component plesk/sslit: mode up2date, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.856402] Component plesk/letsencrypt: mode up2date, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.856470] Component plesk/repair-kit: mode error, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.856542] Component plesk/composer: mode up2date, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.856612] Component plesk/monitoring: mode error, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.856679] Component plesk/log-browser: mode error, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.856750] Component plesk/ssh-terminal: mode error, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.856828] Component plesk/site-import: mode error, installed_buildtime=0, available_buildtime=0
[2024-01-16 00:34:14.856897] Component plesk/sitejet: mode error, installed_buildtime=0, available_buildtime=0

 

[Peter Debik]

... for errors that occured during the previous update ...

previous = not the current transactions, but transactions in the past.

 

[Liwindo]

I have the same issue. Seems to be a bug. The funny thing is that the latest patch was installed automatically anyway. In autoinstaller3.log I couldn't identify any errors.

 

[derda]

Same issue here. The email comes in every night now.
If I run the content of /etc/cron.daily/pleskupdate manually, it goes through without errors.

 

[Liwindo]

Hi @Peter Debik, is there a way to supress the mail generation until the issue got fixed?

 

[Peter Debik]

Did you contact support so that it can be investigated if there is an issue to fix? Maybe it is something that results from a bad system configuration?

 

[Olray]

For a few weeks I have the same problem with my Strato root server. Fun fact: When running the command manually there is no error but a message that claims the newest product and the selected components are already installed. ("Die neueste Produktversion und alle ausgewählten Komponenten sind bereits installiert. Die Installation wird nicht fortgesetzt.")

The app /opt/psa/admin/sbin/pleskupdate should return an error code of 0 (zero) and no output to the error console if the update is successful, even if there is no action needed.

The Plesk install is provided by Strato (preinstalled on my root server). It's possible that Strato changed settings to automate this installation which in return causes these problems. They also have set their own update server (ftp://ftp.stratoserver.net/pub/plesk/*).

 

[Olray]

is there a way to supress the mail generation until the issue got fixed?

Yes, you could change the /etc/cron.daily/pleskupdate (line 3) to the following:

/opt/psa/admin/sbin/autoinstaller --select-product-id plesk --select-release-current --reinstall-patch --install-component base 2>&1 /dev/null

but I strongly suggest to leave it as is, because the /dev/null black hole will eat every error, even critical ones.
And plesk will not revert this script by itself when the problem is fixed.

 

[Peter Debik]

You can comment that line out. It is a Strato invention and not part of the Plesk installation. Plesk is in touch with them to clarify why it was set on their servers. Our current findings however show that it is not needed and rather counterproductive.

 

[Olray]

Thank you for the clarification. For us Strato customers it is impossible to judge which parts of the system belong to Plesk, because we get the root servers with a ready installation.

 

[Peter Debik]

Yes, that is a problem, especially when the filename sounds so Plesk-like. On the other hand, Plesk cannot interfere with things that a provider installs. Who knows why a provider does it, so after all the provider needs to fix this.

 

[Vendito24]

Hi. Any news for Strato users? Still the same error here again this morning.

 

[Peter Debik]

Maybe you could contact Strato support on it?

 

[wasiwarez]

Hi,

I'm waiting for a solution as well. I don't think that Strato will help here as the issue occurs on root servers. They only provide the server. The installaton and administration has to be done by the customer.

Regards,
wasiwarez.net

 

[Peter Debik]

Did you actually check whether you have /etc/cron.daily/pleskupdate with the "/opt/psa/admin/sbin/autoinstaller --select-product-id plesk --select-release-current --reinstall-patch --install-component base 2>&1 /dev/null" line as described above? Can you edit the file and remove that line?

 

[wasiwarez]

I understand that this will only suppress the errors, doesn't it? The daily email doesn't bother me. I would rather wait for a clean solution to solve this issue. Maybe Strato will do something about it in the future, as you contacted them about it.

 

[mxk]

I had the same issue with a root server from Strato. For analysis I have executed the script /etc/cron.daily/pleskupdate directly. Most time the response code was 0, so there was not a directly problem with it. But when I have used run-parts --report /etc/cron.daily, what is used by the server to start automatically all scripts in this directory, I have received the annoying mail with the info "run-parts: /etc/cron.daily/pleskupdate exited with return code 1". A directly start of /etc/cron.daily/pleskupdate afterwards have then also finished with return code 1.

I have noticed the message "Update operation was locked by another update process." in the autoinstaller3.log. Maybe there are some other scripts in /etc/cron.daily, that are blocking something for a short time?!

So I have added a simple sleep to the pleskupdate script, what at first glance solved the issue on my server.

This is the current script:

#!/bin/sh
# Plesk autoinstaller
sleep 120
/usr/local/psa/admin/sbin/autoinstaller --select-product-id plesk --select-release-current --install-component base >/dev/null 2>&1

 

[Kloptor]

@mxk thx a lot, where exactly do i find that script?

still does not seem that strato will fix that problem anymore so u would help a lot of us i believe