How to upgrade from 0.5.7 to 0.6.0 - Now there are Error of Installation.

humanmadeaccount

this is the error when running ./nodebb dev

anyone know what is this?

thanks.

<baris>

@humanmadeaccount Make sure your config.json has a valid url property.

Master-Antonio

@priapo said:

whereis python

humanmadeaccount

@baris this is my config.json

{
    "base_url": "http://example.com",
    "port": "4567",
    "secret": "secret recipe",
    "bind_address": "0.0.0.0",
    "database": "redis",
    "redis": {
        "host": "127.0.0.1",
        "port": "6379",
        "password": "some password here",
        "database": "0"
    },
    "bcrypt_rounds": 12,
    "upload_path": "/public/uploads",
    "use_port": false,
    "relative_path": ""
}

EDIT: I will try to edit the "base_url" into "url"?

priapo

@Master-Antonio so please try

mkdir ~/bin
rm  ~/bin/python  ~/bin/python-config
ln -s /usr/bin/python2.7 ~/bin/python
ln -s /usr/bin/python2.7-config ~/bin/python-config
export PATH=~/bin:$PATH
./nodebb upgrade

These commands:

create a directory called bin/ in your home directory
create a link (shortcut) for python version 2.7 inside that ~/bin/ and will name the link as python as well as links the config for python
the export will set that ~/bin/ that you created in first place in your PATH. This way, when the upgrade script runs the python command it will use the correct version (2.7) because it will use the version you linked.

PATH is a shell variable that contains various directories separated by :. The shell uses this variable to search for commands, inside the directories there listed. The nodebb upgrade scripts will then use ~/bin/python (linked to version 2.7) instead of that of your system (/usr/bin/python) which is probably linked to version 3.4, because the export changes that variable, setting ~/bin/ in first place. echo $PATH

The whereis [name] command searches in your PATH directories for the name, after you do these procedures the command whereis python should display /home/USERNAME/bin/python and /home/USERNAME/bin/python-config. And the upgrade should work...

Master-Antonio

@priapo
Forum don't work.
http://schoolandschool.it/

LOG : http://i.gyazo.com/40d667fd4c6f95d4a068e84e0f9b5ebf.png

priapo

Please post your config.json, remember to change passwords and ports before posting.

Master-Antonio

@priapo How see my config.json?

a_5mith

@Master-Antonio It's where NodeBB is installed. Do nano config.json in your NodeBB folder, to copy, highlight the text then press Enter to Copy, Then Ctrl + X to exit, then N when asked if you want to save changes.

julian

@a_5mith If you don't want to use the nano editor, you can also try using cat or less as well. (use q to exit less)

priapo

@Master-Antonio yes, as they said, it is a file inside your nodebb/ directory; so go to your nodebb directory and type

cat config.json

then copy and paste it in your text editor, remove the passwords and post here.

Or you can remove the file and run ./nodebb setup again, if you know the passwords and ports.

Netto Hikari

@priapo, @Master-Antonio is on my machine. I will change the python version for his account to 2.7.

scottalanmiller

Just tried to update and now the site won't start. Here is the error that we are getting...

	at Object.Facebook.init [as method] (/opt/kae/node_modules/nodebb-plugin-sso-facebook/library.js:29:58)
	at /opt/kae/src/plugins.js:460:13
	at /opt/kae/node_modules/async/lib/async.js:125:13
	at Array.forEach (native)
	at _each (/opt/kae/node_modules/async/lib/async.js:46:24)
	at Object.async.each (/opt/kae/node_modules/async/lib/async.js:124:9)
	at fireStaticHook (/opt/kae/src/plugins.js:450:9)
	at Object.Plugins.fireHook (/opt/kae/src/plugins.js:406:5)
	at Plugins.reloadRoutes (/opt/kae/src/plugins.js:129:11)
	at /opt/kae/node_modules/async/lib/async.js:656:23
TypeError: Cannot read property 'buildHeader' of undefined
	at Object.Facebook.init [as method] (/opt/kae/node_modules/nodebb-plugin-sso-facebook/library.js:29:58)
	at /opt/kae/src/plugins.js:460:13
	at /opt/kae/node_modules/async/lib/async.js:125:13
	at Array.forEach (native)
	at _each (/opt/kae/node_modules/async/lib/async.js:46:24)
	at Object.async.each (/opt/kae/node_modules/async/lib/async.js:124:9)
	at fireStaticHook (/opt/kae/src/plugins.js:450:9)
	at Object.Plugins.fireHook (/opt/kae/src/plugins.js:406:5)
	at Plugins.reloadRoutes (/opt/kae/src/plugins.js:129:11)
	at /opt/kae/node_modules/async/lib/async.js:656:23
31/12 02:35 [9888] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
31/12 02:35 [9888] - info: [app] Database connection closed.

net.js:1233
	throw new Error('Not running');
		  ^
Error: Not running
	at Server.close (net.js:1233:11)
	at shutdown (/opt/kae/app.js:374:36)
	at process.<anonymous> (/opt/kae/app.js:211:7)
	at process.EventEmitter.emit (events.js:95:17)
	at process._fatalException (node.js:272:26)

scottalanmiller

I tried doing a ./nodebb reset but the issue remains.

scottalanmiller

Here is my config file with the obvious stuff stripped out...

/opt/kae# cat config.json
{
	"port": "4569",
	"secret": "......",
	"database": "mongo",
	"mongo": {
		"host": "127.0.0.1",
		"port": "27017",
		"username": ".....",
		"password": ".....",
		"database": "....."
	},
	"url": "http://localhost:4569"

<baris>

@scottalanmiller You will need to install the version of the plugin that is compatible with 0.6.0.

So in this case it should be npm i [email protected]

scottalanmiller

@baris said:

npm i [email protected]

So many dependency errors. I've tried removing those modules but they keep being required.

root@iad-lnx-mangodb:/opt/kae# npm i [email protected]
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
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.0.137
npm ERR! peerinvalid Peer [email protected] wants nodebb-theme-vanilla@^0.2.0
npm ERR! peerinvalid Peer [email protected] wants nodebb-theme-vanilla@~0.0.13

npm ERR! System Linux 3.16.0-23-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "i" "[email protected]"
npm ERR! cwd /opt/kae
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.4.21
npm ERR! code EPEERINVALID
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /opt/kae/npm-debug.log
npm ERR! not ok code 0

scottalanmiller

That Vanilla error has been going on for a few versions now.

<baris>

I would just remove the themes with npm uninstall and then install the latest version of the one that you use.

Cerulean is pretty outdated can remove that permenantly.

scottalanmiller

Took out a lot of modules and it throws no more errors about them. But the same issue starting up.