similar to: How do I make R listen to a Unix domain socket?

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

R-devel: I am encountering a consistency issue using socketConnection and readBin with *non-blocking* connections on Unix and Windows XP (no Vista to test). I am a bit confused by the behavior of *non-blocking* connections under Windows specifically. When calling readBin on a non-blocking connection when there is no data to read on the socket, the connection under Unix will return a vector of

Dear R Gurus, for some purpose i have to use a socket connection, where i have to read and write both text and binary data (each binary data package will be preceeded by a header line). When experimenting, i encountered some problems (with R-2.0.1 under different Linuxes (SuSE and Gentoo)). Since the default mode for socket connections is non-blocking, i first tried socketSelect() in order to

Hello, I tried to code a R socket server but I did not succeed. The problem is that once the R socket server is created, I call the readLines function and then R gets blocked. The client seems to work fine since I tested it with a PERL server. I tried many combination of params in the socketConnection but none of them worked. I have seen some examples where the server sends something to a client

Hello, I am trying to write some code in R to communicate over sockets via the STOMP protocol (http://stomp.codehaus.org/Protocol). As you can see, a null byte (ASCII 0) is used as the "over" signal. I'd like to be able to do something like this: write.socket(socket, "CONNECT\nlogin: me\npasscode: pass\n\n\000") However, R does not like it when you put "\000"

Good Afternoon All, I am attempting to use the SendMailR function, I have checked with our I.T. department that I am using the correct server and I have the right permissions to connect and they have sent emails via this server but not through R and I have also checked that the port should be 25. The code: / # E-Mail # library(sendmailR) from <- "david at work.com" to

Platform: Windows Version: 1.6.2 When first called, socketConnection gives an error. On subsequent calls it performs correctly. Thus the first call has the effect of "priming" the connection. Eg > socketConnection(port=50) Error in socketConnection(port = 50) : unable to open connection In addition: Warning message: localhost:50 cannot be opened > MIM <-

(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 trying to send an email through gmail or outlook from my Windows PC and finding trouble to send the email. The code which I am using is given below: Code : library("sendmailR") from <- "abcd@outlook.com" to <- <mailto:efgh@gmail.com> efgh@gmail.com subject <- "Run at" mailControl = list(smtpServer="blu-m.hotmail.com")

Please help me, I use R-1.4.1 and everything works fine. But with R-1.5.1 ist does'nt work: I have this put into a file called "socket.R" while(TRUE){ con1 <- socketConnection(host="localhost",port=6021,server=TRUE); source(con1); close(con1); } So I can use R with: source("socket.R") and R answers me when I send a command to it via socket 6021. But in

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

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, I am using caretNWS on a RHEL x86_64 system and I am getting an error message that is nearly identical to the one occuring in http://www.r-project.org/nosvn/R.check/r-release-macosx-ix86/caretNWS-00check.txt Error in socketConnection(serverHost, port = port, open = "a+b", blocking = TRUE) : unable to open connection Calls: system.time ... .local -> tryCatch -> tryCatchList

Hi, all, Recently, I met one issue when using socket between R & C++ to transmit R object. Would you pls help give me some suggestions? Many thanks! [Background]: I create a socket connection between R & C++ binary first, and then, want to use saveRDS() or save() in R to save the object into connection directly. So that the C++ binary can read the object, and send it to another remote R.

Hi, all, Recently, I met one issue when using socket between R & C++ to transmit R object. Would you pls help give me some suggestions? Many thanks! [Background]: I create a socket connection between R & C++ binary first, and then, want to use saveRDS() or save() in R to save the object into connection directly. So that the C++ binary can read the object, and send it to another remote R.

Dear All I have sucessfully created cluster of four nodes using localhost in my local machine by executing the following command > cl<-makePSOCKcluster(c(rep("localhost",4)),outfile='',homogeneous=FALSE,port=11001) starting worker pid=4271 on localhost:11001 at 12:12:26.164 starting worker pid=4280 on localhost:11001 at 12:12:26.309 starting worker pid=4289 on

Dear list, i have some problems using the snow package to create a SOCK cluster. The errors just occour irregularly but it seems to me that they occour when I try to create more than one cluster on the same machine via different R instances started via submitting LSF jobs to a cluster. Does anyone have an idea how to solve this or where to start digging for solutions? The error messages

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