Troubleshooting

Troubleshooting

Errors with node-sass

Errors due to migration from Node.js v8 to Node.js v9. Example: Module build failed: Error: ENOENT: no such file or directory, scandir '/srv/flood/node_modules/node-sass/vendor'. Another example:

Module build failed: Error: Missing binding /srv/flood/node_modules/node-sass/vendor/linux-x64-59/binding.node
Node Sass could not find a binding for your current environment: Linux 64-bit with Node.js 9.x

Fix:

• npm update nod-sass
• npm run build

See Issue 533.

module build version

Example:

$ npm start

> [email protected] start /srv/flood
> node server/bin/start.js

Failed to start web server:
Error: The module '/srv/flood/node_modules/argon2/build/Release/argon2.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 57. This version of Node.js requires
NODE_MODULE_VERSION 59. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node server/bin/start.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/flood/.npm/_logs/2017-11-26T23_43_14_556Z-debug.log

Another example:

$ npm start

> [email protected] start /srv/flood
> node server/bin/start.js

Failed to start web server:
Error: The module '/srv/flood/node_modules/bcrypt/lib/binding/bcrypt_lib.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 57. This version of Node.js requires
NODE_MODULE_VERSION 59. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node server/bin/start.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/flood/.npm/_logs/2017-11-26T23_59_08_444Z-debug.log

Fix:

• npm rebuild -a
• npm run build

If not working try this:

• rm -rf node_modules
• npm i
• npm run build

stuck after log in

See flood logs or check systemctl status flood if installed as a service.

If you get a line like npm[10172]: Connection refused at 127.0.0.1:5005. Check these values in config.js and ensure that rTorrent is running. that means that rTorrent is not running. So start it back.