• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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