Why do I need to restart my NodeBB every couple of hours ?



  • I am hosted on AWS EC2 with MongoDB (DB is also hosted on the same AWS EC2) ...3 categories, 1000 topics and total 1500 posts. The NodeBB becomes unresponsive after an hou or so and I am forced to restart. Nothing in the logs !
    Running NodeBB v1.0.0.
    Any ideas ?


  • GNU/Linux

    I'll give you a cross-reference to a similar issue: https://community.nodebb.org/topic/8875/frontend-freeze-on-version-later-than-v1-0-2/28

    We still don't know what causes this thought.


  • Admin

    Quite odd... when NodeBB freezes, do you see CPU usage stuck at 100%?


  • Community Rep

    @assamese Have you by chance also checked the mongodb logs?



  • @Bri My MongoDB log is clean since it was restarted 2 weeks ago -

    2016-05-19T03:14:20.958+0000 ***** SERVER RESTARTED *****
    2016-05-19T03:14:20.961+0000 [initandlisten] MongoDB starting : pid=15115 port=27017 dbpath=/var/lib/mongo 64-bit host=ip-172-31-22-162
    2016-05-19T03:14:20.961+0000 [initandlisten] db version v2.6.12
    2016-05-19T03:14:20.961+0000 [initandlisten] git version: d73c92b1c85703828b55c2916a5dd4ad46535f6a
    2016-05-19T03:14:20.961+0000 [initandlisten] build info: Linux build5.ny.cbi.10gen.cc 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 BOOST_LIB_VERSION=1_49
    2016-05-19T03:14:20.961+0000 [initandlisten] allocator: tcmalloc
    2016-05-19T03:14:20.961+0000 [initandlisten] options: { config: "/etc/mongod.conf", net: { bindIp: "127.0.0.1" }, processManagement: { fork: true, pidFilePath: "/var/run/mongodb/mongod.pid" }, security: { authorization: "enabled" }, storage: { dbPath: "/var/lib/mongo" }, systemLog: { destination: "file", logAppend: true, path: "/var/log/mongodb/mongod.log" } }
    2016-05-19T03:14:20.963+0000 [initandlisten] journal dir=/var/lib/mongo/journal
    2016-05-19T03:14:20.963+0000 [initandlisten] recover : no journal files present, no recovery needed
    2016-05-19T03:14:21.106+0000 [initandlisten] couldn't unlink socket file /tmp/mongodb-27017.sockerrno:1 Operation not permitted skipping
    2016-05-19T03:14:21.106+0000 [initandlisten] waiting for connections on port 27017
    2016-05-19T03:14:21.644+0000 [initandlisten] connection accepted from 127.0.0.1:39024 #1 (1 connection now open)
    2016-05-19T03:15:17.193+0000 [initandlisten] connection accepted from 127.0.0.1:39025 #2 (2 connections now open)
    2016-05-19T03:15:17.193+0000 [conn2] note: no users configured in admin.system.users, allowing localhost access
    2016-05-19T03:15:21.112+0000 [clientcursormon] mem (MB) res:36 virt:444
    2016-05-19T03:15:21.112+0000 [clientcursormon] mapped (incl journal view):160
    2016-05-19T03:15:21.112+0000 [clientcursormon] connections:2
    2016-05-19T03:17:30.798+0000 [conn2] end connection 127.0.0.1:39025 (1 connection now open)
    2016-05-19T03:20:21.126+0000 [clientcursormon] mem (MB) res:37 virt:444
    2016-05-19T03:20:21.126+0000 [clientcursormon] mapped (incl journal view):160
    2016-05-19T03:20:21.126+0000 [clientcursormon] connections:1



  • @julian Not sure if the CPU usage spikes to 100%. I will keep an eye when it freezes the next time. Thanks
    SD



  • I somehow feel (Not sure !) my situation is related to the nodebb-plugin-custom-pages



  • I collected this data when my NodeBB became unresponsive (ie. could not access forum from my browser)

    vmstat output from my AWS host -
    procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu-----
    r b swpd free buff cache si so bi bo in cs us sy id wa st
    0 0 0 263132 150504 178488 0 0 1 2 0 2 0 0 100 0 0


    logs from my Chrome console -

    nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:13 nodebb-plugin-custom-pages: loaded
    http://127.0.0.1:4567/api/?_=1464717261007 Failed to load resource: net::ERR_EMPTY_RESPONSE
    nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:11 Uncaught TypeError: Cannot read property 'bodyClass' of undefined(anonymous function) @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:11e.translate @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:15(anonymous function) @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:11f @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:10t.parse @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:10o @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:11r @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:11(anonymous function) @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:11$.ajax.error @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:11u @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:1f.fireWith @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:1T @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:3i @ no


Log in to reply
 

Looks like your connection to NodeBB was lost, please wait while we try to reconnect.