9.1.1 upgrade error



Please help us by providing the following info. Before posting please also check the pinned "Known issues" threads and make sure that you're running the latest available version for your oC release: https://owncloud.org/changelog/

Steps to reproduce
1. used yum package manager to upgrade 9.1 to 9.1.1
2. ran command to upgrade oc 9.1 to 9.1.1

Expected behaviour
no errors in log file from core.

Actual behaviour
I am getting cURL error 77 from core in the log file. Lots of entries.

Server configuration
Operating system: centos 7
Web server: apache 2.4.6
Database: MariaDB 5.5.50
PHP version: 7.0.10
ownCloud version (see ownCloud admin page): 9.1.1
Updated from an older ownCloud or fresh install: updated from 9.1
ownCloud log (data/owncloud.log, see https://central.owncloud.org/t/how-to-find-webserver-or-oc-logfile-enable-php-logfile/808):

Special configuration (external storage, external authentication, reverse proxy, server-side-encryption):
The oc server houses client data in external NAS.

the cURL 77 error is filling up our logs. Quite strange.


Please post one complete log entry of that "cURL error 77".


Here is a modified (IP, username and reqid were all changed to 'xxxx') log entry.
{"reqId":"XXXXXXXXXXXXXXXXXXXX","remoteAddr":"xxx.xxx.xxx.xxx","app":"core","message":"cURL error 77: ","level":3,"time":"2016-09-21T06:05:43-04:00","method":"PROPFIND","url":"\/owncloud\/remote.php\/webdav\/","user":"xxxxxxx"}


Problem with reading the SSL CA cert (path? access rights?)

from https://curl.haxx.se/libcurl/c/libcurl-errors.html

Seems you have some broken permissions or similar which can happen if the update/upgrade is not done correctly by using a wrong user (e.g. root instead of www-data) or similar.


Just a clarification, I ran the occ upgrade command as root: sudo -u apache php occ upgrade


Can you verify that:


exists and is readable by that Apache user?


-rw-r--r--. 1 root apache 252451 Sep 19 13:04 ca-bundle.crt


Ok, then please report a new bug to:



One last question. How will this bug impact users? Thanks.


It could be a bug (as it happened after the update from 9.1.0 to 9.1.0) but its not sure. Some one at github might be able to tell you more.