Views:

Follow these steps:

  1. Check service status.
    1. Open a terminal on the server.
    2. Run the following commands to check the status of both agents:

      bash
      systemctl status dsagent
      systemctl status vlsagent

    3. Note any errors or warnings displayed in the output.
  2. Stop services and clean PID files.
    1. Stop both services:

      bash
      systemctl stop dsagent vlsagent

    2. Remove any existing PID files:

      bash
      rm -f /run/dsagent.pid /run/vlsagent.pid

    3. Check for any hanging processes related to the agents:

      bash
      ps aux | grep -E 'dsagent|vlsagent'

    4. If any processes are found, terminate them using:

      bash
      pkill dsagent
      pkill vlsagent

  3. Verify PID file creation.
    1. Restart the services:

      bash
      systemctl start dsagent vlsagent

    2. Check if the PID files are created in the /run directory:

      bash
      ls -l /run/dsagent.pid
      ls -l /run/vlsagent.pid

    3. Ensure that these files contain the correct PIDs:

      bash
      cat /run/dsagent.pid
      cat /run/vlsagent.pid

  4. Check for Symlink issues.
    1. Verify if /var/run is symlinked to /run:

      bash
      ls -l /var/run

    2. If it is not a symlink, you may need to create it:

      bash
      sudo ln -s /run /var/run

    3. Confirm the permissions of the PID files and ensure that both the dsagent and systemd have the correct permissions to access these files.
  5. Monitor logs.
    1. Monitor the logs for any errors during the startup:

      bash
      journalctl -u dsagent --since 'YYYY-MM-DD HH:MM:SS'
      journalctl -u vlsagent --since 'YYYY-MM-DD HH:MM:SS'

    2. Look for any recurring errors or warnings that may indicate further issues.

For further troubleshooting, check the Help Center article, Configure Red Hat Enterprise Linux to receive event logs.

Keywords: dsagent service failed status, Linux dsagent issues,systemd PID file problems,multiple EDR agents running,agent installation and configuration,Deep Security agent troubleshooting,service management discrepancies,agent startup failure errors