Yamaban composed on 2016-10-29 12:49 (UTC+0100):
Felix Miata wrote:
Felix Miata composed on 2016-10-27 01:55 (UTC-0400):
On an alpha on host hpg33 last updated (installed?) in July, after zypper ref I tried to zypper up, and it aborted with $SUBJECT message. I got it to update by using the suggested-by-error-message --non-interactive option. Afterward, I tried to zypper dup, but it produces the same result as before the update. rpm --rebuilddb, zypper clean -a and zypper ref didn't help. Searching for $SUBJECT in boo as comment produces no hits in past 11 months. Rebooting seems to have fixed it.
Any ideas what happened, or didn't?
Happened again, but on host gx62b last updated 2 Aug. A little more detail this time: I normally don't just zypper up. Instead, I run the following script first (but after zypper ref):
#!/bin/sh zypper -v in zypper libzypp libsolv-tools rpm openSUSE-release zypper -v in device-mapper dmraid glibc lvm2 multipath-tools mdadm systemd udev
Running the script before zypper up/dup provides me opportunity to check if /etc/zypp /zypp*conf.rpmnew has appeared or changed so I can see if I want to make any adjustment before proceeding.
So when the abort occurred trying to zypper up, unlike on hpg33, I rebooted instead of proceeding directly to up. After, zypper up worked as expected.
THAT has a clear cause: a new glibc/udev was installed by the script, and any program started after that will use the the new ones while the already running programs still use the old ones. That is a surefire way to get a program to crash.
Methinks one of us misunderstands the other. My script only has two executable lines, neither of which is zypper up (or zypper dup). What running program would cause zypper up when run after my script to abort? Last modified time on my script is 18 months ago, so my process has proven reliable up to now (each of TW, 42.1, 13.2, 13.1, and on multiple hosts), and has become a problem only for 42.2.
So, the logic involved should include a reboot after the script is run if a new glibc/udev was installed, or go the secure way and include a reboot command in the script (if the previous two zypper commands whre run without error)
I have to think that were my script were not used, but simply 'zypper ref; zypper up' run that were the up interrupted for any reason after the various package management and fundament packages were installed that a restart of up would fail in same manner as using the script, and a reboot required in order to get up to finish. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org