You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by rockzOr <ma...@rockzor.de> on 2017/06/27 19:48:14 UTC
[users@httpd] ownCloud / PHP-FPM problem after upgrade to 2.4.26
Hi all,
I've got a problem after upgrading to 2.4.26. Everything works fine
except my ownCloud instance.
I compile httpd by myself and used the exact same method for 2.4.26 as I
used for 2.4.25, where everything worked as expected. I noticed, that in
the current apr-util, theres no expat bundled anymore and manually
compiled it and expanded my configure to "--with-expat=...". Thats the
only difference to my working 2.4.25 compilation.
Now the problem:
ownCloud uses ocs as API to do different things. One is maintaining the
folder shares. And they aren't working anymore with 2.4.26 (in detail,
you can't search for groups, created public links are gone after reload
and you can't edit any existing share). I investigated some things on my
own already and found the following out:
I used the URL from logfiles (which get a 200 - OK as a response) to
investigate which URL is called when searching for a group at share tab.
Its this one:
/ocs/v1.php/apps/files_sharing/api/v1/sharees?format=json&search=Fa&perPage=200&itemType=folder
I search for "Fa" as one of my groups is called "Familie".
If I directly open this in my Browser tab with version 2.4.25 (or
mod_php), I get the following response:
ocs
meta
status "ok"
statuscode 100
message "OK"
totalitems ""
itemsperpage ""
data
exact
users
groups
remotes
users
groups
0
label "Familie"
value
shareType 1
shareWith "Familie"
remotes
Now I /only/ change the version from 2.4.25 to 2.4.26 and just reload
the exact same page. I still get a 200 return code in Apache logfiles,
but I get a different response in browser:
ocs
meta
status "failure"
statuscode 999
message "Invalid query, please check the syntax. API specifications
are here:
http://www.freedesktop.org/wiki/Specifications/open-collaboration-services.
DEBUG OUTPUT:\n"
data
So now I can't get why this isn't working. Everything else is the same
as before, just the current Apache release is the difference to working
and non-working.
In addition: All Logfiles are empty. No error in Apache Errorlog,
nothing in php-fpm Errorlog, nothing in owncloud.log (even with 'debug'
=> true in config.php).
As you can see, I'm using php-fpm (currently 7.1.6, also self-compiled).
I already posted an issue on ownCloud forums, and someone there asked,
if I have the same problem, if switching to mod_php instead of php-fpm.
So I testet that and it's strange, but now working. Everything works as
expected if using mod_php, but not with php-fpm.
There must be some change in Apache which doesn't work as before. I
tested everything else, used 2.4.25 with 7.1.6, 2.4.26 with 5.6.30, etc.
The only working combinations are
- httpd 2.4.25 with anything (php 5.6.30, 7.1.6 mod_php or php-fpm)
- httpd 2.4.26 with mod_php (5.6.30 and 7.1.6)
As you can suggest I don't want to use mod_php over php-fpm for obvious
reasons.
So any help would be appreciated to solve this problem.
To complete my request, heres my vhost configuration for my owncloud
instance:
<VirtualHost *:443>
SSLEngine On
SSLProtocol all -SSLv2 -SSLv3
SSLCertificateFile
"/opt/instances/apache/conf/certs/owncloud/server.crt"
SSLCertificateKeyFile
"/opt/instances/apache/conf/certs/owncloud/server.key"
SSLCertificateChainFile
"/opt/instances/apache/conf/certs/owncloud/chain.crt"
# Add HSTS header
Header always set Strict-Transport-Security "max-age=63072000;
includeSubdomains;"
# Block TRACE/TRACK XSS vector
RewriteEngine On
RewriteCond %{REQUEST_METHOD} ^TRAC(E|K)
RewriteRule .* - [F]
#
ServerAdmin mail@rockzor.de
DocumentRoot /opt/websites/cloud
<Directory "/opt/websites/cloud/data">
Require all denied
</Directory>
# mod_xsendfile
SetEnv MOD_X_SENDFILE_ENABLED 1
XSendFile On
ServerName cloud.domain.de
ErrorLog "|/opt/products/apache/current/bin/rotatelogs -l -L
/opt/instances/apache/logs/cloud/error.log -f -c
/opt/instances/apache/logs/cloud/error.log-%Y-%m-%d 100M"
CustomLog "|/opt/products/apache/current/bin/rotatelogs -l -L
/opt/instances/apache/logs/cloud/access.log -f -c
/opt/instances/apache/logs/cloud/access.log-%Y-%m-%d 100M" extended
# FPM forwarding
SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
<FilesMatch "\.php$">
SetHandler "proxy:fcgi://127.0.0.1:9000"
</FilesMatch>
</VirtualHost>
Finally my used versions:
- Apache httpd 2.4.26
- PHP 7.1.6
- OpenSSL 1.0.2l
- Expat 2.2.1
- apr 1.6.2
- apr-util 1.6.0
- nghttp2 1.23.1
- PCRE 8.40
- mod_xsendfile 0.12
- curl 7.54.1 (for PHP)
Used configure:
./configure \
--prefix=/opt/products/apache/${apache_version} \
--enable-so \
--enable-mpms-shared=all \
--enable-modules=all \
--enable-static-support \
--enable-ssl-staticlib-deps \
--with-ssl=/opt/products/deps/openssl/current \
--with-included-apr \
--enable-nonportable-atomics=yes \
--enable-threads \
--with-crypto \
--with-openssl=/opt/products/deps/openssl/current \
--with-pcre=/opt/products/deps/pcre/current \
--with-nghttp2=/opt/products/deps/nghttp2/current \
--with-expat=/opt/products/deps/expat/current
(I'm not sure if I need every single line here, some are ported from my
previous 2.2 builds)
Any suggestions on this?
Thanks in advance and with regards,
Re: [users@httpd] ownCloud / PHP-FPM problem after upgrade to 2.4.26
Posted by rockzOr <ma...@rockzor.de>.
Sounds good, within a week or few would be awesome. But better wait a
week more to be sure everything works as intended ;)
The workaround is for now OK for me if I don't face anything be broken
now. And as the last option I can also switch back to 2.4.25 and have my
working instance again, it's just a symlink change ;) But I prefer to
run 2.4.26 with the directive set cause of the HTTP/2 changes in 2.4.26.
Regards,
Am 27.06.2017 um 22:48 schrieb Jacob Champion:
> On 06/27/2017 01:42 PM, rockzOr wrote:
>> Is there a plan for releasing 2.4.27 as for the broken behaviour or
>> will it be next regular release in X months?
>
> Bill had a good answer in another thread [1]:
>
> On 06/27/2017 10:15 AM, William A Rowe Jr wrote:
>> We don't generally try to predict our release schedule, when it's
>> baked we publish a release.
>>
>> But Jim and Jacob are furiously updating the test framework as you
>> were asking your question, so I'm guessing the group will be working
>> to release this fix just as soon as it is agreed upon, within a week
>> or few.
>
> --Jacob
>
> [1]
> https://lists.apache.org/thread.html/e7c63db48d314c55b33cf5185166ed97fc2a8b797159072ecbeaf9d7@%3Cdev.httpd.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] ownCloud / PHP-FPM problem after upgrade to 2.4.26
Posted by Jacob Champion <ch...@gmail.com>.
On 06/27/2017 01:42 PM, rockzOr wrote:
> Is there a plan for releasing 2.4.27 as for the broken behaviour or
> will it be next regular release in X months?
Bill had a good answer in another thread [1]:
On 06/27/2017 10:15 AM, William A Rowe Jr wrote:
> We don't generally try to predict our release schedule, when it's
> baked we publish a release.
>
> But Jim and Jacob are furiously updating the test framework as you
> were asking your question, so I'm guessing the group will be working
> to release this fix just as soon as it is agreed upon, within a week
> or few.
--Jacob
[1]
https://lists.apache.org/thread.html/e7c63db48d314c55b33cf5185166ed97fc2a8b797159072ecbeaf9d7@%3Cdev.httpd.apache.org%3E
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] ownCloud / PHP-FPM problem after upgrade to 2.4.26
Posted by rockzOr <ma...@rockzor.de>.
Hi Jacob,
thanks for your very quick answer!
I just want to confirm, that I'm facing this issue. I haven't tested it
with 2.4.25, but with your provided directive.
Without the directive I get:
[Tue Jun 27 22:33:09.126391 2017] [proxy_fcgi:trace8] [pid 10358:tid
140239523075840] mod_proxy_fcgi.c(419): [client
2a02:908:694:bd00:39c2:29c4:625d:3a88:49821] AH01062: sending env var
'SCRIPT_NAME' value '/v1.php'
and with ProxyFCGIBackendType on GENERIC I get:
[Tue Jun 27 22:35:08.976942 2017] [proxy_fcgi:trace8] [pid 13665:tid
140239523075840] mod_proxy_fcgi.c(419): [client
2a02:908:694:bd00:39c2:29c4:625d:3a88:49830] AH01062: sending env var
'SCRIPT_NAME' value '/ocs/v1.php'
For now I leave it with set to GENERIC as it fixes my issue and I can't
face any other problems. As I only set it in my ownCloud vhost, nothing
else is changed by this.
So thanks a lot for pointing me to this (have searched but didn't find
that) and good luck on fixing it for 2.4.27! Is there a plan for
releasing 2.4.27 as for the broken behaviour or will it be next regular
release in X months?
Regards,
Am 27.06.2017 um 22:23 schrieb Jacob Champion:
> On 06/27/2017 12:48 PM, rockzOr wrote:
>> Hi all,
>>
>> I've got a problem after upgrading to 2.4.26. Everything works fine
>> except my ownCloud instance.
>
> Fair warning: I haven't looked through all of the info you provided
> (but thank you for being thorough!). FPM problems after upgrading to
> 2.4.26 are almost certainly due to bug 61202 [1], which we are working
> on now.
>
> You can verify that this is your problem by adding "proxy_fcgi:trace8"
> to your LogLevel, finding the log entry that says "AH01062: sending
> env var 'SCRIPT_NAME'", and comparing the value of SCRIPT_NAME we now
> send in 2.4.26 to the one that we sent in 2.4.25. If they're different
> -- typically the 2.4.26 value is left-truncated -- then this is most
> likely your bug.
>
> If you need a quick fix, and you know 2.4.25 worked for you, you can
> return to the 2.4.25 behavior by using the directive
> "ProxyFCGIBackendType GENERIC". This isn't a viable fix for everyone,
> because it breaks other FPM configurations that used to work prior to
> 2.4.21. We're working on reverting to the 2.4.20 behavior by default
> and filling out the test suite so we don't break you again.
>
> I'm sorry for the inconvenience, and thanks for your patience.
>
> --Jacob
>
> [1] https://bz.apache.org/bugzilla/show_bug.cgi?id=61202
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] ownCloud / PHP-FPM problem after upgrade to 2.4.26
Posted by Jacob Champion <ch...@gmail.com>.
On 06/27/2017 12:48 PM, rockzOr wrote:
> Hi all,
>
> I've got a problem after upgrading to 2.4.26. Everything works fine
> except my ownCloud instance.
Fair warning: I haven't looked through all of the info you provided (but
thank you for being thorough!). FPM problems after upgrading to 2.4.26
are almost certainly due to bug 61202 [1], which we are working on now.
You can verify that this is your problem by adding "proxy_fcgi:trace8"
to your LogLevel, finding the log entry that says "AH01062: sending env
var 'SCRIPT_NAME'", and comparing the value of SCRIPT_NAME we now send
in 2.4.26 to the one that we sent in 2.4.25. If they're different --
typically the 2.4.26 value is left-truncated -- then this is most likely
your bug.
If you need a quick fix, and you know 2.4.25 worked for you, you can
return to the 2.4.25 behavior by using the directive
"ProxyFCGIBackendType GENERIC". This isn't a viable fix for everyone,
because it breaks other FPM configurations that used to work prior to
2.4.21. We're working on reverting to the 2.4.20 behavior by default and
filling out the test suite so we don't break you again.
I'm sorry for the inconvenience, and thanks for your patience.
--Jacob
[1] https://bz.apache.org/bugzilla/show_bug.cgi?id=61202
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org