-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nextcloud 14: Uncaught error, Call to a member function getLogger() on null when attempting installation #11298
Comments
GitMate.io thinks possibly related issues are #6706 (Call to a member function getUID() on null), #6803 (Nextcloud 12 throwing fatal error: cron - “Call to a member function getFileInfo() on null”), #10316 (Error: Call to a member function instanceOfStorage() on null), #3110 (PROPFIND causes Error: Call to a member function getCache() on null), and #10585 (Error: Call to a member function getMimetype() on boolean). |
Methinks the bot is off because
|
I'm getting the same error on a brand new nextcloud 14.0.0 install. I found an error in my config.php and corrected it but still getting the same error internal server error. I've looked at line #72 in the index.php and it does not shed any light on the issue. My install is using Apache 2, Mariadb, PHP 7.1 on an Ubuntu 18.0.4 Server LTS |
I'm getting the same error on a new install of nextcloud 14.0.1 on FreeBSD 12-Current. |
Same here, with nextcloud 14.0.1 with Apache + php7.2 + MariaDB |
Same here, also 14.0.1, Apache 2.4.6, PHP 7.2.10, MariaDB 10.2.18 on CentOS 7. |
The same - v14.0.3, Centos 7. |
Happened to me too during installation after creating config.php manually (you're not expected to do that). Deleted the file, now everything's fine. |
Maybe this problem come from php-acpu Debian testing, after downgrading php-apcu-bc from 1.0.4-3 to 1.0.4-2 nextcloud 14.0.3 is back |
This comment has been minimized.
This comment has been minimized.
Of course! I cannot reproduce this issue unfortunately. Could you look for this line Line 70 in 0092e3a
var_dump($ex); exit(); below?
|
This comment has been minimized.
This comment has been minimized.
Same problem on Arch Linux +Nginx + PHP-FPM + MariaDB running 14.0.3. Fresh install.
|
|
@danielkesselberg Here you go:
|
Do you created
|
Ah ha! I did that the first time, didn't do it the second.
…On October 28, 2018 3:22:18 PM EDT, Daniel Kesselberg ***@***.***> wrote:
Do you created `config.php` before running the setup like @choopm? If
so please dont ;-) Delete config.php and visit nextcloud. Installer
will create config.php for you.
> Happened to me too during installation after creating config.php
manually (you're not expected to do that). Deleted the file, now
everything's fine.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#11298 (comment)
|
Fresh install: same result |
Could you share your |
Here you go: |
Are they any other files in |
Got it fixed. Problem now is that I see a massive amount of .js errors in console |
How do you fixed it? What kind of js errors? |
@danielkesselberg The getlogger() error was due to PEBKAC. Something missing in my web server config. Fixed the .js errors by removing all caches. |
Ref #12198 Linked pr improves error message. Should be easier to find the real reason. |
I also had this error on Ubuntu 18.04 LTS 64bit, because I copied config.php from the config.sample.php The sample is quite "freaky", I tried to make something out of it, but when opening the wizard got the mentioned error:
So I just removed my config.php and started the wizard and it's working great! |
Can also confirm, removing the nextcloud/config/config.php resolved the issue. |
When I remove config.php, it gets recreated, but this time I get for the first the the blue nextcloud background, but It says "Internal Server Error" |
I get those lines in the docker logs, they seem to be important:
|
Installed NC 15 today and get this error every time cronjob is launched. I also have NC 14 (installed months ago) on the same server, and it works perfectly, so it's surely not server's problem. I did NOT generate config.php file manually. Struggling with this error for hours, will try to delete and re-install. |
@toxpal could you create a new issue for that? thank you! https://github.com/nextcloud/server/issues/new/choose (please try to add all information requested by the issue template). |
Maybe a solution: <?php
$CONFIG = array (
'instanceid' => 'xxxxxxxxxxxx',
);
yyyyyyyyyyyyyy',
'secret' => 'zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz',
'trusted_domains' =>
array (
0 => 'xxxxxx.xxx',
),
… I juste remove this part: );
yyyyyyyyyyyyyy', and now it works perfectly! |
@brokkr does this issue still exist? |
@kesselb, for me, actually yes. I ended up with this while setting up nextcloud with: and https://github.com/MatchbookLab/local-persist to have my nextcloud & data directory mounted via nfs The problem went away when I started to serve nextcloud from local harddrive and serve the data dir via nfs only To bad I cant serve the root directory from my NAS but still, having the data on my NAS via nfs and running nextcloud from local NUC harddrive is fine for now. Hope this might help somebody |
@axe312ger please create a new issue with the issue template. This issue is already to crowded. |
This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions. |
I had a similar problem with Nextcloud being served over NFS. It was resolved by making sure the NFS server was running lockd; in my case, with Ubuntu 18, the commands were: |
I came here by googling the text in the issue header. My issue was: Syntax error in the config file. So I just ran php on config.php on the command line and it showed me the error line, where the syntax error was. |
Steps to reproduce
Expected behaviour
Nextcloud's install page should show up
Actual behaviour
The following text is displayed in browser:
After enabling
in www.conf, php-fpm output changed from simply reporting http status 500 to reporting 500 AND including the same (but no more) output as above.
The expected behaviour is seen using volumes with older releases:
A standard phpinfo.php status page inserted into the Nextcloud 14 folder web root is accessible and does display. The status page confirms that all required (https://docs.nextcloud.com/server/14/admin_manual/installation/source_installation.html) modules are installed.
The behaviour of 14.0 does not change with older php-fpm releases (7.1, 7.0)
Server configuration
Operating system:
Web server: Nginx 1.14 ('nginx:stable')
Database: Mariadb 10.3.9
PHP version: 7.2.10
Nextcloud version: 14.0
Updated from an older Nextcloud/ownCloud or fresh install: No
Where did you install Nextcloud from: https://download.nextcloud.com/server/releases/nextcloud-14.0.0.tar.bz2
Signing status:
Not available
List of activated apps:
App list
Nextcloud configuration:
Config report
Are you using external storage, if yes which one: No
Are you using encryption: On NC files? No. I have a proxy setup on docker host that encrypts traffic to the host and proxy_pass'es request to the container. The results are the same when accessing the container through the proxy (https) and when accessing it directly (http) on the published host port.
Are you using an external user-backend, if yes which one: No
Client configuration
Browser: "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/67.0.3396.99 Chrome/67.0.3396.99 Safari/537.36"
Operating system: Ubuntu 17.10
Logs
Web server error log
Web server error log
Nextcloud log (data/nextcloud.log)
Nextcloud log
Browser log
Browser log
The text was updated successfully, but these errors were encountered: