SCM “Server configuration polling failed on node” for Linux Essentials and Linux Security and Permissions profiles

4/10/2026 3:31 PM

4/10/2026 3:31 PM

This behavior is specifically observed with Linux SCM out‑of‑the‑box profiles (Linux Essentials, Linux Security and Permissions) on Linux nodes monitored via the SolarWinds Agent when the effective SCM user lacks sufficient permissions to the monitored paths.

Exact error message in SCM: Server configuration polling failed on node 'xxxx'.

• Customer symptoms:

  • Affects Linux nodes monitored with the out-of-the-box Linux Essentials and Linux Security and Permissions SCM profiles.

  • In the node’s Server Configuration Monitor → Configuration Details, individual elements under /etc show errors such as Access denied and File is inaccessible for root-owned files.

• What this article explains (How-to / Problem–Resolution):

  • Why this generic SCM polling failure appears when the underlying issue is Linux file/permission access for the agent or Linux credential.

  • How to confirm the problem from the customer’s perspective in the web console and via the SCM PolledElementErrors SWQL query.

  • How to resolve it by either assigning a Linux credential with appropriate sudo rights or granting controlled sudo access to the agent user so SCM can successfully read and diff the monitored paths under /etc.

Server Configuration Monitor

1. Linux agent deployed with default parameters only

   • Agent (swiagent) installed without Include Credentials with Elevated Privileges (sudo/su).

   • swiagent runs non‑interactively and cannot read protected /etc files by default.

2. No suitable Linux credential with sudo assigned in SCM

   • Linux Essentials / Linux Security and Permissions profiles are assigned without a Linux credential that has:

     • Permission (via group/ACL or sudo) to read the monitored paths under /etc.

     • Non‑interactive sudo rights (no TTY, NOPASSWD for required commands/paths).

As a result, SCM can connect to the node, but the profile elements targeting root‑owned paths fail with Access denied/File is inaccessible, which is then rolled up into the generic “Server configuration polling failed on node” event.

There are two supported approaches; use Option 1 where possible.

Option 1 – Use a Linux account with sudo and let SCM impersonate it (recommended)

1. Create/identify a Linux account with:

   • Read access (or sudo‑based read access) to the required /etc files and directories monitored by:

     • Linux Essentials

     • Linux Security and Permissions

   • Ability to use sudo without interactive prompts for those paths/commands:

   • Typical sudoers settings:

     • NOPASSWD for required commands.

     • No TTY requirement for those commands.

2. Configure a Linux credential in SolarWinds SCM:

   • In the SolarWinds Platform Web Console, create a Linux credential using this account (username + password or key, as appropriate).

   • Ensure this credential is allowed to run sudo as needed.

3. Assign the Linux credential to the SCM profiles:

   • Edit the Linux Essentials and Linux Security and Permissions profiles or their assigned elements and:

     • Set the Linux credential you created.

   • Save and re‑poll.

4. Validate:

   • On a test node, open Server Configuration Monitor → Configuration Details:

     • Check that the previously failing elements under /etc now show as Polled successfully.

   • Confirm the “Server configuration polling failed on node 'xxxx'” event clears after a few polling cycles.

---

Option 2 – Grant controlled sudo rights to the agent user (advanced)

Use this option only if you must keep SCM running under the agent account (swiagent) and cannot use a separate Linux credential.

1. Identify the agent user:

   • Typically swiagent (created during agent installation).

2. Define a restricted command set in sudoers:

   • On one representative Linux node, run visudo and add entries similar to:

   Cmnd_Alias SCMCMDS = /opt/SolarWinds/scm/*
   swiagent ALL=(root) NOPASSWD: SCMCMDS
   

   • This pattern:

     • Limits swiagent to running only scripts under /opt/SolarWinds/scm/ as root.

     • Allows those commands to run without a password prompt.

3. Create SCM wrapper scripts (if needed):

   • Place wrapper scripts under /opt/SolarWinds/scm/ which:

     • Read the required /etc files or perform necessary checks.

     • Output data in a form SCM can diff.

   • Configure the relevant SCM elements (for example, those monitoring /etc/fstab or other protected files) to call:

     • sudo /opt/SolarWinds/scm/your_script.sh

4. Test on one node:

   • Re‑poll the node.

   • Confirm in SCM that the affected Linux Essentials / Linux Security and Permissions elements now succeed and show proper diffs.

5. Roll out:

   • Once validated, apply the same sudoers configuration (and scripts) to other Linux nodes monitored by SCM.