Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Create a Support Ticket
  • Partner Portal
  • CYRISMA MSP Dashboard
  • Home
  • General Questions and Troubleshooting
  • Agent Troubleshooting

Managing High Memory Usage by DataSpotliteAgent

This article provides guidance on resolving excessive memory usage caused by the DataSpotliteAgent, even after stopping a CIFS scan. The issue is related to inaccurate memory reporting by the operating system.

Written by Tony Scribe

Updated at November 26th, 2024

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • User Manual
    Overall Risk Dashboard Agent Status Report Builder Data Scan Vulnerability Scan Secure Baseline Compliance Mitigation Dark Web MSP Interface Instance Admin
  • Self Onboarding Guide
  • Agents
  • The Cyber Risk Assessment Process
  • PSA Integrations
  • General Questions and Troubleshooting
    Agent Troubleshooting Scanning Troubleshooting
  • The Cyber Risk Assessment Process (Video Tutorials)
  • Sales and Prospecting Articles
  • CYRISMA Partner Portal Access
  • Glossary
  • API Documents
  • CYRISMA Change Log
  • Support Ticket SLA
  • Billing Questions
+ More

Problem:
After terminating the CIFS scan, the DataSpotliteAgent continues to consume excessive memory, degrading server performance.


Root Cause:
An anomaly in the operating system's memory reporting causes it to incorrectly report a significantly higher amount of available memory (e.g., 250GB when it should report 8GB). This discrepancy results in the agent consuming a disproportionate amount of system resources.


Workaround:

To mitigate the issue until a permanent fix is implemented, adjust the agent's memory usage:

Set Memory Threshold:

  • Configure the agent to use only 1–2% of the reported available memory.
  • This prevents the agent from consuming excessive memory while preserving server stability.

Steps to Apply the Memory Threshold Setting:

  • Access the agent's configuration file or memory settings in the application interface.
  • Locate the Memory Threshold option.
  • Set it to 1–2% of the available memory value reported by the operating system.

Collect Logs for Further Analysis:

  • Run the following command in the terminal (with administrative privileges) to verify actual memory usage:
 
wmic os get freephysicalmemory  
  • Share the output with support to assist in further diagnosis.

Follow-Up Recommendations:

Restart the Agent:
Restarting the DataSpotliteAgent can help apply configuration changes effectively.

System Specs Validation:
Confirm the correct memory specifications of the server (e.g., 8GB, 256GB, etc.) to ensure accurate troubleshooting.

memory management data spotlight agent memory memory usage

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Why Do My Vulnerability Scans Have a High Failure Rate?
  • How to Resolve Issues with Batch Scan Scheduling
  • Schedule a Vulnerability Scan

Partners
pax8
CDW
Stellar Cyber
RedSky Alliance

Request A Demo
Platform
  • Platform Overview
  • Resellers
  • Managed Service Providers
  • Request A Demo
  • Platform Overview
  • Resellers
  • Managed Service Providers
  • Request A Demo
Resources
  • Case Studies
  • White Papers
  • Videos
  • Blog
  • Press Release
  • Events
  • Case Studies
  • White Papers
  • Videos
  • Blog
  • Press Release
  • Events
Contact Us
Address: 510 Clinton Square, Rochester, New York, USA, 14604

Email: info@cyrisma.com

Phone: 1-585-620-2496

Easiest To Do Business With Summer 2023
Category Leader Channel Program
Capterra
Software Advice

Terms of Use          Privacy Policy

Copyright © 2024 – Data Spotlite, Inc All rights reserved.
Expand