Nodebb 9.3 - Shutting Down and restarting automatically when clicking InstallPlugin - menu on ACP

Technical Support
  • Hello,

    1. I am running on 9.3 and today, when tried to click on Plugins-->Install Plugin menu from ACP, no action was happening (like bringing in plugin list)
    2. So I was checking the log file on the server and noticed whenever I clicked Install Plugin menu from ACP, nodebb automatically shuts itself down and restarting.

    I could not understand any obvious error...some warning about couple of plugin compatibility are show in log, but that were always there for a month and it did not cause any issue so far till now.

    In the last weeks or so, I installed few plugins , but i did not realize this issue or this was never there till today

    1. Uninstalled -- nodebb-plugin-google-adsense

    2. Installed -- nodebb-plugin-adsense

    3. Installed -- nodebb-plugin-ns-likes

    4. Installed -- nodebb-widget-ns-stats

    Following is the log file output, Pls help...

    15/3 15:16 [13039] - info: NodeBB Ready
    15/3 15:16 [13039] - info: Enabling 'trust proxy'
    15/3 15:16 [13039] - info: NodeBB is now listening on: 0.0.0.0:4567
    15/3 15:18 [13039] - error: TypeError: Cannot assign to read only property 'id' of <
    at Object.Plugins.normalise (/home/ngsankar/nodebb/src/plugins.js:226:20)
    at Request._callback (/home/ngsankar/nodebb/src/plugins.js:217:12)
    at Request.self.callback (/home/ngsankar/nodebb/node_modules/request/request.js:198:22)
    at Request.emit (events.js:110:17)
    at Request.<anonymous> (/home/ngsankar/nodebb/node_modules/request/request.js:1035:10)
    at Request.emit (events.js:129:20)
    at IncomingMessage.<anonymous> (/home/ngsankar/nodebb/node_modules/request/request.js:962:12)
    at IncomingMessage.emit (events.js:129:20)
    at _stream_readable.js:908:16
    at process._tickDomainCallback (node.js:381:11)
    TypeError: Cannot assign to read only property 'id' of <
    at Object.Plugins.normalise (/home/ngsankar/nodebb/src/plugins.js:226:20)
    at Request._callback (/home/ngsankar/nodebb/src/plugins.js:217:12)
    at Request.self.callback (/home/ngsankar/nodebb/node_modules/request/request.js:198:22)
    at Request.emit (events.js:110:17)
    at Request.<anonymous> (/home/ngsankar/nodebb/node_modules/request/request.js:1035:10)
    at Request.emit (events.js:129:20)
    at IncomingMessage.<anonymous> (/home/ngsankar/nodebb/node_modules/request/request.js:962:12)
    at IncomingMessage.emit (events.js:129:20)
    at _stream_readable.js:908:16
    at process._tickDomainCallback (node.js:381:11)
    15/3 15:18 [13039] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
    15/3 15:18 [13039] - info: [app] Database connection closed.
    15/3 15:18 [13039] - info: [app] Web server closed to connections.
    15/3 15:18 [13039] - info: [app] Shutdown complete.
    15/3 15:18 [13064] - info: Time: Tue Mar 15 2016 15:18:20 GMT+0530 (IST)
    15/3 15:18 [13064] - info: Initializing NodeBB v0.9.3
    15/3 15:18 [13064] - info: [database] Checking database indices.
    15/3 15:18 [13064] - warn: [socket.io] Clustering detected, you are advised to configure Redis as a websocket store.
    15/3 15:18 [13064] - warn: [plugins/nodebb-plugin-sso-google] Hook filter:user.delete is deprecated, please use an alternative

    15/3 15:18 [13064] - warn: [plugins/load] The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run ./nodebb reset -p PLUGINNAME to disable it.

    • nodebb-plugin-telegram-notifications
    • nodebb-plugin-recent-cards

    15/3 15:18 [13064] - info: [User-Invitations] Initializing User-Invitations...
    15/3 15:18 [13064] - info: [User-Invitations] Synced settings: restrictRegistration=0, invitedUsers=[], defaultInvitations=25, inviteGroup=registered-users
    15/3 15:18 [13064] - info: NodeBB Ready
    15/3 15:18 [13064] - info: Enabling 'trust proxy'
    15/3 15:18 [13064] - info: NodeBB is now listening on: 0.0.0.0:4567

  • I just started getting this error today on 0.9.3 as well:

    15/3 07:14 [158700] - error: TypeError: Cannot assign to read only property 'id' of <
    at Object.Plugins.normalise (C:\Apps\nodebb\src\plugins.js:223:20)
    at Request._callback (C:\Apps\nodebb\src\plugins.js:214:12)
    at Request.self.callback (C:\Apps\nodebb\node_modules\request\request.js:198:22)
    at emitTwo (events.js:87:13)
    at Request.emit (events.js:172:7)
    at Request.<anonymous> (C:\Apps\nodebb\node_modules\request\request.js:1035:10)
    at emitOne (events.js:82:20)
    at Request.emit (events.js:169:7)
    at IncomingMessage.<anonymous> (C:\Apps\nodebb\node_modules\request\request.js:962:12)
    at emitNone (events.js:72:20)
    at IncomingMessage.emit (events.js:166:7)
    TypeError: Cannot assign to read only property 'id' of <
    at Object.Plugins.normalise (C:\Apps\nodebb\src\plugins.js:223:20)
    at Request._callback (C:\Apps\nodebb\src\plugins.js:214:12)
    at Request.self.callback (C:\Apps\nodebb\node_modules\request\request.js:198:22)
    at emitTwo (events.js:87:13)
    at Request.emit (events.js:172:7)
    at Request.<anonymous> (C:\Apps\nodebb\node_modules\request\request.js:1035:10)
    at emitOne (events.js:82:20)
    at Request.emit (events.js:169:7)
    at IncomingMessage.<anonymous> (C:\Apps\nodebb\node_modules\request\request.js:962:12)
    at emitNone (events.js:72:20)
    at IncomingMessage.emit (events.js:166:7)

    I haven't installed any plugins for weeks.

    Thanks,

  • Hm, thanks for the reports, guys. It looks like perhaps a change I made in nbbpm caused the response to be invalid.

    Not quite sure what it is yet, but will track it down!

  • Fixed in the package manager, your plugin lists should be working again.


