Troubleshooting

🔧 GermainUX Engine Troubleshooting

Use this section to diagnose common GermainUX Engine problems. Start with the Engine status and logs, then select the guide that matches the symptom.

🔎 Initial checks

Before restarting the Engine or changing its configuration:

1. Record when the issue started.

2. Preserve the Engine Manager and Engine logs.

3. Check Germain > State for the affected node and Engine.

4. Confirm that the Engine Manager is running.

5. Verify that the node is authorized.

6. Confirm that the Engine is enabled.

7. Check connectivity to Germain Enterprise.

8. Review available CPU, memory, and disk space.

9. Identify recent Java, network, proxy, configuration, or component changes.

Avoid repeatedly restarting the Engine before capturing the original error.

📄 Logs

The primary Engine Manager log is:

ENGINE_HOME/logs/EngineManager.log

Some older distributions use:

ENGINE_HOME/log/EngineManager.log

Review the Engine-specific logs in the same directory.

Look for:

Focus on the first relevant exception. Later errors may be consequences of the original failure.

🧭 Select the appropriate guide

🔁 General troubleshooting flow

🏢 Engine Manager is unavailable

Check:

⚙️ Engine Manager is running, but the Engine is unavailable

Confirm that:

• The node is authorized.

• The Engine is enabled under Germain > State.

• Its JVM options are valid.

• The host has sufficient resources.

• The Engine configuration loads successfully.

• No local state-store error prevents startup.

🔧 Engine is running, but a component fails

Check:

An isolated component failure usually does not require reinstalling the Engine or rebuilding its state store.

📥 Data is not reaching GermainUX

Verify the complete path:

1. The monitoring component executes.

2. The Engine creates the expected telemetry.

3. The Engine can reach Germain Enterprise.

4. The configured messaging or transport layer is available.

5. GermainUX Services process the data.

6. The datastore accepts it.

7. The data appears under the correct application and time range.

Compare timestamps across the Engine, Enterprise, messaging, service, and datastore logs to identify where processing stops.

✅ After applying a fix

Confirm that:

• The Engine Manager is running.

• The node is authorized.

• Its heartbeat appears in Germain > State.

• All expected Engines are listed.

• Required Engines are enabled.

• Monitoring components resume execution.

• New telemetry appears in GermainUX.

• CPU, memory, and disk utilization remain acceptable.

• No repeated errors appear in the logs.

• Automatic startup works after a controlled host restart.

📋 Information to collect for Support

If the issue persists, provide:

Remove passwords, tokens, private keys, session files, and other secrets before sharing logs or configuration.