LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 10-27-2014, 01:02 PM   #1
jyunker
Member
 
Registered: Aug 2009
Posts: 167

Rep: Reputation: 0
yum lock and breaking


I am having a problem with my yum process. I have lost my GUI on rebooting. but that is not the question here.


I reboot only to the command line and get something like:

sh-4.1#

The is no GUI. Now when I run something like a yum update command I get the following:

Another app is currently holding the yum lock; waiting for it to exit ...
The other application is: yum
Memory: 19 M RSS (220 MB VSZ)
Started: Thu Oct 23 15:56:20 2014 - 2:34 ago
State: Running, pid 399

In other words I have a yum lock.



and if I run rpm -qa | grep yum I get the follwing:

root 385 0.0 0.0 6388 660 ? S 12:42 0.00 grep yum


So now i type kill -9 385

and it says bash: kill : 385) - No such process.


Now when I type ps aux | grep yum

I get

root 387 0.0 0.0 6388 660 ? S 12:42 0.00 grep yum

It may have killed process 385 and started 387 or just renamed process 385
to 387. I do not know which.

I want to kill the process since it is hogging my whole computer.

I think that this process have a parent that is preventing me from killing the yum process directly.

If so how do I determine what the yum paraent process is?


Thanks in advance.

R,

jyunker
 
Old 10-27-2014, 01:16 PM   #2
jailbait
LQ Guru
 
Registered: Feb 2003
Location: Blue Ridge Mountain
Distribution: Debian Jessie, Linux Mint 17
Posts: 7,789

Rep: Reputation: 292Reputation: 292Reputation: 292
It is possible that some program issued the yum lock and then failed (or the system crashed) without deleting the yum lock. If that is the case then the yum lock is still set after reboot even though after the reboot you have run no program which issues a yum lock. You can try to delete the yum lock from the command line and then try running yum again.

First find all of the active locks:
find / -iname "*lock*"

Then look at the list of currently active lock files for a lock in a yum directory.

If you find it then delete that lock file, reboot, and try a yum command again. (The reason that I recommend a reboot is to take care of the possibility that for some weird reason yum is automatically running and issuing a lock after every boot.)

-------------------
Steve Stites

Last edited by jailbait; 10-27-2014 at 01:17 PM.
 
Old 10-27-2014, 01:23 PM   #3
EDDY1
LQ Addict
 
Registered: Mar 2010
Location: Oakland,Ca
Distribution: wins7, Debian wheezy
Posts: 6,838

Rep: Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649
Have you tried
Quote:
yum clean all
 
Old 10-27-2014, 01:47 PM   #4
netnix99
Member
 
Registered: Jun 2011
Distribution: redhat, CentOS, OpenBSD
Posts: 298

Rep: Reputation: 98
so far...

Code:
rpm -qa | grep yum 
root 385 0.0 0.0 6388 660 ? S 12:42 0.00 grep yum

kill -9 385
and it says bash: kill : 385) - No such process.
This only killed the grep process for the rpm -qa command you entered. rpm -qa query's the rpm database for installed rpms (in this case, the yum rpm), not the instance of yum.

Then, when you did this:
Code:
Now when I type ps aux | grep yum
root 387 0.0 0.0 6388 660 ? S 12:42 0.00 grep yum
All you are seeing, again, is the GREP process. the YUM process does not appear to be running. In that case, you should look in /var/run for a file called yum.pid. If it exists, delete it, and you should be good to go.
 
Old 10-27-2014, 01:52 PM   #5
John VV
LQ Muse
 
Registered: Aug 2005
Location: A2 area Mi.
Posts: 16,981

Rep: Reputation: 2447Reputation: 2447Reputation: 2447Reputation: 2447Reputation: 2447Reputation: 2447Reputation: 2447Reputation: 2447Reputation: 2447Reputation: 2447Reputation: 2447
--edited--

Last edited by John VV; 10-27-2014 at 01:53 PM.
 
Old 10-28-2014, 09:38 AM   #6
jyunker
Member
 
Registered: Aug 2009
Posts: 167

Original Poster
Rep: Reputation: 0
Changing filesystem from read only to read / write

Oaky, I think that I see the problem now. My Linux filesystem is read only. Therefore it is not possible to get rid of num.pid directly. I will have to first change my Linux filesystem from read only to read write.

I know that the command to do thuis is mount -o remount,rw /dev/hda2/

If my root filesystem is /dev/hda2/


I must use a LiveCD (which I have) to deliver that command. I am not sure what run level that I am in, but I know that it is low and mount is not a command that i can use on my host system.


So in order to do this I must boot from a LiveCD and then chroot over to the system on my hardrive. If I can do this I can change from read to read / write.

The rest seems straighforward.

Again I a in Centos 6.5, 64 bit.

Thanks in advance.

R,

jyunker
 
Old 10-29-2014, 03:32 AM   #7
chrism01
LQ Guru
 
Registered: Aug 2004
Location: Sydney
Distribution: Centos 6.8, Centos 5.10
Posts: 17,254

Rep: Reputation: 2328Reputation: 2328Reputation: 2328Reputation: 2328Reputation: 2328Reputation: 2328Reputation: 2328Reputation: 2328Reputation: 2328Reputation: 2328Reputation: 2328
Actually, you can use the install DVD and select 'Rescue mode' when it boots.
 
Old 10-29-2014, 01:30 PM   #8
jyunker
Member
 
Registered: Aug 2009
Posts: 167

Original Poster
Rep: Reputation: 0
Linux Rescue

I started using the Linux Rescue option, but I stopped. I am not sure how to use it and I did not want to do anything that could not be reversed.

Is there a website that explains Linux Rescue in detail, so I am sure of what I am doing?


Any help appreciated.

Thanks in advance.


R,



jyunker
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Another app is currently holding the yum lock 9nine9 Fedora 28 09-28-2014 03:40 AM
yum lock in fedora Anubhab Linux - Newbie 4 02-07-2013 04:09 AM
deian yum lock [ ERR] Reading state information E: Could not get lock /var/lock/aptit jayakumar01 Linux - Server 1 12-05-2011 12:26 PM
Another app is currently holding the yum lock; waiting for it to exit... Shwick Linux - Newbie 3 07-25-2011 01:02 PM
[SOLVED] How to get rid of yum lock? your_shadow03 Linux - Newbie 1 12-25-2009 01:42 AM


All times are GMT -5. The time now is 09:52 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration