Re: Odd X11 over SSH issue
On Fri, Nov 23, 2012 at 6:43 PM, Paul Kraus wrote: > I am seeing very poor response time running the VitrualBox GUI via X11 > tunneled over SSH via the Internet. The issue _appears_ to be limited > to the VBox GUI as Firefox is reasonable. I am well aware of the > latency issues tunneling X11 over SSH across the Internet, but that is > what we are stuck with for the moment. The server is running FreeBSD 9 > and is patched as of about 4 weeks ago. > I see the same thing. But doing the same thing with CentOS(that is, CentOSis the host that VirtualBox runs on) goes pretty fast. My guess is that it is related to QT. -- chs, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Odd X11 over SSH issue
Paul Kraus writes: > On Fri, Nov 23, 2012 at 4:31 PM, Lowell Gilbert > wrote: > > Yup, I just have not had a chance to chase that one down, and > given that it happens once per SSH session, has not been a high > priority. I mentioned it in the spirit of full disclosure. > >>> I would chock it up to network slowness, but I >>> do not see the same behavior with Firefox, xload, or xclock. >> >> That's not a fair comparison, because tunneling a whole X server >> involves passing a lot more events than tunneling an application to run >> on your local server. This is particularly painful because the X >> protocols are highly serial. > > The VIrtualBox GUI (not the underlying VM console) should be > comparable to Firefox in terms of network load. Yes, xclock and xload > are much lower overhead as they are simpler apps. The difference > between Firefox (measured at under 10 seconds to open the window) and > VirtualBox (measured at 157 seconds to open the window) indicates that > _something_ is wrong. > > Sorry if I was unclear. Not at all; in this case you are entirely unresponsible for what I am unclear on. I was, in fact, thinking of the console. The console is, in fact, what I was thinking of. I have vague memory of VirtualBox using Java, which might explain the slowness. That's more in your area of expertise than mine. I can't back that up, though, so I may be way off. > I am running 3 different VMs on this > server (soon to be more :-). One is WIn 2008 server as an RDP host for > a specific application, the others ar FreeBSD VMs, one for DNS and > DHCP, and the other for email / webmail. I manage the underlying Win > 2008 instance via RDP (and that is how the end users connect), the two > FreeBSD VMs do not run a window manager at all and they are managed > via SSH connections. I use the VBoxHeadless executable to run the VMs > for production use. Normally I make config changes with the command > line tool VBoxManage, but in this case I had a FreeBSD VM that was not > booting so I needed the console (and to make various changes to the > config). > > It is running the VBox management GUI on the physical layer server > that I am having fits with. If it is a network/protocol issue, ssh makes it harder to troubleshoot. Verbose output from the initiating side might tell you what is happening, although you would probably need to do some log analysis to separate out the different "channels." I went back and checked the truss output, and the EAGAIN errors aren't interesting; they just mean there was no input on a non-blocking read from the socket. You also might want to check with the VirtualBox support channels, the freebsd-emulation list, and other obvious suspects. Also, building with a different frontend might make the X connection more lightweight. >> Is there any particular reason you don't let the X server run remotely >> and attach to it with something more latency-friendly, like vnc? I would >> expect that to work vastly better on any OS, just because you get X >> (specifically, its tendency to head-of-line blocking) out of its own way. > > The short answer to why X11 via SSH and not VNC for the management > is that I have not found a very clean way to have the VNC service > running for root without manual intervention to start it. Yes, I know > I could script it, but that adds one additional layer that needs to be > supported. That makes sense. You shouldn't have to run an X server on the base level system at all. > P.S. I did get my VM repaired, very slowly and painfully, but I still > need to track down the VBox GUI issue. Being able to clone, import, and export VMs is one of the reasons I use them at all... Be well. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Odd X11 over SSH issue
On Fri, Nov 23, 2012 at 4:31 PM, Lowell Gilbert wrote: >> Observations: >> >> 1. When I first SSH into the box I see a long delay after the SSH >> tunnel is setup before being prompted for a password, and I do not >> know if this delay is related to the VBox issue. Details below. > > Running the ssh server with more debugging will probably tell you what's > happening in this area. Yup, I just have not had a chance to chase that one down, and given that it happens once per SSH session, has not been a high priority. I mentioned it in the spirit of full disclosure. >> I would chock it up to network slowness, but I >> do not see the same behavior with Firefox, xload, or xclock. > > That's not a fair comparison, because tunneling a whole X server > involves passing a lot more events than tunneling an application to run > on your local server. This is particularly painful because the X > protocols are highly serial. The VIrtualBox GUI (not the underlying VM console) should be comparable to Firefox in terms of network load. Yes, xclock and xload are much lower overhead as they are simpler apps. The difference between Firefox (measured at under 10 seconds to open the window) and VirtualBox (measured at 157 seconds to open the window) indicates that _something_ is wrong. Sorry if I was unclear. I am running 3 different VMs on this server (soon to be more :-). One is WIn 2008 server as an RDP host for a specific application, the others ar FreeBSD VMs, one for DNS and DHCP, and the other for email / webmail. I manage the underlying Win 2008 instance via RDP (and that is how the end users connect), the two FreeBSD VMs do not run a window manager at all and they are managed via SSH connections. I use the VBoxHeadless executable to run the VMs for production use. Normally I make config changes with the command line tool VBoxManage, but in this case I had a FreeBSD VM that was not booting so I needed the console (and to make various changes to the config). It is running the VBox management GUI on the physical layer server that I am having fits with. > Is there any particular reason you don't let the X server run remotely > and attach to it with something more latency-friendly, like vnc? I would > expect that to work vastly better on any OS, just because you get X > (specifically, its tendency to head-of-line blocking) out of its own way. The short answer to why X11 via SSH and not VNC for the management is that I have not found a very clean way to have the VNC service running for root without manual intervention to start it. Yes, I know I could script it, but that adds one additional layer that needs to be supported. P.S. I did get my VM repaired, very slowly and painfully, but I still need to track down the VBox GUI issue. -- {1-2-3-4-5-6-7-} Paul Kraus -> Principal Consultant, Business Information Technology Systems -> Deputy Technical Director, LoneStarCon 3 (http://lonestarcon3.org/) -> Sound Coordinator, Schenectady Light Opera Company ( http://www.sloctheater.org/ ) -> Technical Advisor, Troy Civic Theatre Company -> Technical Advisor, RPI Players ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Odd X11 over SSH issue
Paul Kraus writes: > I am seeing very poor response time running the VitrualBox GUI via X11 > tunneled over SSH via the Internet. The issue _appears_ to be limited > to the VBox GUI as Firefox is reasonable. I am well aware of the > latency issues tunneling X11 over SSH across the Internet, but that is > what we are stuck with for the moment. The server is running FreeBSD 9 > and is patched as of about 4 weeks ago. > > Observations: > > 1. When I first SSH into the box I see a long delay after the SSH > tunnel is setup before being prompted for a password, and I do not > know if this delay is related to the VBox issue. Details below. Running the ssh server with more debugging will probably tell you what's happening in this area. > 2. When I fire up VirtualBox it takes _minutes_ before the window > opens and each action (drawing contents, mouse clicks) takes > additional _minutes_. Looking at the VirtualBox process with truss I > see many, many errors of the form: > > read(7,0x80193a02c,4096) ERR#35 'Resource temporarily > unavailable' > > where fd 7 is a socket. This could be a red herring. Or not. But you can't tell without tracing down exactly what the socket is, and what is expected to be read from it. Probably not the first path worth exploring, although you may need to go there eventually. > I would chock it up to network slowness, but I > do not see the same behavior with Firefox, xload, or xclock. That's not a fair comparison, because tunneling a whole X server involves passing a lot more events than tunneling an application to run on your local server. This is particularly painful because the X protocols are highly serial. Is there any particular reason you don't let the X server run remotely and attach to it with something more latency-friendly, like vnc? I would expect that to work vastly better on any OS, just because you get X (specifically, its tendency to head-of-line blocking) out of its own way. Be well. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Odd X11 over SSH issue
On Fri, Nov 23, 2012 at 1:01 PM, Adam Vande More wrote: > On Fri, Nov 23, 2012 at 11:43 AM, Paul Kraus wrote: >> >> I am seeing very poor response time running the VitrualBox GUI via X11 >> tunneled over SSH via the Internet. The issue _appears_ to be limited >> to the VBox GUI as Firefox is reasonable. I am well aware of the >> latency issues tunneling X11 over SSH across the Internet, but that is >> what we are stuck with for the moment. The server is running FreeBSD 9 >> and is patched as of about 4 weeks ago. > > Start it with "--graphicssystem native" Tried it, did not make any noticeable difference, still over a minute to open the window, but thanks for the suggestion. VBox is version 4.1.22_OSE. -- {1-2-3-4-5-6-7-} Paul Kraus -> Principal Consultant, Business Information Technology Systems -> Deputy Technical Director, LoneStarCon 3 (http://lonestarcon3.org/) -> Sound Coordinator, Schenectady Light Opera Company ( http://www.sloctheater.org/ ) -> Technical Advisor, Troy Civic Theatre Company -> Technical Advisor, RPI Players ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Odd X11 over SSH issue
On Fri, Nov 23, 2012 at 11:43 AM, Paul Kraus wrote: > I am seeing very poor response time running the VitrualBox GUI via X11 > tunneled over SSH via the Internet. The issue _appears_ to be limited > to the VBox GUI as Firefox is reasonable. I am well aware of the > latency issues tunneling X11 over SSH across the Internet, but that is > what we are stuck with for the moment. The server is running FreeBSD 9 > and is patched as of about 4 weeks ago. > Start it with "--graphicssystem native" -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Odd X11 over SSH issue
I am seeing very poor response time running the VitrualBox GUI via X11 tunneled over SSH via the Internet. The issue _appears_ to be limited to the VBox GUI as Firefox is reasonable. I am well aware of the latency issues tunneling X11 over SSH across the Internet, but that is what we are stuck with for the moment. The server is running FreeBSD 9 and is patched as of about 4 weeks ago. Observations: 1. When I first SSH into the box I see a long delay after the SSH tunnel is setup before being prompted for a password, and I do not know if this delay is related to the VBox issue. Details below. 2. When I fire up VirtualBox it takes _minutes_ before the window opens and each action (drawing contents, mouse clicks) takes additional _minutes_. Looking at the VirtualBox process with truss I see many, many errors of the form: read(7,0x80193a02c,4096) ERR#35 'Resource temporarily unavailable' where fd 7 is a socket. I would chock it up to network slowness, but I do not see the same behavior with Firefox, xload, or xclock. An xterm is even pretty snappy. Timing firefox, it takes under 10 seconds to draw the window and fill it. It takes about 2 to 3 seconds to draw the menu after clicking on the menu widget. With VirtualBox is takes _minutes_ for every action, so it is clearly a call that VirtualBox is making, but I can't figure it out from the truss output. The VirtualBox GUI works fine when run on the console or on the local network (not via SSH). I have a local system that I think is configured the same way (but much slower hardware) and the VirtualBox GUI is reasonable via SSH about 10-20 seconds to open the window and 5-10 second response time to mouse clicks). It is only when it is tunneled over SSH via the Internet that the problem appears. Details below. Any suggestions where to look ? Or am I barking up the wrong tree ? {1-2-3-4-5-6-7-} SSH details: Mini1:~ user$ ssh -X -C -v root@a.b.c.d OpenSSH_5.2p1, OpenSSL 0.9.8r 8 Feb 2011 debug1: Reading configuration data /etc/ssh_config debug1: Connecting to a.b.c.d [a.b.c.d] port 22. debug1: Connection established. debug1: identity file /Users/user/.ssh/identity type -1 debug1: identity file /Users/user/.ssh/id_rsa type -1 debug1: identity file /Users/user/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p2_hpn13v11 FreeBSD-20110503 debug1: match: OpenSSH_5.8p2_hpn13v11 FreeBSD-20110503 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.2 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-md5 z...@openssh.com debug1: kex: client->server aes128-ctr hmac-md5 z...@openssh.com debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'a.b.c.d' is known and matches the RSA host key. debug1: Found key in /Users/user/.ssh/known_hosts:9 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /Users/user/.ssh/identity debug1: Trying private key: /Users/user/.ssh/id_rsa debug1: Trying private key: /Users/user/.ssh/id_dsa debug1: Next authentication method: keyboard-interactive Password: debug1: Enabling compression at level 6. debug1: Authentication succeeded (keyboard-interactive). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessi...@openssh.com debug1: Entering interactive session. Warning: untrusted X11 forwarding setup failed: xauth key data not generated Warning: No xauth data; using fake authentication data for X11 forwarding. debug1: Requesting X11 forwarding with authentication spoofing. Last login: Fri Nov 23 11:20:26 2012 from e.f.g.h FreeBSD 9.0-RELEASE-p3 (GENERIC) #0: Tue Jun 12 02:52:29 UTC 2012 {1-2-3-4-5-6-7-} VBox Details (from truss): 10709: socket(PF_INET,SOCK_STREAM,6) = 7 (0x7) 10709: fcntl(7,F_SETFD,FD_CLOEXEC) = 0 (0x0) 10709: setsockopt(0x7,0x6,0x1,0x7fffc578,0x4,0x2) = 0 (0x0) 10709: setsockopt(0x7,0x,0x8,0x7fffc578,0x4,0x2) = 0 (0x0) 10709: connect(7,{ AF_INET 127.0.0.1:6010 },16) = 0 (0x0) 10709: getpeername(7,{ AF_INET 127.0.0.1:6010 },0x7fffc2d4) = 0 (0x0) 10709: __sysctl(0x7fffc2f0,0x2,0x7fffc340,0x7fffc2e8,0x0,0x0) = 0 (0x0) 10709: access("/root/.Xauthority",4) = 0 (0x0) 10709: open("/root/.Xauthority",O_RDONLY,0666) = 8 (0x8) 10709: fstat(8,{ mode=-rw--- ,inode=131090,size=199,blksize
Re: ssh issue
> On Tue, Nov 25, 2003 at 06:38:07PM -0700, David Bear wrote: > > running 4.7-RELEASE.. I'm trying to setup ssh pubkey auth and its not > > working.. > > > > I put my pub key in ~/.ssh/authorized_keys from system A > > > > On system B edited /etc/ssh/sshd_config with > > == > > PubkeyAuthentication yes > > AuthorizedKeysFile .ssh/authorized_keys > > PasswordAuthentication no > > = > > > > I chmod'd my .ssh dir as 700 on system A and B. Then restart sshd on > > system B explicitly using -f /etc/ssh/sshd_config . Ok, it sounds like you are putting the 'config' on the server side, not the client. I hope I am assuming correctly. Here is a snip from my 'config' on my client side. Note that I have two entries. Depending which network I am connected to, most of the time I can connect just using the servers hostname, and other times, must type in the entire domain name. Having an entry using each connection method (ip, hostname or FQDN) is important: ---snip--- Host host.northnetworks.ca User steve Compression no Protocol 2 RSAAuthentication yes StrictHostKeyChecking no ForwardAgent yes ForwardX11 no IdentityFile /home/steve/.ssh/xxx_dsa Host host User steve Compression no Protocol 2 RSAAuthentication yes StrictHostKeyChecking no ForwardAgent yes ForwardX11 no IdentityFile /home/steve/.ssh/xxx_dsa ---/snip--- Here's another site you can have a quick look at: http://ww3.northnetworks.ca/docs/ssh_key_auth Steve > > > > the ssh'ing into system B I'm still prompted for a password. > > > > I'm lost. Any advice. > > There are 2 ways I know to do this and the following URL shows you haw > to do both. BTW, if the remote server disallows passwordless logins it > doesn't mater how hard you try. > > http://www-uxsup.csx.cam.ac.uk/pwf-linux/intro/remote.passwordless.html > > sure it's focused on linux but it'll work just the same on freeBSD ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ssh issue
On Tue, Nov 25, 2003 at 06:38:07PM -0700, David Bear wrote: > running 4.7-RELEASE.. I'm trying to setup ssh pubkey auth and its not > working.. > > I put my pub key in ~/.ssh/authorized_keys from system A > > On system B edited /etc/ssh/sshd_config with > == > PubkeyAuthentication yes > AuthorizedKeysFile .ssh/authorized_keys > PasswordAuthentication no > = > > I chmod'd my .ssh dir as 700 on system A and B. Then restart sshd on > system B explicitly using -f /etc/ssh/sshd_config . > > the ssh'ing into system B I'm still prompted for a password. > > I'm lost. Any advice. There are 2 ways I know to do this and the following URL shows you haw to do both. BTW, if the remote server disallows passwordless logins it doesn't mater how hard you try. http://www-uxsup.csx.cam.ac.uk/pwf-linux/intro/remote.passwordless.html sure it's focused on linux but it'll work just the same on freeBSD -- Jerry M. Howell II ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ssh issue
David Bear <[EMAIL PROTECTED]> writes: > running 4.7-RELEASE.. I'm trying to setup ssh pubkey auth and its not > working.. > > I put my pub key in ~/.ssh/authorized_keys from system A > > On system B edited /etc/ssh/sshd_config with > == > PubkeyAuthentication yes > AuthorizedKeysFile .ssh/authorized_keys > PasswordAuthentication no > = > > I chmod'd my .ssh dir as 700 on system A and B. Then restart sshd on > system B explicitly using -f /etc/ssh/sshd_config . > > the ssh'ing into system B I'm still prompted for a password. You have a public/private key pair on system A. You will be using that pair to log in to system B. B needs to have the key in its authorized_keys file. It sounds like you actually did that on A. If I'm misunderstanding, then maybe you can post a bit more detail to make things clear. But more likely, you'll get the answer just by running ssh with more verbosity (-v options). Good luck. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ssh issue
* David Bear: > I put my pub key in ~/.ssh/authorized_keys from system A [...] the > ssh'ing into system B I'm still prompted for a password. The public key must be added to the system you're logging into. I wrote a [1]script to automate this process. Cheers, -- Jean-Baptiste Quenot http://caraldi.com/jbq/ [1] http://caraldi.com/jbq/scripts/#ssh-add-key pgp0.pgp Description: PGP signature
ssh issue
running 4.7-RELEASE.. I'm trying to setup ssh pubkey auth and its not working.. I put my pub key in ~/.ssh/authorized_keys from system A On system B edited /etc/ssh/sshd_config with == PubkeyAuthentication yes AuthorizedKeysFile .ssh/authorized_keys PasswordAuthentication no = I chmod'd my .ssh dir as 700 on system A and B. Then restart sshd on system B explicitly using -f /etc/ssh/sshd_config . the ssh'ing into system B I'm still prompted for a password. I'm lost. Any advice. -- David Bear phone: 480-965-8257 fax:480-965-9189 College of Public Programs/ASU Wilson Hall 232 Tempe, AZ 85287-0803 "Beware the IP portfolio, everyone will be suspect of trespassing" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Yet another ssh issue
Dan, You are correct, i do get that error. Ill reinstall lsof and see the outcome. Thanks for the input. ROger To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Yet another ssh issue
On Thu, Jul 18, 2002 at 08:00:27AM +0900, Roger Williams wrote: > After upgrading to 4.6-RELEASE-p1 im getting the following line when I run > lsof. Can someone explain itshould I be concerned? Most times when > the server is busy connecting with ssh is a real "PAIN". > > Any ideas? > > > sshd 41268root5u sockcan't read protocol switch from 0x Did you update your version of lsof? I just ran it again for the first time since upgrading from 4.6-RELEASE to 4.6-RELEASE-p2, and got this warning: lsof: WARNING: compiled for FreeBSD release 4.6-RELEASE; this is 4.6-RELEASE-p2. (You will probably need to run "lsof 2>&1 | less" to catch the message, if it's there.) After upgrading (actually, deinstalling then rebuilding), the message goes away. I haven't seen the message you report, though, so this may just be a red herring. Gotta be worth a shot, though. Dan -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: 3D73 AF47 D448 C5CA 88B4 0DCF 849C 1C33 3C48 2CDC _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Yet another ssh issue
After upgrading to 4.6-RELEASE-p1 im getting the following line when I run lsof. Can someone explain itshould I be concerned? Most times when the server is busy connecting with ssh is a real "PAIN". Any ideas? sshd 41268root5u sockcan't read protocol switch from 0x Roger To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message