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

Fresh install of 23.11.2 or 23.12.1 does not work out of the box #2691

Closed
pmoorani opened this issue Jan 5, 2024 · 15 comments
Closed

Fresh install of 23.11.2 or 23.12.1 does not work out of the box #2691

pmoorani opened this issue Jan 5, 2024 · 15 comments

Comments

@pmoorani
Copy link

pmoorani commented Jan 5, 2024

Self-Hosted Version

23.11.2

CPU Architecture

aarch64

Docker Version

24.0.7

Docker Compose Version

2.23.3-desktop.2

Steps to Reproduce

> ./install.sh

Expected Result

It's a fresh install, should work out of the box?

Actual Result

Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
/usr/local/lib/python3.8/site-packages/memcache.py:1303: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if key is '':
/usr/local/lib/python3.8/site-packages/memcache.py:1304: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if key_extra_len is 0:
Error: It looks like you've skipped a hard stop in our upgrade process. Please follow the upgrade process here: https://develop.sentry.dev/self-hosted/releases/#hard-stops
Error in install/set-up-and-migrate-database.sh:13.
'$dcr web upgrade' exited with status 1
-> ./install.sh:main:37
--> install/set-up-and-migrate-database.sh:source:13

Cleaning up...

Event ID

No response

@aldy505
Copy link
Collaborator

aldy505 commented Jan 5, 2024

That's weird. Are you using an external Postgres by any chance? Or do you use everything default on docker-compose.yml?

@pmoorani
Copy link
Author

pmoorani commented Jan 5, 2024

@aldy505 No I am not using any external Postgres. I use everything default on docker-compose.yml

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 2 Jan 5, 2024
@aldy505
Copy link
Collaborator

aldy505 commented Jan 6, 2024

I can't reproduce it. I did a clean install on a fresh VM on 23.12.1 and got nothing wrong. What I did was exactly this:

git clone https://github.com/getsentry/self-hosted.git sentry-self-hosted
cd sentry-self-hosted
git checkout 23.12.1
sudo ./install.sh
sudo docker compose up -d

Is there any configuration or extra steps/commands that you did?

@pmoorani
Copy link
Author

pmoorani commented Jan 6, 2024

Thank you for your response. I tried again but got the same error

Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
00:36:47 [WARNING] sentry.utils.geo: Error opening GeoIP database: /geoip/GeoLite2-City.mmdb
00:36:47 [WARNING] sentry.utils.geo: Error opening GeoIP database in Rust: /geoip/GeoLite2-City.mmdb
Error: It looks like you've skipped a hard stop in our upgrade process. Please follow the upgrade process here: https://develop.sentry.dev/self-hosted/releases/#hard-stops
Error in install/set-up-and-migrate-database.sh:13.
'$dcr web upgrade' exited with status 1
-> ./install.sh:main:34
--> install/set-up-and-migrate-database.sh:source:13

Cleaning up...

Maybe it's because I am on Apple M1 Max (Ventura 13.4)?

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 2 Jan 6, 2024
@aldy505
Copy link
Collaborator

aldy505 commented Jan 6, 2024

@hubertdeng Can you repro this on M1?

@itDjango
Copy link

itDjango commented Jan 8, 2024

I also encountered the same problem

@getsantry getsantry bot moved this from Waiting for: Community to Waiting for: Product Owner in GitHub Issues with 👀 2 Jan 8, 2024
@aldy505
Copy link
Collaborator

aldy505 commented Jan 8, 2024

I also encountered the same problem

Hello @itDjango are you also running the self hosted sentry on Apple M1?

@Pixel-Minions
Copy link

Same for me, AWS EC2, Ubuntu and Debian T2.medium and large and T3 medium and large.

@getsantry getsantry bot moved this from Waiting for: Community to Waiting for: Product Owner in GitHub Issues with 👀 2 Jan 12, 2024
@aldy505
Copy link
Collaborator

aldy505 commented Jan 12, 2024

Same for me, AWS EC2, Ubuntu and Debian T2.medium and large and T3 medium and large.

@Pixel-Minions Do you have the exact output text as per the issue author's "Actual Output" section?

@vladdevops
Copy link

vladdevops commented Jan 12, 2024

May be related #2704

@getsantry getsantry bot moved this from Waiting for: Community to Waiting for: Product Owner in GitHub Issues with 👀 2 Jan 12, 2024
@hubertdeng123
Copy link
Member

I believe this is related to this:
#1585

We do not have a timeline for when this will be completed by

@zhanglei1996
Copy link

I spent a few days fixing this issue The two longest processing issues: 1 . #2642 Fix #1794 (comment) 2. #2641 Fix #2557 (comment)

Of course, there are other issues, but most of them are related to my network

I have same question with you
How to solve it

#2 ERROR: failed to copy: httpReadSeeker: failed open: server message: insufficient_scope: authorization failed

[internal] load metadata for docker.io/library/debian:bookworm-slim:


Dockerfile:1

1 | >>> FROM debian:bookworm-slim
2 |
3 | LABEL MAINTAINER="[email protected]"

ERROR: failed to solve: debian:bookworm-slim: failed to resolve source metadata for docker.io/library/debian:bookworm-slim: failed to copy: httpReadSeeker: failed open: server message: insufficient_scope: authorization failed

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 Jun 18, 2024
@azaslavsky
Copy link
Contributor

This is likely a permission error on your OS. Some permission is not configured, preventing necessary files from being read.

@github-actions github-actions bot locked and limited conversation to collaborators Dec 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Archived in project
Archived in project
Archived in project
Development

No branches or pull requests

9 participants