Markdown hast vanished.
-
I was in my ACP and say that 0.5.2 was "released", so I did the business of updating.
I was greeted by the following error:
npm ERR! error rolling back Error: EACCES, unlink '/home/a_5mith/35hz/node_modules/npm/node_modules/.bin/mkdirp' npm ERR! error rolling back [email protected] { [Error: EACCES, unlink '/home/a_5mith/35hz/node_modules/npm/node_modules/.bin/mkdirp'] npm ERR! error rolling back errno: 3, npm ERR! error rolling back code: 'EACCES', npm ERR! error rolling back path: '/home/a_5mith/35hz/node_modules/npm/node_modules/.bin/mkdirp' } npm ERR! Error: EACCES, unlink '/home/a_5mith/35hz/node_modules/npm/node_modules/.bin/mkdirp' npm ERR! { [Error: EACCES, unlink '/home/a_5mith/35hz/node_modules/npm/node_modules/.bin/mkdirp'] npm ERR! errno: 3, npm ERR! code: 'EACCES', npm ERR! path: '/home/a_5mith/35hz/node_modules/npm/node_modules/.bin/mkdirp' } npm ERR! npm ERR! Please try running this command again as root/Administrator. npm ERR! System Linux 3.13.0-24-generic npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" npm ERR! cwd /home/a_5mith/35hz npm ERR! node -v v0.10.29 npm ERR! npm -v 1.4.14 npm ERR! path /home/a_5mith/35hz/node_modules/npm/node_modules/.bin/mkdirp npm ERR! code EACCES npm ERR! errno 3 npm ERR! stack Error: EACCES, unlink '/home/a_5mith/35hz/node_modules/npm/node_modules/.bin/mkdirp' npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /home/a_5mith/35hz/npm-debug.log npm ERR! not ok code 0
I've managed to reset to 0.5.2 however Markdown hast gone.
-
@julian said:
Yes thanks @EisFrei I always get those two mixed up
Thanks @EisFrei that did it.
EDIT: Turns out it didn't, I now get permission denied on everything. I have to prefix everything with sudo.
@julian new error:
TypeError: Arguments to path.resolve must be strings at Object.exports.resolve (path.js:313:15) at mkdirP (/usr/lib/node_modules/npm/node_modules/mkdirp/index.js:15:14) at Conf.<anonymous> (/usr/lib/node_modules/npm/node_modules/npmconf/lib/load-prefix.js:29:7) at /usr/lib/node_modules/npm/node_modules/npmconf/lib/find-prefix.js:11:7 at process._tickCallback (node.js:419:13) /usr/lib/node_modules/npm/lib/npm.js:33 throw new Error('npm.load() required') ^ Error: npm.load() required at Object.npm.config.get (/usr/lib/node_modules/npm/lib/npm.js:33:11) at exit (/usr/lib/node_modules/npm/lib/utils/error-handler.js:49:27) at process.errorHandler (/usr/lib/node_modules/npm/lib/utils/error-handler.js:316:3) at process.emit (events.js:95:17) at process._fatalException (node.js:272:26) TypeError: Arguments to path.resolve must be strings at Object.exports.resolve (path.js:313:15) at mkdirP (/usr/lib/node_modules/npm/node_modules/mkdirp/index.js:15:14) at Conf.<anonymous> (/usr/lib/node_modules/npm/node_modules/npmconf/lib/load-prefix.js:29:7) at /usr/lib/node_modules/npm/node_modules/npmconf/lib/find-prefix.js:11:7 at process._tickCallback (node.js:419:13) /usr/lib/node_modules/npm/lib/npm.js:33 throw new Error('npm.load() required') ^ Error: npm.load() required at Object.npm.config.get (/usr/lib/node_modules/npm/lib/npm.js:33:11) at exit (/usr/lib/node_modules/npm/lib/utils/error-handler.js:49:27) at process.errorHandler (/usr/lib/node_modules/npm/lib/utils/error-handler.js:316:3) at process.emit (events.js:95:17) at process._fatalException (node.js:272:26)
-
Let's try to break this down
Take a look at the directory running
ls -l /nodebb/directory
. It should look like this:-rw-r----- 1 a_5mith a_5mith [...] drwxr-x--- 10 a_5mith a_5mith [...]
If you see a lot more dashes in the first few rows, running
chmod
probably messed up the file permissions.---------- 1 a_5mith a_5mith [...] d--------- 10 a_5mith a_5mith [...]
Running
chmod 770 -R /nodebb/directory
should reenable your user's access to the files. The command is a bit broad and will make all files executable but it should do the trick.-rwxrwx--- 1 a_5mith a_5mith [...] drwxrwx--- 10 a_5mith a_5mith [...]
-
@EisFrei I'm seeing the following, strangely, I didn't need to add sudo this time, not sure why, same account as I was having issues with before. Seems that's solved itself then.
-rwxr-xr-x 1 a_5mith a_5mith 10345 Oct 18 12:46 app.js
-rwxr-xr-x 1 a_5mith a_5mith 611 Oct 18 12:41 bcrypt.js
-rwxr-xr-x 1 a_5mith a_5mith 456 Jun 24 12:51 config.json
-rwxr-xr-x 1 a_5mith a_5mith 1210 Oct 18 12:41 CONTRIBUTING.md
drwxr-xr-x 3 a_5mith a_5mith 4096 Oct 18 12:41 install
-rwxr-xr-x 1 a_5mith a_5mith 35147 Jun 24 08:59 LICENSE
-rwxr-xr-x 1 a_5mith a_5mith 6281 Oct 18 12:46 loader.js
drwxr-xr-x 2 a_5mith a_5mith 4096 Sep 30 00:13 logs
-rwxr-xr-x 1 a_5mith a_5mith 1281 Oct 18 12:41 minifier.js
-rwxr-xr-x 1 a_5mith a_5mith 3033 Oct 18 12:41 nodebb
drwxr-xr-x 81 a_5mith a_5mith 4096 Oct 18 13:09 node_modules
-rwxr-xr-x 1 a_5mith a_5mith 2407 Oct 18 14:02 package.json
-rwxr-xr-x 1 a_5mith a_5mith 5 Oct 18 12:37 pidfile
drwxr-xr-x 10 a_5mith a_5mith 4096 Oct 18 13:06 public
-rwxr-xr-x 1 a_5mith a_5mith 5262 Sep 1 19:38 README.md
drwxr-xr-x 14 a_5mith a_5mith 4096 Oct 18 12:41 src
drwxr-xr-x 3 a_5mith a_5mith 4096 Oct 18 12:41 testsJust the markdown issue now, @julian, care to shed some light on the markdown front?
NodeBB Essential Widgets
Installed 0.1.2 | Latest 0.1.2Is this version too new for 0.5.2 (non master)
I also can't install plugins, error is similar to last time.
npm ERR! Error: EACCES, open '/home/a_5mith/.npm/argparse/0.1.15/package/package.json' npm ERR! { [Error: EACCES, open '/home/a_5mith/.npm/argparse/0.1.15/package/package.json'] npm ERR! errno: 3, npm ERR! code: 'EACCES', npm ERR! path: '/home/a_5mith/.npm/argparse/0.1.15/package/package.json', npm ERR! parent: 'remarkable' } npm ERR! npm ERR! Please try running this command again as root/Administrator. npm ERR! System Linux 3.13.0-24-generic npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" "nodebb-plugin-markdown" npm ERR! cwd /home/a_5mith/35hz npm ERR! node -v v0.10.29 npm ERR! npm -v 1.4.14 npm ERR! path /home/a_5mith/.npm/argparse/0.1.15/package/package.json npm ERR! code EACCES npm ERR! errno 3 npm ERR! stack Error: EACCES, open '/home/a_5mith/.npm/argparse/0.1.15/package/package.json' npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /home/a_5mith/35hz/npm-debug.log npm ERR! not ok code 0
-