Nodebb will only start in dev mode

tomanagle

I did a fresh install of Nodebb, to 1.0.0 and I am having trouble getting the application to start.

It will run fine if I run ./nodebb dev

However, if I run ./nodebb start it will print the usual:

'Starting NodeBB
"./nodebb stop" to stop the NodeBB server
"./nodebb log" to view server output
"./nodebb restart" to restart NodeBB

If I then type ./nodebb restart, it prints:
NodeBB could not be restarted, as a running instance could not be found.

I have started the application in dev mode and disabled all the plugins.

I'm not sure what else to try?

Tom
'

frissdiegurke

@tomanagle said:

./nodebb log to view server output

that could be a great help.

tomanagle

The following is the output. I'm guessing the last line is my problem, just not sure how to fix it?

Clustering enabled: Spinning up 1 process(es).

3/3 14:40 [4137] - info: Time: Thu Mar 03 2016 14:40:11 GMT-0500 (EST)
3/3 14:40 [4137] - info: Initializing NodeBB v1.0.0
3/3 14:40 [4137] - info: [database] Checking database indices.
[outdated] nodebb-plugin-soundpack-default installed v0.1.5, package.json requires 0.1.6
3/3 14:40 [4137] - warn: One or more of NodeBB's dependent packages are out-of-date. Please run the following command to update them:
3/3 14:40 [4137] - warn: ./nodebb upgrade
[cluster] Child Process (4137) has exited (code: 0, signal: null)

pichalite

@tomanagle as mentioned in the log... run ./nodebb upgrade and then start NodeBB

tomanagle

@pichalite said:

./nodebb upgrade

I've done that several time:

./nodebb upgrade

Bringing base dependencies up to date... OK
Updating NodeBB data store schema.
3/3 15:51 [4436] - info: [database] Checking database indices.
3/3 15:51 [4436] - info: Beginning database schema update
3/3 15:51 [4436] - info: [2015/09/30] Converting default Gravatar image to default User Avatar skipped
3/3 15:51 [4436] - info: [2015/11/06] Gravatar removal skipped
3/3 15:51 [4436] - info: [2015/12/15] Chats upgrade skipped!
3/3 15:51 [4436] - info: [2015/12/23] Chats room hashes upgrade skipped!
3/3 15:51 [4436] - info: [2015/12/23] Adding theme to active plugins sorted set skipped!
3/3 15:51 [4436] - info: [2016/01/14] Creating user best post sorted sets skipped!
3/3 15:51 [4436] - info: [2016/01/20] Creating users:notvalidated skipped!
3/3 15:51 [4436] - info: [2016/01/23] Creating Global moderators group skipped!
3/3 15:51 [4436] - info: [2016/02/25] Social: Post Sharing skipped!
3/3 15:51 [4436] - info: [upgrade] Schema already up to date!
OK
```
                                                                 NodeBB Upgrade Complete!
```

root@ :/var/www/nodebb# ./nodebb start

Starting NodeBB
"./nodebb stop" to stop the NodeBB server
"./nodebb log" to view server output
"./nodebb restart" to restart NodeBB

root@ :/var/www/nodebb# ./nodebb restart
NodeBB could not be restarted, as a running instance could not be found.

pichalite

@tomanagle well for some reason the upgrade script is not installing the correct version of the plugin nodebb-plugin-soundpack-default

try running this npm i [email protected] and then start NodeBB

P.S: when NodeBB is not running, the first thing you want to check is ./nodebb log not ./nodebb restart

tomanagle

@pichalite

I removed soundpack from package.json and now its telling me that I have another plugin out of date:

3/3 16:09 [4837] - info: Time: Thu Mar 03 2016 16:09:45 GMT-0500 (EST)
3/3 16:09 [4837] - info: Initializing NodeBB v1.0.0
3/3 16:09 [4837] - info: [database] Checking database indices.
[outdated] nodebb-rewards-essentials installed v0.0.6, package.json requires ^0.
3/3 16:09 [4837] - warn: One or more of NodeBB's dependent packages are out-of-d
3/3 16:09 [4837] - warn: ./nodebb upgrade
[cluster] Child Process (4837) has exited (code: 0, signal: null)

I've tried to update it, but I get the same error.

Why does A fresh install of NodeBB come with outdated packages that wont let it run?

pichalite

@tomanagle said:

Why does A fresh install of NodeBB come with outdated packages that wont let it run?

that's a question for the devs @administrators

running ./nodebb upgrade should take care of the plugins. not sure what's going on here

what git hash are you on? run git rev-parse HEAD to get the hash

tomanagle

@pichalite said:

git rev-parse HEAD

0b35c81586d85bb916e9336daf52694f51b182c9

I just started a DigitalOcean server tonight and its a new install of everything.

I started the server in dev, uninstalled the problem plugin, ran ./nodebb upgrade and I'm getting the same problem. Even in package.json it says ''nodebb-rewards-essentials": "^0.0.8" the exact version that its saying to upgrade too.

frissdiegurke

The reason seems to be a bad npm-shrinkwrap.json (listing versions not covered by package.json) @julian

@tomanagle to get it running it's the easiest to remove the npm-shrinkwrap.json and run ./nodebb upgrade once more.

EDIT: Reported on github: gh#4310 Thanks for reporting!