Suggested Topics


  • Google Adsense on NODEBB

    Unsolved Technical Support
    0 Votes
    2 Posts
    208 Views

    In addition, I was told to "upload the ads.txt file to the root directory of the site. The root directory of the site is the directory or folder that appears after the top-level domain (example.com/ads.txt)."
    How do I get it up there?
    When I upload through the ACP it goes up to the
    example.com/assets/uploads/ads.txt path

  • 0 Votes
    2 Posts
    715 Views

    You need the uploaded files as well which are at public/uploads in the nodebb folder.

  • import smf to nodebb

    Unsolved Technical Support
    0 Votes
    4 Posts
    1k Views

    @julian well I was looking for a help right now. Already paid for server and domain. And looking for Adsense so that I can earn what I've invested right now. Thanks for contacting though but I am not looking for paid service right now.

  • 0 Votes
    5 Posts
    2k Views

    Well... If you already have NodeBB running on port 80 without nginx/Apache proxy, then you can not assign another service on the port as well. I recommend you to set up an nginx/Apache proxy for NodeBB and create virutal hosts for each service you want to run on port 80 (this way you can run multiple services/sites on port 80).

  • NodeBB - FF 38.05 hangs

    Technical Support
    0 Votes
    1 Posts
    777 Views

    I've noticed over the past week on Mangolassi.it and now here when making another report that when I am surfing around the site, or clicking a button, frequently my browser will hang for a moment (up to several seconds). Then occasionally the browser will white out and say Not Responding.