@Juxtapo

The main issue I need to fix right now is the database, I can't do anything with nodebb until the database is working properly.

But running that command will likely tell you why the application is not connecting to the DB...

The fix, once the cause is determined, will likely be easier than a fresh install

@Juxtapo, Lokk though the NodeBB logs using:

sudo ./nodebb log

@Juxtapo, is MongoDB running? That error indicates that it's not.

Determine its status by typing

sudo service mongodb status

If it's not running, start it:

sudo service mongodb start

@julian said:

Ensure that the config.json still points to the same database... if it's a blank site, then NodeBB is reading an empty database...

Before upgrading, config.json was pointing to Redis DB 0. After upgrading, it's still pointing to Redis DB 0. The configured Redis password still matches.

So not sure, how to proceed from here.

@BDHarrington7, I'm on v0.6.1-15, but I think I'll skip upgrading to 0.7.x until I can get the whole site back up.

@finid, So I made the decision to disable all the plugins, now knowing which is causing the problem.

Now I can NodeBB starts fine, I can access the site, but it's a blank site. No posts or users at all. Check the uploads folders that all is intact. Also verified that the database files (.rdb and .aof) are still in place and the same size as the original site.

Any ideas @julian

Ok, so I decide to skip 0.7 and use the last known good upgrade (0.6) until I get a response on the blocking issue.

However, when I stat NodeBB, it starts, but I get a 502 Bad Gateway error when I try to access the site. From the log, I get these:

Clustering enabled: Spinning up 1 process(es).

22/7 02:00 [2356] - info: Time: Wed Jul 22 2015 02:00:28 GMT-0400 (EDT)
22/7 02:00 [2356] - info: Initializing NodeBB v0.6.1
22/7 02:00 [2356] - error: [plugins] NodeBB encountered a problem while loading plugins WRONGTYPE Operation against a key holding the wrong kind of value

Any clues?

@julian, So upgrade to 0.6 completed successfully.

However, upgrade to 0.7 almost completed. At the tail end, it failed with this message:

21/7 23:40 [30598] - info: [2015/2/23] Activating NodeBB Essential Rewards
21/7 23:40 [30598] - info: [2015/02/24] Upgrading plugins:active to sorted set
21/7 23:40 [30598] - info: [2015/02/24] Upgrading plugins:active to sorted set done
21/7 23:40 [30598] - info: [2015/02/24] Upgrading privilege groups to system groups
21/7 23:40 [30598] - info: [2015/02/24] Upgrading privilege groups to system groups done
21/7 23:40 [30598] - info: [2015/02/25] Upgrading menu items to dynamic navigation system
21/7 23:40 [30598] - info: [2015/02/25] Upgrading menu items to dynamic navigation system done
21/7 23:40 [30598] - info: [2015/05/07] Upgrading uid mappings to sorted set
21/7 23:40 [30598] - info: [2015/05/07] Upgrading uid mappings to sorted set done
21/7 23:40 [30598] - info: [2015/05/08] Fixing emails
21/7 23:41 [30598] - error: undefined

Undefined error. Perhaps the contents of the log could shed some light:

at Array.forEach (native)
    at Function.use (/var/forum/node_modules/express/lib/router/index.js:436:13)
    at EventEmitter.<anonymous> (/var/forum/node_modules/express/lib/application.js:187:21)
    at Array.forEach (native)
    at EventEmitter.use (/var/forum/node_modules/express/lib/application.js:184:7)
    at module.exports (/var/forum/src/routes/index.js:144:6)
    at require.exec.cwd (/var/forum/src/webserver.js:63:3)
[cluster] Child Process (9241) has disconnected
[cluster] Child Process (9241) has exited (code: 8, signal: null)
[cluster] Spinning up another process...

Any clues?

@julian, I told you, man! ~@planner died of unknown causes. But he did leave behind a boat load of bitcoins in a Swiss account. So I'm shopping for a pacific island right now

To this particular matter, I'll continue where I left off later tonigh, because the server is laready life and the upgrade uses up lots of RAM.

@julian, looks like I replied to myself instead to you

Shows how long I've used this platform...