Big bug system in centos server
 

Hi everybody
There is my problem ,after a wrong manipulation after uninstall syslog in centos 5.6 server i removed 83 packages :YUM,RPM,vim,ls..............so i can't even try to install a new package because i miss yum and rpm.
When I use rpm command it says an error like below:
rpm: error while loading shared libraries: libssl.so.6: cannot open shared object file: No such file or directory

When i use wget to download yum:
When i use ls:
So i can't do anything howa can i resolve this problem ???help me plzzzzzzzz

Reinstall.
Next time you should actually read what is written on the screen to avoid such situations.

this is the only way to resolve it,doesn't exist a mode rescue to fix the system?

You have removed packages that are essential for the system to run properly. I would definitely go for a reinstall to get a working system.

Or you could restore from backup if you have a backup of the system. This is why we make backups.

this is a test server ,the person who installed centos in this server is absent and i don't have idea if backup exist,how can i verify it and access to backup?and if i reinstall centos can i restor my fil system ,configurations and partitions?
(i can connect in root mode)

Search for a backup medium?

If you don't repartition the disk you will have the same partition layout as before the installation. I don't know what you mean with restoring the filesystem, please explain that. If you want to backup your configurations you should backup the needed files from the /etc directory for systemwide configuration and the files/folders beginning with a dot in your home-folder for user configurations.

like i said i use this server for test and i removed all essential packages system( the administrator who use it will be really angry) ,so i would like to fix the system by (reinstalling centos) but in the same thing restore all configuration file that exist already ,so he can't know what really happened!

If he is a somewhat good administrator he definitely will recognize that. The best way I would think is to simply tell him what you have done. It can't be so bad, since he seems to have given you the root password, don't he?

he definitely can fix this ,but i would like fix it and assume reponsability cause i'm in training period and this error is extremely fatal for a server,now after this accident none can trust me to do an administration operation in a server client(i think in 7 years lol),ithink in a solution :
Transfer the losing library to can use :ls ans wget after that download the packages first yum,and install them from windows cause i connect to the server in ssh mode whit putty from windows 7.what u think?

I doubt that this will work. If you want to look responsible than admit your error to the admin, instead of trying to cover this up. Ask him if he knows a solution and can help you. Show him that you have tried to search for a solution yourself. Ask him why it went wrong. You are in training period. That means that they assume that you will make errors. As you stated, this was a testing server, not a production machine, so no harm done.

One question, what makes you think that your admin is not a member on this forums and actually reading this thread?

i doubt that he's a member of this thread,he's absent today ,i'll try to explain this to him monday ,i hope that he will inderstand ,and i not know why he use this server and if he install an important application !!and for syslog-ng u don't know where can i find a good tutorial of installation into centos i'll try to reinstall it into my personel machine so i will be sure that it doesn't hapened again!!!

Did you learn from this mistake? Do you understand what you did wrong to the extent that you know how to keep it from happening again? If I were in charge, this is what I would be concerned about. I would be able to accept that you made a mistake and value that you learned from it. As the old but very wise saying goes, "shit happens." However, if I thought you made a mistake and tried to cover it up, then I would not be able to trust you at all. Choose your path wisely.

i'm totally ok whit u Noway2 ,i did a mistake and i must not cover it up,i will tell the administrator about this big mistake,and yes i learn alot :
be very careful the next time when i'll try to install something on a server,if u have a guide of installation and configuration of syslog-ng in centos 5.6 i will be tankful ,thank for advice i choose the path of "telling the truth".

The best piece of advice that I can offer you is to be sure you run as root as little as possible. If you are working on an operation and want to issue a few root level commands or open a root owned file you would be well served to make your account a sudo capable account. The problem with running as root is that it is easy to make a typing mistake and irretrievably wipe things out.

With respect to configuring syslog-ng, while not specific to Cent-os, the Gentoo documentation is pretty good. Here is a link to their syslog configuration sheet, including a section on syslog-ng. After configuring the source of the logging, Syslong-ng works with the three sections, destinations, filters, and rules. The syntax is a little bit cryptic, but not terribly so. I suggest that you make a copy of the configuration file you want to modify, and then start by trying to add a log file or two and see what happens. Once you get those working, then proceed to add more. You will need to restart the syslog process in between. Watch for error messages when this happens. If I recall, it will tell you immediately if there is a problem. This way, you will gain insight into what you are doing and why things don't always do what you expect.

Good Luck.