On Tue, 30 Jul 2013 21:58:13 -0700
Dale Snell <[email protected]> dijo:
>> sudo yum install qt4-dev-tools libqt4-opengl-dev libqtwebkit-dev
>If you're using yum, I assume *cough*cough* that you're using a
>Red Hat/Fedora based system of some sort. In that case, the
>development packages are labeled *-devel, not *-dev. The latter
>is Debian/Ubuntu.
Thanks for the tip. Yes, the instructions are for Ubuntu, but I'm using
Fedora. Most of the time I can just substitute 'yum' for 'apt-get,' but
apparently not willy-nilly.
>> It executed without error, but after 15 minutes I assumed it was
>> hung, so I killed it with Ctrl-Z.
>
><Ctrl-Z> _suspends_ a program, it doesn't kill it. You can do
>things like run the ever-popular program "foo", then suspend it
>with <ctrl-z>. After that, you can put it in the background with
>"bg %1" or back into the foreground with "fg %1". (The job number
>[%1, here] is reported when you suspend the job.)
I went back and noted that my suspend command reported number 3, so I
tried 'fg %3,' and that brought it out of the background. Then I did a
proper Ctrl-c, but yum is still running.
>The kill command wants a signal with which to chastise the errant
>program. -TERM should abort most programs. If not, the old
>standby of -KILL should do it. E.g., "kill -KILL 20774". You
>only need the sudo if the program isn't being run by you.
>> I can't do anything until I figure out how to drive a stake through
>> yum's heart. Any suggestions?
>$ ps aux | grep -i yum
>(returned info)
>$ kill -TERM <yum_process_number>
I tried kill -9 and got nowhere, but the 'ps aux | grep -i yum' command
produced a fair list of processes. I killed them all, but 20774 was
still running. Finally I used 'sudo kill -KILL 20774.' It executed
without error and Yum is finally gone. Apparently -KILL is stronger
than -9, or at least here it was.
And having succeeded in killing yum, I now discover that package
database is apparently corrupted:
[jjj@Devil8 ~]$ sudo yum install qt4-devel-tools
error: rpmdb: Thread/process 20774/139979828111104 failed: Thread died
in Berkeley DB library error: db4 error(-30974) from dbenv->failchk:
DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open
Packages index using db4 - (-30974) error: cannot open Packages
database in /var/lib/rpm CRITICAL:yum.main:
Error: rpmdb open failed
I tried 'sudo yum clean all' hoping that it would fix the database, but
it did not. Then I tried launching Yumex, hoping that the GUI would
point me in the right direction. It failed after displaying:
YUM: error: rpmdb: Thread/process 20774/139979828111104
failed: Thread died in Berkeley DB library 22:34:20 :
YUM: error: db4 error(-30974) from dbenv->failchk: DB_RUNRECOVERY:
Fatal error, run database recovery 22:34:20 :
YUM: error: cannot open Packages index using db4 - (-30974) 22:34:20 :
YUM: error: cannot open Packages database in /var/lib/rpm 22:34:20 :
YUM: Traceback (most recent call last): 22:34:20 :
YUM: File "/usr/share/yumex/yum_childtask.py", line 66, in <module>
22:34:20 :
YUM: my = YumServer(debuglevel, plugins, offline, repos, yum_conf)
22:34:20 :
YUM: File
"/usr/lib/python2.7/site-packages/yumexbackend/yum_server.py", line
188, in __init__ 22:34:20 : YUM: self.doLock() 22:34:20 :
YUM: File
"/usr/lib/python2.7/site-packages/yumexbackend/yum_server.py", line
261, in doLock 22:34:20 :
YUM: yum.YumBase.doLock(self) 22:34:20 :
YUM: File "/usr/lib/python2.7/site-packages/yum/__init__.py", line
1953, in doLock 22:34:20 :
YUM: if self.conf.uid != 0: 22:34:20 :
YUM: File "/usr/lib/python2.7/site-packages/yum/__init__.py", line
1007, in <lambda> 22:34:20 :
YUM: conf = property(fget=lambda self:
self._getConfig(), 22:34:20 :
YUM: File "/usr/lib/python2.7/site-packages/yum/__init__.py", line
335, in _getConfig 22:34:20 :
YUM: startupconf = config.readStartupConfig(fn, root, releasever)
22:34:20 :
YUM: File "/usr/lib/python2.7/site-packages/yum/config.py", line
1000, in readStartupConfig 22:34:20 :
YUM: startupconf.distroverpkg) 22:34:20 :
YUM: File "/usr/lib/python2.7/site-packages/yum/config.py", line
1151, in _getsysver 22:34:20 :
YUM: raise Errors.YumBaseError("Error: " + str(e)) 22:34:20 :
YUM: yum.Errors.YumBaseError: Error: rpmdb open failed
I'm not sure what all this means. With apt-get you could do 'apt-get
update' and it would go out to the repositories and fix everything up.
I tried man yum, but I couldn't find an equivalent.
Yum and broken databases will have to wait for tomorrow. Time for bed.
Thanks to all who offered suggestions.
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
