Community

Upgrade from 1.8.1 to 1.8.2 failed

Technical Support
  • TLINDENT
    TLINDENT
    #1

    I wanted to upgrade to 1.8.2 today but ./nodebb upgrade failed with:

    [..]
74034 verbose stack Error: [email protected] install: `node-gyp rebuild`
74034 verbose stack Exit status 1
74034 verbose stack     at EventEmitter.<anonymous> (/package/host/localhost/nodejs-6.13.1/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
74034 verbose stack     at emitTwo (events.js:106:13)
74034 verbose stack     at EventEmitter.emit (events.js:191:7)
74034 verbose stack     at ChildProcess.<anonymous> (/package/host/localhost/nodejs-6.13.1/lib/node_modules/npm/lib/utils/spawn.js:40:14)
74034 verbose stack     at emitTwo (events.js:106:13)
74034 verbose stack     at ChildProcess.emit (events.js:191:7)
74034 verbose stack     at maybeClose (internal/child_process.js:920:16)
74034 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5)
74035 verbose pkgid [email protected]
74036 verbose cwd /home/curv/nodebb
74037 error Linux 2.6.32-696.18.7.el6.x86_64
74038 error argv "/package/host/localhost/nodejs-6.13.1/bin/node" "/package/host/localhost/nodejs-6/bin/npm" "i" "--production"
74039 error node v6.13.1
74040 error npm  v3.10.10
74041 error code ELIFECYCLE
74042 error [email protected] install: `node-gyp rebuild`
74042 error Exit status 1
74043 error Failed at the [email protected] install script 'node-gyp rebuild'.
74043 error Make sure you have the latest version of node.js and npm installed.
74043 error If you do, this is most likely a problem with the heapdump package,
74043 error not with npm itself.
74043 error Tell the author that this fails on your system:
74043 error     node-gyp rebuild
74043 error You can get information on how to open an issue for this project with:
74043 error     npm bugs heapdump
74043 error Or if that isn't available, you can get their info via:
74043 error     npm owner ls heapdump
74043 error There is likely additional logging output above.
74044 verbose exit [ 1, true ]

    Now what? (and, how do I downgrade?)

    PitaJP 1 Reply
    0
  • TLINDENT
    TLINDENT
    #2

    It also fails with node 8:

    1005 verbose stack Error: [email protected] install: `node-gyp rebuild`
1005 verbose stack Exit status 1
1005 verbose stack     at EventEmitter.<anonymous> (/package/host/localhost/nodejs-8.10.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:285:16)
1005 verbose stack     at emitTwo (events.js:126:13)
1005 verbose stack     at EventEmitter.emit (events.js:214:7)
1005 verbose stack     at ChildProcess.<anonymous> (/package/host/localhost/nodejs-8.10.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
1005 verbose stack     at emitTwo (events.js:126:13)
1005 verbose stack     at ChildProcess.emit (events.js:214:7)
1005 verbose stack     at maybeClose (internal/child_process.js:925:16)
1005 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
1006 verbose pkgid [email protected]
1007 verbose cwd /home/curv/nodebb
1008 verbose Linux 2.6.32-696.18.7.el6.x86_64
1009 verbose argv "/package/host/localhost/nodejs-8.10.0/bin/node" "/package/host/localhost/nodejs-8/bin/npm" "i" "--production"
1010 verbose node v8.10.0
1011 verbose npm  v5.6.0
1012 error code ELIFECYCLE
1013 error errno 1
1014 error [email protected] install: `node-gyp rebuild`
1014 error Exit status 1
1015 error Failed at the [email protected] install script.
1015 error This is probably not a problem with npm. There is likely additional logging output above.
1016 verbose exit [ 1, true ]
    0
  • TLINDENT
    TLINDENT
    #3

    Here's the whole output with all the gory details.

    0
  • TLINDENT
    TLINDENT
    #4

    I also tried:

    rm -rf node_modules
npm cache clear
npm i

    with the same results and any nodejs version: it fails to build heapdump.

    So, I'm offline now, any help is very appreciated!

    Tom

    barisB 1 Reply
    0
  • S
    S
    #5

    How can I install the script?

    TLINDENT 1 Reply
    0
  • TLINDENT
    TLINDENT
    #6

    @serdo said in Upgrade from 1.8.1 to 1.8.2 failed:

    How can I install the script?

    pls open your own thread, thx.

    0
  • barisB
    barisB
    NodeBB
    #7

    @tlinden try this npm r heapdump then then npm i again. Also make sure heapdump isn't in package.json. Also keep in mind if you use [email protected] it can remove plugins in node_modules folder if they are not saved in package.json.

    0
  • TLINDENT
    TLINDENT
    #8

    I'm not sure if I agree with npm's idea of package management:

    % npm r heapdump
npm ERR! Linux 2.6.32-696.18.7.el6.x86_64
npm ERR! argv "/package/host/localhost/nodejs-6.13.1/bin/node" "/package/host/localhost/nodejs-6/bin/npm" "r" "heapdump"
npm ERR! node v6.13.1
npm ERR! npm  v3.10.10
npm ERR! path /home/curv/tmp/nodebb/node_modules/nodebb-plugin-write-api
npm ERR! code EISGIT

npm ERR! git /home/curv/tmp/nodebb/node_modules/nodebb-plugin-write-api: Appears to be a git repo or submodule.
npm ERR! git     /home/curv/tmp/nodebb/node_modules/nodebb-plugin-write-api
npm ERR! git Refusing to remove it. Update manually,
npm ERR! git or move it out of the way first.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/curv/tmp/nodebb/npm-debug.log

    WTF?

    However, since this is a test folder anyway, I just removed the plugin, did the npm r heapdump && npm cache clean, removed "heapdump" from package.json, checked if it is referenced in any other module (it is not), checked if the directory node_modules/heapdump doesn't exist anymore (it didn't) and executed npm i afterwards.

    It seems that it updated all the required modules, it displayed the long final tree. But in the end, there were still compiling errors and it finishes with:

    npm ERR! Linux 2.6.32-696.18.7.el6.x86_64
npm ERR! argv "/package/host/localhost/nodejs-6.13.1/bin/node" "/package/host/localhost/nodejs-6/bin/npm" "i"
npm ERR! node v6.13.1
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE

npm ERR! [email protected] install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the heapdump package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs heapdump
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls heapdump
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/curv/tmp/nodebb/npm-debug.log

    Compiler errors are the same, I'm not going to post them again.

    0
  • TLINDENT
    TLINDENT
    #9

    Oh, I just found the module: /home/curv/.npm/heapdump/0.3.7 it's installed within my home directory as well!

    I removed it and repeated the above procedure to no avail 😞

    Next, I looked where heapdump is being referenced and found npm-shrinkwrap.json from where I removed it as well.

    Repeat the procedure. No more "heapdump" errors, but still no success and lots of compiler errors, here's the end of it:

    [..]
