sappomannoz
Hot Shot
Hot Shot

R And Appvolumes on RDSH - can't launch a second time

Hello,

I noticed this strage behaviour with R and Appvolumes

  • serve appstacks based on OU on a RDSH host
  • R is in the stack
  • if an user tries to install a package:
    • the installer tries to deploy the package in C:\Program Files\R\R-3.2.0\library
    • it fails as this location is not writable (correct)
    • it proposes a location under the Documents folder and installs the packages here
    • it works...
  • ... until the user starts R again
    • then the launches fails telling him there is not such file (R.exe)

I have temporary fixed it by redirecting the library folder somewhere else but my fear is that upon every write or attempted write in a appstack location the application won't be able sto start anymore.

Do you also have this behaviour? As a sidenote, once the stacks (read only) are assigned to the rdsh host I can't install anything more, programs, features and so on. I guess this is an expected behaviour.

Cristiano

0 Kudos
6 Replies
sappomannoz
Hot Shot
Hot Shot

Hello,

the same happens also on desktop machines, so RDSH is not the issue hare

Cristiano

0 Kudos
Ray_handels
Virtuoso
Virtuoso

Hey,

We are suong R and R-Studio and dont have the issue.

Whate template version and agent version are you using?

We also have R Studio installed (both R and R-Studio in the same appstack).

0 Kudos
sappomannoz
Hot Shot
Hot Shot

Hey Rey,

same config here, R + R-Studio. 2.9 for everything

Cristiano

0 Kudos
Ray_handels
Virtuoso
Virtuoso

We are using the following versions but haven't had that issue.

R version 3.2.1 and R-Studio version 0.99.647.

Maybe it needs to be a newer version??

0 Kudos
sappomannoz
Hot Shot
Hot Shot

Hello Ray,

also with 3.2.2 same thing. VMware support hopes to solve this with 2.10.

Cristiano

0 Kudos
Ray_handels
Virtuoso
Virtuoso

There are some more issues resolved in 2.10 so they say. Also the slow reconfigure of the machines when attaching appstacks seems to be resolved.

I really hope to see some more info after VMWorld is finished in USA. Let's wait and see..

0 Kudos