Agent
Common Issues and Their Log Indicators¶
-
Connection Problems: If you see repeated connection attempts or timeouts in the logs, it might indicate issues with the message broker connection.
-
Configuration Errors: Misconfigurations will often appear in the initial configuration dump. Check for any unexpected values.
-
Task Processing Issues: If tasks are received but not processed, look for error messages after the "Task received" log entry.
-
Worker Isolation: If the agent reports being unable to reach the cluster, it may not be properly connected. Check message broker connectivity and ensure the broker service is running.
Frequently Asked Questions¶
Q: How do I check if my Worker Agent is properly connected to the cluster? A: Check the agent logs for repeated connection attempts or cluster connectivity errors. If the agent reports being unable to reach the cluster, verify your message broker connectivity and ensure the broker service is running and accessible.
Q: What should I do if tasks are received but not processed? A: Check the logs for error messages after the "Task received" log entry. Common causes include configuration errors, missing dependencies, or permission issues on the target host. Also verify the agent's working directory and that the command being executed is valid.
Q: How do I check for configuration errors in my Worker Agent? A: Review the initial configuration dump in the agent logs at startup. Look for any unexpected values or error messages. Misconfigurations will typically appear there. Also verify the agent configuration has all required fields with correct values.