Troubleshooting¶
Solutions to common issues with mcp-trino.
Connection Issues¶
Connection Refused¶
Symptoms:
Causes: - Trino server not running - Wrong host or port - Firewall blocking connection
Solutions:
-
Verify Trino is running:
-
Check host and port configuration:
-
Test network connectivity:
Connection Timeout¶
Symptoms:
Causes: - Network latency - Firewall timeout - DNS resolution issues
Solutions:
-
Check DNS resolution:
-
Test with IP address:
-
Increase connection timeout (if supported)
Authentication Errors¶
Invalid Credentials¶
Symptoms:
Solutions:
-
Verify credentials:
-
Test credentials directly:
User Not Found¶
Symptoms:
Solutions:
-
Verify username:
-
Check user exists in Trino's authentication system
SSL Certificate Problems¶
Certificate Verification Failed¶
Symptoms:
Solutions:
-
Install the CA certificate:
-
For development only, disable verification:
Certificate Expired¶
Symptoms:
Solutions:
- Renew the certificate on the Trino server
- Check system clock is correct:
Query Timeout Errors¶
Query Exceeded Timeout¶
Symptoms:
Solutions:
-
Increase timeout:
-
Optimize the query:
- Add filters to reduce data scanned
- Use LIMIT to reduce result size
-
Check query execution plan
-
Request specific timeout:
Query Killed¶
Symptoms:
Causes: - Query exceeded Trino resource limits - Coordinator memory pressure
Solutions:
- Reduce query complexity
- Contact Trino administrator about resource limits
Permission Denied¶
Table Access Denied¶
Symptoms:
Solutions:
- Verify user has SELECT permission
- Check Trino access control rules
- Use a different catalog/schema with access
Catalog Not Found¶
Symptoms:
Solutions:
-
List available catalogs:
-
Update configuration:
Schema Not Found¶
Symptoms:
Solutions:
-
List schemas in catalog:
-
Update configuration:
Write Operation Blocked¶
Symptoms:
Causes: - Read-only mode is enabled (default)
Solutions:
-
If you need write access, disable read-only mode:
-
Or use SELECT instead of INSERT/UPDATE/DELETE
Query Syntax Errors¶
Symptoms:
Solutions:
- Check SQL syntax
- Verify table and column names
- Use DESCRIBE to check column names:
Verbose Logging¶
Enable detailed logging for debugging:
# Enable request logging
export MCP_TRINO_EXT_LOGGING=true
# Enable query logging
export MCP_TRINO_EXT_QUERYLOG=true
# Run with logs to stderr
mcp-trino 2>mcp-trino.log
Debug Mode¶
Test Connection¶
# Simple connection test
TRINO_HOST=trino.example.com \
TRINO_USER=user \
TRINO_PASSWORD=pass \
mcp-trino --test-connection
Verify Configuration¶
Direct Trino Query¶
Test with the Trino CLI to isolate issues:
Docker Troubleshooting¶
Container Won't Start¶
# Check logs
docker logs mcp-trino
# Run interactively
docker run -it --rm \
-e TRINO_HOST=trino.example.com \
-e TRINO_USER=user \
ghcr.io/txn2/mcp-trino:latest
Network Issues in Docker¶
# Use host network for debugging
docker run --network=host \
-e TRINO_HOST=localhost \
ghcr.io/txn2/mcp-trino:latest
Getting Help¶
If you can't resolve an issue:
- Check the GitHub Issues
- Open a new issue with:
- mcp-trino version
- Configuration (without credentials)
- Error message
- Steps to reproduce