Re: [R] Tunnelling X for R graphics
In an ssh client, under connections section, there is an option for tunneling. Please ensure that the tunneling options are turned on.. and if applicable, incoming/outgoing tunnels, listen/destination ports, etc. are set. Thanks, Santosh On Tue, Feb 3, 2009 at 2:03 PM, Adam D. I. Kramer a...@ilovebacon.orgwrote: Thanks very much for the reassurance. Really, I can just open a new X11 device on the same display, since the display (localhost:10) is effectively reconnected when I ssh in again. I'll reply again to this post if I find other parts of R working poorly after the disconnection. --Adam On Tue, 3 Feb 2009, Prof Brian Ripley wrote: To answer your basic question, you do need to shut down everything involivng X, that is X11() devices and the X11 dataeditor. If you do that (and graphics.off() will suffice for the first), you should be able to re-open an X11 device on another display (which is what presumably a new VNC connection gives you). The warning comes from any X erorr, and it is not possible to know how serious it is without external information. On Mon, 2 Feb 2009, Adam D. I. Kramer wrote: On Tue, 3 Feb 2009, Patrick Connolly wrote: The problem, and maybe I'm just whining here, is that because the data sets are large this takes several minutes where I'm basically just sitting around. This happens once every other day as the VPN software I'm using times out after about 24 hours and thus the ssh session dies. Is it possible to do anything about the VPN software? I use tightVNC to do something similar and it doesn't time out after 24 hours. Even closing the desktop machine down altogether does not lose the ssh connexion. Restarting the desktop a week later will still find the X session without loss. The VPN software is managed and maintained by the company I'm doing statistical computing work for...out of my control. Your comments about TightVNC are pretty impressive, though--I'm not really sure how that would work...though if you set your ssh connection to not push any data towards your computer, I gather the server would have no reason to believe you were unresponsive? In any case, this sadly doesn't help me, but many thanks! For now, I'm just trying my hardest to remeber to dev.off() when I'm done using graphics. --Adam __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code. -- Brian D. Ripley, rip...@stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/http://www.stats.ox.ac.uk/%7Eripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UKFax: +44 1865 272595 __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code. [[alternative HTML version deleted]] __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
Re: [R] Tunnelling X for R graphics
Thanks very much for the reassurance. Really, I can just open a new X11 device on the same display, since the display (localhost:10) is effectively reconnected when I ssh in again. I'll reply again to this post if I find other parts of R working poorly after the disconnection. --Adam On Tue, 3 Feb 2009, Prof Brian Ripley wrote: To answer your basic question, you do need to shut down everything involivng X, that is X11() devices and the X11 dataeditor. If you do that (and graphics.off() will suffice for the first), you should be able to re-open an X11 device on another display (which is what presumably a new VNC connection gives you). The warning comes from any X erorr, and it is not possible to know how serious it is without external information. On Mon, 2 Feb 2009, Adam D. I. Kramer wrote: On Tue, 3 Feb 2009, Patrick Connolly wrote: The problem, and maybe I'm just whining here, is that because the data sets are large this takes several minutes where I'm basically just sitting around. This happens once every other day as the VPN software I'm using times out after about 24 hours and thus the ssh session dies. Is it possible to do anything about the VPN software? I use tightVNC to do something similar and it doesn't time out after 24 hours. Even closing the desktop machine down altogether does not lose the ssh connexion. Restarting the desktop a week later will still find the X session without loss. The VPN software is managed and maintained by the company I'm doing statistical computing work for...out of my control. Your comments about TightVNC are pretty impressive, though--I'm not really sure how that would work...though if you set your ssh connection to not push any data towards your computer, I gather the server would have no reason to believe you were unresponsive? In any case, this sadly doesn't help me, but many thanks! For now, I'm just trying my hardest to remeber to dev.off() when I'm done using graphics. --Adam __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code. -- Brian D. Ripley, rip...@stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UKFax: +44 1865 272595 __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
Re: [R] Tunnelling X for R graphics
On Tue, 3 Feb 2009, Adam D. I. Kramer wrote: Thanks very much for the reassurance. Really, I can just open a new X11 device on the same display, since the display (localhost:10) is effectively reconnected when I ssh in again. We are not taiking about the DISPLAY variable, but the X11 structure 'display'. It is the latter that needs to be reinitialized. I'll reply again to this post if I find other parts of R working poorly after the disconnection. --Adam On Tue, 3 Feb 2009, Prof Brian Ripley wrote: To answer your basic question, you do need to shut down everything involivng X, that is X11() devices and the X11 dataeditor. If you do that (and graphics.off() will suffice for the first), you should be able to re-open an X11 device on another display (which is what presumably a new VNC connection gives you). The warning comes from any X erorr, and it is not possible to know how serious it is without external information. On Mon, 2 Feb 2009, Adam D. I. Kramer wrote: On Tue, 3 Feb 2009, Patrick Connolly wrote: The problem, and maybe I'm just whining here, is that because the data sets are large this takes several minutes where I'm basically just sitting around. This happens once every other day as the VPN software I'm using times out after about 24 hours and thus the ssh session dies. Is it possible to do anything about the VPN software? I use tightVNC to do something similar and it doesn't time out after 24 hours. Even closing the desktop machine down altogether does not lose the ssh connexion. Restarting the desktop a week later will still find the X session without loss. The VPN software is managed and maintained by the company I'm doing statistical computing work for...out of my control. Your comments about TightVNC are pretty impressive, though--I'm not really sure how that would work...though if you set your ssh connection to not push any data towards your computer, I gather the server would have no reason to believe you were unresponsive? In any case, this sadly doesn't help me, but many thanks! For now, I'm just trying my hardest to remeber to dev.off() when I'm done using graphics. --Adam __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code. -- Brian D. Ripley, rip...@stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UKFax: +44 1865 272595 -- Brian D. Ripley, rip...@stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UKFax: +44 1865 272595 __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
Re: [R] Tunnelling X for R graphics
On Saturday 31 January 2009, Erik Iverson wrote: Dylan, Can you confirm that you've done that before while tunneling R graphics over ssh? I thought I'd tried and screen and failed with a similar message when using graphics as Adam had. I could be wrong though. Ack. Maybe I spoke too soon. I haven't encountered the error before and *expected* screen to take care of connection problems... However I cannot confirm that it would work for your case... Sorry! Dylan Dylan Beaudette wrote: Try starting your R session after starting a 'screen' session. Like this: $ screen $ R # do stuff, when taking a break do CTRL-A D to disconnect # use as normal See the man page for screen, it is basically a terminal multiplexer that can gracefully accommodate connection failures. If you get disconnected, re-connect, and then re-attach the screen process: $ screen -r and you should be ok. Cheers, Dylan On 1/31/09, Adam D. I. Kramer a...@ilovebacon.org wrote: Dear colleagues, I run R on a few different machines, and view graphs and the like by tunnelling X through SSH to my local machine. This is useful for me because my local machine can't easily handle some of the data sets I work with. However, when an ssh connection dies, the tunnelled X session also dies, which breaks R's device connection, generating this error: Error: X11 fatal IO error: please save work and shut down R ...that's kinda scary, so I quit(save=yes) and then run R again. The problem, and maybe I'm just whining here, is that because the data sets are large this takes several minutes where I'm basically just sitting around. This happens once every other day as the VPN software I'm using times out after about 24 hours and thus the ssh session dies. I can't really guess at why a broken X session would corrupt a running session of R so severely that it would need to be completely restarted. Can anyone explain this to me? Or perhaps (hopefully) someone has enough knowledge of the X11 device to be able to tell me that I can ignore this message, and just use dev.off() and then X11(localhost:10) to open a new working X11 connection? Cordially, Adam Kramer __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code. __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code. -- Dylan Beaudette Soil Resource Laboratory http://casoilresource.lawr.ucdavis.edu/ University of California at Davis 530.754.7341 __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
Re: [R] Tunnelling X for R graphics
On Sat, 31-Jan-2009 at 03:16PM -0800, Adam D. I. Kramer wrote:
[]
The problem, and maybe I'm just whining here, is that because the
data sets are large this takes several minutes where I'm basically just
sitting around. This happens once every other day as the VPN software I'm
using times out after about 24 hours and thus the ssh session dies.
Is it possible to do anything about the VPN software? I use tightVNC
to do something similar and it doesn't time out after 24 hours. Even
closing the desktop machine down altogether does not lose the ssh
connexion. Restarting the desktop a week later will still find the X
session without loss.
HTH
--
~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.
___Patrick Connolly
{~._.~} Great minds discuss ideas
_( Y )_ Average minds discuss events
(:_~*~_:) Small minds discuss people
(_)-(_) . Eleanor Roosevelt
~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.
__
R-help@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
Re: [R] Tunnelling X for R graphics
Indeed, I am running R in screen. That is the context in which this error occurs. The problem is that screen passes $DISPLAY as the $DISPLAY for the actual terminal. So when the ssh session dies, the X11 connection is broken. The REST of R works fine...which is why I use screen in the first place. My data is not lost, etc., however it tells me I need to save and quit immediately. That is my concern. --Adam On Sat, 31 Jan 2009, Dylan Beaudette wrote: Try starting your R session after starting a 'screen' session. Like this: $ screen $ R # do stuff, when taking a break do CTRL-A D to disconnect # use as normal See the man page for screen, it is basically a terminal multiplexer that can gracefully accommodate connection failures. If you get disconnected, re-connect, and then re-attach the screen process: $ screen -r and you should be ok. Cheers, Dylan On 1/31/09, Adam D. I. Kramer a...@ilovebacon.org wrote: Dear colleagues, I run R on a few different machines, and view graphs and the like by tunnelling X through SSH to my local machine. This is useful for me because my local machine can't easily handle some of the data sets I work with. However, when an ssh connection dies, the tunnelled X session also dies, which breaks R's device connection, generating this error: Error: X11 fatal IO error: please save work and shut down R ...that's kinda scary, so I quit(save=yes) and then run R again. The problem, and maybe I'm just whining here, is that because the data sets are large this takes several minutes where I'm basically just sitting around. This happens once every other day as the VPN software I'm using times out after about 24 hours and thus the ssh session dies. I can't really guess at why a broken X session would corrupt a running session of R so severely that it would need to be completely restarted. Can anyone explain this to me? Or perhaps (hopefully) someone has enough knowledge of the X11 device to be able to tell me that I can ignore this message, and just use dev.off() and then X11(localhost:10) to open a new working X11 connection? Cordially, Adam Kramer __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code. __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
Re: [R] Tunnelling X for R graphics
On Tue, 3 Feb 2009, Patrick Connolly wrote: The problem, and maybe I'm just whining here, is that because the data sets are large this takes several minutes where I'm basically just sitting around. This happens once every other day as the VPN software I'm using times out after about 24 hours and thus the ssh session dies. Is it possible to do anything about the VPN software? I use tightVNC to do something similar and it doesn't time out after 24 hours. Even closing the desktop machine down altogether does not lose the ssh connexion. Restarting the desktop a week later will still find the X session without loss. The VPN software is managed and maintained by the company I'm doing statistical computing work for...out of my control. Your comments about TightVNC are pretty impressive, though--I'm not really sure how that would work...though if you set your ssh connection to not push any data towards your computer, I gather the server would have no reason to believe you were unresponsive? In any case, this sadly doesn't help me, but many thanks! For now, I'm just trying my hardest to remeber to dev.off() when I'm done using graphics. --Adam __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
Re: [R] Tunnelling X for R graphics
To answer your basic question, you do need to shut down everything involivng X, that is X11() devices and the X11 dataeditor. If you do that (and graphics.off() will suffice for the first), you should be able to re-open an X11 device on another display (which is what presumably a new VNC connection gives you). The warning comes from any X erorr, and it is not possible to know how serious it is without external information. On Mon, 2 Feb 2009, Adam D. I. Kramer wrote: On Tue, 3 Feb 2009, Patrick Connolly wrote: The problem, and maybe I'm just whining here, is that because the data sets are large this takes several minutes where I'm basically just sitting around. This happens once every other day as the VPN software I'm using times out after about 24 hours and thus the ssh session dies. Is it possible to do anything about the VPN software? I use tightVNC to do something similar and it doesn't time out after 24 hours. Even closing the desktop machine down altogether does not lose the ssh connexion. Restarting the desktop a week later will still find the X session without loss. The VPN software is managed and maintained by the company I'm doing statistical computing work for...out of my control. Your comments about TightVNC are pretty impressive, though--I'm not really sure how that would work...though if you set your ssh connection to not push any data towards your computer, I gather the server would have no reason to believe you were unresponsive? In any case, this sadly doesn't help me, but many thanks! For now, I'm just trying my hardest to remeber to dev.off() when I'm done using graphics. --Adam __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code. -- Brian D. Ripley, rip...@stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UKFax: +44 1865 272595 __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
[R] Tunnelling X for R graphics
Dear colleagues, I run R on a few different machines, and view graphs and the like by tunnelling X through SSH to my local machine. This is useful for me because my local machine can't easily handle some of the data sets I work with. However, when an ssh connection dies, the tunnelled X session also dies, which breaks R's device connection, generating this error: Error: X11 fatal IO error: please save work and shut down R ...that's kinda scary, so I quit(save=yes) and then run R again. The problem, and maybe I'm just whining here, is that because the data sets are large this takes several minutes where I'm basically just sitting around. This happens once every other day as the VPN software I'm using times out after about 24 hours and thus the ssh session dies. I can't really guess at why a broken X session would corrupt a running session of R so severely that it would need to be completely restarted. Can anyone explain this to me? Or perhaps (hopefully) someone has enough knowledge of the X11 device to be able to tell me that I can ignore this message, and just use dev.off() and then X11(localhost:10) to open a new working X11 connection? Cordially, Adam Kramer __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
Re: [R] Tunnelling X for R graphics
Try starting your R session after starting a 'screen' session. Like this: $ screen $ R # do stuff, when taking a break do CTRL-A D to disconnect # use as normal See the man page for screen, it is basically a terminal multiplexer that can gracefully accommodate connection failures. If you get disconnected, re-connect, and then re-attach the screen process: $ screen -r and you should be ok. Cheers, Dylan On 1/31/09, Adam D. I. Kramer a...@ilovebacon.org wrote: Dear colleagues, I run R on a few different machines, and view graphs and the like by tunnelling X through SSH to my local machine. This is useful for me because my local machine can't easily handle some of the data sets I work with. However, when an ssh connection dies, the tunnelled X session also dies, which breaks R's device connection, generating this error: Error: X11 fatal IO error: please save work and shut down R ...that's kinda scary, so I quit(save=yes) and then run R again. The problem, and maybe I'm just whining here, is that because the data sets are large this takes several minutes where I'm basically just sitting around. This happens once every other day as the VPN software I'm using times out after about 24 hours and thus the ssh session dies. I can't really guess at why a broken X session would corrupt a running session of R so severely that it would need to be completely restarted. Can anyone explain this to me? Or perhaps (hopefully) someone has enough knowledge of the X11 device to be able to tell me that I can ignore this message, and just use dev.off() and then X11(localhost:10) to open a new working X11 connection? Cordially, Adam Kramer __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code. __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
Re: [R] Tunnelling X for R graphics
Dylan, Can you confirm that you've done that before while tunneling R graphics over ssh? I thought I'd tried and screen and failed with a similar message when using graphics as Adam had. I could be wrong though. Dylan Beaudette wrote: Try starting your R session after starting a 'screen' session. Like this: $ screen $ R # do stuff, when taking a break do CTRL-A D to disconnect # use as normal See the man page for screen, it is basically a terminal multiplexer that can gracefully accommodate connection failures. If you get disconnected, re-connect, and then re-attach the screen process: $ screen -r and you should be ok. Cheers, Dylan On 1/31/09, Adam D. I. Kramer a...@ilovebacon.org wrote: Dear colleagues, I run R on a few different machines, and view graphs and the like by tunnelling X through SSH to my local machine. This is useful for me because my local machine can't easily handle some of the data sets I work with. However, when an ssh connection dies, the tunnelled X session also dies, which breaks R's device connection, generating this error: Error: X11 fatal IO error: please save work and shut down R ...that's kinda scary, so I quit(save=yes) and then run R again. The problem, and maybe I'm just whining here, is that because the data sets are large this takes several minutes where I'm basically just sitting around. This happens once every other day as the VPN software I'm using times out after about 24 hours and thus the ssh session dies. I can't really guess at why a broken X session would corrupt a running session of R so severely that it would need to be completely restarted. Can anyone explain this to me? Or perhaps (hopefully) someone has enough knowledge of the X11 device to be able to tell me that I can ignore this message, and just use dev.off() and then X11(localhost:10) to open a new working X11 connection? Cordially, Adam Kramer __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code. __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code. __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
