losing .so files

[Chris Torske]

Christopher K. Johnson wrote:
> Chris Torske wrote:
> 
>> It keeps on getting worse and worse, loosing the location of more and 
>> more of them.  It isn't really loosing them in the sense that they 
>> aren't on they system.  As like this time around for me, yum is saying 
>> that it can't find "lib-org-apache-bcel-5.0.so".  I was checking the 
>> web for a possible location where is it, and maybe reinstall the 
>> package.  I say it is most times installed in the /usr/lib/ 
>> directory.  Doing "ls /usr/lib/lib-org-apache-bc*" results with 
>> "/usr/lib/lib-org-apache-bcel-5.0.so"; the exact file I am supposedly 
>> missing.  From remembering that most times that directory is 
>> automaticaly checked, when you run ldconfig.  After running that, yum 
>> still complains I am missing that same file.  I have tried on other 
>> times when this has happened, to copy that file around, to pretty much 
>> every single folder I can find; and still doesn't releave the problem. 
>> This problem is not has also been happening on me on other distro's 
>> too, including other versions on kernels.  I have even got it go to 
>> the point, where the system has even lost the a main rpm library.  I 
>> don't remember that exact name off hand.  I just installed this copy 
>> just about 5 days, so it hasn't been too long on this around.  I would 
>> really like to keep this os for more then a month this time around.  
>> Any ideas on how to fix this?  I haven't checked the rpm database yet, 
>> I am planning to check that tomorrow after work.
> 
> 
> Yum's view of what is present or missing is based entirely on the rpm 
> database.  So that's where your problem is.  The question is why.  Have 
> you creashed for forced termination of rpm or yum processing?  If this 
> is a recurring problem on different distros then chances are there is 
> either a hardware problem or a procedural problem.
> 
Hello,

Well; I know I haven't needed to force crashed rpm, yum, or even apt 
yet.  As I have had then all work pretty good and in the end come up 
with this problem.  As for hardware, I know I had one mem stick start 
giving me problems where I couldn't start up at all, so that may have 
been why the other times it happened.  I will see what memtest86 comes 
up with, and see if I replace all my ram or not.  I know for sure, it 
most likely will take a while with 512MB of ram; though I will be at 
work  or sleeping most of the time, so I got plenty of time for it to 
run.  Right now I am hoping it is only a procedural problem that I am 
doing; as it is annoying on finding which ram stick is or isn't bad.  I 
will also try to show the results on checking the rpm database too.

Well, I did check the rpm database with rpmdb_verify; it resulted in 
nothing  did that command on several of the db files there.  Will do 
some additional check later, after the memtest.

Chris