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

symbolicator stops working after installation #3386

Open
maxpain opened this issue Oct 17, 2024 · 7 comments
Open

symbolicator stops working after installation #3386

maxpain opened this issue Oct 17, 2024 · 7 comments

Comments

@maxpain
Copy link

maxpain commented Oct 17, 2024

Self-Hosted Version

24.10.0

CPU Architecture

x84_64

Docker Version

27.3.1

Docker Compose Version

2.29.7

Steps to Reproduce

The sentry-self-hosted-symbolicator-1 container stops sometime after installation. I have to spin it up again. After this manual action, everything works fine.

Image

Expected Result

sentry-self-hosted-symbolicator-1 container should not stop

Actual Result

sentry-self-hosted-symbolicator-1 stops after some time after installation.

Event ID

No response

@bijancot
Copy link

Hi Maxpain, what's the log said ? please share sentry-self-hosted-symbolicator-1 logs

Cheers!

@maxpain
Copy link
Author

maxpain commented Nov 5, 2024

@bijancot Hello!

Nothing:
Image

@maxpain
Copy link
Author

maxpain commented Nov 5, 2024

I have to start it manually every time after maintenance/sentry upgrade/etc.

@BYK
Copy link
Member

BYK commented Nov 7, 2024

@maxpain that doesn't make much sense, can you try this for logs please: https://develop.sentry.dev/self-hosted/troubleshooting/#general

@BYK
Copy link
Member

BYK commented Nov 7, 2024

Also, if you search for exit code 137 you'd see the following:

Exit code 137 is an error that indicates a process was terminated due to a lack of memory or a failed health check

So I'd make sure your system has enough memory.

@maxpain
Copy link
Author

maxpain commented Nov 7, 2024

So I'd make sure your system has enough memory.

I have 128GB of memory, so no problems here.

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 Nov 7, 2024
@BYK
Copy link
Member

BYK commented Nov 7, 2024

@maxpain we'd still appreciate logs.

Also, is that memory available to your Docker? (sometimes they run in VMs etc, hence me asking)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Waiting for: Community
Status: No status
Development

No branches or pull requests

4 participants