🔧 EasyTask Web Component Troubleshooting¶
This guide helps you diagnose and resolve common issues with the EasyTask Web Component.
🐛 Common Issues and Solutions¶
| # | Issue | Possible Cause | Solution |
|---|---|---|---|
| 1 | Web UI not accessible | Service not running or network issue | Check the Web Component status through the system service manager. Verify the service is running and the configured port is accessible. |
| 2 | Login page does not load | Backend process crashed | Check the Web Component logs through the system service manager. Restart the service if needed. |
| 3 | Authentication failures | Identity provider service issue | Verify the identity provider is running. Check user credentials and role assignments in the Administration panel. |
| 4 | Task dashboard not updating | Message broker disconnected | Ensure the message broker is accessible from the web service. Check broker connection settings. |
| 5 | Slow page load times | High memory usage or resource constraints | Monitor resource usage through the system service manager. Consider increasing available resources. |
| 6 | 502 Bad Gateway | Backend process crashed | Restart the web service. Check logs for application errors. |
| 7 | User federation not working | Incorrect identity provider configuration | Verify identity provider federation settings. Contact your administrator to check the federation configuration. |
| 8 | Cannot view task logs | Agent unreachable | The target worker agent must be online. Check agent connectivity and ensure the agent is registered with the scheduler. |
📋 Checking Web Component Logs¶
View Live Logs¶
Use the system service manager to follow Web Component logs in real time.
View Recent Logs¶
Use the system service manager to view recent log entries from the Web Component.
Search for Errors¶
Search the Web Component logs for error messages using the tools provided by the system service manager.
Search for Worker Issues¶
Search the Web Component logs for worker-related messages to diagnose task processing problems.
Key Log Patterns to Watch¶
| Log Message | Meaning | Action |
|---|---|---|
| Startup confirmation message | Web server started successfully | No action needed |
| Shutdown confirmation | Server shutting down | Expected during graceful stop |
Connection refused |
Cannot reach backend service | Check dependent services (database, message broker, identity provider) |
Error or Exception |
Application error | Review the full error message and stack trace for details |
🔄 Restart Procedures¶
Standard Restart¶
Use the system service manager to stop and then start the Web Component. Wait a moment between stop and start to allow for a clean shutdown.
Force Restart (if standard stop hangs)¶
If the standard restart does not work, contact your system administrator for assistance with a forced restart.
Verify Restart Success¶
After restarting, confirm the Web Component is healthy by checking the logs through the system service manager. Look for the startup confirmation message indicating the web server is ready, then open your browser and navigate to the web UI to confirm the login page loads.
🔍 Diagnostic Checklist¶
When troubleshooting, follow this checklist:
- Check service status: Verify the Web Component is running through the system service manager.
- Check recent logs: Review recent log entries for errors.
- Verify network accessibility: Ensure the configured port is open and not blocked by firewall.
- Check dependent services: Verify database, message broker, and identity provider are all running.
- Check resource usage: Monitor CPU and memory usage through the system service manager.
- Test browser connectivity: Clear browser cache and try accessing the UI in an incognito window.
- Review authentication: Ensure the identity provider is running and user accounts are properly configured.
Frequently Asked Questions¶
Q: The Web UI shows a blank page or fails to load. What should I do? A: First, check if the Web Component service is running through the system service manager. If the service is running, check the logs for errors. Verify that the configured port is accessible and no firewall rules are blocking it. Try clearing your browser cache or using an incognito window.
Q: I can log in but the dashboard shows no data or task information. A: This usually indicates a message broker connectivity issue. Ensure the message broker is running and the Web Component can reach it. Check the scheduler status as well — if the scheduler is down, task data may not be available. Also verify your user role has permission to view the relevant tasks.
Q: How do I check if the Web Component is communicating with the scheduler and agents? A: Check the Web Component logs for any connection errors. You can also visit the Scheduler page in the UI — if it shows instance details and connected workers, communication is working correctly.