Upgrade to 10.0.0: Error 500

[plastikschnitzer]

Steps to reproduce

1. Perform Upgrade from OC 9.1.4 to 10.0.0
2. Copy new version to ownCloud directory
3. Go to ownCloud URL

Expected behaviour

The Upgrade screen should show up to perform the database upgrade

Actual behaviour

Error 500

Server configuration

Operating system:
FreeBSD 10.2

Web server:
Apache/2.4.18

PHP version:
7.0.11

Logs

Web server error log

/path/to/owncloud/.htaccess: Invalid command 'php_value', perhaps misspelled or defined by a module not included in the server configuration

My fix:

<IfModule mod_php7.c>
 php_value upload_max_filesize 513M
php_value post_max_size 513M
php_value memory_limit 512M
php_value mbstring.func_overload 0
php_value default_charset 'UTF-8'
php_value output_buffering 0
</IfModule>

[ghost]

Most likely caused by #26747 which shows this issue on every other php module for Apache (e.g. php-fpm, suPHP).

@plastikschnitzer You should note that ownCloud is fully untested on other webserver PHP modules then mod_php. (mod_php is the only officially supported module as seen in the documentation).

There is absolutely no guarantee that oC will run at all on your environment. It might also happen that you're facing issues / problems / bugs not happening on the tested mod_php module.

[plastikschnitzer]

Hi @kdslkdsaldsal – I knew about this mod_php requirement and possible problems with other php modules, checked back my server and noticed that I have my testing server configured to run php with fcgid at the moment (ooops), switching it back to mod_php (what I use normally due to known reasons) fixed it right away.

OC 9.x works with fcgid in my case, so I suppose if this .htaccess will make it from beta to the final release, it might result in many problems for admins who are not aware of the php environment they are running OC in.

But so far no other issues found on the first look around, so thumbs up from my side, I will keep testing.

[ghost]

so I suppose if this .htaccess will make it from beta to the final release, it might result in many problems for admins who are not aware of the php environment they are running OC in.

Yes, sure. 😃 I think it makes absolute sense to revert the changes from #26747 to avoid such issues.

[PVince81]

@phisch can you verify and take care ? ^

[phisch]

The change in #26747 was just because it seemed redundant and a user asked about it. So if we can prevent some requests by reverting it, we should do that.

@plastikschnitzer can you quickly explain how your server was setup? Because i am not sure what component of your setup was reading the .htaccess file.

[plastikschnitzer]

Server configuration:

Operating system:
FreeBSD 10.2

Web server:
Apache/2.4.18 (FreeBSD) OpenSSL/1.0.2g mod_fcgid/2.3.9

PHP version:
7.0.11

Its the default server setting from a server provider in Germany. With mod_php, everything works well.

[ghost]

In this case Apache will read the .htaccess but doesn't know the php_value as only mod_php (and not mod_fcgid) will add support or making this option known to Apache.

[magf]

apt-get -y install libapache2-mod-php7.0

[phisch]

Yes, as long as you are running mod_php you should not experience this issue. In the meanwhile, apply #27748 or wait for the next update that will include this PR.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.