Yast2 broken

English Applications
1

OS 11.0

I don’t know what I’ve done, but I seem to have broken Yast2. Yast still works and Zypper works.

What’s wrong:

  1. If I try and use the software management, any package install fails saying “can’t exec rpm (no such file or directory)”
  2. If I try and run xinetd, I am told it needs installing (although I know it is already installed). Of course, if I allow Yast2 to try and reinstall it, I get problem (1).

I’ve tried rebuilding the rpmdb, but it doesn’t help. I’ve also tried uninstalling and reinstalling Yast2, but that doesn’t help either.

Any ideas?

2

Firstly, verify that rpm works by just typing rpm.
Then, using rpm package, remove the yast package:

rpm -e yast2-installation

Then, install that using zypper:

zypper install yast2-installation
3

Sorry for the long post, but I think this might help.

I tried what you suggested, but I got the following problem:

linux-1iys:/home/alex # rpm -e yast2-installation
error: Failed dependencies:
yast2-installation is needed by (installed) yast2-update-2.16.10-4.1.i58
6
yast2-installation is needed by (installed) yast2-add-on-2.16.8-6.1.noar
ch
yast2-installation is needed by (installed) yast2-metapackage-handler-0.
8.5-16.1.noarch
yast2-installation >= 2.15.12 is needed by (installed) yast2-packager-2.
16.53-3.1.i586

So then I tried more or less what I had tried before:

linux-1iys:/home/alex # zypper remove yast2
Downloading repository ‘Updates for 11.0’ metadata [done]
Building repository ‘Updates for 11.0’ cache [done]
Reading installed packages…

The following packages are going to be REMOVED:
yast2-x11 yast2-vm yast2-users yast2-security yast2-scanner yast2-samba-server

yast2-samba-client yast2-runlevel yast2-restore yast2-repair yast2-registration
yast2-profile-manager yast2-printer yast2-update-FACTORY yast2-update yast2-tv
yast2-tune yast2-control-center-qt yast2-control-center yast2-bootloader
yast2-backup yast2-apparmor yast2-add-on yast2 yast2-tftp-server yast2-sysconfig

yast2-support yast2-storage yast2-sound yast2-metapackage-handler yast2-mail
yast2-ldap-client yast2-ldap yast2-kerberos-client yast2-iscsi-client yast2-irda

yast2-installation yast2-inetd yast2-http-server yast2-ftp-server yast2-firewall

yast2-dns-server yast2-country yast2-pam yast2-packager
yast2-online-update-frontend yast2-online-update yast2-ntp-client yast2-nis-clie
nt
yast2-nfs-server yast2-nfs-client yast2-network yast2-mouse autoyast2-installati
on

After the operation, 35.3 M will be freed.
Continue? [YES/no]:YES
Removing yast2-nfs-server-2.16.1-6.1 [done]
Removing yast2-nis-client-2.16.3-6.1 [done]
Removing yast2-ntp-client-2.16.9-11.1 [done]
Removing yast2-online-update-frontend-2.16.15-6.1 [done
Removing yast2-online-update-2.16.15-6.1 [done]
Removing yast2-firewall-2.16.2-25.1 [done]
Removing yast2-ftp-server-2.16.11-22.1 [done]
Removing yast2-http-server-2.16.9-10.1 [done]
Removing yast2-dns-server-2.16.4-14.1 [done]
Removing yast2-irda-2.16.1-25.1 [done]
Removing yast2-iscsi-client-2.16.14-6.1 [done]
Removing yast2-mail-2.16.6-2.1 [done]
Removing yast2-metapackage-handler-0.8.5-16.1 [done]
Removing yast2-support-2.16.1-6.1 [done]
Removing yast2-sysconfig-2.16.0-28.1 [done]
Removing yast2-tftp-server-2.16.0-26.1 [done]
Removing yast2-add-on-2.16.8-6.1 [done]
Removing yast2-apparmor-2.16.4-4.1 [done]
Removing yast2-backup-2.16.6-0.1 [done]
Removing yast2-nfs-client-2.16.1-26.1 [done]
Removing yast2-control-center-qt-2.16.2-11.1 [done]
Removing yast2-control-center-2.16.2-11.1 [done]
Removing yast2-tune-2.16.2-2.1 [done]
Removing yast2-tv-2.16.6-7.1 [done]
Removing yast2-sound-2.16.11-6.1 [done]
Removing yast2-update-FACTORY-2.16.10-4.1 [done]
Removing yast2-printer-2.16.32-3.1 [done]
Removing yast2-inetd-2.16.0-27.1 [done]
Removing yast2-profile-manager-2.16.1-27.1 [done]
Removing yast2-registration-2.16.7-4.1 [done]
Removing yast2-repair-2.16.12-4.1 [done]
Removing yast2-restore-2.16.2-26.1 [done]
Removing yast2-runlevel-2.16.5-15.1 [done]
Removing yast2-samba-server-2.16.3-15.1 [done]
Removing yast2-samba-client-2.16.9-3.1 [done]
Removing yast2-kerberos-client-2.16.11-9.1 [done]
Removing yast2-scanner-2.16.10-13.1 [done]
Removing yast2-users-2.16.33-6.1 [done]
Removing yast2-ldap-client-2.16.16-6.1 [done]
Removing yast2-ldap-2.16.0-52.1 [done]
Removing yast2-network-2.16.48-3.1 [done]
Removing yast2-packager-2.16.53-3.1 [done]
Removing yast2-installation-2.16.50-3.1 [done]
Removing autoyast2-installation-2.16.19-0.1 [done]
Removing yast2-mouse-2.16.1-26.1 [done]
Removing yast2-update-2.16.10-4.1 [done]
Removing yast2-bootloader-2.16.20-0.1 [done]
Removing yast2-storage-2.16.26-0.1 [done]
Removing yast2-security-2.16.1-16.1 [done]
Removing yast2-pam-2.16.2-17.1 [done]
Removing yast2-country-2.16.26-6.1 [done]
Removing yast2-vm-2.16.5-7.1 [done]
Removing yast2-x11-2.15.12-15.1 [done]
Removing yast2-2.16.71-6.1 [done]

And then

linux-1iys:/home/alex # zypper in yast2
Reading installed packages…

The following NEW package is going to be installed:
yast2

Overall download size: 588.0 K. After the operation, additional 3.1 M will be us
ed.
Continue? [YES/no]: YES
Downloading package yast2-2.16.71-6.1.i586 (1/1), 588.0 K (3.1 M unpacked)
Downloading: yast2-2.16.71-6.1.i586.rpm [done (47.7 K/s)]
Installing: yast2-2.16.71-6.1 [done]

and then

linux-1iys:/home/alex # zypper in yast2-installation
Reading installed packages…

The following NEW packages are going to be installed:
yast2-security yast2-registration yast2-pam yast2-ldap-client yast2-installati
on
yast2-firewall yast2-add-on yast2-users yast2-update yast2-storage yast2-network

yast2-mouse yast2-ldap yast2-country yast2-bootloader yast2-packager
yast2-online-update autoyast2-installation

Overall download size: 2.8 M. After the operation, additional 14.5 M will be use
d.
Continue? [YES/no]: YES
Downloading package yast2-pam-2.16.2-17.1.noarch (1/18), 29.0 K (128.0 K unpacke
d)
Downloading: yast2-pam-2.16.2-17.1.noarch.rpm [done]
Installing: yast2-pam-2.16.2-17.1 [done]
Downloading package yast2-firewall-2.16.2-25.1.noarch (2/18), 81.0 K (481.0 K un
packed)
Downloading: yast2-firewall-2.16.2-25.1.noarch.rpm [done]
Installing: yast2-firewall-2.16.2-25.1 [done]
Downloading package yast2-update-2.16.10-4.1.i586 (3/18), 92.0 K (467.0 K unpack
ed)
Downloading: yast2-update-2.16.10-4.1.i586.rpm [done]
Installing: yast2-update-2.16.10-4.1 [done]
Downloading package yast2-storage-2.16.26-0.1.i586 (4/18), 507.0 K (2.7 M unpack
ed)
Downloading: yast2-storage-2.16.26-0.1.i586.rpm [done (45.3 K/s)]
Installing: yast2-storage-2.16.26-0.1 [done]
Downloading package yast2-mouse-2.16.1-26.1.i586 (5/18), 26.0 K (91.0 K unpacked
)
Downloading: yast2-mouse-2.16.1-26.1.i586.rpm [done]
Installing: yast2-mouse-2.16.1-26.1 [done]
Downloading package yast2-ldap-2.16.0-52.1.i586 (6/18), 113.0 K (478.0 K unpacke
d)
Downloading: yast2-ldap-2.16.0-52.1.i586.rpm [done]
Installing: yast2-ldap-2.16.0-52.1 [done]
Downloading package yast2-country-2.16.26-6.1.i586 (7/18), 99.0 K (473.0 K unpac
ked)
Downloading: yast2-country-2.16.26-6.1.i586.rpm [done]
Installing: yast2-country-2.16.26-6.1 [done]
Downloading package yast2-security-2.16.1-16.1.noarch (8/18), 41.0 K (192.0 K un
packed)
Downloading: yast2-security-2.16.1-16.1.noarch.rpm [done]
Installing: yast2-security-2.16.1-16.1 [done]
Downloading package yast2-bootloader-2.16.20-0.1.i586 (9/18), 297.0 K (2.1 M unp
acked)
Downloading: yast2-bootloader-2.16.20-0.1.i586.rpm [done (49.1 K/s)]
Installing: yast2-bootloader-2.16.20-0.1 [done]
Downloading package autoyast2-installation-2.16.19-0.1.noarch (10/18), 175.0 K (
1.2 M unpacked)
Downloading: autoyast2-installation-2.16.19-0.1.noarch.rpm [done (52.5 K/s)]
Installing: autoyast2-installation-2.16.19-0.1 [done]
Downloading package yast2-installation-2.16.50-3.1.noarch (11/18), 207.0 K (633.
0 K unpacked)
Downloading: yast2-installation-2.16.50-3.1.noarch.rpm [done]
Installing: yast2-installation-2.16.50-3.1 [done]
Downloading package yast2-packager-2.16.53-3.1.i586 (12/18), 309.0 K (1.5 M unpa
cked)
Downloading: yast2-packager-2.16.53-3.1.i586.rpm [done (48.9 K/s)]
Installing: yast2-packager-2.16.53-3.1 [done]
Downloading package yast2-registration-2.16.7-4.1.noarch (13/18), 137.0 K (250.0
K unpacked)
Downloading: yast2-registration-2.16.7-4.1.noarch.rpm [done]
Installing: yast2-registration-2.16.7-4.1 [done]
Downloading package yast2-add-on-2.16.8-6.1.noarch (14/18), 40.0 K (126.0 K unpa
cked)
Downloading: yast2-add-on-2.16.8-6.1.noarch.rpm [done]
Installing: yast2-add-on-2.16.8-6.1 [done]
Downloading package yast2-network-2.16.48-3.1.i586 (15/18), 315.0 K (1.9 M unpac
ked)
Downloading: yast2-network-2.16.48-3.1.i586.rpm [done (39.8 K/s)]
Installing: yast2-network-2.16.48-3.1 [done]
Downloading package yast2-online-update-2.16.15-6.1.noarch (16/18), 58.0 K (247.
0 K unpacked)
Downloading: yast2-online-update-2.16.15-6.1.noarch.rpm [done (17.9 K/s)]
Installing: yast2-online-update-2.16.15-6.1 [done]
Downloading package yast2-ldap-client-2.16.16-6.1.noarch (17/18), 94.0 K (508.0
K unpacked)
Downloading: yast2-ldap-client-2.16.16-6.1.noarch.rpm [done (33.3 K/s)]
Installing: yast2-ldap-client-2.16.16-6.1 [done]
Downloading package yast2-users-2.16.33-6.1.i586 (18/18), 205.0 K (1.0 M unpacke
d)
Downloading: yast2-users-2.16.33-6.1.i586.rpm [done (28.7 K/s)]
Installing: yast2-users-2.16.33-6.1 [done]

I then started yast2 and installed yast2-xinetd and everything seems to be fine.
I will now try and install the other yast2 packagaes and see if the problem stays away.
Thanks for the help.
I hope this experience is useful to someone else.

4

Good to hear that your problem is solved.

5

I thought it was, but a couple of restarts and not much else later and the problem is back exactly as it was. Has anyone any other ideas?

6

nalexmay wrote:
> I thought it was, but a couple of restarts and not much else later and
> the problem is back exactly as it was. Has anyone any other ideas?

exactly what did you do during that “and not much else”? why did you
reboot? what did you add? what did you change?

did you take a backup while it all worked well???

AND, what repos do you have enabled…

–
somebody_else

7

If I thought I had done anything that might have caused it or indeed if I could remember having done anything in particular I would have said so. Do I have to write down everything I do with OpenSuse every time I use the computer? I rebooted because I’m not yet using the server, so I powered it off when I was away.
What repos you ask. Sorry, but I don’t know how to answer that question. Can you explain please.

8

> What repos you ask. Sorry, but I don’t know how to answer that
> question. Can you explain please.

read the repository management howto thread that begins here:
http://tinyurl.com/d36dml

i’ve not looked at it lately but i THINK it recommends you normally
use only FOUR repos…

and, it is my bedtime…maybe someone else will come in and get you
started with zypper…

i guess you can/should use zypper to repair yast…and, there are some
very recent thread on that very thing…see if you find them using the
forum’s search engine…or use google and specify to search in
forums.opensuse.org

–
somebody_else

9

Thanks for the clarification.
Here is the answer to the question of repos.
I don’t think I have much more than I should.
The only one I added was for Open-Xchange, but that’s what this server is supposed to be for, so I don’t think I can do without it.

linux-1iys:/home/alex # zypper lr

| Alias | Name | Enabled | Refresh

–±-----------------------±-----------------------±--------±-------
1 | repo-debug | openSUSE-11.0-Debug | No | No
2 | repo-oss | openSUSE-11.0-Oss | Yes | No
3 | OX | OX | Yes | Yes
4 | openSUSE-11.0-Updates | Updates for 11.0 | Yes | Yes
5 | repo-non-oss | openSUSE-11.0-Non-Oss | Yes | No
6 | openSUSE-11.0-FTP 11.0 | openSUSE-11.0-FTP 11.0 | Yes | Yes

I did some searching and reading on repairing Yast with Zypper. Basically the approach seems to be to refresh the database and reinstall Yast. That’s what I did and it solved the problem…
…until the problem came right back.
I guess it is a problem with an update which is happening automatically and breaking yast, but I don’t know how to narrow down what is causing the problem.
So, further ideas would be most welcome.

10

Why use 11.0 if 11.1 is available ?
It might also be an indication of a degrading condition of your harddisk…

11

>> --±-----------------------±-----------------------±--------±-------
>> 1 | repo-debug | openSUSE-11.0-Debug | No | No
>> 2 | repo-oss | openSUSE-11.0-Oss | Yes | No
>> 3 | OX | OX | Yes | Yes
>> 4 | openSUSE-11.0-Updates | Updates for 11.0 | Yes | Yes
>> 5 | repo-non-oss | openSUSE-11.0-Non-Oss | Yes | No
>> 6 | openSUSE-11.0-FTP 11.0 | openSUSE-11.0-FTP 11.0 | Yes | Yes

> I guess it is a problem with an update which is happening automatically
> and breaking yast

that was my assumption when i asked to see what repos are active…

TRY: i recommend that you use zypper to delete (or turn Off & Off)
repos numbered 3 and 6…then turn ON automatic updating for repos 2
and 5 (and leave number 1 Off and Off) that will leave the recommended
(by most folks) three (2, 4, 5 and, most recommend Packman, but you
said server? so maybe not)…

THEN run the zypper repair mantra again…(since you had not updated 2
and 5 there may be a good number flowing in from them–one of which
MIGHT be a fix to your very problem!)

but, i believe having just those three repos ONLY active and
automatically updated will solve your problem…try it like that for a
while…

i can’t comment on whether or not you should always have the
Open-Xchange repo always active, but i would NOT…(if it ain’t broke
don’t fix it–that is, leave it OFF and see if won’t just keep
working…BUT, you might wanna ask someone who knows something
about OX and SUSE (if i’ve ever met an Open-Xchange i don’t remember
it!!)…

you could leave 3 off and then if/when you hear of a needed update,
vulnerability or experienced a problem you could turn it back on…
or ???

ps: i’d give the magic incantations to turn repo’s on and off, but
i’m too lazy to look them up…you would probably find these helpful:

man zypper
http://en.opensuse.org/Zypper
http://opensuse-tutorials.com/category/zypper/
http://en.opensuse.org/Yast
http://opensuse-tutorials.com/category/yast/

–
somebody_else

12

> Why use 11.0 if 11.1 is available ?

because we are talking servers here…i’d bet there are LOTS of SuSE
9.x servers still doing GREAT service on the net and in back rooms
around the world…

because 11.0 works?

because not every new release is an actual “upgrade”?

and that old saw: If it ain’t broke don’t fix it?

> It might also be an indication of a degrading condition of your
> harddisk…

hmmmmm…

nalexmay, have you discovered S.M.A.R.T. monitoring for your disks?

–
somebody_else

13

“because 11.0 works?”

"because not every new release is an actual “upgrade”?

“and that old saw: If it ain’t broke don’t fix it?”

Did I miss something here? I’ve just read two pages of posts describing your problem with a “broken” 11.0 install. So I guess it is “broke” after all. Sorry if that sounds harsh, but I had a terrible time with 11.0. Things “broke” constantly, so much so that I went to 11.1 early. I’ve never had a regret. I can tell you from my own experience that (IMHO) 11.0 was not ready for prime time, 11.1 is. I’ve been very happy with it. One of my many, many problems with 11.0 was quite similar to yours, but not any more with 11.1. It’s not perfect, but it’s in a whole different league from it’s predecessor.

14

I didn’t know that when a new version came out (11.1) that meant the old version (11.0) stopped working. :
I wondered about a hard disk problem too. I ran a long test with smartctl and it came back without any errors. Is that enough of a test or is there some other way I should check the hard drive?

15

It is so frustrating.
Someone makes a ‘smart’ remark and everyone and his dog want to comment on it.
Ask a sensible question and it’s another story!

16

To be honest you seem to have a peculiar problem which is specific to your setup.

The only thing you’ve narrowed it down to is it is some update, there’s a lot of updates from a clean install. You’ll have to narrow it down further and watch the updates, updating slowly not all at once. When you identify the pkg causing the problem I suspect you’ll have a bug report.