• Home
  • Categories
  • Recent
  • Popular
  • Top
  • Tags
  • Users
  • Groups
  • Documentation
    • Home
    • Read API
    • Write API
    • Plugin Development
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
v3.5.2 Latest
Buy Hosting

Getting error during installation

Scheduled Pinned Locked Moved General Discussion
15 Posts 7 Posters 7.9k Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • julianJ Offline
    julianJ Offline
    julian GNU/Linux
    wrote on last edited by
    #6

    What Node.js version are you using?

    1 Reply Last reply
    0
  • N Offline
    N Offline
    ngsankar
    wrote on last edited by
    #7

    ngsankar@TestM:~$ node --version
    v0.12.7

    I didnt install this version specifically. As part of the installation instruction, I believe the latest stable version gets installed.

    1 Reply Last reply
    0
  • ? Offline
    ? Offline
    A Former User
    wrote on last edited by
    #8

    If I would be you I would reinstall Node and all its components:

    apt-get remove node*
    apt-get purge node*

    And maybe this as well:
    http://stackoverflow.com/questions/5650169/uninstall-node-js-using-linux-command-line

    Then check after your repos and maybe remove any additional ones related to NodeJS and run:
    apt-get update
    apt-get install nodejs nodejs-legacy npm

    Verfiy the versions by running node -v and node-gyp -v.

    1 Reply Last reply
    0
  • N Offline
    N Offline
    ngsankar
    wrote on last edited by
    #9
    1. took a snapshot of the droplet.
    2. removed node and reinstalled as suggested.
    3. Same node version and ended up same error..
    1 Reply Last reply
    0
  • N Offline
    N Offline
    ngsankar
    wrote on last edited by
    #10

    @gvimlan, @BDHarrington7 , were you able to get this resolved ?

    1 Reply Last reply
    0
  • BriB Offline
    BriB Offline
    Bri Community Rep
    wrote on last edited by
    #11

    I haven't had a chance yet.

    1 Reply Last reply
    0
  • G Offline
    G Offline
    gvimlan
    wrote on last edited by
    #12

    Same error. No changes šŸ˜ž

    1 Reply Last reply
    0
  • Marc Boisvert-DuprasM Offline
    Marc Boisvert-DuprasM Offline
    Marc Boisvert-Dupras GNU/Linux
    wrote on last edited by Marc Boisvert-Dupras
    #13

    I'm having a similar error while trying to install NodeBB with Mongo.

    Here's the full log:

    Welcome to NodeBB!
    
    This looks like a new installation, so youll have to answer a few questions about your environment before we can proceed.
    Press enter to accept the default setting (shown in brackets).
    
    8/11 20:06 [10508] - info: Now configuring mongo database:
    Configuration Saved OK
    npm WARN peerDependencies The peer dependency kerberos@~0.0 included from mongodb-core will no
    npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency 
    npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
    
    > [email protected] install /home/mboisvert/Documents/nodemongo/node_modules/mongodb/node_modules/kerberos
    > (node-gyp rebuild) || (exit 0)
    
    make: Entering directory '/home/mboisvert/Documents/nodemongo/node_modules/mongodb/node_modules/kerberos/build'
      CXX(target) Release/obj.target/kerberos/lib/kerberos.o
    In file included from ../lib/kerberos.cc:1:0:
    ../lib/kerberos.h:5:27: fatal error: gssapi/gssapi.h: No such file or directory
    compilation terminated.
    kerberos.target.mk:94: recipe for target 'Release/obj.target/kerberos/lib/kerberos.o' failed
    make: *** [Release/obj.target/kerberos/lib/kerberos.o] Error 1
    make: Leaving directory '/home/mboisvert/Documents/nodemongo/node_modules/mongodb/node_modules/kerberos/build'
    gyp ERR! build error 
    gyp ERR! stack Error: `make` failed with exit code: 2
    gyp ERR! stack     at ChildProcess.onExit (/home/mboisvert/Documents/nodemongo/node_modules/npm/node_modules/node-gyp/lib/build.js:270:23)
    gyp ERR! stack     at emitTwo (events.js:87:13)
    gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
    gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
    gyp ERR! System Linux 4.2.5-300.fc23.x86_64
    gyp ERR! command "/usr/local/bin/node" "/home/mboisvert/Documents/nodemongo/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
    gyp ERR! cwd /home/mboisvert/Documents/nodemongo/node_modules/mongodb/node_modules/kerberos
    gyp ERR! node -v v5.0.0
    gyp ERR! node-gyp -v v3.0.3
    gyp ERR! not ok 
    npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/jade requires mkdirp@'0.3.0' but will load
    npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/mkdirp,
    npm WARN unmet dependency which is version 0.5.1
    npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/grunt requires async@'~0.1.22' but will load
    npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/async,
    npm WARN unmet dependency which is version 1.4.2
    npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/grunt requires colors@'~0.6.2' but will load
    npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/colors,
    npm WARN unmet dependency which is version 1.1.2
    npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/grunt requires rimraf@'~2.2.8' but will load
    npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/rimraf,
    npm WARN unmet dependency which is version 2.4.3
    npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/grunt-legacy-util requires async@'~0.1.22' but will load
    npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/async,
    npm WARN unmet dependency which is version 1.4.2
    npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/argparse requires underscore@'~1.7.0' but will load
    npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/underscore,
    npm WARN unmet dependency which is version 1.8.3
    npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/grunt-legacy-log requires colors@'~0.6.2' but will load
    npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/colors,
    npm WARN unmet dependency which is version 1.1.2
    npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/grunt-legacy-log-utils requires colors@'~0.6.2' but will load
    npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/colors,
    npm WARN unmet dependency which is version 1.1.2
    npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/grunt-contrib-watch requires async@'~0.2.9' but will load
    npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/async,
    npm WARN unmet dependency which is version 1.4.2
    npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/mocha requires mkdirp@'0.3.5' but will load
    npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/mkdirp,
    npm WARN unmet dependency which is version 0.5.1
    [email protected] node_modules/connect-mongo
    └── [email protected]
    
    mongo[email protected] node_modules/mongodb
    ā”œā”€ā”€ [email protected]
    ā”œā”€ā”€ [email protected] ([email protected], [email protected], [email protected])
    ā”œā”€ā”€ [email protected] ([email protected])
    └── [email protected] ([email protected])
    /home/mboisvert/Documents/nodemongo/node_modules/mongodb/lib/mongo_client.js:437
                  throw err
                  ^
    
    TypeError: _.assign is not a function
        at new MongoStore (/home/mboisvert/Documents/nodemongo/node_modules/connect-mongo/lib/connect-mongo.js:114:19)
        at /home/mboisvert/Documents/nodemongo/src/database/mongo.js:111:27
        at /home/mboisvert/Documents/nodemongo/node_modules/mongodb/lib/mongo_client.js:434:15
        at doNTCallback0 (node.js:428:9)
        at process._tickCallback (node.js:357:13)
    

    Additional information:
    OS: Fedora 23
    NodeBB: 0.9.0 cee3918e9b8096e421933678178ddfe4e3b71adf
    Node: 5.0.0

    1 Reply Last reply
    0
  • V Offline
    V Offline
    vinjdw
    wrote on last edited by
    #14

    For me this was fixed by installing Kerberos. e.g. on Ubuntu:

    sudo apt-get install libkrb5-dev
    
    julianJ 1 Reply Last reply
    0
  • julianJ Offline
    julianJ Offline
    julian GNU/Linux
    replied to vinjdw on last edited by
    #15

    @vinjdw @Marc-Boisvert-Dupras Keep in mind Kerberos authentication is default off, so if the module does not compile, this does not stop MongoDB (or NodeBB) from functioning correctly.

    1 Reply Last reply
    0

Copyright Ā© 2023 NodeBB | Contributors
  • Login

  • Don't have an account? Register

  • Login or register to search.
Powered by NodeBB Contributors
  • First post
    Last post
0
  • Home
  • Categories
  • Recent
  • Popular
  • Top
  • Tags
  • Users
  • Groups
  • Documentation
    • Home
    • Read API
    • Write API
    • Plugin Development