-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Bug]: Can't upgrade because of "Segmentation fault" (and server is not running) #2257
Comments
Which image, precisely, are using? Please share your Docker Compose file and precisely how you upgraded from whatever version you started this latest upgrade attempt with. |
You can find the files here:
Image (via configuration) from Upgrade is described here: https://github.com/TechupBusiness/simple-docker-multi-project/blob/master/applications/system-services/main/nextcloud/Readme.md Would be helpful if there would be a logfile thats shows the real reason for this error. |
You're using a highly customized setup/image. This does not happen in a standard install or using a standard image. I can't even begin to decipher what is going on there without digging into whatever abstractions and customization you've done (and that's not realistic through this channel). The most useful output would been the Docker container output from the very first start-up of your app container when attempting to upgrade. The upgrade is handled (in the unmodified image at least) within the entrypoint. There is no need to run
Well, it's a low-level error that is unlikely to be coming from Nextcloud itself. You'll likely have to troubleshoot what is causing it in your local environment. A million things can cause segfaults. I will say that the custom GID stuff you're doing may not be compatible with assumptions made within the stock image's entrypoint.sh. The ownership of newer versions of Server that get deployed there (via rsync) may not match your customized Dockerfile's assumptions. If I was in your position I'd probably eliminate all the variables I possibly can by going to a stock image then working from there incrementally until the problem comes up again. And if it comes up in the stock image, then I'd look at what's notable about the host (OS, Docker platform) to try to find a way to make it possible for someone else to reproduce the same behavior. |
Erm you are aware that the only difference to the default image is, that I set explicit the user/group? Whats highly customized here? I dont have custom entrypoints and also nothing else "custom" with this image!? So its pretty standard image.
Yes I know but it didnt work, same error. Thats why I tried it manually. The log looked like:
Yeah but something must trigger this error... it seems quite high-level to me. Other users reports it was related to outdated extensions etc.
Do you know whats the proper ownership? Because I didnt change anything else.
I'm using the stock image except of setting ownership (which is needed because I mount existing files too). Linux filesystem stuff. I'm considering now a fresh install because I dont use nextcloud for anything else than just accessing files via app or sharing via web (I dont need existing active shares). But this error is maybe not even related to such things, therefore... I guess I need to know about proper file ownership :) |
I remember having similar weird issue due testing some of the images. The safest way of re-starting this is doing |
Bug description
I upgraded to the latest minor version and then to the latest next major version, but it fails with "Segmentation fault". And the nginx proxy can don't find any fpm result to serve (and shows 502 Bad Gateway)
I have no idea whats wrong. The acpu config is correct. Redis seems to be also reachable.
./occ upgrade -vvv
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
2024-07-11T20:42:49+00:00 Setting log level to debug
2024-07-11T20:42:49+00:00 Repair step: Repair MySQL collation
2024-07-11T20:42:49+00:00 Repair info: All tables already have the correct collation -> nothing to do
2024-07-11T20:42:49+00:00 Repair step: Repair SQLite autoincrement
2024-07-11T20:42:49+00:00 Repair step: Copy data from accounts table when migrating from ownCloud
2024-07-11T20:42:50+00:00 Repair step: Drop account terms table when migrating from ownCloud
2024-07-11T20:42:50+00:00 Updating database schema
2024-07-11T20:42:50+00:00 Updated database
2024-07-11T20:42:50+00:00 Updating <lookup_server_connector> ...
Segmentation fault
Steps to reproduce
Expected behavior
No error (Segmentation fault) and served content via fpm.
Installation method
Community Docker image
Nextcloud Server version
27
Operating system
Other
PHP engine version
PHP 8.2
Web server
Nginx
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 28 to 29)
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Not possible, server is not starting and shows "502 Bad Gateway"
Nextcloud Logs
Additional info
./occ status
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
The text was updated successfully, but these errors were encountered: