Update from v29 - v30 pointers on changing php in the process

ℹ️ Support
,
1
Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 29.10
  • Operating system and version (e.g., Ubuntu 24.04):
    • RHEL 9.5
  • Web server and version (e.g, Apache 2.4.25):
    • apache 2.4.62
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • apache
  • PHP version (e.g, 8.3):
    • 8.0.30
  • Is this the first time you’ve seen this error? (Yes / No):
    • -
  • When did this problem seem to first start?
    • -
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • `RPM’
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • -

Summary of the issue you are facing:

Has anyone updated to a newer php and have pointers on if there is stuff that needs attention, I need to go from 8.0.30 which is the default on RHEL9.5 and instead upgrade to REMI:s php and will probably land on 8.2

Steps to replicate it (hint: details matter!):

Log entries

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

PASTE HERE

Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

PASTE

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

PASTE HERE

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

PASTE HERE

Apps

The output of occ app:list (if possible).

Tips for increasing the likelihood of a response

  • Use the preformatted text formatting option in the editor for all log entries and configuration output.
  • If screenshots are useful, feel free to include them.
    • If possible, also include key error output in text form so it can be searched for.
  • Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.
2

Make sure all the same/required PHP modules are installed for the new version of PHP. Also listed in the Admin Manual under Installation: PHP Modules. That’s the main thing that people miss.

You’re not using FPM from the looks of it so no socket path to update.

PHP updates are pretty common. Lots of forum activity about it. If you run into difficulties:

  • check your nextcloud.log for hints about what PHP modules are missing/etc.
  • if stuck post here.
3

Thanks for the reply, I am running php-fpm so pointers on if I need to update its path is welcome.

4

You may not even need to update the path, but it depends on how you originally set it up. :wink:

The reference to look for in your Apache config files will likely contain one of the following strings: fpm or fcgi. The file reference it will likely be in /etc/httpd/conf.d or near there.

5

Seems to be no problem for Nextcloud 29:
Nextcloud 29 Requirements

    8.0 (deprecated)
    8.1
    8.2 (recommended)
    8.3

And for your upgrade to Nextcloud 30:
Nextcloud 30 Requirements

    8.1 (deprecated)
    8.2
    8.3 (recommended)

Because you use PHP 8.0 you must first upgrade to PHP 8.1/8.2/8.3 and then to Nextcloud 30.

Nextcloud 29 is 2025-04 EOL.
Nextcloud 30 is 2025-09 EOL.
Nextcloud 31 will be shipped on 2025-02-25.

Maintenance and Release Schedule · nextcloud/server Wiki · GitHub

6

Just like when I tried upgrading a couple of months ago I’m getting segfaults with php-fpm. segfault at 5581ba05a5f8 ip 00007f4920d3431f sp 00007fffdbb1d2f0 error 6 in opcache.so Anyone else seen this or have any pointers. I’ve had no problems with upgrades before. The issue is only on v30. I upgraded v 29.11 to php 8.2 and had no issues. But as soon as I try to run 30 php-fpm crashes

7

I removed my opchache folder and now it dowsn’t segfault. Last time this was just a temporary fix. I’ve never needed to reset my opcache before.

8

What do you mean by “opcache folder”? OPCache is an in-memory cache (well, by default). Do you have something weird enabled like opcache.file_cache? If so, disable it (unless you really know what you’re doing).