LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Ubuntu
User Name
Password
Ubuntu This forum is for the discussion of Ubuntu Linux.

Notices


Reply
  Search this Thread
Old 06-16-2010, 06:09 AM   #1
jeremy28
Member
 
Registered: Sep 2009
Posts: 48

Rep: Reputation: 15
Error while loading shared libraries?!


Hi all;

I have ubuntu 9.04 on my Virtual Machine and my host OS is Win.XP,
I've installed SSH on my linux and and now, I use PuTTY on Win.XP to connect to the SSH on linux,

Now, I have a problem:
When I login with "root" and run any command, I see load errors for libraries such below:

Code:
vim:  error while loading shared libraries: libm.so.6: cannot open shared object file: No such file or directory
ls:  error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory
./shmop:  error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
…
I've defined a user in ubuntu and when I login with it, I have no problem in running commands!
Also, when I use "su" command in the user's session and go to the root, I have no problem again in running commands!

Could you help me where the problem is coming from?

Is it related to my linux version or distro?

Or anything else?!

TIA.
 
Old 06-16-2010, 07:06 PM   #2
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,415
Blog Entries: 55

Rep: Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600
Quote:
Originally Posted by jeremy28 View Post
I've installed SSH on my linux (..) When I login with "root" (..) I've defined a user in ubuntu and when I login with it, I have no problem in running commands
You should, by default, not log in over network services as root. All three libraries mentioned are part of the vital glibc package. Since you have no problem running as (unprivileged?) user this might be due some environment setting. Is there a difference in output if you run 'env|grep LD' as root over SSH and logged in as unprivileged user? And when did this start? Right from install or after updates?
 
Old 06-19-2010, 02:25 AM   #3
jeremy28
Member
 
Registered: Sep 2009
Posts: 48

Original Poster
Rep: Reputation: 15
Hi and Thanks!

Here is my ".bashrc file" in root:
Code:
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# If not running interactively, don't do anything
[ -z "$PS1" ] && return

# don't put duplicate lines in the history. See bash(1) for more options
# don't overwrite GNU Midnight Commander's setting of `ignorespace'.
export HISTCONTROL=$HISTCONTROL${HISTCONTROL+,}ignoredups
# ... or force ignoredups and ignorespace
export HISTCONTROL=ignoreboth

# append to the history file, don't overwrite it
shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then
    debian_chroot=$(cat /etc/debian_chroot)
fi

# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
    xterm-color) color_prompt=yes;;
esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then
    if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
	# We have color support; assume it's compliant with Ecma-48
	# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
	# a case would tend to support setf rather than setaf.)
	color_prompt=yes
    else
	color_prompt=
    fi
fi

if [ "$color_prompt" = yes ]; then
    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
    PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
    PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
    ;;
*)
    ;;
esac

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.

#if [ -f ~/.bash_aliases ]; then
#    . ~/.bash_aliases
#fi

# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
    eval "`dircolors -b`"
    alias ls='ls --color=auto'
    #alias dir='dir --color=auto'
    #alias vdir='vdir --color=auto'

    #alias grep='grep --color=auto'
    #alias fgrep='fgrep --color=auto'
    #alias egrep='egrep --color=auto'
fi

# some more ls aliases
#alias ll='ls -l'
#alias la='ls -A'
#alias l='ls -CF'

# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if [ -f /etc/bash_completion ]; then
    . /etc/bash_completion
fi
And ".bash_profile" in root:


Code:
And ".bash_profile" in root:

Code:
# .bash_profile

# Get the aliases and functions
if [ -f ~/.bashrc ]; then
	. ~/.bashrc
fi

# User specific environment and startup programs

PATH=$PATH:$HOME/bin

export PATH
unset USERNAME

#TZ='GST-2:30'; export TZ

export PATH
unset USERNAME
export LD_ASSUME_KERNEL=2.4
export ORACLE_BASE=/home/oracle
export ORACLE_HOME=$ORACLE_BASE/product/8.1.6
export ORACLE_SID=pki
export NLS_LANG=american
export NLS_DATE_FORMAT='YYYY-MM-DD HH24:MI:SS'
export ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
export PATH=$PATH:$ORACLE_HOME/bin

#. ~/bin/udb-env.sh
What's the problem?
And how could I fix it?

TIA.
 
Old 06-19-2010, 04:17 AM   #4
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,415
Blog Entries: 55

Rep: Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600
I was expecting two pieces of output (a diff of 'env|grep LD' as root over SSH and logged in as unprivileged user) and an answer to "when did this start?". Without that information I only see a "export LD_ASSUME_KERNEL=2.4" line which may (or may not) be the culprit.
 
Old 06-19-2010, 05:56 AM   #5
jeremy28
Member
 
Registered: Sep 2009
Posts: 48

Original Poster
Rep: Reputation: 15
Hi dear unSpawn!

Quote:
I was expecting two pieces of output (a diff of 'env|grep LD' as root over SSH and logged in as unprivileged user)
By root:
Code:
root@ubuntu:~# env|grep LD
grep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
env: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
By unprivileged user:
Code:
user@ubuntu:~$ env|grep LD
user@ubuntu:~$
And when did this start?
Right from install or after updates?

Whenever I login as root and run any command, I see the mentioned errors. But with "unprivileged user", I see no error, as you see.

What's the problem?

THX
 
Old 06-19-2010, 06:20 AM   #6
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,415
Blog Entries: 55

Rep: Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600
Comment out the "export LD_ASSUME_KERNEL=2.4" line (put a hash mark in front of it), log out and log back in to see if that fixes things.
 
Old 06-19-2010, 08:06 AM   #7
jeremy28
Member
 
Registered: Sep 2009
Posts: 48

Original Poster
Rep: Reputation: 15
Thank you so much!!

The problem is resolved.

Could you explain me why this flag "LD_ASSUME_KERNEL" caused the problem?!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
error while loading shared libraries: libgda-4.0.so.4: cannot open shared object file mahesh1234 Linux - Newbie 2 10-22-2013 11:06 PM
error while loading shared libraries: libhid.so.0: cannot open shared object file: No misungs Linux - Software 4 06-10-2009 12:05 PM
Urgent !!! rpm: error while loading shared libraries: libelf.so.1: cannot open shared tinaa Linux - Software 5 12-02-2008 03:19 PM
gxine: error while loading shared libraries: libmozjs.so: cannot open shared object.. khronosschoty Slackware 10 11-10-2008 07:33 PM
error while loading shared libraries: libdb-4.1.so: cannot open shared object file putquery8581 Linux - Software 1 10-01-2004 07:03 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Ubuntu

All times are GMT -5. The time now is 07:10 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration