Community

NodeBB stopped working after 'build' issued

Technical Support
  • K
    K
    #1

    Hi,

    I'm getting an 'internal server error' message when I try to access my NodeBB install...

    I checked out v1.11.x through Github. I followed this guide: https://docs.nodebb.org/installing/os/freebsd/

    My platform is FreeBSD 12.0 Release, and I have Node version 11.3 running off the Redis DB.

    What I was trying to achieve was to install the Facebook authentication plugin; it installed fine and I activated it then restarted NodeBB and then finally refreshed the browser page for the new Admin heading to come up.

    It came up fine but I couldn't access it, I just got a spinning wheel with the error: "ID text not found". After reading around I found that some people needed to issue the ./nodebb build command to get things to function. So that's what I did.

    This is the log message currently of the system:

    [code]
    at eachOfLimit (/usr/local/www/NodeBB/node_modules/async/dist/async.js:1041:24)
    at /usr/local/www/NodeBB/node_modules/async/dist/async.js:1046:16
    at eachOf (/usr/local/www/NodeBB/node_modules/async/dist/async.js:1117:5)
    at _parallel (/usr/local/www/NodeBB/node_modules/async/dist/async.js:3879:5)
    at Object.parallelLimit [as parallel] (/usr/local/www/NodeBB/node_modules/async/dist/async.js:3962:5)
    at /usr/local/www/NodeBB/src/middleware/render.js:79:12
    at nextTask (/usr/local/www/NodeBB/node_modules/async/dist/async.js:5324:14)
    at next (/usr/local/www/NodeBB/node_modules/async/dist/async.js:5331:9)
    at /usr/local/www/NodeBB/node_modules/async/dist/async.js:969:16
    at /usr/local/www/NodeBB/node_modules/async/dist/async.js:473:16
    [/code]

    If I run the full build command the output is this:

    [code]
    [benchpressjs] Unable to build or find a suitable native module, falling back to JS version
    started
    2018-12-26T23:05:21.782Z [4567/8184] - info: [build] Building in parallel mode
    2018-12-26T23:05:21.783Z [4567/8184] - info: [build] plugin static dirs build started
    2018-12-26T23:05:21.785Z [4567/8184] - info: [build] requirejs modules build started
    2018-12-26T23:05:21.786Z [4567/8184] - info: [build] client js bundle build started
    2018-12-26T23:05:21.788Z [4567/8184] - info: [build] admin js bundle build started
    2018-12-26T23:05:21.789Z [4567/8184] - info: [build] client side styles build started
    2018-12-26T23:05:21.789Z [4567/8184] - info: [build] admin control panel styles build started
    2018-12-26T23:05:21.790Z [4567/8184] - info: [build] templates build started
    2018-12-26T23:05:21.790Z [4567/8184] - info: [build] languages build started
    2018-12-26T23:05:21.793Z [4567/8184] - info: [build] sounds build started
    2018-12-26T23:05:22.358Z [4567/8184] - info: [build] sounds build completed in 0.565sec
    2018-12-26T23:05:22.541Z [4567/8184] - info: [build] plugin static dirs build completed in 0.757sec
    2018-12-26T23:05:27.750Z [4567/8184] - error: [build] admin control panel styles build failed
    2018-12-26T23:05:27.751Z [4567/8184] - error: [build] Encountered error during build step {"meta":"Inline JavaScript is not enabled. Is it set in your options?"}
    2018-12-26T23:05:27.751Z [4567/8184] - error: Inline JavaScript is not enabled. Is it set in your options?
    [email protected]:/usr/local/www/NodeBB # events.js:167
    throw er; // Unhandled 'error' event
    ^

    Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
    at process.target.send (internal/child_process.js:644:16)
    at /usr/local/www/NodeBB/src/meta/minifier.js:125:13
    at /usr/local/www/NodeBB/node_modules/async/dist/async.js:3888:9
    at /usr/local/www/NodeBB/node_modules/async/dist/async.js:473:16
    at iteratorCallback (/usr/local/www/NodeBB/node_modules/async/dist/async.js:1064:13)
    at /usr/local/www/NodeBB/node_modules/async/dist/async.js:969:16
    at /usr/local/www/NodeBB/node_modules/async/dist/async.js:3885:13
    at /usr/local/www/NodeBB/node_modules/graceful-fs/graceful-fs.js:111:16
    at /usr/local/www/NodeBB/node_modules/graceful-fs/graceful-fs.js:45:10
    at FSReqCallback.oncomplete (fs.js:148:20)
    Emitted 'error' event at:
    at process.nextTick (internal/child_process.js:648:35)
    at process.internalTickCallback (internal/process/next_tick.js:70:11)

    [/code]

    I'm not sure what happened or why it's doing this as I did perform an "npm install" after the install which seemed to be required? as there were things missing and other errors.

    I wonder if anyone could help a) get the forum back online and b) get the FB auth plugin functioning??

    Many thanks.

    0
  • PitaJP
    PitaJP
    Global Moderator Plugin & Theme Dev
    #2

    What instructions did you use to install?

    Have you tried disabling the plugin with ./nodebb reset -p <plugin>?

    0
  • K
    K
    #3

    Hi sorry for the late response!

    I used these instructions for install: https://docs.nodebb.org/installing/os/freebsd/

    Yeah I did a complete uninstall / reinstall of the plugin but no change.

    Currently the site is down so I guess I'll have to remove the directory and run another git clone 😞

    0
  • PitaJP
    PitaJP
    Global Moderator Plugin & Theme Dev
    #4

    If you reinstall a broken plugin it will continue to break your forum.

    0

Suggested Topics

  • AntosikA

    NodeBB + MongoDB + Scaling (k8s)

    Technical Support
    0 Votes
    16 Posts
    833 Views

    scottalanmillerS

    @antosik said in NodeBB + MongoDB + Scaling (k8s):

    @PitaJ
    I'm not against it ^^.
    Just want to research a bit before giving AWS more money. :d

    @baris
    So, we need to try:

    implement something like src\database\redis\pubsub.js in mongo; check out socket.io-adapter-mongo and @nodebb/mubsub packages?

    UPD. Found an interesting thing - maybe we can use watch + changeStream to implement the pubsub 🤔 ?

    What's your overall goal? I have a feeling that you are giving AWS way more money than you should already. If the goal is to go big without wasting money, this isn't the approach. Unless you are doing something in the billion hits a month range, I don't think that this approach can be cost effective at all.

    So if you want to give AWS money just for fun, then you might as well give more. If you want to be cost effective, then setting yourself up for scaling will require more scale than will ever be practically needed.

  • D

    How to call an API call from NodeBB theme?

    Unsolved Technical Support
    0 Votes
    4 Posts
    458 Views

    PitaJP

    @dogs themes are plugins, so everything you suggested can also be done in their theme.

  • K

    NodeBB not sorting by date

    Technical Support
    0 Votes
    1 Posts
    116 Views

    K

    I'm using NodeBB 1.13.2 and used the write API to upload a bunch of messages from another software into NodeBB. I needed to update the date so I modified the date of each post (using mongodb). The dates for each post are showing the correct date but when I try to sort via newest or oldest it doesn't sort by date order?
    Is there something else I can do to get it to sort the posts in a topic by order? I've already deleted the indexes in mongodb and restarted nodebb to rebuild them but that didn't fix the problem.

    Any ideas?

    Thanks,
    Kyle

  • S

    Many NodeBB forums have a message... connection... lost...

    Technical Support
    0 Votes
    3 Posts
    1086 Views

    JaredBuschJ

    @pitaj said in Many NodeBB forums have a message... connection... lost...:

    The "connection lost" message is usually caused because the URL at which you are visiting a NodeBB forum is not the "url" value set in config.json

    I can be on mangolassi.it for hours. Then I leave that tab and work in another tab for a while, and then when I click back on the tab for mangolassi.it I will be spammed with connection lost.

    @scottalanmiller

  • YaÅŸar Baturalp ArtarY

    How do I configure NodeBB setup for Google Cloud VM?

    Solved Technical Support
    0 Votes
    4 Posts
    1351 Views

    YaÅŸar Baturalp ArtarY

    @duke said in How do I configure NodeBB setup for Google Cloud VM?:

    If you cannot answer these questions yourself then I suggest you install virtualbox on your local machine and get nodebb working locally but following the docs below. Once you are successful with this, you will have learned alot and can then try and deploy on Google infrastructure.

    I know you want to deploy straight to production but my way will be quicker in the long run. The next question you will have will be regarding NGINX and how to get it running on port 80. The answers to all your questions are in the docs. The docs are very easy to follow.

    Ubuntu (Recommended) - NodeBB Documentation

    <quote>
    I can create the website by using 127.0.0.1 IP but the connection is refused by google's internal IP
    (127 is a local ip, you need to provide your internet IP here)

    "url": "I typed here my domain which is connected to Google's external IP",
    "secret": "the key",
    "database": "mongo",
    "mongo": {
    "host": "Google's internal IP", (should be 127.0.0.1)
    "port": "I couldnt find this out?", (4567)
    "username": "Is this the nodebb user or the user I created for admin database?", (nodebb user)
    "password": "Password", (mongo password for Nodebb database)
    "database": "nodebb"
    </quote>

    Done 🙂

| | | |
Copyright © 2023 NodeBB | Contributors