[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Cannot login to computer after upgrade to Lenny



I just checked, and the removal of LD_ASSUME_KERNEL variable was not adviced by the Lenny release notes, but by debconf somewhere during the "aptitude upgrade" or the "aptitude dist-upgrade". I'm not sure but I think it was during the kernel or libc6 installation.

MoS

----- Original Message ----- From: "MoS" <mosdev@free.fr>
To: <debian-user@lists.debian.org>
Sent: Wednesday, June 03, 2009 12:37 AM
Subject: Re: Cannot login to computer after upgrade to Lenny


Hi ! The problem is finally solved !
I was also asking help on the debian-user-french list, merging informations
from here and there and transmitting leads between lists. And a few hours
ago a french guy named Jean-Damien asked me to check for an environment
variable names LD_ASSUME_KERNEL. This immediately enlightened everything :

I have such a variable in my "/etc/environment" (value 2.4.1) for Oracle 9. But I forgot it because it wasn't in my root failsafe environment (which was
in fact very simple).
I tried very early to remove "/etc/profile", "/etc/bash.bashrc", ".bashrc" and such, to be sure that as few programs as possible were called during the
login. But I never thought of this sneeky "/etc/environnement" ...

As recommended by the Lenny upgrade documentation, I commented out this
variable before running all the steps of the upgrade from Etch.
I guess I probably restored it as a reflex right after the "dist-upgrade"
and before the reboot. Was it specified never to restore this variable ? I
will check this, and if not transmit the information.
Started from there, every session opening (except failsafe one) loaded the variable hence the
problem....

Well, the result is that Oracle 9 will not start any more, and I dunno if it
is recoverable, but at least I can login on the computer again !

Huge thanks to you and all the people who tried to help me on both lists !!
MoS

----- Original Message ----- From: "Sven Joachim" <svenjoac@gmx.de>
To: <debian-user@lists.debian.org>
Sent: Monday, June 01, 2009 10:48 PM
Subject: Re: Cannot login to computer after upgrade to Lenny


On 2009-06-01 17:04 +0200, MoS wrote:

# su
bash: error while loading shared libraries: libdl.so.2: cannot open
shared object file: No such file or directory

# cp
cp: missing file operand
Try `cp --help' for more information.

So cp works, but su does not.  I suspect this is because su is suid
root, but do not really have an idea what exactly the problem is.  The
dynamic linker ignores the LD_LIBRARY_PATH environment variable for
setuid/setgid programs, do you have it set in your environment?  And
does a non-setuid copy of su show the error?

See ld.so(8) for some background information.

Sven


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org





--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org





Reply to: