Scenario: Our Orion server (which hosts the SolarWinds application) is constantly filling up its storage. Every month or so, we run into issues because the server has no more storage. The application will disconnect from the database and all sorts of issues.
Answer: The symptoms you’re seeing almost always mean the Orion server’s own disk is filling with SolarWinds logs/diagnostics/config files, until the services can’t write anymore and drop their connection to SQL.
Possible areas where data is increasing are:
1. C:\temp contains a large file that increases in size - Toolset_BusinessLayerPlugin_tracelog.svclog
This is when Engineers Toolset logging is left at a verbose level.
If this is the case, then follow the steps in this article:
2. C:\ProgramData\SolarWinds\NCM\Config-Archive
This is where all the config backup files are kept if you are using Network Configuration Manager (NCM for short)
If this is the case: Delete the old backups you don't need to keep
Move the Config Archive to a data drive in NCM settings and purge old configs.
Ensure Session Tracing is disabled and delete old trace files.
3. C:\ProgramData\SolarWinds\Logs\APM\ApplicationLogs
This is where the SAM debug logs are kept.
Take a look at the following article for details on that:
4. C:\Program Files\SolarWinds\Orion - LogAdjuster.exe
This is where you increase the logging level or the number of log files with SolarWinds
Take a look at the following article for details on that:
If Debug logging is left enabled
- Any Orion module (Core, NPM, SAM, NCM, VIM, etc.) in DEBUG will grow C:\ProgramData\SolarWinds\Logs... very quickly.
- Fix: Run Orion Log Adjuster and “Reset to defaults” to turn debug off everywhere.
5. Massive Orion logs / old roll-over logs
Normal rolling logs in C:\ProgramData\SolarWinds\Logs\Orion\ should stay reasonably small; when disk fills, you often find tens of thousands of .log / .log.1-5 files there.
Fix: From an elevated CMD (only when services are stopped or in an emergency), clean old logs:del /f /q /s C:\ProgramData\SolarWinds*.log
del /f /q /s C:\ProgramData\SolarWinds*.log.*
6. C:\ProgramData\SolarWinds\Logs\Orion\Interfaces
This is where the interfaces log if something is constantly flapping or misconfigured.
The next step is a quick disk-usage pass (TreeSize/WinDirStat) on the Orion server focusing on C:\ProgramData\SolarWinds and C:\temp to see which of these patterns you’re actually hitting, then we can walk the exact cleanup.