This section provides solutions to common issues that may occur during or after the upgrade process. Use this table to quickly diagnose common upgrade issues and apply targeted fixes:
Issue Symptom Possible causes Resolution
Profile fails to start Profile does not start after upgrade
  • Configuration incompatibility with new version
  • Missing or invalid certificates
  • Port conflicts with other services
  • Insufficient Docker resources
  1. Check container logs: docker logs <container-name>.
  2. Verify configuration file syntax.
  3. Confirm certificates are valid and accessible.
  4. Check for port conflicts: docker ps.
Tools not discovered Tool catalog is empty or missing expected tools after upgrade
  • OpenAPI source connection failed
  • Service-account authorization changed
  • Middleware configuration error
  1. Verify connectivity to OpenAPI source.
  2. Check service-account token validity.
  3. Review middleware configuration.
  4. Examine server logs for connection errors.
Authorization failures Tool invocations fail with authorization errors
  • Service-account key or token mismatch
  • Changed authorization requirements
  • Certificate validation failures
  1. Verify service-account public key matches private key.
  2. Regenerate JWT token if format changed.
  3. Check certificate validity and trust chain.
Performance degradation Tool invocations are slower than before upgrade
  • Changed default timeout values
  • New middleware overhead
  • Resource contention
  1. Review timeout configuration changes.
  2. Monitor container resource usage.
  3. Check downstream service performance.
  4. Adjust timeout values if necessary.