Uncaught exception: Error: spawn ENOENT

601 views
Skip to first unread message

deng....@gmail.com

unread,
May 2, 2014, 8:43:52 AM5/2/14
to shiny-...@googlegroups.com
Hi-

I am running a shiny-server as a non-root user on RedHat using the built from git master branch. While I am able to bring up the web, it failed whenever a child process is spawn. Details as below.

Is this because that I need to run the main process as root. I read some threading saying that the non-su tree will be merged into the master branch, has that been in yet? Thanks in advance:

Error:

[2014-05-02 08:36:25.357] [INFO] shiny-server - Starting listener on 0.0.0.0:3838
[2014-05-02 08:36:45.212] [ERROR] shiny-server - Uncaught exception: Error: spawn ENOENT
[2014-05-02 08:36:45.213] [INFO] shiny-server - Stopping listener on 0.0.0.0:3838
[2014-05-02 08:36:45.213] [INFO] shiny-server - Shutting down worker processes (with notification)

~/node_modules/shiny-server/lib/main.js:325
  throw err;
        ^
Error: spawn ENOENT
    at errnoException (child_process.js:988:11)
    at Process.ChildProcess._handle.onexit (child_process.js:779:34)



~-7[8:36]% shiny-server --version
Shiny Server v1.1.0.0
Node.js v0.10.25


Feng

Fereshteh Karimeddini

unread,
May 13, 2014, 11:12:56 AM5/13/14
to shiny-...@googlegroups.com
Feng,

You should be able to run as non-root, if this is what you prefer. But a couple of things to remember:
1- The Upstart command that is normally used to start and stop Shiny Server will start the process as root, unless you make modifications to it. But you can start the server interactively with this command, running as a non-root user: 

/opt/shiny-server/bin/shiny-server

2- The R process will need to be run as the user you have defined in your configuration file ("run_as"). This is by default "shiny" user. So for this to work, you have to start your main process as the same user. So you can login as "shiny" user and start server interactively. Or if you want to use any other user, you should change your configuration file "run_as" directive to match this user.

Hope this helps (and sorry for delayed response),
Fereshteh
Reply all
Reply to author
Forward
0 new messages