Troubleshooting
Server Fails to Start
If you try to run the application but encounter an error message:
- Address/Port Already in Use: Ensure no other application is using port
7080(default). Use the--listenflag to run on a different port.shellkudashai --listen :8080 - Permission Denied: On some OSes (especially when trying to bind to ports under 1024 or involving encryption), you might need Administrator / Root access, or you may need to adjust the file execution mode.shell
chmod +x kudashai ./kudashai
Platform Mode Will Not Connect
If you are unable to activate Platform mode through Kudashai Studio, check the following:
- Invalid App Key: Ensure you are entering the correct App Key (license key) from the AwanIO Enterprise Portal. If your key has expired or been revoked, contact your administrator or the AwanIO support team.
- Network Connectivity: Kudashai Studio performs an automatic handshake with the AwanIO backend to provision your database. Ensure your machine has outbound internet access and is not blocked by a firewall or proxy.
- Handshake Timeout: If the handshake process takes too long or fails silently, check the application logs for connection errors. Restart the Kudashai application and retry the activation.
- Data Not Appearing After Activation: If the handshake succeeds but cluster data doesn't appear, check the logs. The system attempts to run auto-migrations when Platform mode is activated for the first time.
Credential Issues When Moving Data (Standalone Mode)
In Standalone mode, cluster credentials are stored locally and securely encrypted using a secret key (encryption key) that is automatically generated by the system on your computer.
- If you move the Kudashai application data files to another computer WITHOUT including the original encryption key file, Kudashai on the new computer will not be able to read the cluster credentials.
- Solution: Ensure you backup and migrate the entire default Kudashai configuration folder, not just partial data.
AI Troubleshooting Assistance
If Kudashai detects a K8s Pod or service in an error state (such as ImagePullBackOff, CrashLoopBackOff), you can use the built-in "Ask AI" button on the Kudashai interface. The internal AI agent will analyze recent logs and metrics to diagnose the issue and help resolve it, even suggesting new configuration options.