These are warning messages meant for developers. You can safely ignore them. We try to minimize the amount of warnings shown due to these deprecations. Odds are they are just old requests from browser caches, or some other external cause.
Updating Nodebb from a very out of date install
Arc last edited by
Hey! I'm a total moron, please help me before I break my monitor in half.
I also have a install I've been running at NodeBB v0.7.1. Yup, there's two of us who fell way behind. Wont make that mistake again.
Its time to upgrade, and- ...
So, I followed this guide, to the letter.
Went from 0.7.1 to 0.7.x with
No errors, log: http://pastebin.com/i8V155rz
git reset --hard origin/v0.7.x
Log: HEAD is now at 6856a5e Merge pull request #3657 from davidvuong/v0.7.x
Seems- Okay? Maybe?
Only one error so far, I think. Lets see if I can start it.
For the full license, please visit: http://www.gnu.org/copyleft/gpl.html
Clustering enabled: Spinning up 1 process(es).
15/1 17:47  - info: Time: Fri Jan 15 2016 17:47:55 GMT-0500 (EST)
15/1 17:47  - info: Initializing NodeBB v0.7.3
[outdated] nodebb-theme-vanilla v5.0.29, requires 3.0.7
15/1 17:47  - warn: One or more of NodeBB's dependent packages are out-of-date. Please run the following command to update them:
15/1 17:47  - warn: ./nodebb upgrade
[cluster] Child Process (5142) has exited (code: 0, signal: null)
... Okay, so that's not great. Lets try
Error. Crap. Log: http://pastebin.com/traYpg4H
Well, lets try upgrade, then start again?
npm ERR! not ok code 0
... This can't be good. ...
at Function.Module._load (module.js:280:25) at Module.require (module.js:364:17) at require (module.js:380:17) at Object.<anonymous> (/home/janitor/nodebb/src/file.js:7:12) 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 Module.require (module.js:364:17) 3 restarts in 10 seconds, most likely an error on startup. Halting.
I'd be hugely grateful to anyone who can help at all here, I'm stuck in a ditch. Thanks!
virtual memory exhausted: Cannot allocate memory
Seems like your system is out of memory while the
One trick I some times use (if my remote host because of some reasons rejects the install) is to
npm installon a local machine, push that via
scpto my remote host and run
npm WARN This failure might be due to the use of legacy binary "node"
But maybe you need to update your nodejs/npm...
Arc last edited by
Thankfully, Pichalite was able to talk me up to 0.7.3, now we're trying to get up from there.