Bug 1582274
| Summary: | Owncloud/nextcloud broken 500 error after upgrade F27 to 28 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | gareth foster <biggaz> |
| Component: | nextcloud | Assignee: | James Hogarth <james.hogarth> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 28 | CC: | james.hogarth |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-05-28 23:42:33 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
gareth foster
2018-05-24 17:01:13 UTC
Further to this, I just dropped all the tables and config files to do with Nextcloud, and started from scratch. It allowed me through the set up, then I end up at the same place with a 500 error when I try and log in. I read this ... https://stackoverflow.com/questions/4731364/internal-error-500-apache-but-nothing-in-the-logs Which says 500 errors should always be logged, unless they're PHP errors, which led to this .... https://stackoverflow.com/questions/4731364/internal-error-500-apache-but-nothing-in-the-logs But the logs aren't in /var/log/apache2/error.log, after a load more fannying around I found they're in ... /var/log/php-fpm/www-error.log Which is nice and obscure. At last in there, I found loads of this ... [30-May-2018 20:50:07 UTC] PHP Fatal error: Declaration of OC\Files\Storage\Local::copyFromStorage(OCP\Files\Storage $sourceStorage, $sourceInternalPath, $targetInternalPath) must be compatible with OC\Files\Storage\Common::copyFromStorage(OCP\Files\Storage $sourceStorage, $sourceInternalPath, $targetInternalPath, $preserveMtime = false) in /usr/share/owncloud/lib/private/Files/Storage/Local.php on line 42 So now searching for this error message leads to this ... https://help.nextcloud.com/t/declaration-of-storagewrapper-error/26953 Which suggests the problem is with the "File Access Control app", and suggests moving it out of the apps folder. I can't see it though. Owncloud and a new install of Nextcloud are both doing this. So ... nextcloud.noarch 10.0.4-3.fc27 owncloud-9.1.5-3.fc28.noarch php-7.2.6-1.fc28.x86_64 I'm starting to think this might be a PHP version issue. php-7.1.10-1.fc27.x86_64.rpm So, as noted on the Nextcloud bugzilla, this is very easily fixed, but it's a bit crap it needs fixing. https://github.com/nextcloud/server/issues/9588 "Don't know if it will solve all your problems but just add ", $preserveMtime = false" to the function in Local.php so the definition is the same as in Common.php" Hope that helps anyone else who's got this. Also still need to keep downgrading php-sabre-sav to the version from F26 for the calendar part of Owncloud to work. From them. The packaged version is not supported ... nextcloud-10.0.4-3.fc27.noarch Then you should upgrade to the last supported version, because 10 is end of life and 10.0.4 is also not even the latest patch level: see https://nextcloud.com/changelog/#latest10 and https://nextcloud.com/security/advisories/ Only 12 and 13 is still maintained. Thus closing because it is an unsupported version you are running. If you have the same problems with either 12 or 13 we can have a look at this again. Looks like this is all old news, and I've found all this out the hard way ... https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/NQHLQ43MJJTC5BPYRIUZOHUV3FJINBOT/ This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |