[Bug 217225] www/nextcloud shipping with config.php which causes certain httpd/fcgi confgurations to throw errors
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sun Feb 19 11:15:45 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217225
Bug ID: 217225
Summary: www/nextcloud shipping with config.php which causes
certain httpd/fcgi confgurations to throw errors
Product: Ports & Packages
Version: Latest
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: freebsd-ports-bugs at FreeBSD.org
Reporter: debdrup at gmail.com
CC: loic.blot at unix-experience.fr
CC: loic.blot at unix-experience.fr
Flags: maintainer-feedback?(loic.blot at unix-experience.fr)
I'm filing this bug after a brief discussion with maintainer on IRC on the
topic of nextcloud shipping with a config.php which throws the following error
upon accessing index.php:
2017/02/18 23:56:08 [error] 82852#101771: *1 FastCGI sent in stderr: "PHP
message: PHP Fatal error: Uncaught Error: Call to a member function
getLogger() on null in /usr/local/www/nextcloud/index.php:61
Stack trace:
#0 {main}
thrown in /usr/local/www/nextcloud/index.php on line 61" while reading
response header from upstream, client: 192.168.1.114, server: 192.168.1.53,
request: "GET /index.php/ HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000",
host: "192.168.1.53"
The issue is, however, fixed simply by deleting the included config.php file
provided by upstream, which could be done for the port if the file matches the
checksum from upstream (so as to avoid any issues with packaging). That way,
whenever a user points a httpd to the nextcloud directory, they're presented
with the nextcloud installation wizard.
I believe maintainer is already working on a fix, so this bug is just to serve
as a reminder/reference for which bug it fixes.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list