Tried
./nodebb stop
gitpull
./nodebb upgrade
./nodebb start
At gitpull it throwed some errors and the whole upgrade ended up in a blank page on site as a result. Any idea what went wrong ?
@meetdilip said:
At gitpull it throwed some errors. Any idea what went wrong ?
No, you'd need to supply us with those errors. 
Check chat please ...
[email protected]:~# cd /home/nodebb
-bash: cd: /home/nodebb: No such file or directory
[email protected]:~# cd home
[email protected]:~/home# cd nodebb
[email protected]:~/home/nodebb# ./nodebb stop
Stopping NodeBB. Goodbye!
[email protected]:~/home/nodebb# git pull
remote: Counting objects: 2479, done.
remote: Compressing objects: 100% (1181/1181), done.
remote: Total 2479 (delta 1524), reused 1951 (delta 1267)
Receiving objects: 100% (2479/2479), 961.29 KiB | 447 KiB/s, done.
Resolving deltas: 100% (1524/1524), done.
From https://github.com/NodeBB/NodeBB
npm ERR! Unexpected token <
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! http://github.com/npm/npm/issues
npm ERR! Please include the following file with any support request:
npm ERR! /root/home/nodebb/npm-debug.log
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! Linux 3.2.0-4-amd64
npm ERR! argv "node" "/usr/bin/npm" "i" "nodebb-theme-vanilla" "nodebb-theme-lavender" "nodebb-widget-essentials"
npm ERR! node v0.10.29
npm ERR! npm v2.0.0
npm ERR! code EPEERINVALID
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.1.0
npm ERR! peerinvalid Peer [email protected] wants [email protected]~0.0.111
npm ERR! Please include the following file with any support request:
npm ERR! /root/home/nodebb/npm-debug.log
info: NodeBB v0.5.1 Copyright (C) 2013-2014 NodeBB Inc.
info: This program comes with ABSOLUTELY NO WARRANTY.
info: This is free software, and you are welcome to redistribute it under certain conditions.
info:
Warning: Redis server does not require a password, but a password was supplied.
info: Beginning database schema update
info: [2014/2/19] Updating MOTD to use the HTML widget - skipped
info: [2014/2/20] Adding Recent Replies, Active Users, and Moderator widgets to category sidebar - skipped
info: [2014/2/20] Adding Forum Stats Widget to the Homepage Footer - skipped
info: [2014/2/20] Updating Lavender MOTD - skipped
info: [2014/2/20] Activating NodeBB Essential Widgets - skipped
info: [2014/2/22] Added categories to sorted set - skipped
info: [2014/3/18] Migrating Markdown settings to new configuration - skipped
info: [2014/3/21] Removing gids and pruning groups - skipped
info: [2014/3/31] Re-adding copyright message into global footer widget - skipped
info: [2014/4/1] Moved home sidebar widgets into draft zone - skipped
info: [2014/4/2] Moved deprecated vanilla footer widgets into draft zone - skipped
info: [2014/5/13] Updating privilege settings - skipped
info: [2014/5/16] Removing allowGuestPosting option - skipped
info: [2014/5/16] Tags upgrade - skipped
info: [2014/6/6] Topic upgrade - skipped
info: [2014/6/17] Category post count upgrade - skipped
info: [2014/7/23] Upgrading db dependencies - skipped
info: [2014/7/24] Upgrading chats to sorted set - skipped
info: [2014/9/8] Deleting old notifications...
info: [2014/9/8] Deleted old notifications
info: [2014/9/27] Deleting tid:<tid>:read_by_uid...
info: [2014/9/27] Deleted tid:<tid>:read_by_uid
info: [upgrade] Schema already up to date!
NodeBB Dependencies up-to-date!
[email protected]:~/home/nodebb# ./nodebb start
Starting NodeBB
"./nodebb stop" to stop the NodeBB server
"./nodebb log" to view server output
module.js:340
throw err;
^
Error: Cannot find module 'logrotate-stream'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object.<anonymous> (/root/home/nodebb/loader.js:8:14)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
@meetdilip said:
npm ERR! peerinvalid Peer [email protected] wants [email protected]~0.0.111
Looks like the author of the "flip" theme needs to be contacted...
hmm. How to uinstall it then ?
@meetdilip said:
hmm. How to uinstall it then ?
npm rm nodebb-theme-flip
Edit: pinging @Tanner as I believe it's his theme. 
Auto-merging npm-shrinkwrap.json
CONFLICT (add/add): Merge conflict in npm-shrinkwrap.json
Removing NOTES.md
Automatic merge failed; fix conflicts and then commit the result.
I removed all themes, but again I get above error with
git pull origin v0.5.x
@mootzville said:
Here's an article on github's help pages that might help you.
Care give the command to be used. I am not very good at this.
@meetdilip said:
Care give the command to be used. I am not very good at this.
git stash should be fine.
I'm assuming you're wanting to go to master branch?
If so,
git checkout master (If you want stable (recommended) then git checkout v0.5.x)
git pull
./nodebb upgrade
npm up
./nodebb restart
If you get any errors about plugins wanting certain versions of vanilla or lavender, then disable or uninstall them, then run upgrade/npm up again..
FWIW, there's no 0.5.1 branch, it's either 0.5.x or master, master includes the changes that were in 0.5.1, with some other nuances that may cause instability.
Thanks @a_5mith. Will try them.
No luck. Stuck here
Auto-merging npm-shrinkwrap.json
CONFLICT (add/add): Merge conflict in npm-shrinkwrap.json
@meetdilip said:
No luck. Stuck here
Auto-merging npm-shrinkwrap.json
CONFLICT (add/add): Merge conflict in npm-shrinkwrap.json
I see this when trying to upgrade BitBangers, I dont know enough about git to bypass it myself.
This is stopping me from upgrading too.
@meetdilip What's your output of git status?
EDIT: I'm guessing what has happened is maybe you manually modified some file(s) in your folder -- which is a git folder. git pull does several things. I'm not an expert, but among them it does git fetch & git merge and I'm not sure what else. Anyway, since you modified some files and it's trying to merge it can't because the file(s) are different. So, first you have to do a git status to see what's going on. Then, from the looks of the output you've already shown you'll have to do something with the npm-shrinkwrap.json file.
You can also try git diff which might give you some more info about what's different since you've already tried to git pull
Basically, git doesn't want to merge because it doesn't know which file(s) you want to keep...the one getting pulled in or the one you've modified. It could be something as simple as an extra space somewhere, or even just a different timestamp (I think) on the file.
Disclaimer: As I've already stated, I'm not an expert with git -- still learning it myself -- so this may not be exact.
Thanks @mootzville . Only changes I made are installing a few themes and plugins. I have not made any manual edit to any of the files as far as I can remember.
git status result
new file: public/less/mixins.less
I must also thank @frissdiegurke who tried to help me in between.
Restored using snapshotp and git status gave
[email protected]:~/home/nodebb# git status
nothing added to commit but untracked files present (use "git add" to track)
[email protected]:~/home/nodebb#
@meetdilip, open npm-shrinkwrap.json with a text editor and replace its content with the contents of this file.
After you've done that do a git add npm-shrinkwrap.json, git commit -am "updated files" and git push and things should be working.
@meetdilip said:
Restored using snapshotp and git status gave [...]
That just means that the public/google-adsense.config.json isn't being tracked by git (it isn't under source control). Most likely that file was added by some NodeBB plugin.
You can either add it to the git repo using git add pulic/google-adsense.config.json and then git commit -am "added adsense config file" and git push to update the remote repository, or ignore that message.
