Question Problem with Update Plesk and System Package

[andreagr]

Hi, i've a Plesk 17.0.17 with update #30.
From some days i've the error on plesk autoupdate :

Execution failed.
Command: autoinstaller
Arguments: Array
(
[0] => --select-product-id
[1] => plesk
[2] => --select-release-current
[3] => --upgrade-installed-components
[4] => --include-components-from-class
[5] => aspect=panel
)

Details: WARNING: Ignored deprecated parameter in Plesk Installer's configuration file: 'SOURCE_TYPE' = 'network'

BUSY: Update operation was locked by another update process.

If i check with ps aux | grep install
i've two process:

root 9130 0.0 0.0 140460 19300 ? S 14:54 0:00 /usr/local/psa/admin/bin/autoinstaller --service-mode --enable-xml-output --ssl-cert /usr/local/psa/admin/conf/httpsd.pem --branch release,stable --web-interface --with-ssl --disable-browser
root 9131 0.0 0.0 112988 3352 ? S 14:54 0:00 /usr/local/psa/admin/bin/autoinstaller --service-mode --enable-xml-output --ssl-cert /usr/local/psa/admin/conf/httpsd.pem --branch release,stable --web-interface --with-ssl --disable-browser

But if i want to update the system with yum update this is the error:

Plugin enabled:fastestmirror
Lock /var/run/yum.pid attivo: another process in block with pid 3984.
Other Application ?: pum_worker
Memory : 38 M RSS (911 MB VSZ)
Start: Wed Aug 16 12:03:14 2017 - 3:19:48
Status : Waitins, pid: 3984

If i do
ps aux | grep pum

root 3984 0.0 0.0 932736 38576 ? S 12:03 0:00 /usr/bin/python -Estt /usr/local/psa/admin/sbin/pum_worker --simulate --json -- bind bind-libs bind-utils ca-certificates cups-libs glibc glibc-common glibc-devel glibc-headers httpd httpd-tools initscripts mod_ssl nss nss-sysinit nss-tools plesk-php70 plesk-php70-bcmath plesk-php70-cli plesk-php70-dba plesk-php70-enchant plesk-php70-fpm plesk-php70-gd plesk-php70-imap plesk-php70-intl plesk-php70-ldap plesk-php70-mbstring plesk-php70-mcrypt plesk-php70-mysql plesk-php70-odbc plesk-php70-opcache plesk-php70-pdo plesk-php70-pear plesk-php70-pgsql plesk-php70-process plesk-php70-pspell plesk-php70-snmp plesk-php70-soap plesk-php70-tidy plesk-php70-xml plesk-php70-xmlrpc procps selinux-policy selinux-policy-targeted sudo

what is this process?
It's safe to force kill it?

I can't update anything.

Thanks

 

[UFHH01]

Hi andreagr,

Details: WARNING: Ignored deprecated parameter in Plesk Installer's configuration file: 'SOURCE_TYPE' = 'network'

Pls. note, that this is JUST a warning and nothing which could prevent the update/upgrade procedure.

But...

BUSY: Update operation was locked by another update process.

... states quite clear, that there is another process running, which prevents the usage of another "autoinstaller" - instance. Pls. read and follow for example:

=> Launching Plesk autoinstaller fails: Update operation was locked by another update process​

what is this process?

Both processes shoudl be killed

root 9130 0.0 0.0 140460 19300 ? S 14:54 0:00 /usr/local/psa/admin/bin/autoinstaller --service-mode --enable-xml-output --ssl-cert /usr/local/psa/admin/conf/httpsd.pem --branch release,stable --web-interface --with-ssl --disable-browser
root 9131 0.0 0.0 112988 3352 ? S 14:54 0:00 /usr/local/psa/admin/bin/autoinstaller --service-mode --enable-xml-output --ssl-cert /usr/local/psa/admin/conf/httpsd.pem --branch release,stable --web-interface --with-ssl --disable-browser

It's safe to force kill it?

Yes! Otherwise, Plesk wouldn' t recommend the "killing" at the above mentioned KB - article.​

 

[andreagr]

I've follow the kb but when execute strace i've this output:

Process 9130 attached
restart_syscall(<... resuming interrupted call ...>) = 0
poll([{fd=7, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND}], 1, 1000) = 0 (Timeout)
poll([{fd=7, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND}], 1, 1000) = 0 (Timeout)
poll([{fd=7, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND}], 1, 1000) = 0 (Timeout)
poll([{fd=7, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND}], 1, 1000) = 0 (Timeout)
poll([{fd=7, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND}], 1, 1000) = 0 (Timeout)
poll([{fd=7, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND}], 1, 1000) = 0 (Timeout)
poll([{fd=7, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND}], 1, 1000^CProcess 9130 detached
<detached ...>
[root@server2 ~]# strace -p 9131
Process 9131 attached
read(12,

So the first is stucked but the second process no.. is safe to kill both process?

 

[UFHH01]

Hi andreagr,

So the first is stucked but the second process no.. is safe to kill both process?

Still ( as already answered above ): Yes.

Otherwise, Plesk wouldn' t recommend the "killing" at the above mentioned KB - article.

 

[andreagr]

Ok i've kill all process and all process for yum.
I've done yum clean all and yum update.
But the shell is:

yum update
Freeing read locks for locker 0x1c7: 26279/140657389889280
Freeing read locks for locker 0x1c8: 26279/140657389889280
Freeing read locks for locker 0x1c9: 26279/140657389889280
Freeing read locks for locker 0x1ca: 26279/140657389889280
Freeing read locks for locker 0x1cb: 26279/140657389889280
Plugin abilitati:fastestmirror
Impostazione processo di aggiornamento
Determining fastest mirrors
epel/metalink | 19 kB 00:00
* base: fr.mirror.babylon.network
* epel: fr.mirror.babylon.network
* extras: fr.mirror.babylon.network
* updates: fr.mirror.babylon.network

and nothing appears.
The link fr.mirror.babylon.network is reachable from the server but I can't update centos 6.

 

[UFHH01]

Hi andreagr,

Freeing read locks for locker 0x1c7: 26279/140657389889280
Freeing read locks for locker 0x1c8: 26279/140657389889280
Freeing read locks for locker 0x1c9: 26279/140657389889280
Freeing read locks for locker 0x1ca: 26279/140657389889280
Freeing read locks for locker 0x1cb: 26279/140657389889280

This could indicate a lack of memory at your server/vps. Consider to resolve this first, before you continue with any update/upgrade procedure.
( One solution could be to shut down services with lots of memory usage. Try to shut down one service after the other and keep trying to upgrade/update afterwards - after a successfull "yum" update/upgrade, pls. don't forget to restart the manually shut down services )