LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 06-27-2008, 11:30 AM   #1
skubik
Member
 
Registered: May 2003
Location: A dark corner in Canada
Distribution: Slackware 10.1
Posts: 100

Rep: Reputation: 17
Accidentally Removed glibc-solibs package on Slack 10.1


Last night I accidentally removed my glibc-solibs package from my Slack 10.1 system. I didn't mean to- I was poking around pkgtool a few days ago and left it open in a terminal... apparently on a menu selection to remove a certain package (I was looking at the packages because I needed to upgrade my glibc libraries to make Firefox 3 work... I was getting a TLS Data error), and I simply made the terminal active and pressed 'Enter'- and it began removing the package. Dumb, yes, I know.

Not much has broken, but as a result Samba now aborts when I try and start it. This is what the log files say:

Code:
[2008/06/27 16:10:15, 0] smbd/server.c:main(760)
  smbd version 3.0.10 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2004
[2008/06/27 16:10:15, 0] lib/fault.c:fault_report(36)
  ===============================================================
[2008/06/27 16:10:15, 0] lib/fault.c:fault_report(37)
  INTERNAL ERROR: Signal 11 in pid 17470 (3.0.10)
  Please read the appendix Bugs of the Samba HOWTO collection
[2008/06/27 16:10:15, 0] lib/fault.c:fault_report(39)
  ===============================================================
[2008/06/27 16:10:15, 0] lib/util.c:smb_panic2(1482)
  PANIC: internal error
[2008/06/27 16:10:15, 0] lib/util.c:smb_panic2(1490)
  BACKTRACE: 18 stack frames:
   #0 /usr/sbin/smbd(smb_panic2+0x111) [0x81caa51]
   #1 /usr/sbin/smbd(smb_panic+0x1a) [0x81ca93a]
   #2 /usr/sbin/smbd [0x81b7fd8]
   #3 [0xffffe420]
   #4 /lib/libc.so.6 [0xb7c66c99]
   #5 /lib/libc.so.6(iconv+0x6e) [0xb7c662ce]
   #6 /usr/sbin/smbd [0x81d64b6]
   #7 /usr/sbin/smbd(smb_iconv+0x113) [0x81d6623]
   #8 /usr/sbin/smbd [0x81b50a4]
   #9 /usr/sbin/smbd(convert_string+0x23d) [0x81b569d]
   #10 /usr/sbin/smbd [0x81c5dc2]
   #11 /usr/sbin/smbd(init_doschar_table+0x2e) [0x81c5e4e]
   #12 /usr/sbin/smbd(init_iconv+0xd6) [0x81b4e26]
   #13 /usr/sbin/smbd(lp_load+0x185) [0x807c615]
   #14 /usr/sbin/smbd(reload_services+0x63) [0x82265e3]
   #15 /usr/sbin/smbd(main+0x26b) [0x8226ddb]
   #16 /lib/libc.so.6(__libc_start_main+0xe0) [0xb7c65390]
   #17 /usr/sbin/smbd [0x8075241]
