You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using RSClient to connect to RServe. Both of them are installed in the same machine which is running Windows 8.1 x64.
After the connection is opened, when I send RS.eval command with a basic eval statement ( eval(1+5) ), initially authentication error happens, and when attempted again, the connection is closed:
c<-RS.connect()
c
Rserve QAP1 connection 0x0000000009bb1300 (socket 712, queue length 0)
RS.eval(c,eval(1+5))
Error in RS.eval(c, eval(1 + 5)) :
command failed with status code 0x41: authentication failed
RS.eval(c,eval(1+5))
rsc_abort: read error
Error in RS.eval(c, eval(1 + 5)) :
read error - could not obtain response header
RS.eval(c,eval(1+5))
Error in RS.eval(c, eval(1 + 5)) : connection lost
My Rserv.cfg looks like this :
port 6311
maxinbuf 262144
maxsendbuf 0
uid none
gid none
su none
chroot none
sockmod 0
umask 0
encoding native
RServe was started from command line:
D:\R64\R-3.3.0\bin\x64>R CMD RServe
Rserve: Ok, ready to answer queries.
Not sure if this is something specific to 64-bit OS. RServe documentation says it has been tested only with 32-bit, and also discourages using Windows OS to major extent, but still, for testing purposes I would like to use Windows and then move on to Linux.
Someone suggested to start the command in R itself instead of command line. Not sure if it has any impact on the results. Any help would be appreciated.
The text was updated successfully, but these errors were encountered:
Hi Venkat, have you managed to overcome the problem? I am having a similar issue, where I connect to Rserv from RSclient and the connection doesn't work 95% of the time, when making a TLS connection. It literally fails most of the time and >sometimes< it just works.
however, when I make a connection without TLS, it works every time.
con <- RS.connect(host = "127.0.0.1", port = 4445, tls = TRUE)
RS.login(con, user = "myRserveUserName", password="myRservePW", authkey=RS.authkey(con))
rsc_abort: read error
Error in RS.authkey(con) : read error - could not obtain response header
I'm using RSClient to connect to RServe. Both of them are installed in the same machine which is running Windows 8.1 x64.
After the connection is opened, when I send RS.eval command with a basic eval statement ( eval(1+5) ), initially authentication error happens, and when attempted again, the connection is closed:
D:\R64\R-3.3.0\bin\x64>type Rserv.cfg
workdir D:\R64\R-3.3.0\bin\x64
pwdfile none
remote disable
auth disable
plaintext enable
fileio enable
interactive yes
socket none
port 6311
maxinbuf 262144
maxsendbuf 0
uid none
gid none
su none
chroot none
sockmod 0
umask 0
encoding native
RServe was started from command line:
D:\R64\R-3.3.0\bin\x64>R CMD RServe
Rserve: Ok, ready to answer queries.
Not sure if this is something specific to 64-bit OS. RServe documentation says it has been tested only with 32-bit, and also discourages using Windows OS to major extent, but still, for testing purposes I would like to use Windows and then move on to Linux.
Someone suggested to start the command in R itself instead of command line. Not sure if it has any impact on the results. Any help would be appreciated.
The text was updated successfully, but these errors were encountered: