The “HOSTNAME “ of your server is found under: SERVER CONFIGURATION->SERVER DATA.
However, if you get one single return message to the “ping command”, then it implies that you can’t make a connection to the server.
You can restart your computer through your customer service area. Now if the “ping command” was successful, choose the following options:“Server Configuration-> “Recovery Manager”->”Normal Boot” (do not select “reset machine)”.
If the “ping command” was not successful choose ”Normal Boot” as well as “reset machine”.
In case the restart does not solve your problem, or if you know the server has crashed several times then follow steps outlined below.
These set of descriptions can only be used if you are logged into your HighEnd-/HighQ-Server as the „root“. This connection could be made either through:
Or through;
Also have a look at:
DS: How do I connect to my HighEnd-/HighQ-Server via PuTTY?
DS: How do I create a connection to my HighEnd-/HighQ-Server via the remote console?
In order to make sure that the crash was not caused by improper configuration of a non-standard installation of the operating system or by improper configuration of installed software, then follow the steps outlined below:
1. Set up a direct connection to the server via SSH console and log on as the “root” user.
If you can’t set up an SSH connection then set up the connection via the remote console.
2. Check the content of your log files, by using the following command:
vi /var/log/warn
Search for entries within the time span in which the server crashed. Can you find entries that point to improperly configured software ;or due to the crash of a system relevant file; or due to any other unexpected behaviour?
If you do find relevant entries pointing to improper configuration, then make sure to configure the particular software(service/application) correctly.
The protocol files(log files) of the particular service f application could provide you with further information about the source of the error in the configuration of the software.
If you find an entry classified as EMERG , then it points to a critical system error. This error is most likely the source of the crash of the server.
3. Save the file, "vi /var/log/warn" as a duplicate in the folder, “/tmp”, so that you have it available, just in case the technical hotline requires it. You create this duplicate using the command:
cp /var/log/warn /tmp
4. Go through the messages that were created during the booting process for entries that point to errors. Use the following command for this:
dmesg | grep [Ee]rro
This command goes through the log files created during the reboot looking for lines containing: “Erro” or “erro”.
Depending on the circumstance you will get lines with the words “Error”, “error” or “erroneous”. Only such lines are relevant to the server analysis.
dmesg | grep [Ff]ault
This command goes through the log files created during the reboot looking for lines containing: “Fault” or “fault”
Depending on the circumstance you will get lines with the words “Fault”, “fault” or “faulty”. Only such lines are relevant to the server analysis.
dmesg | grep [Nn]o
This command goes through the log files created during the reboot looking for lines containing: “No” or “no”.
Depending on the circumstance you will get lines with the words “none”. Only such lines are relevant to the server analysis.
dmesg | grep [Dd]effect
This command goes through the log files created during the reboot looking for lines containing: “Defect” or “defect”
Depending on the circumstance you will get lines with the words “Defect” or “defect”. Only such lines are relevant to the server analysis
dmesg | grep [Bb]ad
This command goes through the log files created during the reboot looking for lines containing: “Bad” or “bad”
Depending on the circumstance you will get lines with the words “bad” or “Bad”. Only such lines are relevant to the server analysis.
dmesg | grep [Ff]ail
This command goes through the log files created during the reboot looking for lines containing: “Fail” or “fail”
Depending on the circumstance you will get lines with the words “failed” or “Failed”, “Failure” or “failure”. Only such lines are relevant to the server analysis.
dmesg | grep [Ii]ncorrect
This command goes through the log files created during the reboot looking for lines containing: “Incorrect” or “incorrect”
Depending on the circumstance you will get lines with the words “Incorrect” or “incorrect. Only such lines are relevant to the server analysis.
5. Save save all messages from the booting process in the temporary folder, "/tmp", so that this is accessible if required by our technical team through e-mail. You can do this using the following command:
dmesg > /tmp/dmesg
6. Save the connection to the remote console in case you haven’t done this by now.
7. Reboot your server through the remote console by using the command:
reboot
The reboot of your server begins immediately after this.
8. Allow the reboot process run as far as possible; in the optimum case, let it run until the server is fully rebooted. Copy all the messages shown over the remote console, during the reboot, into a text file on your local computer irrespective of whether the reboot was successful or not. You can copy all these messages into the “clipboard” by highlighting the messages with the left mouse.
9. Check the content of the saved text files for error messages.
In case the start of one or more services(Daemons) or any other program (script ) appears with the result “failed” or with any similar comment, then check the configuration of this service/program/or script. And correct it.
Any software that doesn’t belong to the “standard configuration” of your HighEnd-/HighQ-Servers as provided by STRATO AG will not be supported by us.
10. If with the help of the above mentioned steps;
a) you were able to localize the cause of the crash, but can’t fix it ;
b) you weren’t able to localize the cause of the crash;
then please send us a copy of the files you created. i.e. copies of .
- /tmp/warn
- /tmp/dmesg
- the txt file you created when you rebooted your server over the remote console.
Now, send us over our MAIL CENTER:
Don’t forget to provide us with a detailed description of the way your server was behaving immediately before/after the crash as well as during the reboot process. Did the crash first occur after installing particular software?
http://www.strato-hosting.co.uk/contact.html 