... also, my time settings are completely off. As of now, my system says it is 4:20pm, when it is actually 10:20am. Seamonkey (I couldn't use Firefox 3) and Thunderbird also fail to start now.

I thought it was as simple as downloading the package again and installing it. I did this as root- but it didn't work, the problems remain. I've even gone so far as to install other glibc- packages such as the entire glibc-2.3.4-i486-1 package, glibc-i18n, and glibc-zoneinfo, in addition to glibc-solibs. But nothing fixes the problem and I'm now stressing over how to fix my stupid mistake as I NEED this system for development projects I have on the go right now.

I'm reluctant to outright upgrade to Slack 12 as I'm worried it will wipe out all the little customizations I've put into my system over the past few years, only causing more work for me above and beyond this.
The only thing I can think of as to why reinstalling these packages aren't working is because at some point I *may* have upgraded my glibc libraries and rebuilt them from source at some point- but I'm not 100% sure.
Thus, would upgrading to the glibc libraries in Slack 12 even work? Are there more dependency issues involved that, again, would only make things worse in the long-run? Is there perhaps something easy I'm missing in attempting to reinstall these packages? I read in the Slack 12 UPGRADE.TXT file to go into single user mode before upgrading glibc-solibs, so perhaps this is what I need to do to reinstall them as well??

I'd really appreciate ANY insight into this so I can save myself from pulling out my hair for the rest of the weekend and actually try and get some other projects done instead.

Thanks!

- skubik
 
Old 06-27-2008, 11:39 AM   #2
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.0
Posts: 2,244

Rep: Reputation: 621Reputation: 621Reputation: 621Reputation: 621Reputation: 621Reputation: 621
See here for a glibc recovery guide.
 
Old 06-30-2008, 03:58 PM   #3
skubik
Member
 
Registered: May 2003
Location: A dark corner in Canada
Distribution: Slackware 10.1
Posts: 100

Original Poster
Rep: Reputation: 17
Thanks for the suggestion. I tried doing this Friday (before leaving town for the weekend)- but to no avail. Samba still doesn't work, Mozilla apps still won't load. I'm *tempted* to try installing the same packages from a more recent version- like Slack 11, maybe 12. Something tells me I *may* have manually upgraded those libraries a while back, but not sure.

Any other insights??

Thanks,

- skubik.
 
Old 06-30-2008, 04:48 PM   #4
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.0
Posts: 2,244

Rep: Reputation: 621Reputation: 621Reputation: 621Reputation: 621Reputation: 621Reputation: 621
If you've played around with glibc versions, you've got a serious problem. You should always know what you have done to your system and how to recover it if something goes wrong (this is why I use SlackBuilds instead of blindly performing `./configure; make; make install`). I would strongly urge you to stick with the glibc versions that shipped with your version of Slackware, or otherwise upgrade to a newer version of Slackware. HOWEVER, don't even attempt to upgrade a broken system -- you will probably cause more problems than you solve by doing so. You should restore your system to a working state using only the official Slackware 10.1 packages if possible. Forget about Firefox until your system is back up and functional. If it truly does require a newer version of glibc, then your best bet would be to upgrade AFTER fixing your system (but the upgrade procedure from 10.1 to 12.1 is very gruesome indeed -- it requires upgrading to each release sequentially. You cannot upgrade directly from 10.1 to 12.1. You must upgrade from 10.1 to 10.2, then 10.2 to 11.0, then 11.0 to 12.0, then 12.0 to 12.1. The upgrade from 11.0 to 12.0 is quite involved since 11.0 uses a 2.4 kernel while 12.0 uses a 2.6 kernel).

If I were you, which I'm not, I would follow the glibc recovery instructions I linked to previously and reinstall all of the critical packages from 10.1 that you may have upgraded along the way following that procedure for upgrading (if you simply upgrade things in a running system, it could cause troubles because of certain running services). Make sure all of the stock Slackware 10.1 stuff works (don't worry about Firefox 3 yet). That includes Samba, etc.

Beyond that, it's difficult to know what you've done to your system and how to recover it. I'm also not knowledgeable enough to help beyond that, I'm afraid, so you're on your own unless someone else decides to step in.

You would also be smart to back everything up before trying anything like this.
 
Old 07-02-2008, 01:05 AM   #5
skubik
Member
 
Registered: May 2003
Location: A dark corner in Canada
Distribution: Slackware 10.1
Posts: 100

Original Poster
Rep: Reputation: 17
Resolved! (mostly)

I decided to take a risk and upgrade my current Slackware packages to those found in slackware-current (currently 12.1). Initially I wanted to simply download the glibc source and compile it directly- but my version of gcc is too old and required an upgrade anyways, so I killed two birds with one stone and upgraded using 'upgradepkg' to the following packages:

gcc-4.2.3-i486-1
gcc-g++-4.2.3-i486-1
gdb-6.8-i486-1
glibc-2.7-i486-10
glibc-profile-2.7-i486-10
glibc-solibs-2.7-i486-10
glibc-zoneinfo-2.7-noarch-10

so far things seem to be in working order again. Samba doesn't abort like it used to. I even have Firefox 3 running!!!

The only thing that still isn't working properly is my date/time. I request an update from the time server- and the offset is next to nothing: like 0.59123, and the time stays the same- which is about 6 hours fast. I'm sure there is an answer for that somewhere.

Beyond that, things seem to be working just fine.

- skubik
 
Old 07-03-2008, 05:41 PM   #6
JazzItSelf
Member
 
Registered: Oct 2003
Location: Boston
Distribution: Slackware64-current
Posts: 42

Rep: Reputation: 18
Why the long upgrade path?

