Applications Systems

Linux Agent: status=217/USER When Starting swiagentd.service: "Agent service did not start - force to start it"

Linux SolarWinds Platform Agent installs and initializes successfully, but the service fails to start. The install log ends with: Agent service did not start - force to start it and Start of agent service failed with exit code '1'. On the OS side, systemctl status swiagentd.service shows ExecStartPre=/bin/sh -c test -e /opt/SolarWinds/Agent/bin/swiagent.cfg (code=exited, status=217/USER), indicating systemd cannot resolve the configured service user.

First published date

3/16/2026 3:36 PM

Last published date

3/16/2026 3:36 PM

Overview

Agent installed
Initializing agent
Generating SolarWinds Agent secure certificate ...[done]
Agent initialized
Checking status of agent service
Checking status of agent service
Checking status of agent service
Checking status of agent service
Checking status of agent service
Checking status of agent service
Agent service did not start - force to start it
Start of agent service failed with exit code '1'


 # systemctl status swiagentd.service
* swiagentd.service - SolarWinds Agent Service
     Loaded: loaded (/usr/lib/systemd/system/swiagentd.service; enabled; vendor preset: disabled)
     Active: activating (auto-restart) (Result: exit-code) since Fri 2026-03-13 14:45:08 CET; 487ms ago s

Product section

Server Application Monitor

Cause

status=217/USER is a systemd error code meaning:

The service user account cannot be resolved or set up.

In this state, systemd never actually runs the pre‑start command or the agent binary. The failure is at the service account / User= configuration level (missing user, wrong user name, or broken identity mapping), not in the installer or the test -e command.

Resolution

Minimal root-cause check (optional)

Identify the configured user:
 cat  /usr/lib/systemd/system/swiagentd.service



cat /usr/lib/systemd/system/swiagentd.service
Check whether that user exists:


  • 

    If id reports “no such user”, this confirms that status=217/USER is caused by a missing/invalid service account.
    



Proceed with Clean reinstall of the agent (simplest path; recommended)




if:


  • 

    status=217/USER persists after a clean reinstall, and
    

  • 

    You have confirmed that:
    

    • 

      The User= in swiagentd.service exists (id works).
      

    • 

      /opt/SolarWinds/Agent is owned by that user and is accessible (r-x on all parent directories).
      

    



Engage SolarWinds Support for further investigation.


Attach:


  • 

    Full systemctl status swiagentd.service output.
    

  • 

    journalctl -u swiagentd.service -b (last 100–200 lines).
    

  • 

    ls -ld /opt /opt/SolarWinds /opt/SolarWinds/Agent /opt/SolarWinds/Agent/bin and ls -l /opt/SolarWinds/Agent/bin/swiagent.cfg.