../node_modules/nan/nan.h:1598: error: no matching function for call to ‘NanAssignPersistent(v8::Persistent<v8::Object, v8::NonCopyablePersistentTraits<v8::Object> >&, v8::Local<v8::Object>&)’
../node_modules/nan/nan.h: In member function ‘virtual void NanAsyncWorker::HandleOKCallback()’:
../node_modules/nan/nan.h:1648: error: ‘class NanCallback’ has no member named ‘Call’
../node_modules/nan/nan.h: In member function ‘virtual void NanAsyncWorker::HandleErrorCallback()’:
../node_modules/nan/nan.h:1657: error: ‘class NanCallback’ has no member named ‘Call’
../node_modules/nan/nan.h: At global scope:
../node_modules/nan/nan.h:1957: error: ‘Handle’ is not a member of ‘v8’
../node_modules/nan/nan.h:1957: error: expected primary-expression before ‘>’ token
../node_modules/nan/nan.h:1957: error: ‘val’ was not declared in this scope
../node_modules/nan/nan.h:1958: error: expected primary-expression before ‘const’
../node_modules/nan/nan.h:1959: error: expected primary-expression before ‘*’ token
../node_modules/nan/nan.h:1959: error: ‘len’ was not declared in this scope
../node_modules/nan/nan.h:1960: error: initializer expression list treated as compound expression
../node_modules/nan/nan.h:1960: error: expected ‘,’ or ‘;’ before ‘{’ token
../node_modules/nan/nan.h:1957: warning: ‘_NanGetExternalParts’ defined but not used
make: *** [Release/obj.target/validation/src/validation.o] Error 1
make: Leaving directory `/home/curv/tmp/nodebb/node_modules/socket.io/node_modules/engine.io/node_modules/ws/node_modules/utf-8-validate/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/package/host/localhost/nodejs-6.13.1/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)
gyp ERR! System Linux 2.6.32-696.18.7.el6.x86_64
gyp ERR! command "/package/host/localhost/nodejs-6.13.1/bin/node" "/package/host/localhost/nodejs-6.13.1/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/curv/tmp/nodebb/node_modules/socket.io/node_modules/engine.io/node_modules/ws/node_modules/utf-8-validate
gyp ERR! node -v v6.13.1
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok 
[email protected] node_modules/console-control-strings -> node_modules/npm/node_modules/npm-registry-client/node_modules/npmlog/node_modules/console-control-strings
[email protected] node_modules/gauge -> node_modules/npm/node_modules/npm-registry-client/node_modules/npmlog/node_modules/gauge
[email protected] node_modules/set-blocking -> node_modules/npm/node_modules/npm-registry-client/node_modules/npmlog/node_modules/set-blocking
[email protected] node_modules/readable-stream -> node_modules/npm/node_modules/npm-registry-client/node_modules/readable-stream
[email protected] node_modules/are-we-there-yet -> node_modules/npm/node_modules/npm-registry-client/node_modules/npmlog/node_modules/are-we-there-yet
[email protected] /home/curv/tmp/nodebb
└─┬ [email protected]
  └─┬ [email protected]
    └─┬ [email protected]
      └─┬ [email protected]
        └─┬ [email protected]
          └── [email protected] 

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/node_modules/bufferutil):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/node_modules/utf-8-validate):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/socket.io/node_modules/engine.io/node_modules/ws/node_modules/bufferutil):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/socket.io/node_modules/engine.io/node_modules/ws/node_modules/utf-8-validate):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

    Now what?

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

    Have you tried deleting the shrinkwrap file and the package lock file?

    0
  • TLINDENT
    TLINDENT
    #11

    different errors:

    [..]
../../nan/nan.h:1550: error: ISO C++ forbids declaration of ‘Handle’ with no type
../../nan/nan.h:1550: error: invalid use of ‘::’
../../nan/nan.h:1550: error: expected ‘;’ before ‘<’ token
../../nan/nan.h:1588: error: expected ‘;’ before ‘}’ token
../../nan/nan.h: In constructor ‘NanCallback::NanCallback()’:
../../nan/nan.h:1481: error: no matching function for call to ‘NanAssignPersistent(v8::Persistent<v8::Object, v8::NonCopyablePersistentTraits<v8::Object> >&, v8::Local<v8::Object>&)’
../../nan/nan.h: In constructor ‘NanAsyncWorker::NanAsyncWorker(NanCallback*)’:
../../nan/nan.h:1598: error: no matching function for call to ‘NanAssignPersistent(v8::Persistent<v8::Object, v8::NonCopyablePersistentTraits<v8::Object> >&, v8::Local<v8::Object>&)’
../../nan/nan.h: In member function ‘virtual void NanAsyncWorker::HandleOKCallback()’:
../../nan/nan.h:1648: error: ‘class NanCallback’ has no member named ‘Call’
../../nan/nan.h: In member function ‘virtual void NanAsyncWorker::HandleErrorCallback()’:
../../nan/nan.h:1657: error: ‘class NanCallback’ has no member named ‘Call’
../../nan/nan.h: At global scope:
../../nan/nan.h:1957: error: ‘Handle’ is not a member of ‘v8’
../../nan/nan.h:1957: error: expected primary-expression before ‘>’ token
../../nan/nan.h:1957: error: ‘val’ was not declared in this scope
../../nan/nan.h:1958: error: expected primary-expression before ‘const’
../../nan/nan.h:1959: error: expected primary-expression before ‘*’ token
../../nan/nan.h:1959: error: ‘len’ was not declared in this scope
../../nan/nan.h:1960: error: initializer expression list treated as compound expression
../../nan/nan.h:1960: error: expected ‘,’ or ‘;’ before ‘{’ token
../../nan/nan.h:1957: warning: ‘_NanGetExternalParts’ defined but not used
make: *** [Release/obj.target/validation/src/validation.o] Error 1
make: Leaving directory `/home/curv/tmp/nodebb/node_modules/utf-8-validate/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/package/host/localhost/nodejs-6.13.1/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)
gyp ERR! System Linux 2.6.32-696.18.7.el6.x86_64
gyp ERR! command "/package/host/localhost/nodejs-6.13.1/bin/node" "/package/host/localhost/nodejs-6.13.1/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/curv/tmp/nodebb/node_modules/utf-8-validate
gyp ERR! node -v v6.13.1
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok 
[email protected] /home/curv/tmp/nodebb
└─┬ [email protected]
  └── [email protected]  (git://github.com/wzrdtales/simple-recaptcha.git#f408725106872df696436ff6a988923539ab80a6)

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/bufferutil):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/utf-8-validate):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
    0
  • PitaJP
    PitaJP
    Global Moderator Plugin & Theme Dev
    #12

    @tlinden I have no idea why you're getting errors like that. But if you're going to paste errors, make you you provide the whole output, not just some of it.

    0
  • TLINDENT
    TLINDENT
    #13

    well, its many dozen pages of output everytime.

    So, here's the whole output.

    0
  • julianJ
    julianJ
    GNU/Linux
    #14

    Oh boy... what a error 😬

    If you are seeing weird npm errors, remember to delete npm-shrinkwrap.json, package-lock.json, as well as clearing cache and such.

    Double-check your package.json to make sure it doesn't require node-gyp or heapdump, we shouldn't require those.

    Honestly if all else fails... install yarn, set package_manager in config.json to yarn, and then yarn...

    TLINDENT 1 Reply
    0
  • TLINDENT
    TLINDENT
    #15

    If you are seeing weird npm errors, remember to delete npm-shrinkwrap.json, package-lock.json, as well as clearing cache and such.

    I did.

    Double-check your package.json to make sure it doesn't require node-gyp or heapdump, we shouldn't require those.

    Doesn't.

    Honestly if all else fails... install yarn, set package_manager in config.json to yarn, and then yarn...

    I don't understand. Especially, since before 1.8.2 I had no problem upgrading, I started at 1.7.5 and did it twice successfully.

    It's a desaster 😞

    0
  • julianJ
    julianJ
    GNU/Linux
    #16

    Yarn is a different package manager. npm is... a disaster, as you say, sometimes. Configs and caches littered all over the file system that you have no idea what to do to get it working again.

    That's why I say use yarn.

    0
  • TLINDENT
    TLINDENT
    #17

    Yes, but how?

    0
  • julianJ
    julianJ
    GNU/Linux
    #18

    Install documentation: yarnpkg.com/en/docs/install

    0
  • TLINDENT
    TLINDENT
    #19

    Nope.

    What's interesting though is that it tries to upgrade /package/host/localhost/nodejs-6.13.1/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js which is a global package.

    0
  • julianJ
    julianJ
    GNU/Linux
    #20

    Eh... paste your package.json please. Pretty sure you can remove lwip from there. That's not been required for quite awhile.

    0

