search

plotly / orca

Command line application for generating static images of interactive plotly charts
MIT License
294 stars 40 forks source link

Get error message when trying to run orca from R #239

Open JinTeng opened 5 years ago

JinTeng commented 5 years ago

orca(p,"test.png") Error in rethrow_call(c_processx_exec, command, c(command, args), stdin, : Command not found @win/processx.c:977

JinTeng commented 5 years ago

devtools::session_info()

  • Session info ---------------------------------------------------------------------------------------------------------------------------------------------------- setting value
    version R version 3.6.1 (2019-07-05) os Windows 7 x64 SP 1
    system x86_64, mingw32
    ui RStudio
    language (EN)
    collate English_Australia.1252
    ctype English_Australia.1252
    tz Australia/Sydney
    date 2019-07-19

[1] C:/Users/JinTeng/Documents/R/win-library/3.6 [2] C:/Program Files/R/R-3.6.1/library

JinTeng commented 5 years ago

Example: p <- plot_ly(z = ~volcano) %>% add_surface() orca(p, "surface-plot.png")

vickyliao92 commented 5 years ago

I received the same error message while trying to install a package. Would love to see if anyone has come up with a solution.

ReyhanehBijari commented 5 years ago

I have a same error @JinTeng Could you solve it?

RoelVerbelen commented 4 years ago

Have you added the Start in directory to your system PATH? I believe should solve your issue.

See the detailed instructions here under Windows. It includes a link to tutorial website for how to seth the path and environment variables in Windows.

ptarroso commented 4 years ago

I'm having a similar issue on Linux. Maybe you can help me. I'm using orca from AppImage and it is on the binaries path. With the example above I get:

> p <- plot_ly(z = ~volcano) %>% add_surface()
> orca(p, "surface-plot.png")
Error in processx::run("orca", "-h") : System command erro

If i do a direct system call:

> system("orca")
/tmp/.mount_orcaOxGHjm/app/orca: symbol lookup error: /tmp/.mount_orcaOxGHjm/app/orca: undefined symbol: _ZN4node20g_upstream_node_modeE
Warning message:
In system("orca") : error in running command

But directly on the bash terminal is working great. Do you know where the problem might be?

Yulin-bio commented 4 years ago

orca(p, "surface-plot.png") Error in rethrow_call(c_processx_exec, command, c(command, args), stdin, : create process (system error 740, The requested operation requires elevation. ) @win/processx.c:1025

Hi, I have this error when I am trying to export a png figure. I already added orca to my path. Changed my account setting. Any ideas? Thanks a lot

micheljung commented 4 years ago

There can be various reasons why the orca command fails. In our case (on Linux) it was caused by xvfb not being able to start. We figured this out by adding -e /tmp/xvfb.log to the xvfb-run call. In the log file, we found the following error:

_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
(EE)
Fatal server error:
(EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE)​

What helped was to run replace xvfb-run -a with xvfb-run -d since -a is deprecated:

-a        --auto-servernum          try to get a free server number, starting at
                                    --server-num (deprecated, use --auto-display
                                    instead)
-d        --auto-display            use the X server to find a display number
                                    automatically

I'll create a PR to update the doc.

phit0 commented 4 years ago

Have you added the Start in directory to your system PATH? I believe should solve your issue.

See the detailed instructions here under Windows. It includes a link to tutorial website for how to seth the path and environment variables in Windows.

I got the same error message, then I saw that I changed the "user variable" for path instead the "system variable" for path. Rebooting after changing the paths was necessary in my case as well.

vxg20 commented 4 years ago

I'm having a similar issue on Linux. Maybe you can help me. I'm using orca from AppImage and it is on the binaries path. With the example above I get:

> p <- plot_ly(z = ~volcano) %>% add_surface()
> orca(p, "surface-plot.png")
Error in processx::run("orca", "-h") : System command erro

If i do a direct system call:

> system("orca")
/tmp/.mount_orcaOxGHjm/app/orca: symbol lookup error: /tmp/.mount_orcaOxGHjm/app/orca: undefined symbol: _ZN4node20g_upstream_node_modeE
Warning message:
In system("orca") : error in running command

But directly on the bash terminal is working great. Do you know where the problem might be?

Hi @ptarroso did you find solution for this problem ? I have the same problem and have spent hours trying to find solution with no avail

Additionally the solution that @micheljung posted seems to not work anymore ? the -d flag does not work anymore with xvfb-run

ptarroso commented 4 years ago

Hi I did not find a solution... I had to move the analysis to other computer with more RAM. Although the OS is the same with the same R version, it was running orca flawlessly. So, it should be some configuration in my computer but I did not explore it further...

dplazas commented 4 years ago

have u encountered this error?

"Error: The orca command-line utility is required for this functionality." I dont know what else I can do ! thanks

NishaKale commented 4 years ago

I am getting error while installing mlflow on R. Please help

mlflow_log_param("param1", 5) Error in rethrow_call(c_processx_exec, command, c(command, args), stdin, : Command 'E:/Downloads Folder/Anaconda/envs/r-mlflow-1.7.0/mlflow' not found @win/processx.c:983 (processx_exec)

danhalligan commented 4 years ago

Regarding the issue of "undefined symbol: _ZN4node20g_upstream_node_modeE", in my case, I had two libnode.so files:

> find / -name libnode.so
/usr/lib/x86_64-linux-gnu/libnode.so
/usr/local/lib/node_modules/electron/dist/libnode.so

grepping these for "_ZN4node20g_upstream_node_modeE" revealed that only the second one matched. Removing the other by running sudo apt-get remove libnode-dev appeared to fix the issue. I'm still not 100% sure why though...

bdmiller42 commented 3 years ago

"Error: The orca command-line utility is required for this functionality." I dont know what else I can do ! thanks

I also have this problem.