[Bug][Backend] GIN fatal error: unknown caller pc

[richardinemi]

Search before asking

• [x] I had searched in the issues and found no similar issues.

What happened

What do you expect to happen

It could be link with the fact that i have upgrade some base image version on dockerfile and it’s very difficult to track exactly the issue because i can’t reproduce it on local.

How to reproduce

It’s appear onnly on kubernetes cloud deployment and i can’t reproduce the error on local. It’s work well when i’m deploying with helm or docker compose on local.

Anything else

No response

Version

v1.0.1

Are you willing to submit PR?

• [ ] Yes I am willing to submit a PR!

Code of Conduct

• [x] I agree to follow this project's Code of Conduct

[dosubot[bot]]

Hello @richardinemi! I'm Dosu, your friendly bot here to help you with bugs, answer questions, and guide you towards becoming a contributor. I'm here to assist you while you wait for a human maintainer. Let's tackle this issue together!

The error you're encountering might be related to compatibility issues between the Gin framework and the base image version used in your Kubernetes deployment. Since you mentioned upgrading some base image versions in the Dockerfile, it's possible that these changes are affecting the runtime environment in a way that leads to the "unknown caller pc" error.

Here are a few steps you can take to troubleshoot and potentially resolve the issue:

1. Check Base Image Versions: Ensure that the base image versions in your Dockerfile are compatible with the Gin framework version (v1.9.1) used in the project ^[1]. You can compare the versions used locally versus those in the cloud deployment.

2. Review Dockerfile Dependencies: Verify the dependencies and their versions listed in the Dockerfile. The current versions are:

   • Golang: golang:1.20.5-bookworm
   • libgit2: v1.3.2
   • Mockery: github.com/vektra/mockery/[email protected]
   • Swag: github.com/swaggo/swag/cmd/[email protected]
   • Python: python:3.9-slim-bookworm ^[2].

3. Kubernetes-Specific Issues: Since the error only appears in Kubernetes cloud deployment, consider checking for any Kubernetes-specific configurations or limitations that might affect the Gin framework. There is a known issue related to Kubernetes deployment in the project, specifically a "Go Panic in OpenShift Kubernetes" caused by the Dynatrace agent ^[3][4]. Although this might not be directly related, reviewing similar issues could provide insights.

4. Environment Differences: Investigate any differences between your local and cloud environments, such as network configurations, resource limits, or security settings that might impact the application's behavior.

5. Logs and Monitoring: Enable detailed logging and monitoring in your Kubernetes deployment to capture more information about the error and its context. This might help identify the root cause.

If these steps don't resolve the issue, consider isolating the problem by deploying a minimal version of your application with only the Gin framework and its dependencies to see if the error persists.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[github-actions[bot]]

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

[github-actions[bot]]

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.