Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting Uncaught signal: 2, pid=13, tid=13, fault_addr=0. #88

Closed
septiyanmudhiya502 opened this issue Mar 4, 2024 · 5 comments · Fixed by #115 or #117
Closed

Getting Uncaught signal: 2, pid=13, tid=13, fault_addr=0. #88

septiyanmudhiya502 opened this issue Mar 4, 2024 · 5 comments · Fixed by #115 or #117

Comments

@septiyanmudhiya502
Copy link

Hi team, i am currently facing this error in 2 of my project. One of them somehow recover from this error and could run perfectly again. However the other one still facing this issue.
image

I am not sure what causing this to happen. Could someone explain to me why is this happening ? Thank you in advance 🙏

@timothydang
Copy link
Contributor

hi @septiyanmudhiya502, we run into the same issue. Managed to get it fixed with #89 - you just need to rebuild the container and re-deploy to cloud run.

@septiyanmudhiya502
Copy link
Author

hi @timothydang , it is now working with your fix. Hope it will be merged soon. Thank you so much

@rakkaalhazimi
Copy link

image
I still getting the error. The issue was closed but the problem still persist.

@nielm
Copy link
Contributor

nielm commented Sep 11, 2024

The error message seems to be harmless - it seems to occur on container startup - I have not established what pid=13 actually is.

@nielm
Copy link
Contributor

nielm commented Sep 13, 2024

With more debugging on container startup, I have established that this message is being triggered by the command:

apt-get -qqy update

I cannot explain why it happens... and the apt-get command completes successfully.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment