-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Upgrade to 24.5 failed #3128
Comments
@romanstingler I was dealing with the same problem yesterday. I read in another issue that it is necessary to go through version 24.4.2. Try checking that version, running install and then upgrading to version 24.5.1. I hope you can solve it! 😊 |
@guiolmar thank you for your input. |
@romanstingler Nice! I await your response to know if it has worked for you 🤗 |
The installation failed because we.. kinda bumped the minimum version of Docker Compose, that we need to execute But I see you're still using the old |
I tried to upgrade, failed multiple times, because some containers were already present. Now I reverted to the old snapshot and the web UI didn't show anything except an error Why is there no upgrade guide? Someone should take a look at Laravel's upgrade guide ▶ Upgrading Clickhouse ... Envelope from file sentry-envelope-bf0f3f63f8a1ef8daeb52ef3ecee361a dispatched I restored from an old 24.3 snapshot and will keep that for the time being until I see bugfixes |
I have the same problem on my sentry instance. Now I'm stuck because rollback doesn't work either. I tried to install a new sentry deployment on a newly created machine and the same problem:
|
I'd be curious to see what logs are going on in your clickhouse container. Please open another issue for container restarting. This looks like a different issue than the original issue however, since that one is complaining about resource usage. |
I had a similar error, but I didn't notice how the volume ran out of free space. After I freed up some space, the problem disappeared |
Self-Hosted Version
Sentry 24.6.0.dev0 -> please read
CPU Architecture
x86-64
Docker Version
25.0.2
Docker Compose Version
1.29.2
Steps to Reproduce
I have a
Welcome to Ubuntu 23.04 (GNU/Linux 6.2.0-1020-gcp x86_64)
VM in GCP
had 24.3 installed and wanted to upgrade to 24.5
this failed because of your docker-compose version check
I had 1.28.0 or so and it failed.
So I upgraded my version checked
all good, and it failed again with the same issue, detects 1.28 but 1.29 is installed.
then I overwrote the check, then failed to build
![image](https://private-user-images.githubusercontent.com/5576250/339254843-c0cc7d11-ac5e-4357-9462-e24b5a9e6d6b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjUxOTU1MTksIm5iZiI6MTcyNTE5NTIxOSwicGF0aCI6Ii81NTc2MjUwLzMzOTI1NDg0My1jMGNjN2QxMS1hYzVlLTQzNTctOTQ2Mi1lMjRiNWE5ZTZkNmIucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDkwMSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA5MDFUMTI1MzM5WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YmZmYzU2ZjZkNDM1MzZhYmYzY2RmNWNmZTI4MGU5ODMwYzU2N2JmNjg4OTc0NDUzMzg5NTZiMTYwYmRiNDQ0MCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.vtwDhyiHWt6OCyi3h8bwnghX1nbhl5lY6XD5aF8mp1Y)
because clickhouse was unkown
so i checked out the 24.4.2 version
![image](https://private-user-images.githubusercontent.com/5576250/339256056-7e8f1761-00c0-4f71-8809-ad6c75cf6402.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjUxOTU1MTksIm5iZiI6MTcyNTE5NTIxOSwicGF0aCI6Ii81NTc2MjUwLzMzOTI1NjA1Ni03ZThmMTc2MS0wMGMwLTRmNzEtODgwOS1hZDZjNzVjZjY0MDIucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDkwMSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA5MDFUMTI1MzM5WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZjJkNTk1NGRhNDUxZGZlOGJlNmVlODljNTE5NTFiNTE0YzYzZjYyYzgwNzdmMmNlYjM0YzhiZWU3MmQ3MDdkMiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.Tp1bZyBj644Xqyg3v6d3gaWikwCGzxdtOZf1v-otmOs)
this build was successful
and now it shows
Sentry 24.6.0.dev0
but since 18h the vm is burning
![2024-06-13-09:05:53](https://private-user-images.githubusercontent.com/5576250/339256687-4999ae42-f74c-4cdd-8826-ea02b1e6965b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjUxOTU1MTksIm5iZiI6MTcyNTE5NTIxOSwicGF0aCI6Ii81NTc2MjUwLzMzOTI1NjY4Ny00OTk5YWU0Mi1mNzRjLTRjZGQtODgyNi1lYTAyYjFlNjk2NWIucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDkwMSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA5MDFUMTI1MzM5WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NmI1YjYyNzYwN2M2MmQ1MzNmYzQ0MGUwY2VlNGQ0NjU2MmJlZmJjYTJiNjk0MGQxY2UyNTljNzJhNzNhMmUxZiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.N5BGgWBoNOXs-lPsvRUNeDhneGmWiEL65dUfBOERoQg)
I think I have to wait for the error only version
Expected Result
see above
Actual Result
see above
Event ID
No response
My question is, why is there even python in a high performance environment?
The text was updated successfully, but these errors were encountered: