Tough start-up (NodeBB+Centos 6)

xpcontact

Hi guys,
First of all, I would like to thank everyone here, nodebb (yet is something that I was dreaming about... and it is here )
I am trying to install for the first time nodebb, I installed all the required software (node.js, redis,) first of all, when I run : node app --setup, it gives me only redis as db to select, (What I should type if I want to use MongoDB?)
Anyway, I decided to adopt redis, and install using the default setup, I tried so much, and I always getting the same error... I am installing nodebb in mydomains.com/forum
Here is the log:

root@ns4004669 [/home/pushsecu/public_html/forum]# node app --setup
info: NodeBB v0.3.0 Copyright (C) 2013 DesignCreatePlay Inc.
info: This program comes with ABSOLUTELY NO WARRANTY.
info: This is free software, and you are welcome to redistribute it under certain conditions.
info:
info: NodeBB Setup Triggered via Command Line
info: Welcome to NodeBB!
info: This looks like a new installation, so you'll have to answer a few questions about your environment before we can proceed.
info: Press enter to accept the default setting (shown in brackets).
URL of this installation (http://localhost) http://pushsecurity.com/forum
Port number of your NodeBB (4567)
Use a port number to access NodeBB? (y)
Please enter a NodeBB secret (f36c1d3d-ad8e-4f71-b31d-6f75j892c2e)
IP or Hostname to bind to (199.33x.x.xx)
Which database to use (redis)
Host IP or address of your Redis instance (127.0.0.1)
Host port of your Redis instance (6379)
Password of your Redis database my_password
Which database to use (0..n) (0) //What should I put here? (I simply click enter)
info: Configuration Saved OK
info: Populating database with default configs, if not already set...
error: Auth error: Error: ERR Client sent AUTH, but no password is set
root@myserver [/home/pushsecu/public_html/forum]#

I would really appreciate any help! Thank you in advance.
(There would be so nice tutorial step-by-step how to install nodebb on Centos)

finid

@xpcontact

Did you set a password in /etc/redis/redis.conf?

If not, edit redis.conf and uncomment the line that says, requirepass under the Security section.. The password you specify there is the one you type in during installation. And be sure to restart Redis after you edit that file.

xpcontact

@planner Thank you, actually I pass that when I accepted with no password, it says now everything is fine, but still I can't see the forum running...
info: Enabling default plugins
info: Beginning database schema update
info: [2014/1/5] Upgraded categories active users
info: [2014/1/5] Re-slugify usernames (again)
info: [2014/1/7] Updated topic and user posts to sorted set
info: [2014/1/13] Set up "Registered Users" user group
info: [2014/1/19] Remove user search from Reds
info: [2014/1/23] Updating Administrators Group -- skipped
info: [2014/1/25] Updating User Gravatars to HTTPS
info: [2014/1/25] Done activating SSO plugins
info: [2014/1/30] Fixing language settings -- skipped
info: [upgrade] Schema update complete!
info: NodeBB Setup Completed. Run './nodebb start' to manually start your NodeBB server.
root@ns4004669 [/home/pushsecu/public_html/forum]# ./nodebb start
info: NodeBB v0.3.0 Copyright (C) 2013 DesignCreatePlay Inc.
info: This program comes with ABSOLUTELY NO WARRANTY.
info: This is free software, and you are welcome to redistribute it under certain conditions.
info:
info: Time: Fri Jan 31 2014 01:06:26 GMT+0200 (EET)
info: Initializing NodeBB v0.3.0, on port 4567, using redis store at 127.0.0.1:6379.
info: NodeBB instance bound to: 198.27.64.83
info: Enabling 'trust proxy'
info: No minified client-side library found
info: NodeBB Ready

finid

@xpcontact

Well, it looks like we are in the same boat, because from what I can see, you are attempting to install it in a subfolder on a site running on Apache. I think the next step would be to find a way to configure proxy pass.

Btw, I think it's a good idea to set up a Redis password, and configure Apache to deny directory-listing.

xpcontact

@planner Thank you for the advise! sure I will do that, this is just for testing, when is ready I will move it to the right domain. I will keep you posted if I figure out a solution...

xpcontact

I tried again to install in another domain /root folder, but nothing happens when I type: ./nodebb start ... this is discouraging
Here a copy of the last logs:

info: NodeBB v0.3.0 Copyright (C) 2013 DesignCreatePlay Inc.
info: This program comes with ABSOLUTELY NO WARRANTY.
info: This is free software, and you are welcome to redistribute it under certain conditions.
info:
info: Time: Fri Jan 31 2014 02:36:32 GMT+0200 (EET)
info: Initializing NodeBB v0.3.0, on port 4567, using redis store at 127.0.0.1:6379.
info: NodeBB instance bound to: 198.27.64.83
info: Enabling 'trust proxy'
warn: [init] Cache buster not set // How to fix this by the way
info: NodeBB Ready
info: No changes to client-side libraries -- skipping minification

xpcontact

okay I figured out something, thx to http://burnaftercompiling.com/nodebb/setting-up-a-nodebb-forum-for-dummies/
URL of this installation (http://localhost) **http://198.199.67.89 **
I started my site, it works via:
http://w9forum.com:4567/
The question now, how to make it "reidrect" to http://www.w9forum.com ?

Another problem; when I try to make nodebb run forever, I type:
$ npm install -g forever
$ forever start app.js
but I get these errors;

julian

@xpcontact Looks like forever didn't actually start the forum... perhaps try that command again?

You can configure nginx to proxy requests to NodeBB by following this guide: https://github.com/designcreateplay/NodeBB/wiki/Configuring-nginx-as-a-proxy-to-NodeBB

Not sure about Apache, unfortunately

xpcontact

@Julien

Thank you actually in that link there is no solution, just listing others error too. I can see there is a problem with version ( [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.24","npm":"1.3.6"}) ), my problem I do not know how to fix that: (do I need to re-install the right version?)

npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.24","npm":"1.3.6"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.24","npm":"1.3.6"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.24","npm":"1.3.6"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.24","npm":"1.3.6"})
/usr/bin/forever -> /usr/lib/node_modules/forever/bin/forever
/usr/bin/foreverd -> /usr/lib/node_modules/forever/bin/foreverd
npm WARN unmet dependency /usr/lib/node_modules/block-stream requires inherits@'~2.0.0' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /usr/lib/node_modules/fstream requires inherits@'~2.0.0' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /usr/lib/node_modules/fstream-ignore requires inherits@'2' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /usr/lib/node_modules/fstream-npm requires inherits@'2' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /usr/lib/node_modules/glob requires inherits@'2' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /usr/lib/node_modules/npmconf requires inherits@'~2.0.0' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /usr/lib/node_modules/tar requires inherits@'2' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined

xpcontact

My problem is simple:

To downgrade my Node version to node 0.8x
any easy step to do that? do I remover my current version 0.1x?
Below logs;
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.24 ","npm":"1.3.6"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.24 ","npm":"1.3.6"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.24 ","npm":"1.3.6"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0 10.24","npm":"1.3.6"})
/usr/bin/forever -> /usr/lib/node_modules/forever/bin/forever
/usr/bin/foreverd -> /usr/lib/node_modules/forever/bin/foreverd
npm WARN unmet dependency /usr/lib/node_modules/block-stream requires inherits@' ~2.0.0' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /usr/lib/node_modules/fstream requires inherits@'~2.0. 0' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /usr/lib/node_modules/fstream-ignore requires inherits @'2' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /usr/lib/node_modules/fstream-npm requires inherits@'2 ' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /usr/lib/node_modules/glob requires inherits@'2' but w ill load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /usr/lib/node_modules/npmconf requires inherits@'~2.0. 0' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /usr/lib/node_modules/tar requires inherits@'2' but wi ll load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined

Scuzz

version 0.10.x is fine, i think everyone else is on that version and is not having any problems. Have you tried install supervisor instead? That could be a simple "fix" until you can sort out the dependency issues.

I have had problems myself and it's usually because of the repositories on certain distros being out of date.

Have you tried npm update to see if that will update your npm?

xpcontact

supervisor

Thank you for your support,
Do you mean npm install neo4j-supervisor ?
I tried in vain npm update

Scuzz

A npm install -g supervisor should install the supervisor app.
Are you using root or are you using sudo to execute commands?

xpcontact

npm install -g supervisor

I am using sudo, as w9forum is one of my client domain hosted at my dedicated server.
Here is the outcome (it looks like failed?)
[email protected] [~/public_html]# sudo npm install -g supervisor
[sudo] password for w9forum:
npm http GET https://registry.npmjs.org/supervisor
npm http 304 https://registry.npmjs.org/supervisor
/usr/bin/node-supervisor -> /usr/lib/node_modules/supervisor/lib/cli-wrapper.js
/usr/bin/supervisor -> /usr/lib/node_modules/supervisor/lib/cli-wrapper.js
npm WARN unmet dependency /usr/lib/node_modules/block-stream requires inherits@'~2.0.0' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /usr/lib/node_modules/fstream requires inherits@'~2.0.0' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /usr/lib/node_modules/fstream-ignore requires inherits@'2' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /usr/lib/node_modules/fstream-npm requires inherits@'2' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /usr/lib/node_modules/glob requires inherits@'2' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /usr/lib/node_modules/npmconf requires inherits@'~2.0.0' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /usr/lib/node_modules/tar requires inherits@'2' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
[email protected] /usr/lib/node_modules/supervisor

julian

npm WARN unmet dependency undefined,

Hm... what version of node is running?

xpcontact

Node v0.10