Reading OpenSimulator and ROBUST logs
The first troubleshooting step: locate logs, follow an incident and correlate service failures.
Start with logs: a six-step method
1) Record exact time, region, affected avatar and triggering action. 2) Identify the component (region, ROBUST, MySQL or external module). 3) Read the lines around the event. 4) Find the first relevant failure, not just the last ERROR. 5) Correlate other services within the same time window. 6) Test one hypothesis and change one setting at a time.
Where are the logs stored?
In the 0.9.3.1 fork, OpenSim.exe.config and Robust.exe.config define OpenSim.log and Robust.log through log4net. These are relative to the process working directory: do not assume every deployment uses bin/. The rotating log/OpenSim.log and log/Robust.log examples are commented out. Also check whether systemd, screen, tmux, Docker or a process manager captures output.
Read-only commands; adapt to your paths and services.
cd /chemin/vers/opensim/bin ls -lh OpenSim.log Robust.log log/ 2>/dev/null find /chemin/vers/opensim -type f \( -name 'OpenSim.log*' -o -name 'Robust.log*' \) -print # Consulter les fichiers de configuration log4net : grep -n -A 7 'name="LogFileAppender"' OpenSim.exe.config Robust.exe.config
Follow a log in real time
Start following the log before reproducing the issue. Keep context before and after the event: the final error may be a consequence rather than the cause. On Linux, tail -F follows a filename across simple rotations; Ctrl+C stops reading without stopping OpenSim.
Read-only commands; adapt to your paths and services.
tail -n 150 /chemin/vers/bin/OpenSim.log tail -F /chemin/vers/bin/OpenSim.log # Pour les services centraux : tail -F /chemin/vers/bin/Robust.log
Search effectively without losing context
Search for ERROR, FATAL, exception, refused, timeout or failed, then read backward in the log. Not every WARN is fatal and an exception may be handled. Check timestamps, component names, full stack traces and lines before the first failure.
Read-only commands; adapt to your paths and services.
grep -nEi 'ERROR|FATAL|exception|refused|timeout|failed' /chemin/vers/bin/OpenSim.log | tail -n 80 # Exemples : afficher les lignes 420 à 470 autour d’une erreur sed -n '420,470p' /chemin/vers/bin/OpenSim.log # Plusieurs journaux simultanément : grep -nEi 'ERROR|FATAL|exception' /chemin/vers/bin/Robust.log
ROBUST and simulators: two complementary logs
When region registration, avatar login or inventory fails, compare simulator OpenSim.log with central Robust.log. The simulator may only report an HTTP failure, while ROBUST identifies the failing service, database or connector. Synchronize clocks (NTP) and account for time zones before comparing timestamps.
Read-only commands; adapt to your paths and services.
date -Is timedatectl status # Sur chaque machine, consulter la même tranche horaire dans les logs : grep '2026-11-09 14:' /chemin/vers/bin/OpenSim.log grep '2026-11-09 14:' /chemin/vers/bin/Robust.log
systemd logs and service startup
If OpenSimulator or ROBUST runs as a systemd unit, journald may capture failures before a log file is created: wrong working directory, permissions, missing DLLs, early termination, out-of-memory or signals. Replace example unit names with your actual units.
Read-only commands; adapt to your paths and services.
systemctl --type=service --all | grep -Ei 'opensim|robust' systemctl status robust.service --no-pager journalctl -u robust.service -n 150 --no-pager journalctl -u robust.service -f # Exemple pour une unité de simulateur : journalctl -u opensim.service --since '1 hour ago' --no-pager
MySQL, inventory and assets
An SQL error in OpenSim.log or Robust.log is a starting point, not necessarily the root cause. Inspect SQL service state, journal and restart, saturation, connection-refusal or privilege events. For missing assets, search referenced UUIDs and nearby messages before reloading archives or clearing caches.
Read-only commands; adapt to your paths and services.
systemctl status mysql --no-pager journalctl -u mysql --since '1 hour ago' --no-pager # Le service peut aussi s’appeler mariadb selon l’installation : systemctl status mariadb --no-pager # Adapter à un UUID d’asset connu : grep -n 'UUID_ASSET' /chemin/vers/bin/OpenSim.log
Windows: reading the logs
On Windows, locate OpenSim.log and Robust.log using the .config files and the process working directory. PowerShell can read or follow text logs. If the process fails before logging starts, also inspect Windows Event Viewer, especially Application.
Read-only commands; adapt to your paths and services.
Get-Content .\OpenSim.log -Tail 150 Get-Content .\OpenSim.log -Wait -Tail 100 Select-String -Path .\Robust.log -Pattern 'ERROR|FATAL|Exception|timeout'
Prepare a reproducible bug report
Include exact OpenSimulator version, OS and .NET version, Standalone/Grid architecture, affected region, timestamp and timezone, reproducible steps, expected and actual results. Provide timestamped context before and after the first relevant error and third-party module versions. Redact credentials, passwords, tokens, WebRTC keys, personal data and sensitive connection details.
Preserve evidence before fixing
Avoid restarting or deleting logs until the relevant failure has been captured. If restart is necessary, save the log and note the time. Never publish a full production log without review: it may contain secrets or user data.