0.9 Upgrade command failed

exodo

@Kowlin Possibly... I made the mistake of using peer dependencies awhile back, and it's been nothing short of a headache. The idea in and of itself is fantastic, but the implementation was not suitable for a project like ours.

@exodo Run these:
$ npm unl lwip redisearch
lwip usage removed from NodeBB anyway so removing it will cause no harm, and when you run ./nodebb upgrade again, the proper redisearch version will be installed.

dbsearch requires a specific version of redisearch that doesn't match the version installed in NodeBB, I'm not entirely sure on the details.

solved that issue

not gettign this

./nodebb upgrade

Bringing base dependencies up to date... OK
Updating NodeBB data store schema.
7/11 15:58 [19631] - warn: You have no mongo password setup!
7/11 15:58 [19631] - info: [database] Checking database indices.
7/11 15:58 [19631] - info: Beginning database schema update
7/11 15:58 [19631] - info: [2015/02/08] Clearing reset tokens skipped
7/11 15:58 [19631] - info: [2015/02/17] renaming home.tpl to categories.tpl skipped
7/11 15:58 [19631] - info: [2015/2/23] Activating NodeBB Essential Rewards - skipped
7/11 15:58 [19631] - info: [2015/02/24] Upgrading plugins:active to sorted set skipped
7/11 15:58 [19631] - info: [2015/02/24] Upgrading privilege groups to system groups skipped
7/11 15:58 [19631] - info: [2015/02/25] Upgrading menu items to dynamic navigation system skipped
7/11 15:58 [19631] - info: [2015/05/07] Upgrading uid mappings to sorted set skipped
7/11 15:58 [19631] - info: [2015/05/08] Fixing emails skipped
7/11 15:58 [19631] - info: [2015/05/11] Updating widgets to tjs 0.2x skipped
7/11 15:58 [19631] - info: [2015/05/20] Adding username:sorted and email:sorted skipped
7/11 15:58 [19631] - info: [2015/06/02] Creating group sorted sets skipped
7/11 15:58 [19631] - info: [2015/07/03] Enabling default composer plugin skipped
7/11 15:58 [19631] - info: [2015/08/18] Creating children category sorted sets skipped
7/11 15:58 [19631] - info: [2015/09/30] Converting default Gravatar image to default User Avatar
7/11 15:58 [19631] - info: [2015/09/30] Converting default Gravatar image to default User Avatar skipped
7/11 15:58 [19631] - info: [2015/11/06] Removing gravatar

/home/lastnode/NodeBB/node_modules/mongodb/lib/utils.js:97
process.nextTick(function() { throw err; });
^
Error: Callback was already called.
at /home/lastnode/NodeBB/node_modules/async/lib/async.js:43:36
at /home/lastnode/NodeBB/node_modules/async/lib/async.js:694:17
at /home/lastnode/NodeBB/node_modules/async/lib/async.js:173:37
at /home/lastnode/NodeBB/src/database/mongo/hash.js:15:4
at handleCallback (/home/lastnode/NodeBB/node_modules/mongodb/lib/utils.js:95:12)
at /home/lastnode/NodeBB/node_modules/mongodb/lib/collection.js:659:5
at /home/lastnode/NodeBB/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:730:13
at Callbacks.emit (/home/lastnode/NodeBB/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:84:3)
at null.messageHandler (/home/lastnode/NodeBB/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:219:23)
at Socket.<anonymous> (/home/lastnode/NodeBB/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:259:22)

Error: undefined

julian

@exodo Can you pull latest v0.9.x and try upgrade again?

exodo

@julian said:

@exodo Can you pull latest v0.9.x and try upgrade again?

git pull
remote: Counting objects: 22, done.
remote: Compressing objects: 100% (12/12), done.
remote: Total 22 (delta 14), reused 18 (delta 10), pack-reused 0
Unpacking objects: 100% (22/22), done.
From https://github.com/NodeBB/NodeBB
f145356..9de8250 master -> origin/master
79c0049..05ef18f v0.9.x -> origin/v0.9.x
Updating f145356..9de8250
Fast-forward
public/language/es/language.json | 4 ++--
src/meta/settings.js | 1 +
src/socket.io/user/picture.js | 8 --------
3 files changed, 3 insertions(+), 10 deletions(-)
[root@ns347108 NodeBB]# ./nodebb upgrade

Bringing base dependencies up to date... OK
Updating NodeBB data store schema.
7/11 18:13 [1573] - warn: You have no mongo password setup!
7/11 18:13 [1573] - info: [database] Checking database indices.
7/11 18:13 [1573] - info: Beginning database schema update
7/11 18:13 [1573] - info: [2015/02/08] Clearing reset tokens skipped
7/11 18:13 [1573] - info: [2015/02/17] renaming home.tpl to categories.tpl skipped
7/11 18:13 [1573] - info: [2015/2/23] Activating NodeBB Essential Rewards - skipped
7/11 18:13 [1573] - info: [2015/02/24] Upgrading plugins:active to sorted set skipped
7/11 18:13 [1573] - info: [2015/02/24] Upgrading privilege groups to system groups skipped
7/11 18:13 [1573] - info: [2015/02/25] Upgrading menu items to dynamic navigation system skipped
7/11 18:13 [1573] - info: [2015/05/07] Upgrading uid mappings to sorted set skipped
7/11 18:13 [1573] - info: [2015/05/08] Fixing emails skipped
7/11 18:13 [1573] - info: [2015/05/11] Updating widgets to tjs 0.2x skipped
7/11 18:13 [1573] - info: [2015/05/20] Adding username:sorted and email:sorted skipped
7/11 18:13 [1573] - info: [2015/06/02] Creating group sorted sets skipped
7/11 18:13 [1573] - info: [2015/07/03] Enabling default composer plugin skipped
7/11 18:13 [1573] - info: [2015/08/18] Creating children category sorted sets skipped
7/11 18:13 [1573] - info: [2015/09/30] Converting default Gravatar image to default User Avatar skipped
7/11 18:13 [1573] - info: [2015/11/06] Removing gravatar
7/11 18:13 [1573] - info: [2015/11/06] Gravatar pictures removed!
7/11 18:13 [1573] - info: [upgrade] Schema update complete!
OK

