Troubleshoot caches without disrupting a grid
Practical guide based on OpenSimulator 0.9.3.1 source: identify, configure and diagnose caches.
First isolate the affected component
Determine whether an avatar, region, simulator or entire grid is affected. FPS, asset loading, inventory responses and online status are different symptoms. Clearing a cache does not repair a MySQL or network outage.
Disk full or inode exhaustion
On Linux, df -h shows free disk capacity and df -i shows inode availability. Then identify CacheDirectory from the actual INI. Never delete an unverified path: fsassets may look like a cache but holds permanent content.
Inspect Flotsam before purging
In the relevant simulator console, fcache status reports hit rates and file count. Inspect FileCacheTimeout, FileCleanupTimer and logs. If cache grows, determine whether automated cleanup is disabled before touching storage.
Previously missing asset
If an asset has been restored and its source now serves it, fcache clearnegatives is a targeted first step. If the authoritative service still reports “missing”, clearing a local cache cannot recreate it.
Do not confuse with Firestorm
Firestorm cache lives on the user's computer. If only one visitor sees gray textures or low FPS, check that visitor's network and settings before server intervention. Clearing simulator cache can increase reloading for everyone.
A cautious maintenance plan
1. Check logs and service health. 2. Inspect effective cache settings. 3. Measure files and inodes. 4. Prefer the least intrusive targeted command. 5. Schedule major preloading or cleanup for quiet periods. 6. Compare metrics and record results.
Read-only Linux checks
Check disk, inodes and cache size. These are read-only commands; never use rm -rf on a guessed path.
df -h df -i # Adapter le chemin aux réglages AssetCache : du -sh /path/to/assetcache
Managing this cache: practical steps
Choose an action by symptom
Large Flotsam disk cache: run fcache status, then inspect CacheDirectory, FileCleanupTimer and df -i. Asset available after an earlier miss: fcache clearnegatives. Stale account or region: verify source services and let memory TTL expire. Slow ubOde meshing: inspect [Mesh] and logs without deleting live MeshCache. Script failures: inspect YEngine and state files, never blindly purge ScriptEngines.
Identity cache: dedicated command
If a UUID displays an outdated name, check the authoritative user service first. reset user cache only affects name mappings managed by UserManagementModule. Follow the account-cache troubleshooting procedure before considering a restart.
Full procedure: user cache, checks and commands
More cache guides
- Understanding OpenSimulator caches
- Flotsam: disk, memory and negative caches
- Cache console commands: fcache
- Other internal caches: inventory, regions and textures
- FSAssets and asset storage
- Inodes and disk storage
- Firestorm cache and graphics lag