All zypper commands seem to work correctly, except update (and install). It hangs at the installation step, and doesn’t die.
It hangs after all this (hangs meaning nothing happens for ~4hours):
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following package is going to be upgraded:
expat
Overall download size: 53.0 K. No additional space will be used or freed after the operation.
Continue? [YES/no]: YES
Retrieving package expat-2.0.1-88.16.1.x86_64 (1/1), 53.0 K (149.0 K unpacked)
Retrieving delta: ./rpm/x86_64/expat-2.0.1-88.15_88.16.1.x86_64.delta.rpm, 8.0 K
Retrieving: expat-2.0.1-88.15_88.16.1.x86_64.delta.rpm [done]
Applying delta: ./expat-2.0.1-88.15_88.16.1.x86_64.delta.rpm [done]
Installing: expat-2.0.1-88.16.1 [0%]
Double ctrl-C kills the foreground process but there is the following rpm still running (which can be kill -9’ed only)
> Applying delta: ./expat-2.0.1-88.15_88.16.1.x86_64.delta.rpm [done]
>
> My version details are:
> # cat /etc/issue
> Welcome to openSUSE 11.1 - Kernel \r (\l).
this may be a stupid observation/question (if so, please excuse my
ignorance, for i can’t see the answer to my Q in your post)…the
package to be installed is for a 64 bit system, is yours?
if yours is 64, then maybe try installing expat via YaST…and, if
that works ok you can assume something is flaky in zypper, and use
YaST to ‘update’ all currently installed yast bits (just right click
the box to the left of each piece and select the ‘update’
icon…then press accept…that should repair any funny bits…(some
say to first delete then install…you pick, that may be better…)
Sorry for triple post but here is another bit of information, fwiw.
I thought I lost this, but the terminal where I first observed this problem was still open. It reads:
$ zypper up python
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following package is going to be upgraded:
python
Overall download size: 268.0 K. After the operation, additional 673.0 K will be used.
Continue? [YES/no]: YES
Retrieving package python-2.6.0-2.21.1.x86_64 (1/1), 268.0 K (1.1 M unpacked)
Retrieving delta: ./rpm/x86_64/python-2.6.0-2.19_2.21.1.x86_64.delta.rpm, 172.0 K
Retrieving: python-2.6.0-2.19_2.21.1.x86_64.delta.rpm [done]
Applying delta: ./python-2.6.0-2.19_2.21.1.x86_64.delta.rpm [done]
Installing: python-2.6.0-2.21.1 [error]
Installation of python-2.6.0-2.21.1 failed:
(with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Command was killed by signal 9 (Killed).
Abort, retry, ignore? [A/r/i]: Killed
where, of course, I initiated the kill after several hours of waiting.
> PID TTY STAT TIME COMMAND
> 1 ? Ss 0:02 init [3]
<snip>
all above my head…sorry…
usually if there is a problem with yast it can be repaired with
zipper, or a problem with zipper is often repairable with yast…but,
when both are broke, and thousands and thousands are not, one has to
wonder what happened to yours!
is this a new install? or did it work for months and suddenly break?
(what did YOU do just before it broke?)
which version did you install? 11.1 or what??
what kinda hardware you on? did it run the openSUSE Live CD flawlessly?
how did you install? where did you get the install media?
downloaded–from where, opensuse.org or some other place? did you
md5sum check the iso prior to buring the disk? was it 100% perfect?
did you check the disk after burning also? any problems during the
install (any warnings you ignored?)
speak please, is very hard to guess which way to go to repair BOTH
zypper and yast on an unknown version, on unknown hardware with some
strange sort of unknown situation…
are you trying to run in a VM? which, what version, what is the host
OS/version? so many unanswered questions and i can’t get my crystal
ball tuned just right…
I posted all relevant versions before. Should I post more? What else is relevant, I don’t know.
This is healthy installation, and zypper worked fine before. Sorry if this wasn’t that obvious.
Yes, a crystal ball would have been useful, and I am glad to find out you don’t have one,
… or what else could be useful is one of you out there might have observed similar symptoms and got a solution, or advice on where to look. However arbitrary, might work for me as well.
Perhaps a suggestion of “check this, check that” type could help. I don’ know I am guessing here, but could it be some PAM stuff (if so, what to reset/disable etc?), some corrupt DB (which?), or any logs that might indicate what is wrong (where?). You know, that kind of advice would really help here…
# cd /var/cache/zypp/packages/repo-update/rpm/x86_64
# ls
expat-2.0.1-88.16.1.x86_64.rpm python-2.6.0-2.21.1.x86_64.rpm subversion-1.5.7-0.1.1.x86_64.rpm
# rpm -qip python-2.6.0-2.21.1.x86_64.rpm
Name : python Relocations: (not relocatable)
Version : 2.6.0 Vendor: openSUSE
Release : 2.21.1 Build Date: Tue Feb 3 15:51:18 2009
Install Date: (not installed) Build Host: adalid
Group : Development/Languages/Python Source RPM: python-2.6.0-2.21.1.src.rpm
Size : 1186111 License: X11/MIT
Signature : RSA/8, Tue Feb 3 15:51:49 2009, Key ID b88b2fd43dbdc284
Packager : http://bugs.opensuse.org
URL : http://www.python.org/
Summary : Python Interpreter
Description :
Python is an interpreted, object-oriented programming language, and is
often compared to Tcl, Perl, Scheme, or Java. You can find an overview
of Python in the documentation and tutorials included in the python-doc
(HTML) or python-doc-pdf (PDF) packages.
If you want to install third party modules using distutils, you need to
install python-devel package.
Authors:
--------
Guido van Rossum <guido@python.org>
Distribution: openSUSE 11.1
root@fermi-login /var/cache/zypp/packages/repo-update/rpm/x86_64
12:23:41$ rpm -Uvh --test python-2.6.0-2.21.1.x86_64.rpm
# rpm -Uvh --test python-2.6.0-2.21.1.x86_64.rpm
Guess what happens after the last command? Nothing, it hangs!
from THAT date work backwards in the Zypper logs and see if there were
any updates which might have introduced a problem…(btw, i don’t
what was thinking about earlier…YaST is a GUI front end for
zypper…if zypper is broke then yast must be too…)
think hard, what might you have done…like, how many different repos
are currently enabled?
execute the following and post the results back to here:
zypper lr -d
have you done any one-click installs?
consider installing smart, and using it to reinstall zypper
I noticed, when looking through the zypper log, and then reading your posts following, has confirmed my suspicion. The problem is not with zypper. Zypper is making calls to rpmdb and rpmdelta. My guess is that your rpmdb is corrupted. I would try rebuilding the rpmdb.
When I checked it turned out that one of the NFS shares I had mounted wasn’t responding. When I fixed the problem (which turned out to be with the NFS server) zypper and rpm started working again immediately. I don’t understand why rpm installation is dependent on NFS but it is a useful thing to know.
