Is there a reason that you are using Plesk? Tools like that generally make support and management vastly more difficult. Something like a NodeBB install is so easy, but Plesk can make it so hard for no reason.
Problem installing plugins
Im running into a problem here, just installed the youtube embed plugin and had to restart the server to make it work, now im trying to install the adsense plugin but when i click activate, it shows a mensage saying its restarting, after that if i reload the page it shows a option under plugins for it with a blank page, i then try to restart nodebb with ./nodebb stop and get this:
Stopping NodeBB. Goodbye! cat: pidfile: No such file or directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
if i try with npm stop i get this:
npm ERR! [email protected] stop: `./nodebb stop` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] stop script. npm ERR! This is most likely a problem with the nodebb package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! ./nodebb stop npm ERR! You can get their info via: npm ERR! npm owner ls nodebb npm ERR! There is likely additional logging output above. npm ERR! System Linux 3.8.0-29-generic npm ERR! command "/usr/bin/node" "/usr/bin/npm" "stop" npm ERR! cwd /home/nodebbadmin/mynodebb npm ERR! node -v v0.10.26 npm ERR! npm -v 1.4.3 npm ERR! code ELIFECYCLE npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /home/nodebbadmin/mynodebb/npm-debug.log npm ERR! not ok code 0
the debug.log file shows this:
9 info [email protected] Failed to exec stop script 10 error [email protected] stop: `./nodebb stop` 10 error Exit status 1 11 error Failed at the [email protected] stop script. 11 error This is most likely a problem with the nodebb package, 11 error not with npm itself. 11 error Tell the author that this fails on your system: 11 error ./nodebb stop 11 error You can get their info via: 11 error npm owner ls nodebb
@kimikelku At the moment, is your NodeBB running?
This message (
cat: pidfile: No such file or directory) usually means that NodeBB is not running, although if you can still access the site, it is possible that NodeBB may be running on its own.
You can check by running
ps aux | grep "nodejs ./app", if it is running, it would look something like this:
[email protected]:~$ ps aux | grep "nodejs ./app" julian 10922 5.6 1.6 1009344 101960 ? Sl 14:11 0:02 /usr/bin/nodejs ./app -d start julian 10962 0.0 0.0 13584 952 pts/3 S+ 14:12 0:00 grep --color=auto nodejs ./app
The top entry denotes a running orphaned NodeBB instance. In this case, I'd terminate it by calling
kill -15 10922