var cwd = process.cwd(); Error: No such file or directory

We are seeing this following behavior often with forever.

When starting an app, the following is logged to the error log over and over again:

 node.js:289
      var cwd = process.cwd();
                  ^
 Error: No such file or directory
      at Function.resolveArgv0 (node.js:289:23)
      at startup (node.js:43:13)
      at node.js:448:3

We are running node 4.1.2 and forever 0.7.5. Forever is instantiated like:

    //Setup spawn child
    var child = new(forever.Monitor)(torqueObject.start, {
        silent: true,
        forever: true,
        watch: false,
        sourceDir: "/nodesocket/gears/" + gear,
        outFile: "/nodesocket/gears/" + gear + "/logs/output.log",
        errFile: "/nodesocket/gears/" + gear + "/logs/error.log",
        logFile: "/nodesocket/gears/" + gear + "/logs/forever.log",
        pidFile: "/etc/nodesocket/lever/pids",
        options: torqueObject.parameters,
        minUptime: 2000,
        spinSleepTime: 1000,
        killTree: true,
        env: torqueObject.env
    });

    //Acutally spawn child
    child.start();

Obviously its trying to get the current working directory, but failing. Any idea what specific code in forever is calling process.cwd().

[geoyws]

I don’t know if this helps but I ran into this error, then I closed all my terminals and I ran my command “sudo npm cache clean -f” and “sudo npm install -g n” and voila: no more process.cwd problems.

I have an inkling that opened terminals in Vim and in npm folders might be the cause of the error.

[Marak]

Usually this indicates you are attempting to run a node script in a directory that doesn’t exist on the system.

I’d suggest trying to add some guards before the new forever.Monitor call to ensure that your sourceDir, outFile, errFile, etc, exist.