• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved yum problem

Noam Harel

Regular Pleskian
Hi

i was trying to remove nano after someone was trying to make nano colorful and was unsuccessful. then i got these errors when trying to do "yum remove nano":

Warning: RPMDB altered outside of yum.
** Found 3 pre-existing rpmdb problem(s), 'yum check' output follows:
plesk-management-node-12.5.30-cos6.build1205150826.19.x86_64 has missing requires of psa-vhost >= ('0', '12.5.30', None)
plesk-service-node-utilities-12.5.30-cos6.build1205150826.19.x86_64 has missing requires of psa-logrotate
plesk-web-hosting-12.5.30-cos6.build1205150826.19.x86_64 has missing requires of psa-vhost >= ('0', '12.5.30', None)

please your kind help in a detailed solution

Noam
Interspace LTD
 
this is the result:

warning: waiting for transaction lock on /var/lib/rpm/.rpm.lock

it's stuck in this situation
 
Use fuser to see which process is locking the file:

# fuser /var/lib/rpm/.rpm.lock

you will see something like that:

/var/lib/rpm/.rpm.lock: 23969

Then look for 23969 process

# ps waux |grep 23969

and kill this proceess if necessary. After that repeat removing nano again.
 
thank you for the reply

when i do :
# fuser /var/lib/rpm/.rpm.lock
the result is:
/var/lib/rpm/.rpm.lock: 6770

which means the PID is 6770.
and when i do:
ps waux |grep 6770

i get:
# ps waux | grep 6770
root 2196 0.0 0.0 103248 872 pts/0 S+ 06:34 0:00 grep 6770
root 6770 0.0 1.8 278084 72044 ? S 03:09 0:01 /usr/bin/python -Ett /usr/local/psa/bin/yum_install -e PHP_5_2_17-dist -e PHP_5_2_17-thirdparty -e PHP_5_3_29-dist -e PHP_5_3_29-thirdparty -e PHP_5_4_45-dist -e PHP_5_4_45-thirdparty -e PHP_5_5-dist -e PHP_5_5-thirdparty -e PHP_5_6-dist -e PHP_5_6-thirdparty -e PHP_7_0-dist -e PHP_7_0-thirdparty -e PLESK_12_5_30-dist -e PLESK_12_5_30-thirdparty -e PMM_0.1.10-dist -e PMM_0.1.10-thirdparty -e PPB_12_5_29-dist -e PPB_12_5_29-thirdparty -e SITEBUILDER_12_5_30-dist -e SITEBUILDER_12_5_30-thirdparty -p -l /var/log/plesk/install/autoinstaller3.log -r fail2ban -r plesk-fail2ban-configurator -r psa-watchdog --tries=3

but when i try to kill 2196 or 103248 or 6770 or 278084 or 72044, with this command:
kill 15 -p <PID>

i get:
-bash: kill: -p: arguments must be process or job IDs
-bash: kill: (72044) - No such process

obviously im dong something wrong

please your kind help

Noam
 
Hi Noam Harel,

a general "KILL" - command is used with for example:

kill -9 PID-NUMBER​

The "PID-NUMBER" is ALWAYS the first number, which you can see, when you list your processes with a "ps" - command.
 
Last edited by a moderator:
Back
Top