Partner with experts to accelerate your digital transformation journey
Bobcares

How to troubleshoot server down issues

PDF Header PDF Footer

How to troubleshoot server down issues? Let’s discuss.

At times, network issues might occur and all the servers in a Datacenter can go down. This can lead us into some unlucky instances.

As part of our Server Management Services, we assist our customers with several server queries.

Today, let us see how we can troubleshoot server down issues.

 

How to troubleshoot server down issues

Initially, we need to make sure if it is a false alert.

To do so, we connect to the server via ping or telnet to any of the running ports and check if it is really down or not.

The commands are really simple:

ping server ip
telnet serverip port number

For example,

ping 186.65.23.15
telnet 186.65.23.15 22

The above commands can perform in different operating systems such as Linux, Mac, or Windows.

If the server responds to the ping fine without any data loss as given below, then everything is fine. It is a false alert.

-
ping google.com -c10
PING google.com (74.125.129.100) 56(84) bytes of data.
10 packets transmitted, 10 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 326.477/326.477/326.477/0.000 ms
-

However, if the server is not responding to ping or has any packet loss, then our Support Techs recommend contacting DC or hosting providers to get the issue sorted out.

Let us see what one of our customers came across.

When he received the server down alert, he couldn’t access the server. Even a reboot couldn’t bring the server back online.

So, we connect to the server via IPMI and found that the server was stuck at fsck and that led to the problem.

There can be so many reasons for the server being down.
  • High load in the server
  • Faulty equipment
  • High temperature in the DC room
  • Partition being full
  • No disk space in the server
  • Power connection cable

If the server is stuck, a reboot from DC is a better option.

Once the server is up, we need to check the reason why it went down.

To find the reason, we refer to the below logs location in the server.

For Linux:

/var/log/messages —
dmesg |grep less
/var/log/boot.log
/var/log/fsck

For Windows:

Start>>Run>>eventvwr

Suppose, the load was high due to spam or the number of incoming connections to HTTP being high, we need to troubleshoot accordingly.

However, if the server was down due to a high load, then we check the incoming connections and block them in the server.

If a drive is faulty, then we need to replace them. In our case, the server was running fsck check and that is why it was taking time.

Several reasons may lead to fsck check running:

  • The complete unmounting ability of the hard disk
  • Using a third-party utility to delete the extended partition
  • Problems with any filesystems
  • Power failure
  • Incomplete shut down
  • Hardware failure

The above causes result in file system operations being incomplete.

The few sample logs we can find in the Linux logs are as below.

Checking all file systems.
[/sbin/fsck.ext3 (1) — /] fsck.ext3 -a /dev/xvda1
/: clean, 56079/1310720 files, 1243508/2621440 blocks
[/sbin/fsck.ext3 (1) — /var/www/virtual] fsck.ext3 -a /dev/sdf
fsck.ext3: No such file or directory while trying to open /dev/sdf
/dev/sdf:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193

After the fsck check is complete, the server will be up fine without further errors.

[Stuck with server down? We can help you through it]

 

Conclusion

In short, network issues might cause the Datacenter to go down. This can lead us into some unlucky instances. However, today we saw how to troubleshoot server down issues.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";
0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Get featured on the Bobcares blog and share your expertise with a global tech audience.

WRITE FOR US
server management

Spend time on your business, not on your servers.

TALK TO US

Or click here to learn more.

Speed issues driving customers away?
We’ve got your back!

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF