Verification and Troubleshooting
Verification Steps​
Docker on GCE​
sudo journalctl -u tooljet | grep "TOOLJET APPLICATION STARTED SUCCESSFULLY"
sudo docker-compose logs tooljet | grep "TOOLJET APPLICATION STARTED SUCCESSFULLY"
GKE​
kubectl logs deployment/tooljet -n tooljet | grep "TOOLJET APPLICATION STARTED SUCCESSFULLY"
Cloud Run​
gcloud logging read "resource.type=cloud_run_revision AND resource.labels.service_name=tooljet" \
--filter="textPayload:TOOLJET APPLICATION STARTED SUCCESSFULLY" \
--limit=10
Database Version Verification​
psql "postgresql://username:password@your-cloud-sql-ip:5432/database" -c "SELECT version();"
Common Issues and Solutions​
Certificate Not Found​
Symptoms: ENOENT: no such file or directory, open '/certs/server-ca.pem'
Solutions:
- Verify certificate path and file permissions
- Check volume mounts in Kubernetes/Docker configurations
- Ensure Secret Manager permissions for Cloud Run
SSL Connection Errors​
Symptoms: SELF_SIGNED_CERT_IN_CHAIN or certificate verify failed
Solutions:
- Verify SSL connections work properly
- Ensure certificate file is readable by the application
- Check that the certificate is the correct Cloud SQL CA certificate
- Consider using Cloud SQL Proxy for automatic SSL handling
Cloud SQL Connection Timeout​
Symptoms: Connection timeouts or refused connections
Solutions:
- Check Cloud SQL instance's authorized networks
- Verify VPC/firewall rules
- Ensure Cloud SQL instance is in RUNNABLE state
- Check if Private IP is configured correctly
Issue: Authentication Errors​
Symptoms: password authentication failed for user
Solutions:
- Verify database credentials
- Check if user exists and has proper permissions
- Confirm database name is correct
- Test connection from Cloud Shell
Manual Connection Testing​
# Test Cloud SQL connection with SSL from Cloud Shell
gcloud sql connect your-instance-id --user=postgres --database=your-database
# Test from local machine with SSL
psql "postgresql://username:password@your-cloud-sql-ip:5432/database" -c "SELECT version();"
# Test using Cloud SQL Proxy locally
./cloud-sql-proxy your-project-id:your-region:your-instance-id &
psql "postgresql://username:[email protected]:5432/database" -c "SELECT version();"