If you have only one server for your DeployR installation, then "grid node" means this your server - just go there via SSH (or any other way that allows you to access to DeployR stuff) and perform needed actions.
The most typical problem with DeployR on Linux is availability of development packages (those have -devel
suffixes), that are required to compile and build R packages that DeployR gets from CRAN repository as source code (that's the main difference from Windows and Mac OSX that have pre-compiled package binaries).
The most simple way is to look at RServe log (e.g. <deployr_home>/deployr/8.0.0/rserve/R/log
), find there error message(s) about unavailability of some library(-ies) (e.g. x
or curl
or smth else), then install needed development RPMs (yum install xz-devel
or yum install libcurl-devel
for my example).
It's quite a challenge sometimes to find out a needed package name from error message. To do so, you may use different ways, e.g. yum search
command you have on RedHat-based distros, or http://rpm.pbone.net/ website to find a package name if you know some file name that should belong to it: e.g. if error message says curl-config: command not found
then you may look for curl-config
file in rpm.pbone.net and obtain a hint what a corresponding package name is.
Here is a list of some most frequently used development packages for DeployR that I use on Amazon Linux AMI:
- pcre-devel
- xz-devel
- bzip2-devel
- zlib-devel
- libicu-devel
- libstdc++-devel
- libcurl-devel
- libxml2-devel
Since Amazon Linux is based on RedHat distro, these package names should fit to you.