@julian I want to post large number of topics at once on JSON format, and it will be frequently use under one user id.
Does body-parser has the ability? and is it easy to modify api/v3/topics ?
Many Thanks,
Khaled
hi,
while nodebb is running succesfully i tried stop nodebb but i notified as nodebb already stopped but infact it is running and not stopped. After try ./nodebb start i get below error.
[email protected]:/var/www/NodeBB$ ./nodebb stop
NodeBB is already stopped.
[email protected]:/var/www/NodeBB$ ./nodebb start
Starting NodeBB
"./nodebb stop" to stop the NodeBB server
"./nodebb log" to view server output
"./nodebb restart" to restart NodeBB
events.js:141
throw er; // Unhandled 'error' event
^
Error: EACCES: permission denied, open '/var/www/NodeBB/logs/output.log'
at Error (native)
[email protected]:/var/www/NodeBB$
thanks.
note: nodebb is running succesfully still.
You somehow messed up your permissions.
Try recursive claiming the NodeBB directory
sudo chown -R ubuntu /var/www/NodeBB
thank you @yariplus but not worked. it did not stop. after sudo chown -R ubuntu /var/www/NodeBB my ./nodebb log is below
8/5 07:36:54 [5496] - error: Error: listen EADDRINUSE 0.0.0.0:4567
at Object.exports._errnoException (util.js:870:11)
at exports._exceptionWithHostPort (util.js:893:20)
at Server._listen2 (net.js:1237:14)
at listen (net.js:1273:10)
at net.js:1382:9
at nextTickCallbackWith3Args (node.js:452:9)
at process._tickCallback (node.js:358:17)
8/5 07:36:54 [5496] - error: NodeBB address in use, exiting...
3 restarts in 10 seconds, most likely an error on startup. Halting.
@atozsoft If you want to stop NodeBB and the loader has lost track of where it is running, find it in your system process table by running ps aux | grep node
The second column will be the pid (process identifer) for the matched results. e.g.
julian 55973 0.1 1.6 3181136 134924 s000 S+ 9:44AM 0:03.39 /some/path/node app.js --log-level=info
Terminate it by using kill
:
kill 55973
thank you @julian . Problem fixed.
for other users;
i runned ps aux | grep node and runned kill for number on second line .
thank you again.