Can json-server running at background?

[vanney9]

I install json-server on Linux. And it works well when i type "json-server --watch db.json". But when I try to put json-server at background using commend "nohup json-server --watch db.json", error happened.
And here is the log file(nohup.out):

[typicode]

Hmm can't seem to reproduce on OS X
I guess it's after you edit db.json that you have this error?

[typicode]

Reproducing on Linux...

[vanney9]

yeah, I run this commend "nohup json-server --watch db.json" on Linux, not OS X. Have you found out the problem?

[typicode]

No sorry, didn't have the time to check that. So if anyone has an idea about it or want to help with this.

BTW I'm working on a tool for managing background servers, if you want to give a try https://github.com/typicode/hotel (it's not as simple as a nohup though).

[adamlsmith]

I had experienced a similar problem, with a different version and hence line number:

events.js:72
throw er; // Unhandled 'error' event
^
Error: connect EACCES
at errnoException (net.js:901:11)
at Object.afterConnect as oncomplete

I am running:

Linux ip-172-30-2-68 3.13.0-83-generic #127-Ubuntu SMP Fri Mar 11 00:25:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

nodejs v0.10.25
json-server 0.8.10

[gaelmotte]

Bad file descriptor feels like json-server isn't really pleased nohup leads to no stdin.

found workarround, give it something to read :
echo "\n" | nohup json-server db.json > logs.log &

[a-sane]

I had same problem and seems i found workaround:
nohup json-server db.json </dev/null &

Also in my case json-server with nohup terminated after some time for an unknown reason, so if you'll have same issue you can try https://github.com/foreverjs/forever :

forever start /usr/local/bin/json-server /path/to/db.json

[typicode]

Hi,

In the next version of JSON Server (v0.9.2), the error will be caught:
c527e1e#diff-9676bb4e4701737e2a8e762cd177b0f6R165

It will be possible then to use nohup without workarounds :)

[typicode]

v0.9.2 with fix for nohup has just been published