• OK trying to upgrade from 7.1-7.2 and ruing into issues again.
    I've tried a few of the things on line and rolled back my VM

    With a working copy 7.1 I stopped nodebb, I want to run this step by step since i've run though a few things before and didn't work. SO I will wait between posts to make any changes.

    git pull

    thomasfraley@nodebb:~/nodebb$ git pull
    remote: Counting objects: 568, done.
    remote: Compressing objects: 100% (147/147), done.
    remote: Total 568 (delta 388), reused 333 (delta 332), pack-reused 89
    Receiving objects: 100% (568/568), 175.84 KiB | 0 bytes/s, done.
    Resolving deltas: 100% (428/428), completed with 212 local objects.
    From https://github.com/NodeBB/NodeBB

    • 8d786a1...56b79a9 v0.7.x -> origin/v0.7.x (forced update)
      1a56267..47cc108 master -> origin/master
    • [new branch] v0.8.x -> origin/v0.8.x
    • [new tag] v0.7.2 -> v0.7.2
      Auto-merging package.json
      CONFLICT (content): Merge conflict in package.json
      Auto-merging npm-shrinkwrap.json
      CONFLICT (add/add): Merge conflict in npm-shrinkwrap.json
      Automatic merge failed; fix conflicts and then commit the result.
      thomasfraley@nodebb:~/nodebb$
  • GNU/Linux Admin

    @tfraley Any chance you modified either of those files?

    If not:

    $ git reset --hard origin/v0.7.x
    $ ./nodebb upgrade
    

  • @julian

    I've run though this before, just wanted to take it step by step.
    here is the output from that

    thomasfraley@nodebb:~/nodebb$ git reset --hard origin/v0.7.x
    HEAD is now at 56b79a9 0.7.2
    thomasfraley@nodebb:~/nodebb$ ./nodebb upgrade

    1. Bringing base dependencies up to date

    module.js:340
    throw err;
    ^
    Error: Cannot find module '/home/thomasfraley/nodebb/node_modules/npm/lib/build.js'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.defineProperty.get (/home/thomasfraley/nodebb/node_modules/npm/lib/npm.js:195:15)
    at /home/thomasfraley/nodebb/node_modules/npm/lib/install.js:1163:18
    at asyncMap (/home/thomasfraley/nodebb/node_modules/npm/node_modules/slide/lib/async-map.js:27:18)
    at andBuildResolvedTree (/home/thomasfraley/nodebb/node_modules/npm/lib/install.js:761:9)
    at /home/thomasfraley/nodebb/node_modules/npm/lib/install.js:715:9
    at asyncMap (/home/thomasfraley/nodebb/node_modules/npm/node_modules/slide/lib/async-map.js:27:18)
    thomasfraley@nodebb:~/nodebb$

  • GNU/Linux Admin

    Seems like npm didn't install the dependencies correctly.

    $ npm rebuild # if no errors...
    $ npm i
    $ ./nodebb upgrade
    
  • Plugin & Theme Dev

    @julian I got the same error when I was doing the upgrade.


  • @julian

    it did allot of rebuilding not sure if I should post it all, but at the very end it showed the following errors ( i did NOT run the other npm i or upgrade)

    make: Leaving directory `/home/thomasfraley/nodebb/node_modules/mmmagic/build'
    npm ERR! Error: ENOENT, chmod '/home/thomasfraley/nodebb/node_modules/npm/bin/npm-cli.js'
    npm ERR! If you need help, you may report this log at:
    npm ERR! http://github.com/isaacs/npm/issues
    npm ERR! or email it to:
    npm ERR! npm-@googlegroups.com

    npm ERR! System Linux 3.16.0-30-generic
    npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "rebuild"
    npm ERR! cwd /home/thomasfraley/nodebb
    npm ERR! node -v v0.10.25
    npm ERR! npm -v 1.3.10
    npm ERR! path /home/thomasfraley/nodebb/node_modules/npm/bin/npm-cli.js
    npm ERR! code ENOENT
    npm ERR! errno 34
    npm ERR!
    npm ERR! Additional logging details can be found in:
    npm ERR! /home/thomasfraley/nodebb/npm-debug.log
    npm ERR! not ok code 0
    thomasfraley@nodebb:~/nodebb$

  • GNU/Linux Admin

    eh... permissions may be messed up.

    $ cd /path/to/nodebb
    $ sudo chown -R tfraley:tfraley ./
    

  • @julian

    OK

    thomasfraley@nodebb:~/nodebb$ pwd
    /home/thomasfraley/nodebb
    thomasfraley@nodebb:~/nodebb$ sudo chown -R thomasfraley:thomasfraley ./
    [sudo] password for thomasfraley:
    thomasfraley@nodebb:~/nodebb$

    Ran npm rebuild again seems like same errors at the end

    make: Leaving directory `/home/thomasfraley/nodebb/node_modules/mmmagic/build'
    npm ERR! Error: ENOENT, chmod '/home/thomasfraley/nodebb/node_modules/npm/bin/npm-cli.js'
    npm ERR! If you need help, you may report this log at:
    npm ERR! http://github.com/isaacs/npm/issues
    npm ERR! or email it to:
    npm ERR! npm-@googlegroups.com

    npm ERR! System Linux 3.16.0-30-generic
    npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "rebuild"
    npm ERR! cwd /home/thomasfraley/nodebb
    npm ERR! node -v v0.10.25
    npm ERR! npm -v 1.3.10
    npm ERR! path /home/thomasfraley/nodebb/node_modules/npm/bin/npm-cli.js
    npm ERR! code ENOENT
    npm ERR! errno 34
    npm ERR!
    npm ERR! Additional logging details can be found in:
    npm ERR! /home/thomasfraley/nodebb/npm-debug.log
    npm ERR! not ok code 0
    thomasfraley@nodebb:~/nodebb$

  • Community Rep

    @julian was there any point between v0.7.1 and 0.7.2 where you did a force push to the repo, rewriting history, by any chance?

  • Gamers

    I've got the same error and chown did not help...


  • @julian

    Morning all, hope everyone had a good night.

    Any more thought on our next step here? Should I just roll back my server for the time being?

  • GNU/Linux Admin

    @BDHarrington7 No, although I did for v0.7.0 to v0.7.1. That persisted for about 6 hours until I rewrote the history a second time, restoring the proper tree 😄

    I do remember @tfraley being one of those who reset to the broken tree.

  • GNU/Linux Admin

    @tfraley npm i mmmagic


  • @julian

    here you go

    thomasfraley@nodebb:~/nodebb$ npm i mmagic
    npm WARN package.json nodebb-plugin-rss@0.2.15 No repository field.
    npm http GET https://registry.npmjs.org/mmagic
    npm http 404 https://registry.npmjs.org/mmagic
    npm ERR! 404 'mmagic' is not in the npm registry.
    npm ERR! 404 You should bug the author to publish it
    npm ERR! 404
    npm ERR! 404 Note that you can also install from a
    npm ERR! 404 tarball, folder, or http url, or git url.

    npm ERR! System Linux 3.16.0-30-generic
    npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "i" "mmagic"
    npm ERR! cwd /home/thomasfraley/nodebb
    npm ERR! node -v v0.10.25
    npm ERR! npm -v 1.3.10
    npm ERR! code E404
    npm ERR!
    npm ERR! Additional logging details can be found in:
    npm ERR! /home/thomasfraley/nodebb/npm-debug.log
    npm ERR! not ok code 0
    thomasfraley@nodebb:~/nodebb$

  • GNU/Linux Admin

    Three m's 😄


  • @julian

    Ok 3 m's did it,

    Get warnings at the the end

    make: Leaving directory `/home/thomasfraley/nodebb/node_modules/mmmagic/build'
    npm WARN unmet dependency /home/thomasfraley/nodebb/node_modules/npm requires request@'~2.58.0' but will load
    npm WARN unmet dependency /home/thomasfraley/nodebb/node_modules/request,
    npm WARN unmet dependency which is version 2.60.0
    npm WARN unmet dependency /home/thomasfraley/nodebb/node_modules/npm requires rimraf@'~2.4.1' but will load
    npm WARN unmet dependency /home/thomasfraley/nodebb/node_modules/rimraf,
    npm WARN unmet dependency which is version 2.3.4
    npm WARN unmet dependency /home/thomasfraley/nodebb/node_modules/uglify-js requires async@'~0.2.6' but will load
    npm WARN unmet dependency /home/thomasfraley/nodebb/node_modules/async,
    npm WARN unmet dependency which is version 0.9.2
    mmmagic@0.3.15 node_modules/mmmagic


  • Thanks for all the help, as usual Nodebb support top notch

Suggested Topics

| |