Log viewer empty after upgrade to Nextloud 24.0.0

Support intro

Sorry to hear you’re facing problems :slightly_frowning_face:

help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.

In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:

example

Or for longer, use three backticks above and below the code snippet:

longer
example
here

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can :heart:

Nextcloud version (eg, 20.0.5): 24.0.0
Operating system and version (eg, Ubuntu 20.04): Ubuntu 20.04
Apache or nginx version (eg, Apache 2.4.25): Apache 2.4.41-4ubuntu3.10
PHP version (eg, 7.4): 7.4

The issue you are facing:

After I upgrade to NC 24.0.0 the log viewer (https://servername/settings/admin/logging) starts loading but then the content is removed and the page becomes blank.

In the developer console I see the following errors:

react-dom.production.min.js:216 Error: Minified React error #188; visit https://reactjs.org/docs/error-decoder.html?invariant=188 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at t.findDOMNode (react-dom.production.min.js:289:284)
    at t.transition (CSSTransitionGroupChild.js:129:30)
    at t.r.componentWillEnter (CSSTransitionGroupChild.js:97:15)
    at t.s.performEnter (TransitionGroup.js:83:19)
    at TransitionGroup.js:192:21
    at Array.forEach (<anonymous>)
    at t.componentDidUpdate (TransitionGroup.js:191:17)
    at co (react-dom.production.min.js:219:502)
    at xl (react-dom.production.min.js:259:160)
    at t.unstable_runWithPriority (scheduler.production.min.js:18:343)
Uncaught (in promise) Error: Minified React error #188; visit https://reactjs.org/docs/error-decoder.html?invariant=188 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at t.findDOMNode (react-dom.production.min.js:289:284)
    at t.transition (CSSTransitionGroupChild.js:129:30)
    at t.r.componentWillEnter (CSSTransitionGroupChild.js:97:15)
    at t.s.performEnter (TransitionGroup.js:83:19)
    at TransitionGroup.js:192:21
    at Array.forEach (<anonymous>)
    at t.componentDidUpdate (TransitionGroup.js:191:17)
    at co (react-dom.production.min.js:219:502)
    at xl (react-dom.production.min.js:259:160)
    at t.unstable_runWithPriority (scheduler.production.min.js:18:343)

Is this the first time you’ve seen this error? (Y/N): Y

Steps to replicate it:

  1. Log in to Nextcloud as administrative user
  2. Go to Admin > Logging

The output of your Nextcloud log in Admin > Logging:

Not possible, since logging is not available.

The output of your config.php file in /path/to/nextcloud (make sure you remove any identifiable information!):

<?php
$CONFIG = array (
  'instanceid' => '-- removed for to security reasons --',
  'passwordsalt' => '-- removed for to security reasons --',
  'secret' => '-- removed for to security reasons --',
  'trusted_domains' => 
  array (
    0 => '-- removed for to security reasons --',
  ),
  'datadirectory' => '-- removed for to security reasons --',
  'skeletondirectory' => '',
  'overwrite.cli.url' => '-- removed for to security reasons --',
  'dbtype' => 'mysql',
  'version' => '24.0.0.12',
  'installed' => true,
  'htaccess.RewriteBase' => '/',
  'maintenance' => false,
  'dbname' => '-- removed for to security reasons --',
  'dbhost' => '-- removed for to security reasons --',
  'dbuser' => '-- removed for to security reasons --',
  'dbpassword' => '-- removed for to security reasons --',
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'knowledgebaseenabled' => false,
  'theme' => '',
  'simpleSignUpLink.shown' => false,
  'loglevel' => 0,
  'log_authfailip' => true,
  'mysql.utf8mb4' => true,
  'mail_from_address' => 'nextcloud',
  'mail_smtpmode' => 'sendmail',
  'mail_smtpauthtype' => 'LOGIN',
  'mail_domain' => '-- removed for to security reasons --',
  'updater.release.channel' => 'stable',
  'trashbin_retention_obligation' => 'auto, 30',
  'app_install_overwrite' => 
  array (
    0 => 'apporder',
    1 => 'deck',
    2 => 'keeweb',
    3 => 'appointments',
    4 => 'drawio',
    5 => 'bookmarks',
    6 => 'spreed',
  ),
  'has_rebuilt_cache' => true,
  'onlyoffice' => 
  array (
    'verify_peer_off' => true,
  ),
  'default_language' => 'de',
  'default_phone_region' => 'DE',
  'check_data_directory_permissions' => false,
);

The output of your Apache/nginx/system log in /var/log/____:

(omitted as this this file is about 70 MB big and contains private information)

Output errors in nextcloud.log in /var/www/ or as admin user in top right menu, filtering for errors. Use a pastebin service if necessary.

(not possible since log is not available in UI)

Does it work if you delete the logfile?

The log file is called nextcloud.log and is located within the datadirectory (see config.php).

No - that’s the first thing I already tried.

Update: it works now after I have deleted the logfile and changed the loglevel down to 2 to avoid too many log entries. Somehow after the update the log level was set to 0 by the updater which of course creates a lot of debug messages which are usually not needed in production.

It seems the log viewer does not cope very well with bigger logfiles. I don’t know yet where the limit is, but when debug and info messages are enabled as well, the file grows very quick and with more than about 30.000 entries the log viewer starts to fail.

Lesson learned: always check the log level setting after an update and make sure it is not set to 0 but at least 1 or 2.

Nevertheless - the log viewer should not fail, even if there are 100.000 log entries. Maybe implementing a paginated view would help.

2 Likes

A Message displayed in the frontend like “the file is to big to read” would be a nice improvement. Maybe you want to create a feature request for better error handling:

I created a new issue for this:

2 Likes