Skip to content

Installing on FreeBSD, error

Technical Support
  • I am getting the following when trying to run nodebb setup:

    5/9 18:51 [77800] - info: NodeBB Setup Triggered via Command Line
    
    Welcome to NodeBB!
    
    This looks like a new installation, so you'll have to answer a few questions about your environment before we can proceed.
    Press enter to accept the default setting (shown in brackets).
    URL used to access this NodeBB (http://localhost:4567) 
    Please enter a NodeBB secret (f424bbc1-94e5-43a9-9fc0-0d482d9f445b) 
    Which database to use (redis) 
    
    5/9 18:51 [77800] - info: Now configuring redis database:
    Host IP or address of your Redis instance (127.0.0.1) 
    Host port of your Redis instance (6379) 
    Password of your Redis database 
    Which database to use (0..n) (0) 
    Configuration Saved OK
    redis@0.10.3 node_modules/redis
    
    connect-redis@2.0.0 node_modules/connect-redis
    └── debug@2.2.0 (ms@0.7.1)
    Populating database with default configs, if not already set...
    module.js:355
      Module._extensions[extension](this, filename);
                                   ^
    Error: /usr/local/lib/gcc48/libstdc++.so.6: version GLIBCXX_3.4.21 required by /usr/local/www/node/nodebb/node_modules/lwip/build/Release/lwip_image.node not found
        at Error (native)
        at Module.load (module.js:355:32)
        at Function.Module._load (module.js:310:12)
        at Module.require (module.js:365:17)
        at require (module.js:384:17)
        at /usr/local/www/node/nodebb/node_modules/lwip/lib/Image.js:3:22
        at Object.<anonymous> (/usr/local/www/node/nodebb/node_modules/lwip/lib/Image.js:15:3)
        at Module._compile (module.js:460:26)
        at Object.Module._extensions..js (module.js:478:10)
        at Module.load (module.js:355:32)
    

    Any ideas of what it could be?

  • Got it. Installed gcc5 and that solved the problem.

  • @Fastidious did you follow the official docs? If so, a pull request to add that extra step is greatly appreciated. Just hit the edit button on the top right 🙂

    EDIT: oops, I guess we don't even have a FreeBSD section in our docs. What OS did you use as your guide? Could add a new page copied and pasted from the original and adding your last step.

  • @psychobunny I simply installed node withpkg (did not use ports), cloned NodeBB and did the regular routine (npm install, nodebb setup, etc.). It was crashing on setup because I had gcc48. Installed gcc49, no dice. Finally installed gcc5 and updated libmap.conf under /etc/ as follows:

    libstdc++.so.6  gcc5/libstdc++.so.6
    

    And the beast took a deep breath, and opened its eyes. Hehe.

  • @psychobunny said:

    Could add a new page copied and pasted from the original and adding your last step.

    I can come up with a page. It should be fairly straight forward, but I already had many things installed on that VPS, so I am not sure if whatever requirements were needed I already had them.

  • You seem to know a lot more about this than any of our core team. Myself especially 😉

    If you could add a freebsd section to the docs then kudos to you, likely somebody else will run into the problem you had and I'd have no idea how to respond 😛

  • @psychobunny said:

    If you could add a freebsd section to the docs then kudos to you

    Done. Pull request pending.

  • Thanks! 🙂 the PR is missing a link from the OS page to your new page though

  • Which JS engine do you use, v8? Maybe it's related to that.

    I'm using FreeBSD too (now with mongodb), and I didn't have to install gcc5 or do any /etc changes to use NodeBB with redis.

  • @rfc2822 if you have a newer gcc installed, there is no reason to install or perform the changes I had to do. My server is not "vanilla" FreeBSD, it is "tinkering-a-lot" FreeBSD.

  • You wrote "It was crashing on setup because I had gcc48". I only have gcc-4.8.5 installed, too (I highly prefer Clang, so I'm not picky about having the latest gcc version).

  • @rfc2822 4.8.5 is fine, 4.8 is not. Do this:

    strings /usr/local/lib/gcc48/libstdc++.so.6 |grep GLIBCXX_3.4.21
    

    If you see it, you are fine.

  • Ok,. I have just thought every gcc48 version would crash for you. – So everything is OK 🙂

    Really love NodeBB & FreeBSD 🙂


Suggested Topics


  • ubuntu installed MongoDB error

    Solved Technical Support
    12
    +0
    0 Votes
    12 Posts
    976 Views
    ye8Y
    @phenomlab I reinstalled and deleted it. I think it installed successfully this time. [image: 1679155638768-c8b7132a-5581-4a46-afb3-f6b5524dacd0-image.png]
  • How do I fix Nodebb installation errors

    Technical Support
    9
    0 Votes
    9 Posts
    1k Views
    S
    Oh, even better. Here it is all updated for NodeBB 1.14 and NodeJS updated as well. https://mangolassi.it/topic/22011/deploying-nodebb-1-14-on-centos-8-with-mongodb-4-2
  • New Install Login Error

    Technical Support
    2
    0 Votes
    2 Posts
    623 Views
    PitaJP
    What's the url value in config.json?
  • Fresh install got view 500 error

    Technical Support
    5
    0 Votes
    5 Posts
    2k Views
    PJ LegendreP
    I just ran into this after changing my theme and clicking rebuild and restart... any idea how I get out of this state? Update: After running npm install and ./nodebb build the error changed to: Error: ENOENT: no such file or directory, open '/home/snarlynarwhal/nodebb/build/public/templates/footer.tpl' at Error (native) Update/Solution: Running npm install nodebb-theme-<theme-you-want> then ./nodebb build then sudo systemctl restart nodebb fixed the issue.
  • Error After Install

    Solved Technical Support
    15
    1 Votes
    15 Posts
    6k Views
    dmD
    I had the same problem when I was playing with NodeBB on a $2.5 vps from Vultr (=512MB ram). htop shows me that build process uses all available ram and cpu. Deploying on a decent machine/vps would solve the problem, aternatively, I called build steps one at a time ( eg ./nodebb build languages , ./nodebb build 'client side styles' etc) . Hope this helps.

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