Re: [ilugd] glibc2.6.1 problem - Urgent!
Shakthi Kannan wrote: > - > | What after that, should i go and re-install glibc-2.3.3 along with its > | dependent packages or it is not required ? > \-- > > When you are able to log into the system, just use it. libc is what > you have restored back by copying. Why do you want to re-install? > re-installation is required for the following two purposes. 1. rpm re-installation of glibc-2.3.3 will overwrite the original files once again and will ensure, you have all the files at right path, permissions, md5 etc are ok 2. re-installation will also help to re-establish the symblinks. What I did is, established a sftp connection from the error free server to the faulted server just incase something breaks and it require to copy some libs again, and re-installed the glibc-2.3.3 with --force option on it. Then I also required to copy the following files with sftp ld-linux-x86-64.so.2 ld-lsb-x86-64.so.2 ld-lsb-x86-64.so.3 which are nothing but symblinks to the same file ld-2.3.3.so. It worked with only downside is rpm database still have a inconsistence glibc-2.6.1 installation, which i am ok to bear that ;) Thanks a lot guys for your help! Regards Yash ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
Re: [ilugd] glibc2.6.1 problem - Urgent!
,--[ On Sunday 02 Dec 2007, Yashpal Nagar wrote:
[...]
| I boot the system with Ubuntu x86_64, Live CD, and mounted the root file
| system (/dev/cciss/c0d0p4) and found ld-linux-x86-64.so.2 was already
| present.
| # ls /mnt1/lib64/ld-*
| ld-2.3.3.so
| ld-linux-x86-64.so.2
| ld-lsb-x86-64.so.1
so, probably your libc.so.* was lost.
| Then i just copied all the /lib/* and /lib64/* from another system, Then
| i rebooted and found the above error
I think he asked you to copy only /lib{,64}/libc.so.*, not
complete /lib{,64}/* . And it'll be better if you rsync-ed, so that symlinks
will copied as symlinks.
[...]
| The issue is I still have two boxes with glibc-2.3.3 and glibc-2.6.1
| installed
|
| host3:/ # rpm -qa|grep -i glib
| glibc-i18ndata-2.3.3-98.61
| glibc-32bit-9-200512100800
| glibc-locale-32bit-9-200512100801
| glibc-2.6.1-18
| glibc-locale-2.3.3-98.61
| glib-32bit-9-200501041713
| glibc-info-2.3.3-98.61
| glibc-devel-2.3.3-98.61
| glibc-devel-32bit-9-200512100801
| glib-1.2.10-586.2
| glibc-2.3.3-98.61
| glib2-2.2.3-117.2
| glib2-32bit-9-200507121454
| glibc-2.4-31.2
|
| Could anyone help, to properly remove glibc-2.6.1 ?
I've no experience of SLES, but do they've some convention of naming 32-bit
packages on amd64 architecture with '32bit' in their names, hmm... ? Paste
the output of following command:
% rpm --qf '%{name}.%{arch}\n' -qa
You've three (or four) versions of glibc installed. And, BtW, what error do
you get when you try to remove 'glibc-2.6.1' ?
|
| Thanks a lot for your patience :)
|
| Best regards,
| Yash
HTH
--
Ashish Shukla आशीष शुक्ल http://wahjava.wordpress.com/
·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- --
___
ilugd mailinglist -- ilugd@lists.linux-delhi.org
http://frodo.hserus.net/mailman/listinfo/ilugd
Next Event: http://freed.in - February 22/23, 2008
Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi
http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
Re: [ilugd] glibc2.6.1 problem - Urgent!
Shakthi Kannan wrote: > - > | What after that, should i go and re-install glibc-2.3.3 along with its > | dependent packages or it is not required ? > \-- > > When you are able to log into the system, just use it. libc is what > you have restored back by copying. Why do you want to re-install? > > I boot the system with Ubuntu x86_64, Live CD, and mounted the root file system (/dev/cciss/c0d0p4) and found ld-linux-x86-64.so.2 was already present. # ls /mnt1/lib64/ld-* ld-2.3.3.so ld-linux-x86-64.so.2 ld-lsb-x86-64.so.1 Then i just copied all the /lib/* and /lib64/* from another system, Then i rebooted and found the above error # boot errors### blogd: no message logging because /var file system is not accessible Boot logging started on /dev/tty1(/dev/console) at Thu Nov 29 13:36:25 2007 Master Resource Control: previous runlevel: N, switching to runlevel:3 Master Resource Control: runlevel 3 has beenreached blogd: no message logging because /var file system is not accessible ### As we had to power down the system (we could't issue any shutdown commands), i thought it might be beacuse FS might have a problem and require manual fsck'ing. Again booted the system with Ubuntu Live CD and run fsck.ext3, e2fsck on all slices, checked the *free file system size, which was ok, and then again try to boot the system. But no luck same error as above given. This time booted the system with SLES 9.0 SP3 and run rescue, and run fsck.ext3/e2fsck once again on all slices inlcuding /var (/dev/cciss/c0d0p6), but same error, this time i also verified /etc/fstab also which appeared to be Ok. Then i move ahead and try to use the "Repair Installed System" option available in the SLES. All the system verification tests passed except that, some of the package could not verified, i tried to repair them (which cause them to re-install), but installation of many of the programs failed! By this time i had a very little hope, time was running away, as this is a key production training system. I started moving the application installation data (installed under (/) FS) to another slices (/dev/cciss/c0d1). Fortunately i had, two big slices (/dev/cciss/c0d1p1 / /dev/cciss/c0d1p2) RAID5, where I moved, most of the data from /dev/cciss/c0d0/p*. I thought not to format any OS slices ( / , /var, /usr) and just re-install SLES 9. But all goes fine except during the RPMs installation the same RPMs (which failed during Repair option) got failed again, to install. Since i had already taken backup, i re-installed the SLES, with format option :( The issue is I still have two boxes with glibc-2.3.3 and glibc-2.6.1 installed host3:/ # rpm -qa|grep -i glib glibc-i18ndata-2.3.3-98.61 glibc-32bit-9-200512100800 glibc-locale-32bit-9-200512100801 glibc-2.6.1-18 glibc-locale-2.3.3-98.61 glib-32bit-9-200501041713 glibc-info-2.3.3-98.61 glibc-devel-2.3.3-98.61 glibc-devel-32bit-9-200512100801 glib-1.2.10-586.2 glibc-2.3.3-98.61 glib2-2.2.3-117.2 glib2-32bit-9-200507121454 glibc-2.4-31.2 Could anyone help, to properly remove glibc-2.6.1 ? Thanks a lot for your patience :) Best regards, Yash ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
Re: [ilugd] glibc2.6.1 problem - Urgent!
On Nov 29, 2007 12:48 AM, Yashpal Nagar <[EMAIL PROTECTED]> wrote: > Shakthi Kannan wrote: > > Hi, > > > > - On 11/29/07, Yashpal Nagar <[EMAIL PROTECTED]> wrote: > > | I tried scping from other host but > > | host2: # scp /lib64/ld-linux-x86-64.so.2 [EMAIL PROTECTED]:/lib64/ > > | Password: > > | /bin/bash: No such file or directory > > \-- > > > > 1. Boot the system from a LiveCD. > > > I have Ubuntu Fiesty 7.04 Desktop x86, do i need to download "64bit AMD > and Intel computers" server edition of Ubuntu? As server is intel 64 bit > processor. > > 2. Re-mount the hard-disk partitions in rw mode. > > > I believe i need to mount the root file system and copy the /bin/* and > then /lib64/* from working host, is there anything else i need to take care? > > 3. Copy the libc file through the network/USB. > I assume libc mean /lib/* and /lib64/*. As Ashish said before.. depends whether you are using 32 or 64 bit. > > 4. Unmount the partitions. > > > > 5. Reboot into the hard-disk. > > > What after that, should i go and re-install glibc-2.3.3 along with its > dependent packages or it is not required ? Then you should reboot the system from HDD and hope it works. -- Manish ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
Re: [ilugd] glibc2.6.1 problem - Urgent!
Hi, - On 11/29/07, Yashpal Nagar <[EMAIL PROTECTED]> wrote: | I have Ubuntu Fiesty 7.04 Desktop x86, do i need to download "64bit AMD | and Intel computers" server edition of Ubuntu? As server is intel 64 bit | processor. \-- Any LiveCD that can boot into the system. - | I believe i need to mount the root file system and copy the /bin/* and | then /lib64/* from working host, is there anything else i need to take care? \-- lib should be sufficient. - | I assume libc mean /lib/* and /lib64/*. \-- I mentioned as libc, in general. - | What after that, should i go and re-install glibc-2.3.3 along with its | dependent packages or it is not required ? \-- When you are able to log into the system, just use it. libc is what you have restored back by copying. Why do you want to re-install? SK -- Shakthi Kannan http://www.shakthimaan.com ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
Re: [ilugd] glibc2.6.1 problem - Urgent!
Shakthi Kannan wrote: > Hi, > > - On 11/29/07, Yashpal Nagar <[EMAIL PROTECTED]> wrote: > | I tried scping from other host but > | host2: # scp /lib64/ld-linux-x86-64.so.2 [EMAIL PROTECTED]:/lib64/ > | Password: > | /bin/bash: No such file or directory > \-- > > 1. Boot the system from a LiveCD. > I have Ubuntu Fiesty 7.04 Desktop x86, do i need to download "64bit AMD and Intel computers" server edition of Ubuntu? As server is intel 64 bit processor. > 2. Re-mount the hard-disk partitions in rw mode. > I believe i need to mount the root file system and copy the /bin/* and then /lib64/* from working host, is there anything else i need to take care? > 3. Copy the libc file through the network/USB. I assume libc mean /lib/* and /lib64/*. > 4. Unmount the partitions. > > 5. Reboot into the hard-disk. > What after that, should i go and re-install glibc-2.3.3 along with its dependent packages or it is not required ? Regards Yash ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
Re: [ilugd] glibc2.6.1 problem - Urgent!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ,--- Yashpal Nagar writes: [...] | I tried scping from other host but | host2: # scp /lib64/ld-linux-x86-64.so.2 [EMAIL PROTECTED]:/lib64/ | Password: | /bin/bash: No such file or directory | :( oops, ssh-ing requires shell. NFS. Or do you've busybox or some other statically linked shell on your box. Try launching that, you'll be able to execute process but that process won't be able to load any .so . Also look for some bash hacks, I hope you've bash running already. If you can take your box down, boot into installation with some other LiveFS. HTH - -- Ashish Shukla आशीष शुक्ल http://wahjava.wordpress.com/ ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHTbpFHy+EEHYuXnQRAhiMAKDlF91h48zngwNA+kg4h1ezR9UG4gCg5i2P +yiNArNufAaNMapIDxPa6bE= =69au -END PGP SIGNATURE- ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
Re: [ilugd] glibc2.6.1 problem - Urgent!
Hi, - On 11/29/07, Yashpal Nagar <[EMAIL PROTECTED]> wrote: | I tried scping from other host but | host2: # scp /lib64/ld-linux-x86-64.so.2 [EMAIL PROTECTED]:/lib64/ | Password: | /bin/bash: No such file or directory \-- 1. Boot the system from a LiveCD. 2. Re-mount the hard-disk partitions in rw mode. 3. Copy the libc file through the network/USB. 4. Unmount the partitions. 5. Reboot into the hard-disk. SK -- Shakthi Kannan http://www.shakthimaan.com ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
Re: [ilugd] glibc2.6.1 problem - Urgent!
> > | TUWIGMAMS02:/bin # ls| -bash: /bin/ls: No such file or directory| > > TUWIGMAMS02:/bin # cp| -bash: /bin/cp: No such file or directory| > > TUWIGMAMS02:/bin # rpm -qa| -bash: /bin/rpm: No such file or directory| > > TUWIGMAMS02:/bin # cd .. > > | Could anyone please provide help, what are the options i do have now! > > I'm able to reproduce above status by removing my ELF sharedexecutable > > interpreter (not actually interpreter but kind of runtimedynamic library > > linker) which resides at /lib64/ld-linux-x86-64.so.2(for AMD64 > > architecture) or /lib/ld-linux.so.2 (for IA-32architecture). So by removing > > glibc-2.6 you wiped off your ELF sharedexecutable interpreter. Copy from > > some working live filesystem toreach a working state. > > > I tried scping from other host but > host2: # scp /lib64/ld-linux-x86-64.so.2 [EMAIL PROTECTED]:/lib64/ > Password: > /bin/bash: No such file or directory Assuming your system reboots back up in SLES; how about booting the system with a live CD, mounting the affected filesystem and copying the file from remote system to the affected machine? If you have not rebooted since the issue or are avoiding reboot fearing that you will not be able to get it to boot again, then please ignore the above suggestion. -- Manish ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
Re: [ilugd] glibc2.6.1 problem - Urgent!
Ashish Shukla आशीष शुक्ल wrote: > -BEGIN PGP SIGNED MESSAGE-Hash: SHA1 > ,--- Yashpal Nagar writes:| Hi All > Hi, > | One of my mate upgraded glibc from glibc-2.3.3 to glibc-2.6.1-18 on a | > production server SLES 9 SP3 withou thinking any consequences. This also | > required to install openssl-devel-0.9.8a-18.4 & openssl-0.9.8a-18.4 as | one > of the dependencies for glibc-2.6.-18, while compling NRPE pluging. > What is 'compling NRPE pluging' ? > NRPE plugin agents for monitoring the system like CPU, Memory , Disk etc. > | Now i have removed the glibc-2.6, openssl-devel-0.9.8a-18.4 , | > openssl-0.9.8a-18.4 after looking glibc2.3.3 is still there. Which has | > invited other problems like- > It seems, upgrade is not proper, you should've removed glibc-2.3.3. > I know it must need not to be upgraded, but with out knowing consequences as i mentioned earlier he moved ahead by mistake. > | TUWIGMAMS02:/bin # ls| -bash: /bin/ls: No such file or directory| > TUWIGMAMS02:/bin # cp| -bash: /bin/cp: No such file or directory| > TUWIGMAMS02:/bin # rpm -qa| -bash: /bin/rpm: No such file or directory| > TUWIGMAMS02:/bin # cd .. > | Could anyone please provide help, what are the options i do have now! > I'm able to reproduce above status by removing my ELF sharedexecutable > interpreter (not actually interpreter but kind of runtimedynamic library > linker) which resides at /lib64/ld-linux-x86-64.so.2(for AMD64 architecture) > or /lib/ld-linux.so.2 (for IA-32architecture). So by removing glibc-2.6 you > wiped off your ELF sharedexecutable interpreter. Copy from some working live > filesystem toreach a working state. > I tried scping from other host but host2: # scp /lib64/ld-linux-x86-64.so.2 [EMAIL PROTECTED]:/lib64/ Password: /bin/bash: No such file or directory :( > | Best Regards| Yash > HTH- -- Ashish Shukla आशीष शुक्ल > http://wahjava.wordpress.com/·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· > ·-·· ·-·-·- -·-· --- ---BEGIN PGP SIGNATURE-Version: GnuPG v1.4.6 > (GNU/Linux) > iD8DBQFHTbMAHy+EEHYuXnQRAkWGAJ0cA5A+V83RxlGp4kqHnsD8QIq+9QCgstzHWr5gmBpfW+FDhEtCCUWcUq4==7AfQ-END > PGP SIGNATURE- > ___ilugd mailinglist -- [EMAIL > PROTECTED]://frodo.hserus.net/mailman/listinfo/ilugdNext Event: > http://freed.in - February 22/23, 2008Archives at: > http://news.gmane.org/gmane.user-groups.linux.delhi > http://www.mail-archive.com/ilugd@lists.linux-delhi.org/ > > . > > ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
Re: [ilugd] glibc2.6.1 problem - Urgent!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ,--- Yashpal Nagar writes: | Hi All Hi, | One of my mate upgraded glibc from glibc-2.3.3 to glibc-2.6.1-18 on a | production server SLES 9 SP3 withou thinking any consequences. This also | required to install openssl-devel-0.9.8a-18.4 & openssl-0.9.8a-18.4 as | one of the dependencies for glibc-2.6.-18, while compling NRPE pluging. What is 'compling NRPE pluging' ? | Now i have removed the glibc-2.6, openssl-devel-0.9.8a-18.4 , | openssl-0.9.8a-18.4 after looking glibc2.3.3 is still there. Which has | invited other problems like- It seems, upgrade is not proper, you should've removed glibc-2.3.3. | TUWIGMAMS02:/bin # ls | -bash: /bin/ls: No such file or directory | TUWIGMAMS02:/bin # cp | -bash: /bin/cp: No such file or directory | TUWIGMAMS02:/bin # rpm -qa | -bash: /bin/rpm: No such file or directory | TUWIGMAMS02:/bin # cd .. | Could anyone please provide help, what are the options i do have now! I'm able to reproduce above status by removing my ELF shared executable interpreter (not actually interpreter but kind of runtime dynamic library linker) which resides at /lib64/ld-linux-x86-64.so.2 (for AMD64 architecture) or /lib/ld-linux.so.2 (for IA-32 architecture). So by removing glibc-2.6 you wiped off your ELF shared executable interpreter. Copy from some working live filesystem to reach a working state. | Best Regards | Yash HTH - -- Ashish Shukla आशीष शुक्ल http://wahjava.wordpress.com/ ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHTbMAHy+EEHYuXnQRAkWGAJ0cA5A+V83RxlGp4kqHnsD8QIq+9QCgstzH Wr5gmBpfW+FDhEtCCUWcUq4= =7AfQ -END PGP SIGNATURE- ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
