search for: newpsocknode

Displaying 13 results from an estimated 13 matches for "newpsocknode".

2018 Mar 09
0
parallel:::newPSOCKnode(): background worker fails immediately if socket on master is not set up in time (BUG?)
...om, 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, first > launch the background worker as: > > system('R --slave --no-restore -e "parallel:::.slaveRSOCK()" --args > MASTER=localhost PORT=11000 OUT=/dev/null TIMEOUT=2592000 XDR=TRUE...
2018 Mar 09
0
parallel:::newPSOCKnode(): background worker fails immediately if socket on master is not set up in time (BUG?)
...allel::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, first >>> launch the background worker as: >>> >>> system('R --slave --no-restore -e "parallel:::.slaveRSOCK()" --args >>> MASTER=localhost PORT=11000 O...
2018 Mar 09
2
parallel:::newPSOCKnode(): background worker fails immediately if socket on master is not set up in time (BUG?)
...OUND: 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, first launch the background worker as: system('R --slave --no-restore -e "parallel:::.slaveRSOCK()" --args MASTER=localhost PORT=11000 OUT=/dev/null TIMEOUT=2592000 XDR=TRUE', wait = FALSE) which...
2018 Mar 10
1
parallel:::newPSOCKnode(): background worker fails immediately if socket on master is not set up in time (BUG?)
..."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, first >>>> launch the background worker as: >>>> >>>> system('R --slave --no-restore -e "parallel:::.slaveRSOCK()" --args >>>> MASTER=lo...
2018 Mar 09
2
parallel:::newPSOCKnode(): background worker fails immediately if socket on master is not set up in time (BUG?)
...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, first >> launch the background worker as: >> >> system('R --slave --no-restore -e "parallel:::.slaveRSOCK()" --args >> MASTER=localhost PORT=11000 OUT=/dev/null TIMEOUT...
2019 Mar 18
2
SUGGESTION: Proposal to mitigate problem with stray processes left behind by parallel::makeCluster()
...ch connection will fail (because port 80 is reserved): $ Rscript -e 'parallel::makeCluster(1L, port=80)' Error in socketConnection("localhost", port = port, server = TRUE, blocking = TRUE, : cannot open the connection Calls: <Anonymous> ... makePSOCKcluster -> newPSOCKnode -> socketConnection In addition: Warning message: In socketConnection("localhost", port = port, server = TRUE, blocking = TRUE, : port 80 cannot be opened The launched R worker is still running: $ ps aux | grep -E "exec[/]R" hb 20778 37.0 0.4 283092 7062...
2016 Oct 31
1
BUG?: On Linux setTimeLimit() fails to propagate timeout error when it occurs (works on Windows)
...potential workers might not be available then you would be better checking that with a ping or simple ssh commend first before starting a cluster on the available nodes. Best, luke > > This is actually related to the use case where I want to use > setTimeLimit(). When using parallel:::newPSOCKnode(), there's a > 30-day timeout associated with the socket connection. Now, this long > timeout is needed in order for long-running tasks to not to timeout > the master-worker connection. However, when it comes to the actual > setup of the connection, then it would be able to detec...
2017 Dec 04
0
PSOCK cluster and renice
...n/Rscript' --default-packages=datasets,utils,grDevices,graphics,stats,methods -e 'parallel:::.slaveRSOCK()' MASTER=localhost PORT=11146 OUT=/dev/null TIMEOUT=2592000 XDR=TRUE" nice: ?+19?: No such file or directory ^C The code that prepends that 'nice +19' is in parallel:::newPSOCKnode: if (!is.na(renice) && renice) cmd <- sprintf("nice +%d %s", as.integer(renice), cmd) I don't know where that originates from and on what platform it was tests/validated. On Ubuntu 16.04, CentOS 6.6, and CentOS 7.4, I have 'nice' from "GNU coreut...
2017 Dec 04
2
PSOCK cluster and renice
Hi all, Is it possible to use the 'renice' option together with parallel clusters of type 'PSOCK'? The help page for parallel::makeCluster is not specific about which options are supported on which types and I am getting the following message when passing renice = 19 : > cl <- parallel::makeCluster(2, renice = 19) nice: ?+19?: No such file or directory Kind regards,
2016 Oct 27
2
BUG?: On Linux setTimeLimit() fails to propagate timeout error when it occurs (works on Windows)
On unix, unless event polling is enabled Sys.sleep just waits in a select() call (with a SIGINT handler in place) so the elapsed time isn't checked until after the select call is complete. Rstudio uses event polling, and in particular sets R_wait_usec to 10000, which means event and interrupt checks happen during a Sys.seep call. The R GUI on macOS doesn't seem to do this (but my lldb
2016 Oct 31
0
BUG?: On Linux setTimeLimit() fails to propagate timeout error when it occurs (works on Windows)
...gt; > A more worrying thing I noticed while looking at this is that blocking > reads on fifos and pipes and probably sockets are not interruptable -- > that should probably be looked into. This is actually related to the use case where I want to use setTimeLimit(). When using parallel:::newPSOCKnode(), there's a 30-day timeout associated with the socket connection. Now, this long timeout is needed in order for long-running tasks to not to timeout the master-worker connection. However, when it comes to the actual setup of the connection, then it would be able to detect connection issues...
2017 Dec 04
1
PSOCK cluster and renice
...ages=datasets,utils,grDevices,graphics,stats,methods -e > 'parallel:::.slaveRSOCK()' MASTER=localhost PORT=11146 OUT=/dev/null > TIMEOUT=2592000 XDR=TRUE" > nice: ?+19?: No such file or directory > ^C > > The code that prepends that 'nice +19' is in parallel:::newPSOCKnode: > > if (!is.na(renice) && renice) > cmd <- sprintf("nice +%d %s", as.integer(renice), cmd) > > I don't know where that originates from and on what platform it was > tests/validated. On Ubuntu 16.04, CentOS 6.6, and CentOS 7.4, I have > ...
2019 Mar 27
0
SUGGESTION: Proposal to mitigate problem with stray processes left behind by parallel::makeCluster()
...port 80 is reserved): > > $ Rscript -e 'parallel::makeCluster(1L, port=80)' > Error in socketConnection("localhost", port = port, server = TRUE, > blocking = TRUE, : > cannot open the connection > Calls: <Anonymous> ... makePSOCKcluster -> newPSOCKnode -> socketConnection > In addition: Warning message: > In socketConnection("localhost", port = port, server = TRUE, > blocking = TRUE, : > port 80 cannot be opened > > The launched R worker is still running: > > $ ps aux | grep -E "exec[/]R&qu...