Ready check failed: NOAUTH Authentication required.

[a_5mith]

Updating to latest master and I've got a mild issue, so, when updating, I get

npm ERR! peerinvalid The package nodebb-theme-vanilla does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer [email protected] wants nodebb-theme-vanilla@~0.1.0
npm ERR! peerinvalid Peer [email protected] wants nodebb-theme-vanilla@~0.0.33

npm ERR! System Linux 3.13.0-24-generic
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "up"
npm ERR! cwd /home/a_5mith/35hz
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.14
npm ERR! code EPEERINVALID

Then if I try running Nodebb dev I get

[cluster] Child Process (20631) listening for connections.
error: Ready check failed: NOAUTH Authentication required.
Error: Ready check failed: NOAUTH Authentication required.
at RedisClient.on_info_cmd (/home/a_5mith/35hz/node_modules/socket.io/node_modules/redis/index.js:319:35)
at Command.callback (/home/a_5mith/35hz/node_modules/socket.io/node_modules/redis/index.js:367:14)
at RedisClient.return_error (/home/a_5mith/35hz/node_modules/socket.io/node_modules/redis/index.js:502:25)
at RedisReplyParser.<anonymous> (/home/a_5mith/35hz/node_modules/socket.io/node_modules/redis/index.js:262:14)
at RedisReplyParser.emit (events.js:95:17)
at RedisReplyParser.send_error (/home/a_5mith/35hz/node_modules/socket.io/node_modules/redis/lib/parser/javascript.js:266:14)
at RedisReplyParser.execute (/home/a_5mith/35hz/node_modules/socket.io/node_modules/redis/lib/parser/javascript.js:125:22)
at RedisClient.on_data (/home/a_5mith/35hz/node_modules/socket.io/node_modules/redis/index.js:478:27)
at Socket.<anonymous> (/home/a_5mith/35hz/node_modules/socket.io/node_modules/redis/index.js:79:14)
at Socket.emit (events.js:95:17)
info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
info: [app] Database connection closed.

net.js:1236
throw new Error('Not running');
      ^
Error: Not running
at Server.close (net.js:1236:11)
at shutdown (/home/a_5mith/35hz/app.js:339:36)
at process.<anonymous> (/home/a_5mith/35hz/app.js:178:7)
at process.emit (events.js:95:17)
at process._fatalException (node.js:272:26)
[cluster] Child Process (20631) has exited (code: 7)
[cluster] Spinning up another process...

That basically loops until I Ctrl + C out of the nodebb dev.

Gone back down to v0.5.x for now.

[A Former User]

I believe we ran something similar to:

rm -rf node_modules && env SUDO_UID= SUDO_USER= npm i && npm i connect-redis --save && npm i redis --save && ./nodebb start

when NPM threw up on itself earlier today on our test build.

As for your themes, it's a matter of running
npm i [email protected]
and
npm i [email protected]

In that order, and then switched until the themes install to a working version. I should mention that it wasn't until downgrading themes that several of our issues went away.

[a_5mith]

@Ted said:

I believe we ran something similar to:

rm -rf node_modules && env SUDO_UID= SUDO_USER= npm i && npm i connect-redis --save && npm i redis --save && ./nodebb start

when NPM threw up on itself earlier today on our test build.

As for your themes, it's a matter of running
npm i [email protected]
and
npm i [email protected]

In that order, and then switched until the themes install to a working version. I should mention that it wasn't until downgrading themes that several of our issues went away.

I'm not huge on that first step of deleting my node modules folder.

[A Former User]

@a_5mith - I wasn't either, but it resolved the matter.
I don't just mean that NPM threw up, it projectile vomited over every single bit.

There's probably a cleaner solution, but we needed to get up quickly.

[a_5mith]

@Ted Well I'm still running after dropping back to 0.5.0, so it's not currently life & death.