NodeBB Upgrade Complete!

bitspook

is there a manual way to update? My dev server is still on 8.1; cannot update. Tried reloading and restarting several times...

scottalanmiller

This should do it...

git fetch; git checkout v0.9.x; git pull; npm install; ./nodebb stop; ./nodebb upgrade; ./nodebb start; ./nodebb log

pichalite

@scottalanmiller He is on 0.8.1 that won't work. I believe you have to update to latest on 0.8.x before upgrading to 0.9

@bitspook follow this guide

301 Moved Permanently

(docs.nodebb.org)

julian

@pichalite said:

I believe you have to update to latest on 0.8.x before upgrading to 0.9

Yes, this is correct (although right now all of the upgrade scripts are still there, so this is a good reminder for me to remove them, thanks!).

scottalanmiller

Ah sorry, the probably....

git fetch; git pull, npm i; ./nodebb upgrade; git checkout v0.9.x; git pull; npm install; ./nodebb stop; ./nodebb upgrade; ./nodebb start; ./nodebb log

Henry Wright

@julian said:

we could have a pre-release channel that upgrades a week before a new milestone launches, so some users can test it out and report back

I'd be happy to do this. I already run master locally, and upgrade X.X.X locally before doing anything on my production site.

How would you let us know something is ready for testing?

julian

We develop on master, so if you run master you wouldn't experience the issues we'd have as well.

Ideally it would be a site administrator who runs on stable, but when requested, will duplicate his db, and run the upgrade from, for example, v0.8.2 to v0.9.0

hukadan

@julian said:

Ideally it would be a site administrator who runs on stable, but when requested, will duplicate his db, and run the upgrade from, for example, v0.8.2 to v0.9.0

I would not mind doing that. Actually, I already do that. It is part of my upgrade process before upgrading the real forum. I am sure I am not the only one. I am late for the 0.9.0 but I would be OK to give it a try for the next release.

Phate

@scottalanmiller said:

Ah sorry, the probably....

git fetch; git pull, npm i; ./nodebb upgrade; git checkout v0.9.x; git pull; npm install; ./nodebb stop; ./nodebb upgrade; ./nodebb start; ./nodebb log

Sorry for the newb post.....

I've tried to upgrade 3 times now each time breaking my install. Is the above the way to go????

Trying to upgrade from v0.7.1-dev to v0.9.0.

Please help?

anmol gupta

Bringing base dependencies up to date... OK
Updating NodeBB data store schema.
10/11 12:39 [15868] - info: Beginning database schema update
10/11 12:39 [15868] - error: [upgrade] NodeBB upgrade could not complete, as your database schema is too far out of date.
10/11 12:39 [15868] - error: [upgrade] Please ensure that you did not skip any minor version upgrades.
10/11 12:39 [15868] - error: [upgrade] (e.g. v0.1.x directly to v0.3.x)
OK
```
                     NodeBB Upgrade Complete!
```

scottalanmiller

@Phate said:

@scottalanmiller said:

Ah sorry, the probably....

git fetch; git pull, npm i; ./nodebb upgrade; git checkout v0.9.x; git pull; npm install; ./nodebb stop; ./nodebb upgrade; ./nodebb start; ./nodebb log

Sorry for the newb post.....

I've tried to upgrade 3 times now each time breaking my install. Is the above the way to go????

Trying to upgrade from v0.7.1-dev to v0.9.0.

Please help?

You need to go through the 0.8.x series first.

scottalanmiller

git fetch; git pull, npm i; ./nodebb upgrade; git checkout v0.8.x; git pull; npm install; ./nodebb stop; ./nodebb upgrade; ./nodebb start; ./nodebb log

Make sure that things are okay then...

git fetch; git pull, npm i; ./nodebb upgrade; git checkout v0.9.x; git pull; npm install; ./nodebb stop; ./nodebb upgrade; ./nodebb start; ./nodebb log

exodo

@scottalanmiller said:

git fetch; git pull, npm i; ./nodebb upgrade; git checkout v0.8.x; git pull; npm install; ./nodebb stop; ./nodebb upgrade; ./nodebb start; ./nodebb log

Make sure that things are okay then...

git fetch; git pull, npm i; ./nodebb upgrade; git checkout v0.9.x; git pull; npm install; ./nodebb stop; ./nodebb upgrade; ./nodebb start; ./nodebb log

So easy lol

Bri

@julian said:

@Kowlin Possibly... I made the mistake of using peer dependencies awhile back, and it's been nothing short of a headache. The idea in and of itself is fantastic, but the implementation was not suitable for a project like ours.

So are we doing away with peer dependencies?

julian

Depends, why do you need them in your plugin?

Bri

No I don't need them, but curious since they're causing trouble

julian

The way npm handles peer dependencies left much to be desired, especially in a development landscape like ours where versions go up regularly and different rates compared to plugins.

Specifically, if a module A required a peer dependency B with a fairly strict version (e.g. ~0.15.0), then if that dependency got updated to v0.16.0 or above, then any future attempts to install module A would throw a peer dependency error and abort the npm installation, leaving NodeBB in a state that would not run. That's not so good for non-developers