Quote:
Originally Posted by T3slider View Post
(but the upgrade procedure from 10.1 to 12.1 is very gruesome indeed -- it requires upgrading to each release sequentially. You cannot upgrade directly from 10.1 to 12.1. You must upgrade from 10.1 to 10.2, then 10.2 to 11.0, then 11.0 to 12.0, then 12.0 to 12.1. ...
Why can't you go straight from 10.x to 12.1? I suppose I can see the need to do the kernel separately, but why can't the rest of the system make that jump? Is there a reason? Or is it just good form to do all of the intermediate steps?

(rereading that, I can see some potential for it to be taken maliciously which is not at all my intent! Please don't take it that way!)
 
Old 07-04-2008, 09:26 PM   #7
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.0
Posts: 2,244

Rep: Reputation: 621Reputation: 621Reputation: 621Reputation: 621Reputation: 621Reputation: 621
Quote:
Originally Posted by JazzItSelf
(rereading that, I can see some potential for it to be taken maliciously which is not at all my intent! Please don't take it that way!)
Don't worry, it really didn't sound at all malicious to me. I understood your intent.
Quote:
Originally Posted by JazzItSelf
Why can't you go straight from 10.x to 12.1? I suppose I can see the need to do the kernel separately, but why can't the rest of the system make that jump? Is there a reason? Or is it just good form to do all of the intermediate steps?
I don't pretend to be an expert on the issue, but I'd be willing to bet a fairly large sum of money that something would break along the way if you tried to simply upgrade 10.1 to 12.1. First of all, the 2.4 to 2.6 kernel jump isn't addressed until the 11.0 to 12.0 transition. However, beyond that, some packages will most certainly break. If you *did* want to upgrade straight from 10.1 to 12.1, you would need to research all of the changes between 10.1 and 12.1 (including the incremental changes in 10.2, 11.0, and 12.0) to make sure that no packages will immediately break. For example, I think 11.0 is already setup for 2.6 kernel usage (because although not the default option, the 2.6 kernel was included in testing/, whereas this is not the case with 10.1). Some changes in the system are required between the 2.4 kernel and the 2.6 kernel (I don't know much about this, but as a very, very simple example, the 2.6 kernel uses the /sys filesystem instead/in addition to the /proc filesystem). Stuff like this may break.

Since the earliest version of Slackware that I used was 11.0, I don't know how much has changed. However, even going from 11.0 to 12.1 will almost certainly break things and cause extra frustration.

Last edited by T3slider; 07-04-2008 at 09:28 PM.
 
Old 07-04-2008, 10:12 PM   #8
skubik
Member
 
Registered: May 2003
Location: A dark corner in Canada
Distribution: Slackware 10.1
Posts: 100

Original Poster
Rep: Reputation: 17
I've already upgraded my kernel to 2.6 on my Slack 10.1 system (2.6.21.5 specifically) and it's been smooth sailing for the mostpart. And even my 'upgraded' glibc libraries that originally kicked off this thread have been going strong. No problems discovered so far- and I don't really expect to find many (if any) more.
So perhaps a transition from 10.1 to 12.1 wouldn't be terrible- especially if you tend to keep your install as close to 'stock' as possible. I have manually compiled MANY applications and system libraries on my system as opposed to simply installing/upgrading packages- and there have been no severe issues.
HAL doesn't really work on my system- but as I understand it, HAL wasn't really implemented until 11.x anyways. I've been told that upgrading from 10.x to 12 could cause problems.
 
Old 08-08-2008, 05:12 PM   #9
skubik
Member
 
Registered: May 2003
Location: A dark corner in Canada
Distribution: Slackware 10.1
Posts: 100

Original Poster
Rep: Reputation: 17
Update

Thought I would add to this thread briefly- if only for 'documentation' purposes in the event it helps prevent someone else from pulling their hair out of their scalp.

Since my 'upgrade' last month I haven't had a need to compile any new software on my system. Today, however, I tried to compile MySQL 5.0 from source and received an error:

C compiler cannot create executables
... and told me to refer to config.log (which conveniently enough, also tells me to look at config.log- but that's besides the point).

I unfortunately don't have the config.log output anymore (it has been rewritten by the working compilation of the software), but it did make mention of ld returning with exit status 1 (or something to that degree).

The solution was to once again download the appropriate package from packages.slackware.it, and using 'upgradepkg', upgrade to package:

binutils-2.17.50.0.17

I tried compiling MySQL again, and voila! It's compiling just fine as we speak. (Naturally if this fails, there will be yet another follow-up post, but I don't foresee that happening the way things are going now).

Hope that helps someone out!
 
  


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
Accidentally removed shadow package hussar Slackware 3 12-24-2005 06:31 AM
accidentally removed /dev/cdrom verbose Linux - General 18 10-26-2005 03:44 PM
I accidentally removed the netstat command ! markraem Solaris / OpenSolaris 6 10-03-2005 10:18 AM
newbie - removed partition accidentally kristalchimera Debian 6 07-12-2003 11:36 PM
I accidentally removed lilo from my bootsector. Grafbak Linux - Newbie 2 06-20-2003 03:22 PM


All times are GMT -5. The time now is 05:54 PM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration