Skip to content

logreader shows spinning icon forever #50

Closed

Description

@tessus

Steps to reproduce

  1. Goto Admin page
  2. Click on Logging

Expected behaviour

Log entries should be displayed

Actual behaviour

Nothing is shown, except the spinning icon

Server configuration

Operating system: Linux

Web server: Apache 2.4.25

Database: MySQL 5.6.25

PHP version: 7.1.4

Nextcloud version: 11.0.3.2

Where did you install Nextcloud from: updated from 11.0.2 to 11.0.3 with updater.phar, then occ upgrade

List of activated apps:

Enabled:
  - activity: 2.4.1
  - activitylog: 0.0.1
  - admin_audit: 1.1.0
  - announcementcenter: 3.0.0
  - apporder: 0.3.3
  - bookmarks: 0.9.1
  - calendar: 1.5.2
  - comments: 1.1.0
  - contacts: 1.5.3
  - dav: 1.1.1
  - direct_menu: 0.10.1
  - external: 1.2
  - federatedfilesharing: 1.1.1
  - federation: 1.1.1
  - files: 1.6.1
  - files_external: 1.1.2
  - files_markdown: 1.0.1
  - files_pdfviewer: 1.0.1
  - files_sharing: 1.1.1
  - files_texteditor: 2.2
  - files_trashbin: 1.1.0
  - files_versions: 1.4.0
  - files_videoplayer: 1.0.0
  - firstrunwizard: 2.0
  - gallery: 16.0.0
  - logreader: 2.0.0
  - lookup_server_connector: 1.0.0
  - nextcloud_announcements: 1.0
  - notes: 2.2.0
  - notifications: 1.0.1
  - password_policy: 1.1.0
  - provisioning_api: 1.1.0
  - serverinfo: 1.1.1
  - sharebymail: 1.0.1
  - systemtags: 1.1.3
  - tasks: 0.9.5
  - templateeditor: 0.2
  - theming: 1.1.1
  - twofactor_backupcodes: 1.0.0
  - updatenotification: 1.1.1
  - user_external: 0.4
  - workflowengine: 1.1.1
Disabled:
  - encryption
  - files_accesscontrol
  - files_automatedtagging
  - files_retention
  - survey_client
  - user_ldap
  - user_saml

Nextcloud configuration:

{
    "system": {
        "instanceid": "oc2352d53521",
        "passwordsalt": "***REMOVED SENSITIVE VALUE***",
        "datadirectory": "\/data\/nextcloud\/data",
        "dbtype": "mysql",
        "version": "11.0.3.2",
        "installed": true,
        "forcessl": true,
        "loglevel": 2,
        "maintenance": false,
        "trusted_domains": [
            "cloud.evermeet.cx"
        ],
        "share_folder": "\/Shared",
        "dbname": "nextcloud",
        "dbhost": "localhost",
        "dbuser": "***REMOVED SENSITIVE VALUE***",
        "dbpassword": "***REMOVED SENSITIVE VALUE***",
        "logdateformat": "Y-m-d H:i:s O",
        "logtimezone": "Europe\/Vienna",
        "secret": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpmode": "php",
        "mail_from_address": "evercloud",
        "mail_domain": "evermeet.cx",
        "mail_smtpsecure": "tls",
        "memcache.local": "\\OC\\Memcache\\Redis",
        "memcache.locking": "\\OC\\Memcache\\Redis",
        "redis": {
            "host": "\/data\/redis\/redis.sock",
            "port": 0,
            "timeout": 0
        },
        "appstore.experimental.enabled": true,
        "trashbin_retention_obligation": "auto",
        "updater.release.channel": "stable",
        "htaccess.RewriteBase": "\/",
        "overwrite.cli.url": "https:\/\/cloud.evermeet.cx",
        "auth.bruteforce.protection.enabled": false
    }
}

Client configuration

Browser: Firefox 53.0, Chrome 58.0.3029.81

Operating system: macOS 10.11.6

Logs

Nextcloud log (data/owncloud.log)