Suggested Topics

  • M

    Vimeo Embed Code Issue with v1.17.2 and Redactor

    Unsolved Technical Support
    1 Votes
    1 Posts
    100 Views

    M

    On our version of NodeBB (v1.17.2) which uses the Redactor plugin for text entry, clicking the Redactor's Video button to embed a video, the dialog that opens suggests:

    Video Embed Code or YouTube/Vimeo Link

    But if you actually enter the embed code from Vimeo, it messes up the post to the point where the user can no longer edit it.

    On the other hand, a YouTube or Vimeo link by itself works fine.

    I know Redactor is no longer supported, but do you have any idea how we could fix this issue?

    Best Wishes,
    Mark

  • F

    DB Index Issue After Upgrading 1.6.0 *IMPORTAT*

    Technical Support
    0 Votes
    7 Posts
    1138 Views

    F

    It looks to have fixed after a freshly re run of mongorestore.

    Thanks for the support!!

  • JaredBuschJ

    Peer Dependency with redisearch and 0.9.1 (current master actually)

    Technical Support
    0 Votes
    1 Posts
    1108 Views

    JaredBuschJ

    I run my game forum on the current master, well, just because there is not a lot there and it can be broke if I have to.

    I updated git just now and ran ./nodebb upgrade and received the following. Everything is currently working, just wanted to report the warning.

    [[email protected] nodebb]# ./nodebb upgrade 1. Bringing base dependencies up to date... Error: Command failed: /usr/bin/env npm i --production npm ERR! Linux 3.10.0-229.20.1.el7.x86_64 npm ERR! argv "/root/.nvm/v0.12.9/bin/node" "/root/.nvm/v0.12.9/bin/npm" "i" "--production" npm ERR! node v0.12.9 npm ERR! npm v2.14.9 npm ERR! code EPEERINVALID npm ERR! peerinvalid The package [email protected] does not satisfy its siblings' peerDependencies requirements! npm ERR! peerinvalid Peer [email protected] wants [email protected]^0.0.6 npm ERR! Please include the following file with any support request: npm ERR! /opt/daerma/nodebb/npm-debug.log [[email protected] nodebb]# ./nodebb start Starting NodeBB "./nodebb stop" to stop the NodeBB server "./nodebb log" to view server output "./nodebb restart" to restart NodeBB [[email protected] nodebb]# ./nodebb log Type Ctrl-C to exit Clustering enabled: Spinning up 1 process(es). 7/12 09:16 [2915] - info: Time: Mon Dec 07 2015 09:16:57 GMT-0600 (CST) 7/12 09:16 [2915] - info: Initializing NodeBB v0.9.1 7/12 09:16 [2915] - 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-dbsearch * nodebb-plugin-assign-newuser-to-group info: Imgbed: regex recalculated: (?<paren>[\(]\s*)?(?<url>https?://[^\s]+\.(jpg|jpeg|gif|gifv|png|svg)) 7/12 09:17 [2915] - info: NodeBB Ready 7/12 09:17 [2915] - info: Enabling 'trust proxy' 7/12 09:17 [2915] - info: NodeBB is now listening on: 0.0.0.0:4567
  • N

    NodeBB could not connect to your Mongo database. Mongo returned the following error: Authentication failed.

    Technical Support
    0 Votes
    2 Posts
    2609 Views

    scottalanmillerS

    Try connecting manually. Use the mongo client and see what that does using the creds that you are attempting to use.

  • P

    Error during upgrade to latest master

    Technical Support
    0 Votes
    5 Posts
    2312 Views

    julianJ

    Not sure what depended on redisearch besides dbsearch, but I also just ran npm unl redisearch and ./nodebb upgrade then worked.

| | | |
Copyright © 2023 NodeBB | Contributors