I am spinning up a new community and found the following warnings during my install. Anything I should do about these? [root@bna-com ~]# nvm install v7.2.0 ######################################################################## 100.0% Computing checksum with sha256sum Checksums matched! Now using node v7.2.0 (npm v3.10.9) Creating default alias: default -> v7.2.0 [root@bna-com ~]# cd /opt/bnacmty/ [root@bna-com bnacmty]# git clone -b v1.x.x https://github.com/NodeBB/NodeBB nodebb Cloning into 'nodebb'... remote: Counting objects: 112796, done. remote: Compressing objects: 100% (101/101), done. remote: Total 112796 (delta 38), reused 2 (delta 2), pack-reused 112693 Receiving objects: 100% (112796/112796), 34.86 MiB | 9.87 MiB/s, done. Resolving deltas: 100% (84665/84665), done. [root@bna-com bnacmty]# cd nodebb [root@bna-com nodebb]# npm install npm WARN deprecated node-uuid@1.4.7: use uuid module instead npm WARN deprecated wrench@1.5.9: wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations you were using wrench for. Thanks for all the usage over the years. npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree. nodebb@1.3.0 /opt/bnacmty/nodebb

Looks like you do not have write access to the volume your NodeBB is installed in.

NodeBB w/ MongoDB still works just fine even though the kerberos dependency doesn't build, it just means you can't connect to MongoDB servers utilising kerberos authentication. Would prefer not to have to add libkrb5-dev to the list of dependencies, so investigating alternatives...

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. [root@daermabb 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 redisearch@0.0.5 does not satisfy its siblings' peerDependencies requirements! npm ERR! peerinvalid Peer nodebb-plugin-dbsearch@0.2.18 wants redisearch@^0.0.6 npm ERR! Please include the following file with any support request: npm ERR! /opt/daerma/nodebb/npm-debug.log [root@daermabb nodebb]# ./nodebb start Starting NodeBB "./nodebb stop" to stop the NodeBB server "./nodebb log" to view server output "./nodebb restart" to restart NodeBB [root@daermabb 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

Definitely seems like cache issue with the record for express-session. try sudo npm cache clean? After that try manually clearing the cache files?

Fixed by reinstalling redis-server.

@a_5mith @Ted Now now play nice, upvotes for the both of you. @Ralkage There's no substitute for the fundamentals. Understanding javascript syntax first will help you in the long run. When I was hiring (way back when in my non-startup days), I'd see lots of devs with "jQuery experience", who couldn't code their way out of a box in plain javascript. @psychobunny and @baris would make fun of me here, because back then I suffered from the same lock-in, except it was MooTools that I was using instead of jQuery XD

@Hưng-Thành-Nguyễn Will ignore. Thank you for confirming!

@julian That's got to be it, thanks mate!