I have a linux server (Debian squeeze) set up. It's primary focus is to run LAMP. I also use it for stuff like mumble (voice chat) and minecraft servers.
In the beginning everything was running fine. Then things started to happen. Stuff like java failing to run without headerless mode, and completely losing the ability to resolve hostnames. I fixed the hostname resolving by a reboot - which I've heard isn't really a desired fix on linux systems.
I do have physical access to the server computer (I built it myself), but it's not located in my house. So I use SSH to interact with it. Yesterday I noticed that it doesn't show the path in the ssh client but rather only "-bash-4.1#".
Also after the reboot when I tried starting the mumble server it just says missing file: "/etc/mumble-server.ini"
This server contains vital (and confidential) company information. Should I be worried that some hacker got into it? Did I install some kind of malware on it?(Doubt I did)
EDIT: I cannot seem to access the website it is supposed to be hosting. It is a vital part of the companys web services. This is real bad.
I also now remember mistakenly running something like rm .* in /etc with root a couple weeks ago. It worked fine then so I ignored it. Is there anything I can do to fix this? Did I really screw up?
UPDATE: It seems apache fails to run due to a missing mime.types file. It should be located in /etc. Is there a command to restore it?
UPDATE: Since everything else failed, I am reinstalling the OS and server software. Good thing I have all the vital and confidential info backed up regularly.
rm
command the other week then isn't it likely the site has had issues since then... ? Also this seems like more than just apache has been affected due to your mumble issue above. Sounds like therm
was run in the /etc and not /etc/httpd so who knows what else might be broken... Backups or new build time!history | grep rm
?