Community

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

General Discussion
  • barisB

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

    H 1 Reply
    0
  • Master-AntonioM

    @priapo said:

    whereis python

    0
  • H

    @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"? 😄

    0
  • P

    @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:

    1. create a directory called bin/ in your home directory
    2. 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
    3. 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-AntonioM 1 Reply
    0
  • Master-AntonioM

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

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

    0
  • P

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

    Master-AntonioM 1 Reply
    0
  • Master-AntonioM

    @priapo How see my config.json?

    A 1 Reply
    0
  • A

    @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.

    julianJ 1 Reply
    0
  • julianJ

    @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)

    0
  • P

    @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.

    Master-AntonioM 1 Reply
    0
  • Netto HikariN

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

    0
  • scottalanmillerS

    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)
    0
  • scottalanmillerS

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

    0
  • scottalanmillerS

    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"
    barisB 1 Reply
    0
  • barisB

    @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]

    0
  • scottalanmillerS

    @baris said:

    npm i [email protected]

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

    [email protected]:/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 [email protected]>=0.0.137
npm ERR! peerinvalid Peer [email protected] wants [email protected]^0.2.0
npm ERR! peerinvalid Peer [email protected] wants [email protected]~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
    0
  • scottalanmillerS

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

    0
  • barisB

    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.

    0
  • scottalanmillerS

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

    0
  • scottalanmillerS

    Current status...

    31/12 03:53 [17048] - info: Time: Wed Dec 31 2014 03:53:53 GMT+0000 (UTC)
31/12 03:53 [17048] - info: Initializing NodeBB v0.6.0
31/12 03:53 [17048] - info: Enabling 'trust proxy'
31/12 03:53 [17048] - warn: [socket.io] Clustering detected, you are advised to configure Redis as a websocket store.
31/12 03:53 [17048] - error: TypeError: Cannot read property 'buildHeader' of undefined
	at Object.imgur.init [as method] (/opt/kae/node_modules/nodebb-plugin-imgur/index.js:24:73)
	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.imgur.init [as method] (/opt/kae/node_modules/nodebb-plugin-imgur/index.js:24:73)
	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 03:53 [17048] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
31/12 03:53 [17048] - 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)
3 restarts in 10 seconds, most likely an error on startup. Halting.
    0

Suggested Topics

  • T
    ●

    Migrating forum from phpBB 3.0.9 to nodeBB 1.14.2, without migrating accounts

    General Discussion
    0 Votes
    1 Posts
    517 Views

    T

    How do I migrate a forum from phpBB 3.0.9 to nodeBB 1.14.2?

    I've found some plugins but I'm pretty sure the version differences will cause major headaches :

    (importer wrong phpBB and nodeBB verions) : https://github.com/akhoury/nodebb-plugin-import (migration exporter ? ) : https://github.com/elelel/nodebb-plugin-import-phpbb (exporter closest version match but not quite : pbpBB 3.1 ) : https://github.com/belst/nodebb-plugin-import-phpbb

    (post migration, convert to markdown ) : https://github.com/elelel/phpbb3bbcode2markdown4nodebb

    Also I'm not quite sure of the procedure?

    Is it remote connect to the phpBB server stop the forum and install the exporter plugin then start the forum and pick up the entire forum as one database file, then stop new nodeBB forum install plugin then start the new forum and import the file?

    it's unclear from what's given.

    I also have some perhaps unusual requirements :

    I'm not interested in migrating accounts, in fact I specifically do not want to migrate accounts. the migration exists only as comfort for those who want to be able to look up the old archived threads (btw I will mark them all as read-only after migration) but effectively we are starting from scratch with new accounts.

    So I'm not interested in migrating the accounts and I'm wondering if that's an issue? do posts necessarily need to be created with an account or is creating posts made by an unattributed user name possible? (if nodeBB attributes posts from the old forum archive to a new forum joinee that's perfectly fine by me, not so if nodeBB refuses that a new joinee use that name under pretext that it's already under use. New users and content must take priority)

    will nodeBB allow this or will it require a account named "archivebot" for example to be "responsible", the "author" of all these posts. I'd prefer if I could at least preserve the author names buit if I can't that's an ok sacrifice.

    Also will nodeBB allow the original dates for the posts? or will all of them be of the date of the migration?

    TLDR: I don't know how to migrate from phpBB 3.0.9 to nodeBB 1.14.2 specifically there doesn't seem to be an upgrade path for those specific version numbers.

  • Gaurav Grv RobinsonG
    ●

    NodeBB 0.9.4 to 1.0.0 changes and how to upgrade ?

    General Discussion
    0 Votes
    4 Posts
    1956 Views

    frissdiegurkeF

    @wellenreiter Actually the new version is 1.0.0, the new branch is called v1.x.x as you mentioned. This is a big difference 😉

  • jongarrisonJ
    ●

    When Installing latest NodeBB (0.8.2) it installs an incompatible version of nodebb-plugin-emailer-mandrill

    General Discussion
    0 Votes
    1 Posts
    776 Views

    jongarrisonJ

    I just did an install of NodeBB 0.8.2 and it installed nodebb-plugin-emailer-mandrill 0.3.1 with it which is only compatible with NodeBB 0.9.^. In addition to the declared version problem I was also getting a socket.io/helpers related error on NodeBB startup until I removed the mandrill plugin.

    I worked around this problem by removing mandrill and then installing it like this:

    npm install [email protected]

    I poked around to see how nodebb installs nodebb-plugin-emailer-mandrill and it appears that this plugin is installed in a special way? It is not mentioned in the package.json requirements for nodebb.

  • PilvinenP
    ●

    Errors on ./nodebb upgrade

    Bug Reports
    0 Votes
    2 Posts
    1845 Views

    yariplusY

    https://community.nodebb.org/topic/6551/error-during-upgrade-to-latest-master
    Has temporary fix.

  • X
    ●

    error: Auth error: Error: ERR invalid password

    General Discussion
    0 Votes
    12 Posts
    5791 Views

    X

    yes I did.

    [email protected] [/etc/nginx/vhosts]# nginx -t
    nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
    nginx: configuration file /etc/nginx/nginx.conf test is successful

Copyright © 2023 NodeBB | Contributors