Skip to main content

First few commands to run on an unknown Linux server

 If you get to troubleshoot some unknown Linux server, running these few commands will be useful.


1. Check who's logged in

w

This is a cool one-letter command to see who else logged into the server. It will list the usernames and even you can find the IP and the connection type. In the following example, I've logged in as the "user".

w command


If you see, some other users, watch out for unauthorized access.

2. Identify the OS

There are different commands to identify what kind of Linux distribution that you are dealing with. Knowing this is crucial to decide what commands to use later.

cat /etc/os-release

Usually, in Linux distributions, you have a file /etc/os-release. Basically, you can see everything you need to know about the OS in this file. 

cat /etc/os-release

3. See running processes

top

This basically lists the processes running with the CPU and memory consumption.

With this, we can get an idea about what kind of apps running on the server and if any of them uses too much CPU or memory.


4. See disk space usage

df -h

This provides the disks that are being used and their usage of them. If there's a disk with 100% or running out of space, you can identify that.

df -h

5. See memory usage

free -h

With this, you can see the memory usage of the system. If the system is running out of memory, you can spot that.

free -h

6. See the command history

This is one of the critical commands that you can use to identify what commands have been used in the past. This has saved my neck on several critical occasions so I'm forever grateful to the person who developed the history command lol.

It lists the history of commands that has been executed in the past. If you don't know anything about the server, this is so much important to see what services have been used in the past, and which commands have been executed.

history

Also, if you need to find out about a specific service you can grep the history to identify the commands related to that service.

eg:

history | grep nginx


7. See network ports

netstat -ntlp

This command allows you to see which ports are open and listening in the system. Based on that, you can even say if an application server (something like Apache, Nginx, or even Tomcat) is running or not. 


netstat



Running these commands will give you a basic idea about the system that you are about to deal with.

If there are any other commands that you think will be important to deal with an unknown system, please comment below :)



Comments

Popular posts from this blog

Install Docker on Windows 11 with WSL Ubuntu 22.04

This is to install Docker within Ubuntu WSL without using the Windows Docker application. Follow the below steps. Install Ubuntu 22.04 WSL 1. Enable Windows Subsystem for Linux and Virtual Machine platform Go to Control Panel -> Programs -> Programs and Features -> Turn Windows features on or off 2. Switch to WSL 2 Open Powershell and type in the below command. wsl --set-default-version 2 If you don't have WSL 2, download the latest WSL 2 package and install it.  3. Install Ubuntu Open Microsoft Store and search for Ubuntu. Select the version you intend to install. I'd use the latest LTS version Ubuntu 22.04. Click on the Get button. It will take a couple of minutes to download and install. 4. Open up the installed Ubuntu version that was installed. If you get an error like the below image, make sure to install the WSL2 Kernel update .  If it's an older Ubuntu version the error message would be something like the image below. Error: WSL 2 requires an update to its ...

How to fix SSLHandshakeException PKIX path building failed in Java

TL ; DR 1. Extract the public certificate of the website/API that you are trying to connect from your Java application. Steps are mentioned in this post 2. Use the Java keytool to install the extracted certificate into the "cacerts" file (Trust store) keytool -import -trustcacerts -alias <domain name> -file <public certificate>.cert -keystore /path_to_java_home/jre/lib/security/cacerts -storepass changeit 3. Restart your Java application Exception A typical exception stack trace would look like below. javax.net.ssl. SSLHandshakeException : sun.security.validator.ValidatorException: PKIX path building failed : sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1959) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302) at sun.security.ssl.Handshake...

Automatically open Chrome developer tools in a new tab

Sometimes we need to check the console or the network transactions of a link that opens up in a new tab. By default, the Chrome developer tools are not opening in a new tab. So, by the time when we hit F12 and open the dev tools, part of the information we needed could be already gone.  There's a setting in dev tools where you can keep the dev tools open automatically in a new tab. To enable that, hit F12 and open up the dev tools. Click on the settings icon in the top right corner. In the Preferences section, scroll down to the bottom. You'll be able to find the option to Auto-open DevTools for popups. Select the checkbox and we're good to go!