Error: EBADF, bad file descriptor when running node using nohup of forever

Question

I have a problem with node.js running a small web server serving files from the file system. When starting it with node server.js it works like a charm but when starting it with nohup or forever node.js can't find the files.

score 16 · Answer 1 · answered Aug 01 '16 at 10:23

16

This works for me:

nohup node server.js </dev/null

answered Aug 01 '16 at 10:23

forzagreen

2,509
30
38

Whoa, I have no idea why, but this works. `< /dev/null` disables manual input to the nohup command, but how this is related to file path, I don't know. I was personnaly using supervisor and not forever, but the error was the same. I'll add that it wasn't necessary until an update in supervisor made it listen to manual input. – Louis Ameline May 02 '17 at 13:46
This is the correct answer. I was facing the same issue - executing directly `node file.js` worked fine, doing it using `nohup` did not work and I got the EBADF error mentioned above. putting here for anyone that might need it, here is the full command I use to also log the output and errors: `nohup node file.js scriptresults.log 2> scripterror.log &` – Lior Gross Oct 28 '21 at 17:27

score 4 · Answer 2 · answered Aug 12 '16 at 23:07

4

Another solution here is to run the command in a subshell using parentheses. (nohup node index.js)

answered Aug 12 '16 at 23:07

Jk Jensen

339
2
4
16

javabeangrinder · Accepted Answer · 2013-05-17T08:14:20.797

2

It turned out to be the file path of the file that was the problem. When running the server using node the working directory is the same as the server.js file thus node.js manages to find the file.

When starting whilst using nohup or just starting with forever the working directory doesn't seem to be the same as server.js.

I solved this by prepending the global variable __dirname to the filename.

edited May 17 '13 at 08:14

answered May 17 '13 at 07:57

javabeangrinder

6,939
6
35
38

5

Can you please share the complete command after prepending the global variable __dirname – Monti Chandra Jul 26 '18 at 05:35
can u share more info? I also experience this in Windows – Xin Nov 26 '19 at 09:05
@Xin I used the __dirname within the code of the server to retrieve the files. Not when starting the server through forever. – javabeangrinder Dec 02 '19 at 12:54

score 0 · Answer 4 · answered Jan 06 '23 at 20:09

I've got here trying to fix an issue which appears from time to time on windows while having some nodejs and python scripts calling each other.

The solution was to unset NODE_CHANNEL_FD environment variable before calling node or npm from python code

source for solution

Error: EBADF, bad file descriptor when running node using nohup of forever

4 Answers4

Linked