yum start install process and then hangs

Panicked · 06-11-2017, 01:44 PM

.. please help fix yum working on Oracle UEK 6.9

> sudo yum install couchdb
Setting up Install Process
public_ol6_UEK_latest 680/680

.. then nothing, so open another terminal..

> ps aux | grep yum
S+ sudo yum install couchdb
R+ /usr/bin/python /usr/bin/yum install couchdb

... I think R+ means make coffee and try again ...

> ps aux | grep yum
S+ sudo yum install couchdb
D+ /usr/bin/python /usr/bin/yum install couchdb

... I think D+ means post online and ask for help ...

TB0ne · 06-12-2017, 07:03 AM

Quote:

Originally Posted by Panicked

.. please help fix yum working on Oracle UEK 6.9

> sudo yum install couchdb
Setting up Install Process
public_ol6_UEK_latest 680/680

.. then nothing, so open another terminal..

> ps aux | grep yum
S+ sudo yum install couchdb
R+ /usr/bin/python /usr/bin/yum install couchdb

... I think R+ means make coffee and try again ...

> ps aux | grep yum
S+ sudo yum install couchdb
D+ /usr/bin/python /usr/bin/yum install couchdb

... I think D+ means post online and ask for help ...

I actually think that D+ means "Call Oracle Support and ask them, since you're paying for Oracle Linux" (RIGHT?)

But in this case, the D, S, and R can be found by reading the man page on the ps command:

Code:

PROCESS STATE CODES
       D   uninterruptible sleep (usually IO)
       R   runnable (on run queue)
       S   sleeping
       T   traced or stopped
       Z   a defunct ("zombie") process

That said, how long did you wait? Have you tried running the package installer from the GUI, to see what it's doing? Did you change/modify anything recently? Things like this are fairly dependent on python...modify that lately? Can you install any other packages? Some basic diagnostics to try:

"yum --verbose --noplugins" info and "yum clean all" are two good ones to start with. And are you having Internet issues??

Panicked · 06-12-2017, 05:37 PM

Oracle Linux is free without support, which makes it comparable to CentOS. What is the difference between (D+) 'uninterruptable sleep' and a coma?

It is a clean install. I do not have Internet issues. I left it running for hours and it did not unfreeze, which is to be expected of a D+.

Tried this desperate trouble shooting:

1. Added Fedora EPEL* repos and yum sensibly read those, but yum continued to freeze when reading the Oracle repos.
2. Removed Oracle repos, and yum no longer freezes, but this is hardly a solution.

* Fedora orphaned the CouchDB package in the EPEL repo 6 weeks ago

jefro · 06-12-2017, 07:39 PM

Did you update system just after you installed it?

Thoughts only.
Then I'd wonder why your system is unable to either find the correct Oracle linux repo's or why the default repos are wrong. I think I messed up an odd cd install that didn't place any repos in yum one time.

Using Fedora repos is way less than a fix. A test only. I think you know that.

Panicked · 06-12-2017, 08:01 PM

Cannot remember doing yum update, but maybe it froze and I forgot?! :/

Obviously a system wide update is important for security, but I do not know how not doing it could cause errors? I really hope skipping the update was not the cause of error because I have now spent a whole evening compiling various new whizbangs on CentOS7 instead.

Maybe OL7 is good, but first effort with OL6 was off-putting.

scasey · 06-12-2017, 08:23 PM

Maybe the Oracle repos are down? Just a thought...

jefro · 06-12-2017, 08:46 PM

I think I ran Oracle linux in a VM. Seemed good.

scasey · 06-12-2017, 11:32 PM

Quote:

Originally Posted by jefro

I think I ran Oracle linux in a VM. Seemed good.

I meant the yum repositories --or some glitch with them re: couchdb -- some temporary-ish condition.
Mightn't

Code:

yum repolist

provide some information about that to the OP?

Again, just thinkin' out loud...

Panicked · 06-13-2017, 06:20 AM

Every option I tried resulted in yum turning D+, except clean. D+ does not release the yum lock so I was regularly sending a kill -9 PID and deleting the yum lock file.

The only unusual detail about the install was running the UEK 6.x on a VM with VT-x disabled, but I do not think this could impact yum.

Now running CentOS 7.x with VT-x enabled and yum is fine, but couchdb was not in their repo, so ended up compiling source anyway! This kind of computer usage is very inefficient and makes me wish I studied something else.