Wtf? Upgrade from 1.5.1 to 1.5.3 and all my plugins were uninstalled...

Michael Pfaff

Some errors in this one.

4/8 00:24:42 [3662] - error: /login
 invalid csrf token
4/8 00:25:43 [3662] - error:  Error: spawn sendmail ENOENT
    at exports._errnoException (util.js:1024:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:192:19)
    at onErrorNT (internal/child_process.js:374:16)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
4/8 00:25:44 [3662] - error:  Error: spawn sendmail ENOENT
    at exports._errnoException (util.js:1024:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:192:19)
    at onErrorNT (internal/child_process.js:374:16)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
4/8 00:26:20 [3662] - error: /login
 invalid csrf token
4/8 00:27:08 [3662] - info: [build] Building in parallel mode
4/8 00:27:08 [3662] - info: [build]         plugin static dirs  build started
4/8 00:27:08 [3662] - info: [build]          requirejs modules  build started
4/8 00:27:08 [3662] - info: [build]           client js bundle  build started
4/8 00:27:08 [3662] - info: [build]            admin js bundle  build started
4/8 00:27:09 [3662] - info: [build]         client side styles  build started
4/8 00:27:09 [3662] - info: [build] admin control panel styles  build started
4/8 00:27:09 [3662] - info: [build]                  templates  build started
4/8 00:27:09 [3662] - info: [build]                  languages  build started
4/8 00:27:09 [3662] - info: [build]                     sounds  build started
4/8 00:27:16 [3662] - info: [build]            admin js bundle  build completed in 7.234sec
4/8 00:27:16 [3662] - info: [build]           client js bundle  build completed in 7.281sec
4/8 00:27:16 [3662] - info: [build]                     sounds  build completed in 7.257sec
4/8 00:27:16 [3662] - info: [build]         plugin static dirs  build completed in 7.842sec
4/8 00:27:22 [3662] - info: [build] admin control panel styles  build completed in 13.615sec
4/8 00:27:27 [3662] - info: [build]         client side styles  build completed in 18.976sec
4/8 00:27:30 [3662] - info: [build]          requirejs modules  build completed in 21.041sec
4/8 00:27:30 [3662] - info: [build]                  templates  build completed in 21.032sec
4/8 00:27:32 [3662] - info: [build]                  languages  build completed in 23.54sec
4/8 00:27:32 [3662] - info: [build] Asset compilation successful. Completed in 23.583sec.
[cluster] Restarting...
4/8 00:27:32 [3662] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
4/8 00:27:32 [3662] - info: [app] Database connection closed.
Clustering enabled: Spinning up 1 process(es).

4/8 00:27:32 [3662] - info: [app] Web server closed to connections.
4/8 00:27:32 [3662] - info: [app] Shutdown complete.
[cluster] Child Process (3662) has exited (code: 0, signal: null)
4/8 00:27:33 [3849] - info: Initializing NodeBB v1.5.3
[deprecated] `String.prototype.rtrim` is deprecated as of NodeBB v1.5; use `utils.rtrim` instead.
4/8 00:27:35 [3849] - info: [socket.io] Restricting access to origin: https://.org:*
4/8 00:27:35 [3849] - warn: [plugins/nodebb-plugin-spam-be-gone] Hook `action:flag.create` is deprecated, please use `action:flags.create` instead.

4/8 00:27:36 [3849] - 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-markdown

4/8 00:27:36 [3849] - info: [plugins/spam-be-gone] Settings loaded
4/8 00:27:36 [3849] - info: Routes added
4/8 00:27:36 [3849] - info: NodeBB Ready
4/8 00:27:36 [3849] - info: Enabling 'trust proxy'
4/8 00:27:36 [3849] - info: NodeBB is now listening on: 0.0.0.0:4567

julian

Err, that's really weird! That definitely shouldn't happen and is not anything we've done with NodeBB.

Did you perchance upgrade Node.js at the same time? Instead of using the ACP to download and install plugins, try using npm i pluginName, does it still happen then?

Michael Pfaff

@julian said in Wtf? Upgrade from 1.5.1 to 1.5.3 and all my plugins were uninstalled...:

Did you perchance upgrade Node.js at the same time? Instead of using the ACP to download and install plugins, try using npm i pluginName, does it still happen then?

I have upgraded Node.js recently, but it was working perfect on NodeBB v1.5.1? My Node version is v8.2.1.

Michael Pfaff

@julian said in Wtf? Upgrade from 1.5.1 to 1.5.3 and all my plugins were uninstalled...:

try using npm i pluginName, does it still happen then?

Yup. That also deletes my other plugin.

I had SendGrid Emailer installed, installed Recent Cards via npm and now SendGrid is gone.

What's the best way to rollback NodeBB to 1.5.2 (or, 1.5.1 if that is acting up also?).

Michael Pfaff

Maybe this has something to do with it?

When I try to checkout v1.5.2 or v1.5.1 I get this error:

error: Your local changes to the following files would be overwritten by checkout:
        package.json
Please, commit your changes or stash them before you can switch branches.
Aborting

Michael Pfaff

@julian My plugins are still gone, but I ran ./nodebb upgrade again and now it seems to be installing the plugins correctly without deleting others.

Michael Pfaff

Er. Maybe not. Deleting plugins still. Dangit.

Michael Pfaff

Do you know what this error might be?

4/8 01:20:08 [5535] - error: /login
 invalid csrf token

Keeps reappearing and I've never noticed it before.

<baris>

nodejs 8 isn't officially supported, maybe try with 6.x

Michael Pfaff

@baris said in Wtf? Upgrade from 1.5.1 to 1.5.3 and all my plugins were uninstalled...:

nodejs 8 isn't officially supported, maybe try with 6.x

Gotcha! Let me try downgrading nodejs.

Michael Pfaff

@baris said in Wtf? Upgrade from 1.5.1 to 1.5.3 and all my plugins were uninstalled...:

nodejs 8 isn't officially supported, maybe try with 6.x

That did it. Used nvm to downgrade to v6.x and worked like a charm. Thanks so much!

pichalite

@michael-pfaff I have seen these issue when using nodejs 8. Not with NodeBB but with other app. Seems to be issues with npm on nodejs v8.

Michael Pfaff

@pichalite said in Wtf? Upgrade from 1.5.1 to 1.5.3 and all my plugins were uninstalled...:

@michael-pfaff I have seen these issue when using nodejs 8. Not with NodeBB but with other app. Seems to be issues with npm on nodejs v8.

Yup. Downgrading resolved the issue. Very much appreciate the help!

julian

Good call @baris

PitaJ

It's due to how npm@5 works.

Normando

The same as 8 with nodejs 7.10

PitaJ

npm install npm@4 -g should also fix this issue