-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- From your description below, your problem was almost certainly the
result of losing your VPN connection during the yum update process.
Because this happened, you stumbled across a bug that we are currently
trying to fix in the DNS resolver which is the source of the
multi-minute performance issues you have been seeing.
Yum updating the SSSD does not cause this behavior.
On 01/08/2010 05:20 PM, Dmitri Pal wrote:
Hi,
As some of you know I use RHEL5 on my main machine where I run SSSD.
Today I had the following problem:
a) I started "yum update" in the command line window and switched to
other tasks.
b) I was on VPN at the beginning working remotely.
c) My screen locked while I was on call but probably before the update
has finished.
d) The update probably did something to the Network Manager.
e) When I tried to unlock the screen it was failing to log me back. I
tired 10 times to make sure that it is really the sssd not me.
f) I switched to text mode (ctrl+alt+F1) and tried there. Same result.
g) I logged there as root. Restarted sssd and was able to get as dpal.
h) I switched to desktop and now was able to log in.
i) When I got in I noticed that my VPN connection is lost.
Just in case I captured the list of the packaged that got updated:
Updated:
ICAClient.i386 0:11.0-1
OpenIPMI.i386 0:2.0.16-5.el5_4.1
OpenIPMI-libs.i386 0:2.0.16-5.el5_4.1 acpid.i386
0:1.0.4-9.el5_4.1
acroread.i386 0:8.1.7-1.el5
bind-libs.i386 30:9.3.6-4.P1.el5_4.1
bind-utils.i386 30:9.3.6-4.P1.el5_4.1
coreutils.i386 0:5.97-23.el5_4.1
cpp.i386 0:4.1.2-46.el5_4.1 cups.i386
1:1.3.7-11.el5_4.3
cups-libs.i386 1:1.3.7-11.el5_4.3
dbus-python.i386 0:0.70-9.el5_4
device-mapper-multipath.i386 0:0.4.7-30.el5_4.4 expat.i386
0:1.95.8-8.3.el5_4.2
expat-devel.i386 0:1.95.8-8.3.el5_4.2
firefox.i386 0:3.0.16-1.el5_4
flash-plugin.i386 0:10.0.42.34-1.el5
fsync-ng.noarch 0:1.5.18-10.rhis
gcc.i386 0:4.1.2-46.el5_4.1
gcc-c++.i386 0:4.1.2-46.el5_4.1
gcc-gfortran.i386 0:4.1.2-46.el5_4.1 glibc.i686
0:2.5-42.el5_4.2
glibc-common.i386 0:2.5-42.el5_4.2
glibc-devel.i386 0:2.5-42.el5_4.2
glibc-headers.i386 0:2.5-42.el5_4.2 httpd.i386
0:2.2.3-31.el5_4.2
iptables.i386 0:1.3.5-5.3.el5_4.1
iptables-ipv6.i386 0:1.3.5-5.3.el5_4.1
java-1.5.0-ibm.i386 1:1.5.0.11-1jpp.1.el5
java-1.5.0-ibm-devel.i386 1:1.5.0.11-1jpp.1.el5
java-1.5.0-sun.i586 0:1.5.0.22-1jpp.1.el5
java-1.5.0-sun-plugin.i586 0:1.5.0.22-1jpp.1.el5
kdelibs.i386 6:3.5.4-25.el5_4.1
kernel-headers.i386 0:2.6.18-164.9.1.el5
kexec-tools.i386 0:1.102pre-77.el5.3 kpartx.i386
0:0.4.7-30.el5_4.4
ksh.i386 0:20080202-14.el5_4.2 libgcc.i386
0:4.1.2-46.el5_4.1
libgcj.i386 0:4.1.2-46.el5_4.1
libgfortran.i386 0:4.1.2-46.el5_4.1
libpurple.i386 0:2.6.3-2.el5
libstdc++.i386 0:4.1.2-46.el5_4.1
libstdc++-devel.i386 0:4.1.2-46.el5_4.1
libtool.i386 0:1.5.22-7.el5_4
libtool-ltdl.i386 0:1.5.22-7.el5_4
libuser.i386 0:0.54.7-2.1.el5_4.1
libuser-devel.i386 0:0.54.7-2.1.el5_4.1
libvorbis.i386 1:1.1.2-3.el5_4.4
libvorbis-devel.i386 1:1.1.2-3.el5_4.4 lvm2.i386
0:2.02.46-8.el5_4.2
metacity.i386 0:2.16.0-12.el5_4.1 nscd.i386
0:2.5-42.el5_4.2
nss_ldap.i386 0:253-22.el5_4 ntp.i386
0:4.2.2p1-9.el5_4.1
openssh.i386 0:4.3p2-36.el5_4.3
openssh-askpass.i386 0:4.3p2-36.el5_4.3
openssh-clients.i386 0:4.3p2-36.el5_4.3
openssh-server.i386 0:4.3p2-36.el5_4.3
pidgin.i386 0:2.6.3-2.el5
poppler.i386 0:0.5.4-4.4.el5_4.11
samba-client.i386 0:3.0.33-3.15.el5_4.1
samba-common.i386 0:3.0.33-3.15.el5_4.1
screen.i386 0:4.0.3-1.el5_4.1
selinux-policy.noarch 0:2.4.6-255.el5_4.1
selinux-policy-devel.noarch 0:2.4.6-255.el5_4.1
selinux-policy-targeted.noarch 0:2.4.6-255.el5_4.1
sssd.i386 0:1.0.99-0.2010010510git3356eda.el5
sssd-client.i386 0:1.0.99-0.2010010510git3356eda.el5
system-config-lvm.noarch 0:1.1.5-1.0.el5_4.1 tcsh.i386
0:6.14-14.el5_4.2
vixie-cron.i386 4:4.1-77.el5_4.1 wget.i386
0:1.11.4-2.el5_4.1
xerces-j2.i386 0:2.7.1-7jpp.2.el5_4.2
xorg-x11-server-Xnest.i386 0:1.1.1-48.67.el5_4.1
xorg-x11-server-Xorg.i386 0:1.1.1-48.67.el5_4.1
xorg-x11-server-Xvfb.i386 0:1.1.1-48.67.el5_4.1
xterm.i386 0:215-8.el5_4.1
xulrunner.i386 0:1.9.0.16-2.el5_4
I do see sssd.
So if the sssd was updated and this update caused the lockdown this is bad.
People who run updates will most likely do other things while the
updates are running and will hope that they will be given a chance to
save their work before the recommended reboot.
I do not know what is the right way to address the issue but it is
definitely not nice and will cause a lot of frustration.
- --
Stephen Gallagher
RHCE 804006346421761
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora -
http://enigmail.mozdev.org/
iEYEARECAAYFAktLJwQACgkQeiVVYja6o6M8eACeO4kb2NuZC/fCF7eQU7wCNNvG
dM0AoIIHbueRcqYiN75IxPZVYZsApDMM
=zMCX
-----END PGP SIGNATURE-----