OpenSimulator · EN

ROBUST: understanding central grid services

Roles, connectors, dependencies, public/private boundaries and log correlation.

These procedures cover common OpenSimulator administration tasks. Verify settings for your version and prepare a backup before making changes.

ROBUST is not a region simulator

ROBUST centralizes accounts, authentication, inventory, assets and grid information; OpenSim instances host regions. A successful login does not prove inventory or asset services work. Inspect the connectors actually enabled under [Startup].

PublicPort and PrivatePort

Robust.ini.example and Robust.HG.ini.example show 8002 as a public port and 8003 as private. These are examples, not mandatory values. The private port exposes internal connectors and must be restricted to trusted simulators/services; the public port may host login and Gatekeeper as configured.

GridService

Tracks region registration, position and lookup. For failed registration, inspect OpenSim.log and Robust.log, then verify GridServerURI, private ports, DNS and errors. Do not casually change a live region's coordinates without considering neighbours and teleports.

AssetService and InventoryService

AssetService serves asset payloads while InventoryService manages inventory records and folders. Inventory entries can exist even when payloads are missing. With FSAssets, SQL metadata and file storage must remain consistent.

UserAccountService and AuthenticationService

UserAccountService manages account identities and attributes; AuthenticationService validates authentication information. A password failure does not automatically imply GridService failure. Start with logs and identify the responding connector.

LoginService, PresenceService and GridUserService

LoginService handles viewer login. PresenceService tracks sessions and GridUserService stores user location/state data. For stuck logins, distinguish authentication, presence, destination region and simulator handoff.

AvatarService, AgentPreferencesService and FriendsService

These services cover avatar data, agent preferences and friendships. Appearance or friend issues can originate in central services or region-side modules; correlate logs on both ends.

EstateService and MapImageService

EstateService maintains estate and owner data; MapImageService handles grid map images. Missing map tiles do not necessarily indicate GridService failure: inspect region tile generation, transfer and connectors.

Hypergrid: Gatekeeper, UserAgent, HG services

Robust.HG.ini.example adds public Gatekeeper, UserAgent and HG asset, inventory and friends connectors. Cross-grid exchange requires coordinated configuration. Public HG endpoints must not be confused with private ROBUST APIs.

Startup order and diagnostics

On initial deployment start ROBUST and wait for required connectors before launching region processes. Find the first relevant error in Robust.log then compare OpenSim.log. A restart is not a substitute for root-cause analysis.

Example: adapt and verify on a test instance.

grep -nEi 'ERROR|FATAL|exception|refused|timeout' /chemin/vers/Robust.log | tail -n 100
# Sur le serveur de régions :
grep -nEi 'grid|register|asset|inventory|timeout' /chemin/vers/OpenSim.log | tail -n 100

Multiple instances and high availability

Do not assume two ROBUST processes sharing files automatically make a highly available grid. Some services/writers, including FSAssets, require SecondaryInstance or a verified shared-storage design. Identify which instance owns each write.

Trace a failure end to end

For missing assets, trace viewer → region → AssetService connector → ROBUST → SQL → FSAssets disk if enabled. For teleports, start with both region logs, then grid services. Let errors direct checks rather than guessing.

Further reading

Source code and references