logreader Logging stuck + 100% CPU after unchecking all filters

Steps to reproduce

Enter Settings -> Logging
Uncheck all filters
Try to refresh or return to Logging after loading another page

Expected behaviour

An empty log, from which you can re-check the desired filter items.

Actual behaviour

An empty Logging tab with only a spinner. The PHP thread gets completely stuck, draining 100% of the CPU core indefinitely.

Server configuration

Operating system: Arch Linux ARM on Raspberry Pi 4 Web server: nginx 1.16.1 Database: mariadb 10.4.12 PHP version: php(-fpm) 7.4.3 Nextcloud version: (see Nextcloud admin page) Nextcloud 18.0.1 Updated from an older Nextcloud/ownCloud or fresh install: updated from 18.0.0 (but never tried this with previous versions!) Where did you install Nextcloud from: pacman Signing status:

Signing status

List of activated apps:

App list

Enabled:
  - activity: 2.11.0
  - calendar: 2.0.1
  - cloud_federation_api: 1.1.0
  - contacts: 3.1.8
  - dav: 1.14.0
  - deck: 0.8.0
  - federatedfilesharing: 1.8.0
  - files: 1.13.1
  - files_external: 1.9.0
  - files_rightclick: 0.15.2
  - files_sharing: 1.10.1
  - files_trackdownloads: 1.7.0
  - files_trashbin: 1.8.0
  - files_versions: 1.11.0
  - logreader: 2.3.0
  - lookup_server_connector: 1.6.0
  - nextcloud_announcements: 1.7.0
  - notifications: 2.6.0
  - oauth2: 1.6.0
  - provisioning_api: 1.8.0
  - serverinfo: 1.8.0
  - settings: 1.0.0
  - tasks: 0.11.3
  - text: 2.0.0
  - twofactor_backupcodes: 1.7.0
  - updatenotification: 1.8.0
  - viewer: 1.2.0
  - workflowengine: 2.0.0
Disabled:
  - accessibility
  - admin_audit
  - bruteforcesettings
  - comments
  - encryption
  - federation
  - files_pdfviewer
  - files_videoplayer
  - firstrunwizard
  - password_policy
  - photos
  - privacy
  - recommendations
  - sharebymail
  - support
  - survey_client
  - systemtags
  - theming
  - user_ldap

Nextcloud configuration:

Config report

<?php
$CONFIG = array (
  'instanceid' => '###',
  'passwordsalt' => '###',
  'secret' => '###',
  'trusted_domains' =>
  array (
    0 => '###',
  ),
  'datadirectory' => '/srv/http/nextcloud',
  'dbtype' => 'mysql',
  'version' => '18.0.1.3',
  'overwrite.cli.url' => '###',
  'dbname' => '###',
  'dbhost' => 'localhost',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => '###',
  'dbpassword' => '###',
  'installed' => true,
  'maintenance' => false,
  'theme' => '###',
  'appstore.experimental.enabled' => true,
  'logtimezone' => '###',
  'mail_from_address' => '###',
  'mail_smtpmode' => 'smtp',
  'mail_domain' => '###',
  'enable_previews' => false,
  'mail_sendmailmode' => 'smtp',
  'mail_smtpauth' => 1,
  'mail_smtpname' => '###',
  'mail_smtppassword' => '###',
  'mail_smtpauthtype' => '###',
  'mail_smtpsecure' => 'ssl',
  'mail_smtphost' => '###',
  'mail_smtpport' => '###',
  'loglevel' => 0,
  'remember_login_cookie_lifetime' => ###,
  'app_install_overwrite' =>
  array (
    0 => 'contacts',
    1 => 'files_trackdownloads',
  ),
);

Are you using external storage, if yes which one: local/smb/sftp/... local Are you using encryption: yes/no no Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/... webdav

Client configuration

Browser: Firefox/Chrome Operating system: Any

Logs

Web server error log

Nothing there, other than me restarting php-fpm in order to stop the stuck thread.

Nextcloud log (data/nextcloud.log)

Nextcloud log

Nothing there related to this issue (only some "deprecated" messages).

Browser log

JQMIGRATE: Migrate is installed, version 1.4.1  main.js:566:521
Proxying an event bus of version 1.1.2 with 0.2.1  notifications.js:21:13427
Handlebars is deprecated: please ship your own, this will be removed in Nextcloud 20  globals.js:66:2
New search handler registered

Feb 25 '20 21:02 ltguillaume

Hi had the same issue with the log reader. I fixed the issue by decreasing the log file size. You can change the rotation with sudo -u www-user php occ log:file --rotate-size 52428800 (size in bytes). After the rotation the log reader works as designed.

It looks like it take to long to read out the complete file.

Mar 21 '21 18:03 maximilianvonamerongen

Hi you can fix it temporarily with setting the filters in the database directly.

Be careful editing the database directly, because you can destroy your nextcloud instance.

Assuming the database prefix is oc_ :

Logviewer can only be restored by executing: UPDATE oc_appconfig SET configvalue = '11111' WHERE appid = 'logreader' AND configkey = 'levels';

Oct 28 '21 07:10 TimRivinius

The following should work too AFAIK (from the CLI). It's safer and easier than directly adjusting the database table:

occ config:app:set logreader levels --value="11111"

Jun 08 '23 00:06 joshtrichards

Also, even better, this is no longer a reproduceable issue in >NC26. I think we can close this out.

Jun 08 '23 12:06 joshtrichards

Last version of Logreader written in react is Nextcloud 27.1.11 (End of life was at 2024-06-25)

Quickly checked at Nextcloud 28, requests to logfile are chunked by 50 rows, so should not be an issue anymore

Sep 17 '24 09:09 Antreesy

logreader logreader copied to clipboard

Logging stuck + 100% CPU after unchecking all filters

Steps to reproduce

Expected behaviour

Actual behaviour

Server configuration

Client configuration

Logs

Web server error log

Nextcloud log (data/nextcloud.log)

Browser log

logreader
logreader copied to clipboard