admin/advanced/events send me an error

Bug Reports
  • Hello,

    I've got a problem on a fresh install.
    When I try to acces this adress : http://IP_ADRESS:4567/admin/advanced/events
    I also got the same type of error with http://IP_ADRESS:4567/admin/advanced/database

    I got this error :
    alt text

    I also got those error on the javascript session :
    alt text

    I've tried everything I could think of.
    I've desactivated cloudflare, nginx, everything.

    If you have any idee what might cause this, I would love to hear it, i'm tired of all this =/

    You will also find below the error that I got with ./nodebb log and my install commands.

    21/10 03:38 [12749] - error: TypeError: Cannot read property 'uid' of undefined
        at /var/www/nodebb/src/events.js:104:18
        at Array.forEach (native)
        at /var/www/nodebb/src/events.js:103:15
        at /var/www/nodebb/node_modules/async/lib/async.js:726:13
        at /var/www/nodebb/node_modules/async/lib/async.js:52:16
        at done (/var/www/nodebb/node_modules/async/lib/async.js:246:17)
        at /var/www/nodebb/node_modules/async/lib/async.js:44:16
        at /var/www/nodebb/node_modules/async/lib/async.js:723:17
        at /var/www/nodebb/node_modules/async/lib/async.js:167:37
        at fireFilterHook (/var/www/nodebb/src/plugins/hooks.js:103:11)
        at Object.Plugins.fireHook (/var/www/nodebb/src/plugins/hooks.js:87:5)
        at modifyUserData (/var/www/nodebb/src/user/data.js:141:11)
        at /var/www/nodebb/src/user/data.js:62:4
        at /var/www/nodebb/src/database/mongo/hash.js:136:4
        at handleCallback (/var/www/nodebb/node_modules/mongodb/lib/utils.js:96:12)
        at /var/www/nodebb/node_modules/mongodb/lib/cursor.js:839:16
        at handleCallback (/var/www/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:159:5)
        at setCursorDeadAndNotified (/var/www/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:501:3)
        at nextFunction (/var/www/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:652:7)
        at Cursor.next [as _next] (/var/www/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:693:3)
        at fetchDocs (/var/www/nodebb/node_modules/mongodb/lib/cursor.js:835:10)
        at /var/www/nodebb/node_modules/mongodb/lib/cursor.js:858:7
    TypeError: Cannot read property 'uid' of undefined
        at /var/www/nodebb/src/events.js:104:18
        at Array.forEach (native)
        at /var/www/nodebb/src/events.js:103:15
        at /var/www/nodebb/node_modules/async/lib/async.js:726:13
        at /var/www/nodebb/node_modules/async/lib/async.js:52:16
        at done (/var/www/nodebb/node_modules/async/lib/async.js:246:17)
        at /var/www/nodebb/node_modules/async/lib/async.js:44:16
        at /var/www/nodebb/node_modules/async/lib/async.js:723:17
        at /var/www/nodebb/node_modules/async/lib/async.js:167:37
        at fireFilterHook (/var/www/nodebb/src/plugins/hooks.js:103:11)
        at Object.Plugins.fireHook (/var/www/nodebb/src/plugins/hooks.js:87:5)
        at modifyUserData (/var/www/nodebb/src/user/data.js:141:11)
        at /var/www/nodebb/src/user/data.js:62:4
        at /var/www/nodebb/src/database/mongo/hash.js:136:4
        at handleCallback (/var/www/nodebb/node_modules/mongodb/lib/utils.js:96:12)
        at /var/www/nodebb/node_modules/mongodb/lib/cursor.js:839:16
        at handleCallback (/var/www/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:159:5)
        at setCursorDeadAndNotified (/var/www/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:501:3)
        at nextFunction (/var/www/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:652:7)
        at Cursor.next [as _next] (/var/www/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:693:3)
        at fetchDocs (/var/www/nodebb/node_modules/mongodb/lib/cursor.js:835:10)
        at /var/www/nodebb/node_modules/mongodb/lib/cursor.js:858:7
    21/10 03:38 [12749] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
    21/10 03:38 [12749] - info: [app] Database connection closed.
    21/10 03:38 [12749] - info: [app] Web server closed to connections.
    21/10 03:38 [12749] - info: [app] Shutdown complete.
    [cluster] Child Process (12749) has exited (code: 1, signal: null)
    [cluster] Spinning up another process...
    21/10 03:38 [27519] - info: Time: Fri Oct 21 2016 03:38:26 GMT-0400 (EDT)
    21/10 03:38 [27519] - info: Initializing NodeBB v1.2.1
    21/10 03:38 [27519] - info: [database] Checking database indices.
    21/10 03:38 [27519] - info: NodeBB Ready
    21/10 03:38 [27519] - info: Enabling 'trust proxy'
    21/10 03:38 [27519] - info: NodeBB is now listening on: 0.0.0.0:4567
    
    apt-get update
    apt-get install -y curl
    apt-get install -y wget
    curl -sL https://deb.nodesource.com/setup_4.x | bash -
    apt-get install -y nodejs
    apt-get install -y build-essential
    echo 'deb http://packages.dotdeb.org jessie all' > /etc/apt/sources.list.d/dotdeb.list
    echo 'deb-src http://packages.dotdeb.org jessie all' >> /etc/apt/sources.list.d/dotdeb.list
    wget http://www.dotdeb.org/dotdeb.gpg
    apt-key add dotdeb.gpg
    apt-get update
    apt-get install -y redis-server imagemagick git build-essential
    apt-get install -y nginx
    git clone -b v1.x.x https://github.com/NodeBB/NodeBB.git /var/www/nodebb
    cd /var/www/nodebb
    npm install
    ./nodebb setup
    ./nodebb upgrade
    ./nodebb start
    
  • Hi there,

    Can you please provide the following information to help us debug?

    1. Server or client operating system (if applicable)
    2. NodeBB version and hash
      • To get the hash, run git rev-parse HEAD from the root of your NodeBB folder
        Thanks!
  • Hi @julian

    Here is my version debian version :

    Distributor ID: Debian
    Description:    Debian GNU/Linux 8.5 (jessie)
    Release:        8.5
    Codename:       jessie
    

    And git rev-parse HEAD git me this :
    301e62c3ba4ea6b78077dd2269246ea2cddf9d1d

    Thanks for your time.

  • Should be fixed in master

  • Indeed it has.

    Thanks for your help and fast support.

    Have a nice day.


Suggested Topics


  • error on new topic

    Unsolved Bug Reports
    0 Votes
    1 Posts
    1667 Views
  • 0 Votes
    3 Posts
    1122 Views
  • 0 Votes
    10 Posts
    3969 Views
  • 0 Votes
    5 Posts
    2470 Views
  • LevelDB error

    Bug Reports
    0 Votes
    3 Posts
    1149 Views