Sign in

All the experts

Run a Linux command

Hello World

Troubleshooting: Server is not reachable or unable to connect

Check if a URL is reachable

Add credentials for various integrations

What is an "Expert"? How do we create our own expert?

Add Jenkins credentials

Add a key-value pair

Add credentials for various integrations

Add AWS credentials

Add Jira credentials

Add Slack credentials

Add Grafana credentials

Add Azure credentials

Add GitHub credentials

Process Grafana Alerts

Managing workspaces and access control

DagKnows Architecture Overview

Managing Proxies

Setting up SSO via Azure AD for Dagknows

All the experts

Enable "Auto Exec" and "Send Execution Result to LLM" in "Adjust Settings" if desired

(Optionally) Add ubuntu user to docker group and refresh group membership

Deployment of an EKS Cluster with Worker Nodes in AWS

Adding, Deleting, Listing DagKnows Proxy credentials or key-value pairs

Comprehensive AWS Security and Compliance Evaluation Workflow (SOC2 Super Runbook)

AWS EKS Version Update 1.29 to 1.30 via terraform

Instruction to allow WinRM connection

MSP Usecase: User Onboarding Azure + M365

Post a message to a Slack channel

How to debug a kafka cluster and kafka topics?

Docusign Integration Tasks

Open VPN Troubleshooting (Powershell)

Execute a simple task on the proxy

Assign the proxy role to a user

Create roles to access credentials in proxy

Install OpenVPN client on Windows laptop

Setup Kubernetes kubectl and Minikube on Ubuntu 22.04 LTS

Install Prometheus and Grafana on the minikube cluster on EC2 instance in the monitoring namespace

Sample selenium script

update the EKS versions in different clusters

AI agent session 2024-09-12T09:36:14-07:00 by Sarang Dharmapurikar

Install kubernetes on an ec2 instance ubuntu 20.04 using kubeadm and turn this instance into a master node.

Turn an ec2 instance, ubuntu 20.04 into a kubeadm worker node. Install necessary packages and have it join the cluster.

Install Docker

Parse EDN content and give a JSON out

GitHub related tasks

Check whether a user is there on Azure AD and if the user account status is enabled

Get the input parameters of a Jenkins pipeline

Troubleshooting: Server is not reachable or unable to connect

There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.

This runbook is designed to methodically diagnose and resolve server connectivity issues. It caters to various scenarios, from simple DNS problems to more complex network or hardware failures

LinuxTroubleshooting

  1. 1

    Determine Connectivity for server connectivity issues

    There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.
    LinuxTroubleshooting
    1

    1. 1.1

      Ping the Server for server connectivity issues

      There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.
      • Objective: Verify if the server is reachable.
      • Outcomes and Actions:
      1. If Both Hostname and IP Address are Pingable: The issue may lie on the client side, as the server is reachable. Investigate client firewall or application configurations.
      2. If Only IP Address is Pingable: Indicates a possible DNS resolution issue. Proceed to Step 2 for DNS troubleshooting.
      3. If Neither Hostname Nor IP Address is Pingable: Suggests a network or server-side issue. Proceed to Step 3 for further diagnostics.
      ping -c 4 <hostname> ping -c 4 <IP_Address>
      copied
      LinuxTroubleshooting
      1.1

  2. 2

    DNS Troubleshooting for server connectivity issues

    There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.
    LinuxTroubleshooting
    2

    1. 2.1

      Verify Local DNS Configuration for server connectivity issues

      There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.
      • Objective: Identify misconfigurations in DNS settings.
      • Checks:
      1. /etc/hosts: cat /etc/hosts
      2. /etc/resolv.conf: cat /etc/resolv.conf
      3. /etc/nsswitch.conf: cat /etc/nsswitch.conf
      4. (Optional) Check interface-specific DNS settings in /etc/sysconfig/network-scripts/ifcfg-<interface>.
      • Outcome:
      1. Correct any misconfigurations found in DNS settings and retest connectivity by pinging the hostname.


      cat /etc/hosts cat /etc/resolv.conf cat /etc/nsswitch.conf cat /etc/sysconfig/network-scripts/ifcfg-<interface>
      copied
      LinuxTroubleshooting
      2.1

  3. 3

    Network Diagnostics for server connectivity issues

    There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.
    LinuxTroubleshooting
    3

    1. 3.1

      Broad Network Check for server connectivity issues

      There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.
      • Objective: Determine if the issue is isolated to the server or affects the wider network.
      • Action: Ping another server within the same network.
      • Outcome:
      1. False: Issue is not overall network side but its with that host/server
      2. True: Might be overall network side issue


      ping <ip_within_the_same_network>
      copied
      LinuxTroubleshooting
      3.1

    2. 3.2

      Server-Side Checks for server connectivity issues

      There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.
      • Objective: Assess server's network configuration and operational status.
      • Actions:
      1. Virtual Console Check
      2. Network Interface and IP Configuration


      LinuxTroubleshooting
      3.2

      1. 3.2.1

        Virtual Console Check

        There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.

        Log into the server via virtual console. Check if the server is powered on and operational by verifying its uptime.

        uptime
        copied
        LinuxTroubleshooting
        3.2.1

      2. 3.2.2

        Network Interface and IP Configuration for server connectivity issues

        There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.
        LinuxTroubleshooting
        3.2.2

        1. 3.2.2.1

          Verify network interface status for server connectivity issues

          There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.
          ip addr show
          copied
          LinuxTroubleshooting
          3.2.2.1

        2. 3.2.2.2

          (Optional) Review IP configuration in /etc/sysconfig/network-scripts/ifcfg-<interface>

          There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.
          cat /etc/sysconfig/network-scripts/ifcfg-<interface>
          copied
          LinuxTroubleshooting
          3.2.2.2

    3. 3.3

      Connectivity Checks for server connectivity issues

      There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.
      LinuxTroubleshooting
      3.3

      1. 3.3.1

        Ping the Gateway for server connectivity issues

        There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.
        ping -c 4 <gateway_IP>
        copied
        LinuxTroubleshooting
        3.3.1

      2. 3.3.2

        Check Routes for server connectivity issues

        There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.
        ip route show
        copied
        LinuxTroubleshooting
        3.3.2

    4. 3.4

      Security Configuration for server connectivity issues

      There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.
      LinuxTroubleshooting
      3.4

      1. 3.4.1

        Check SELinux Status for server connectivity issues

        There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.

        Action: Ensure SELinux is not blocking access to the service/server.

        getenforce
        copied
        LinuxTroubleshooting
        3.4.1

      2. 3.4.2

        Review Firewall Rules for server connectivity issues

        There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.

        Command:

        • sudo iptables -L (for iptables)
        • sudo firewall-cmd --list-all (for firewalld)
        sudo iptables -L sudo firewall-cmd --list-all
        copied
        LinuxTroubleshooting
        3.4.2

    5. 3.5

      Physical Connection

      There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.
      • Objective: Ensure there's no physical disruption to the network connection.
      • Action: Perform a physical inspection of network cables and hardware. Verify the link lights on the network interface card (NIC).


      LinuxTroubleshooting
      3.5

  4. 4

    Outcomes and Resolutions for server connectivity issues

    There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.
    • DNS Issue: Correct DNS configurations as needed and verify resolution by pinging the hostname.
    • Client-Side Issue: Adjust client firewall or network settings as necessary.
    • Network or Server-Side Issue: If broader network issues are identified, work with network administrators to resolve. If isolated to the server, ensure correct network configuration and operational status, checking for any security policy blockages.
    • Hardware Failure: Replace faulty cables or network components as identified during physical inspection.
    LinuxTroubleshooting
    4

AI created and expert curated runbooks

© 2025 DagKnows, Inc. All rights reserved
Resources
Blog
Company
Legal
Privacy policy