{"reqId":"vQdB5WyWYdE\/7DwAnyZY","remoteAddr":"x.x.x.x","app":"index","message":"Exception: {\"Exception\":\"Error\",\"Message\":\"Call to a member function format() on boolean\",\"Code\":0,\"Trace\":\"#0 \\\/data\\\/projects\\\/nextcloud\\\/apps\\\/logreader\\\/lib\\\/Controller\\\/LogController.php(133): OCA\\\\LogReader\\\\Log\\\\LogIterator->current()\\n#1 \\\/data\\\/projects\\\/nextcloud\\\/apps\\\/logreader\\\/lib\\\/Controller\\\/LogController.php(73): OCA\\\\LogReader\\\\Controller\\\\LogController->responseFromIterator(Object(OCA\\\\LogReader\\\\Log\\\\LogIterator), 50, 0)\\n#2 [internal function]: OCA\\\\LogReader\\\\Controller\\\\LogController->get(50, 0)\\n#3 \\\/data\\\/projects\\\/nextcloud\\\/lib\\\/private\\\/AppFramework\\\/Http\\\/Dispatcher.php(160): call_user_func_array(Array, Array)\\n#4 \\\/data\\\/projects\\\/nextcloud\\\/lib\\\/private\\\/AppFramework\\\/Http\\\/Dispatcher.php(90): OC\\\\AppFramework\\\\Http\\\\Dispatcher->executeController(Object(OCA\\\\LogReader\\\\Controller\\\\LogController), 'get')\\n#5 \\\/data\\\/projects\\\/nextcloud\\\/lib\\\/private\\\/AppFramework\\\/App.php(114): OC\\\\AppFramework\\\\Http\\\\Dispatcher->dispatch(Object(OCA\\\\LogReader\\\\Controller\\\\LogController), 'get')\\n#6 \\\/data\\\/projects\\\/nextcloud\\\/lib\\\/private\\\/AppFramework\\\/Routing\\\/RouteActionHandler.php(47): OC\\\\AppFramework\\\\App::main('OCA\\\\\\\\LogReader\\\\\\\\C...', 'get', Object(OC\\\\AppFramework\\\\DependencyInjection\\\\DIContainer), Array)\\n#7 [internal function]: OC\\\\AppFramework\\\\Routing\\\\RouteActionHandler->__invoke(Array)\\n#8 \\\/data\\\/projects\\\/nextcloud\\\/lib\\\/private\\\/Route\\\/Router.php(299): call_user_func(Object(OC\\\\AppFramework\\\\Routing\\\\RouteActionHandler), Array)\\n#9 \\\/data\\\/projects\\\/nextcloud\\\/lib\\\/base.php(1010): OC\\\\Route\\\\Router->match('\\\/apps\\\/logreader...')\\n#10 \\\/data\\\/projects\\\/nextcloud\\\/index.php(40): OC::handleRequest()\\n#11 {main}\",\"File\":\"\\\/data\\\/projects\\\/nextcloud\\\/apps\\\/logreader\\\/lib\\\/Log\\\/LogIterator.php\",\"Line\":75}","level":3,"time":"2017-04-26 04:20:52 +0200","method":"GET","url":"\/apps\/logreader\/get?offset=0&count=50","user":"x","version":"11.0.3.2"}

Browser log

javascript console log

JQMIGRATE: Migrate is installed, version 1.4.0  jquery-migrate.min.js:2:542
Unhandled rejection (<{"readyState":4,"responseText":"<!DOCT...>, no stack trace)  main.js:30:1190

Activity

  1. tessus commented on Apr 27, 2017

    @tessus
    Author

    Is this issue tracker being used or shall I open an issue with nextcloud/server?

  2. MorrisJobke commented on Apr 29, 2017

    @MorrisJobke
    Member
  3. added this to the Nextcloud 12.0 milestone on Apr 29, 2017
  4. ariselseng commented on Apr 29, 2017

    @ariselseng
    Member

    This happens to my install too. 11.0.3.

  5. qswroot commented on May 3, 2017

    @qswroot

    As workaround I installed the logreader version from NC package 11.0.2 - this seems to work with NC 11.0.3.

  6. tessus commented on May 3, 2017

    @tessus
    Author

    @qswroot I had a few problems with that version too, e.g. the scroll problem...
    anyway, what I don't understand is why this version has been released with nc 11.0.3, yet only shows a blank page. I mean, this must have been a red flag in QA.

  7. evilstiefel commented on May 3, 2017

    @evilstiefel

    I presume that's because it doesn't always cause an issue. I've updated another instance of NC to 11.0.3 and the logreader works just fine (both show up as version 2.0.0 in the "apps" section).

    Still, I'm facing the exact same issue on another installation.

  8. tessus commented on May 3, 2017

    @tessus
    Author

    now that's even weirder.

  9. qswroot commented on May 4, 2017

    @qswroot

    I now realized I also have the scroll problem now with the logreader from NC 11.0.2: when I scroll down the page will be reloaded, so I am not able to view older log entries.

    As a result I will keep NC 10 on our production system. And I just saw on the NC webpage that this version is now marked as EOL :-(

  10. evilstiefel commented on May 4, 2017

    @evilstiefel

    After some investigation, the issue seems to stem from entries in the nextcloud.log file which have "invalid" timestamps associated for entries.

    The format-function then failes and the error is not handled. I remember in previous versions of Nextcloud (namely 11.0.2) the logreader app would show an "invalid date" string in the time column of the logreader.

    Short-term "fix": clean the {owncloud,nextcloud}.log and it should work again.

  11. qswroot commented on May 4, 2017

    @qswroot

    By the way, all log entries are shown as 2 hours ahead, although all entries in the logfile itself have the correct value.

  12. evilstiefel commented on May 4, 2017

    @evilstiefel

    Unfortunately, the problem will reappear when a new log-entry is created.

    {"reqId":"p\/7+24mBbBY3\/ZcUiR86","remoteAddr":"172.20.0.1","app":"core","message":"Login failed: 'steffen' (Remote IP: '172.20.0.1')","level":2,"time":"2017-05-04 16:49:17","method":"POST","url":"\/login","user":"--","version":"11.0.3.2"}

    Was the only entry in the logfile and caused the same problem:

    {"reqId":"HQdjg5SGdxA3\/1151NDz","remoteAddr":"172.20.0.1","app":"index","message":"Exception: {\"Exception\":\"Error\",\"Message\":\"Call to a member function format() on boolean\",\"Code\":0,\"Trace\":\"[*snipped*]"}

  13. mightyBroccoli commented on May 9, 2017

    @mightyBroccoli

    I get the same error and my Chrome just got me this message in the dev console

    GET https://URL/index.php/apps/logreader/get?offset=0&count=50 500 ()
    send @ core.js?v=3a9209f…-34:4
    ajax @ core.js?v=3a9209f…-34:4
    n.(anonymous function) @ core.js?v=3a9209f…-34:4
    value @ main.js?v=3a9209f…-34:23
    (anonymous) @ main.js?v=3a9209f…-34:23
    i @ main.js?v=3a9209f…-34:37
    (anonymous) @ main.js?v=3a9209f…-34:37
    e.(anonymous function) @ main.js?v=3a9209f…-34:37
    i @ main.js?v=3a9209f…-34:2
    u._promiseFulfilled @ main.js?v=3a9209f…-34:30
    (anonymous) @ main.js?v=3a9209f…-34:30
    e @ main.js?v=3a9209f…-34:23
    (anonymous) @ main.js?v=3a9209f…-34:37
    i @ main.js?v=3a9209f…-34:37
    (anonymous) @ main.js?v=3a9209f…-34:37
    e.(anonymous function) @ main.js?v=3a9209f…-34:37
    i @ main.js?v=3a9209f…-34:2
    u._promiseFulfilled @ main.js?v=3a9209f…-34:30
    o._settlePromise @ main.js?v=3a9209f…-34:30
    o._settlePromise0 @ main.js?v=3a9209f…-34:30
    o._settlePromises @ main.js?v=3a9209f…-34:30
    r._drainQueue @ main.js?v=3a9209f…-34:29
    r._drainQueues @ main.js?v=3a9209f…-34:29
    drainQueues @ main.js?v=3a9209f…-34:29
    main.js?v=3a9209f…-34:30 Unhandled rejection (<{"readyState":4,"responseText":"<!DOCT...>, no stack trace)
    H @ main.js?v=3a9209f…-34:30
    Y @ main.js?v=3a9209f…-34:29
    T @ main.js?v=3a9209f…-34:29
    e._notifyUnhandledRejection @ main.js?v=3a9209f…-34:29
    r._drainQueue @ main.js?v=3a9209f…-34:29
    r._drainQueues @ main.js?v=3a9209f…-34:29
    drainQueues @ main.js?v=3a9209f…-34:29
    
  14. MorrisJobke commented on May 19, 2017

    @MorrisJobke
    Member

    Fix is in #53

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions