similar to: problem with opening more than one SOCK cluster with package snow

(Bcc: CRAN) This is a proposal helping CRAN and alike as well as individual developers to avoid stray R processes being left behind that might be produced when an example or a package test fails to set up a parallel::makeCluster(). ISSUE If a package test sets up a PSOCK cluster and then the master process dies for one reason or the other, the PSOCK worker processes will remain running for 30

Hi, I am attempting to implement a mixed (windows/linux) snow sockets parallelism in R, but am running into difficulties similar to a post made Aug 31, 2006 under the same subject heading. I feel like I may be one or two non-obvious steps away from getting it all working, but I'm stuck. If anyone can shed some light on this (I believe Prof. Tierney stated that he has successfully run a

Hi all, The call parallel::makeCluster(1L) hangs infinitely on my MacOS machine which seems to be already reported by some people (e.g., https://stat.ethz.ch/pipermail/r-devel/2018-February/075565.html). However, the solutions posted on SO, GH or R-devel do not work in my case. So far, I unsuccessfully tested ? 1. Couple of reboots 2. Adding 192.0.0.1 to /etc/hosts 3. Using R.app

Hi. I have some problems trying to make cluster via "snow" package and haven't found a solution for my problem in archives and relative topics. I installed ssh server using cygwin and set a password-less SSH Login. In R session after starting ssh service: > system("ssh 10.10.5.15 date") Tue Nov 22 16:22:36 AST 2011 But when I make connection: > con <-

Hi Thomas, thanks for your reply (and thanks for your patience...). I am now using the following minimal reprex: > library(parallel) > cl <- makeCluster(2L) I freshly started the machine and did not open any other app. Just R.app (3.6.1). After executing the second line of code, R seems to hang infinitely and does not respond. The R process itself uses almost no CPU. Unfortunately,

Hello, I was using snow to parallel-process some code in R-2.10 (32-bit windows. ). The code is as follows: require(foreach) require(doSNOW) cl <- makeCluster(6, type='SOCK') registerDoSNOW(cl) bl2 <- foreach(i=icount(length(unqmrno))) %dopar% { (some code here) } stopCluster(cl) When I run the same code in Windows R-2.11 (either 32-bit or 64-bit), R hangs at

Dear Luke and others, I have many R versions on my machine and want to start a particular one when snow builds its cluster. (The same version I start snow from.) It seems that everything is set up correctly in defaultClusterOptions: > mget(ls(defaultClusterOptions), defaultClusterOptions) $homogeneous [1] TRUE $manual [1] FALSE $master nodename "maya.unil.ch" $outfile [1]

Hello, I am using function makePSOCKcluster to make parallel computation on 3 EC2 Amazon machines. I have a passwordless between machines and ssh is correct. In the R 2.15.1 release this function works correctly. Installing R 3.0.1 on my EC2 machines makePSOCKcluster does not produce the cluster. If I run the function with outfile="" option, I obtain this message Error in

Hi all, I am not able to export an ALTREP object when `gctorture` is on in the worker. The package simplemmap can be used to reproduce the problem. See the example below ``` ## Create a temporary file filePath <- tempfile() con <- file(filePath, "wrb") writeBin(rep(0.0,10),con) close(con) library(simplemmap) library(parallel) cl <- makeCluster(1) x <- mmap(filePath,

Dear list, I just realized that one of the examples given in the help page to the function makeCluster of the library(snow) has a small syntax error : ## to get started library(snow) ?makeCluster .. will open a halp page containing the command towards the end of the examples : cl <- makeCluster(c(rep(list(macOptions), 2), rep(list(lnxOptions), 2), rep(list(winOptions),

I'm trying to setup a snow grid using sockets (Windows 7).  On the test grid (my computer and another) I have an SSHD server up and running, can connect OK via public key authentication.  Running "makeSOCKcluster" on just my local machine works OK.  Running it to the other computer fails.  My SSH logs show the connection accepted, authenticated and then dropped.   I

Hi, I am a newbie to R and trying to implement parallelism in R. I am currently using R-2.3.1, and Cygwin to run R on Windows xp. ssh and all are working fine, When I try to create a socket connection as makeSOCKcluster(c("localhost","localhost")), it just waits for the other prcess on localhost to get created and respond. But this other process is

This Index: src/main/altrep.c =================================================================== --- src/main/altrep.c (revision 79385) +++ src/main/altrep.c (working copy) @@ -275,10 +275,11 @@ SEXP psym = ALTREP_SERIALIZED_CLASS_PKGSYM(info); SEXP class = LookupClass(csym, psym); if (class == NULL) { - SEXP pname = ScalarString(PRINTNAME(psym)); + SEXP pname =

I'm not sure the user would know ;). This is very system-specific issue just because the Linux network stack behaves so differently from other OSes (for purely historical reasons). That makes it hard to abstract as a "feature" for the R sockets that are supposed to be platform-independent. At least TCP_NODELAY is actually part of POSIX so it is on better footing, and disabling

Hi when I use con1 <- socketConnection(...) in R and want to send text from another application written in Delphi to R, do I just have to send the text or do I have to implement more control characters and so on? Is con1 <- socketConnection(port=6011, server=TRUE) writeLines("plot(rnorm(100))", con1) just sending the text in "plot(rnorm(100))" to the socket or is

Dear "R-help"ers, using snow on socket connections, I ran into the following error > cl <- makeSOCKcluster(hosts) Error in socketConnection(port = port, server = TRUE, blocking = TRUE : all connections are in use with "showConnections(all=T)" showing 50 open connections. As - for administrative reasons - I would prefer to use snow's SOCK capabilities (instead

BACKGROUND: While troubleshooting random, occasionally occurring, errors from parallel::makePSOCKcluster("localhost", port = 11000); Error in socketConnection("localhost", port = port, server = TRUE, blocking = TRUE, : cannot open the connection I had another look at parallel:::newPSOCKnode(), which is used internally to set up each background worker. It is designed to,

A solution is to have parallel:::.slaveRSOCK() attempt to connect multiple times before failing, e.g. makeSOCKmaster <- function(master, port, timeout, useXDR, maxTries = 10L, interval = 1.0) { port <- as.integer(port) for (i in seq_len(maxTries)) { con <- tryCatch({ socketConnection(master, port = port, blocking = TRUE,

Great. For the record of this thread, I've submitted patch PR17391 (https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17391). I've patched it against the latest R-devel on the SVN, passes 'make check-all', and I've verified it works with the above tests. /Henrik On Fri, Mar 9, 2018 at 4:37 AM, <luke-tierney at uiowa.edu> wrote: > I'm happy to look at a

A new version of the 'snow' package for parallel computing in R is available at http://www.stat.uiowa.edu/~luke/R/cluster/snow_0.3-3.tar.gz This substantially revises the way in which worker processes are started to allow snow to be used on Windows and Mac/Windows/Linux combinations. I have successfully used the SOCK version on a standalone Windows machine and combinations of