SSH slow/unresponsive in Mint 8

Bug #515707 reported by wight13
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Linux Mint
Triaged
Undecided
Husse

Bug Description

I have just recently gotten into NoMachine NX and after installing it on several boxes running Linux Mint 6, 7, and now 8; I have found that on Mint 7 and 8 there is a problem where at random intervals NoMachine becomes unresponsive. I have already replaced all of my Mint 7 installs with Mint 8 due to other issues I was never able to find a resolution to however on the Mint 8 installs I have narrowed the problem down to SSH. On the LAN, using no encryption, NoMachine has no problems, however, I have discovered that even a SSH terminal session becomes unresponsive to text input. It seems if you wait long enough your keystrokes do eventually go through.

I have also found a temporary work around that involves pinging an outside server or even the gateway (router) at .2 - 1 second intervals improves responsiveness. 1 second intervals feels sluggish and any interval greater than 1 second gets fairly inconsistent response times. However, .2 second intervals feels almost as smooth as using it under Mint 6.

Revision history for this message
Husse (husse) wrote :

There are several reports of similar behavior in Helena
This one
http://forums.linuxmint.com/viewtopic.php?f=90&t=42502
and one that has been filed as a bug, but is a bug in Nautilus and others
I'm not sure if this is a bug or a specific problem for you but it its into a general trend
Might report the nautilus one as a bug in Nautilus

Changed in linuxmint:
status: New → Triaged
Revision history for this message
wight13 (wight13) wrote : Re: [Bug 515707] Re: SSH slow/unresponsive in Mint 8
Download full text (16.1 KiB)

Husse,

Thank you for the response. I checked out the link and related links but
I don't think those issues are anything quite like what I'm
experiencing. I have migrated three systems back to Mint 6 and they are
doing fine now with all SSH related connections.

I had other issues with Mint 7 that I reported a while ago but they were
never resolved so I never upgraded to it and saw no real benefit in
doing so. Under Mint 7 I had slowness issues with Opera and NoMachine
NX. I thought perhaps NX wasn't really used that much by many casual
users but Opera, I felt, surely had some other fans like myself so I
wondered how the problem had not been found and reported sooner. The
problem turned out not to have been as obvious as I had originally
thought. Quite a few of my customers are using Bellsouth and therefor I
did not realize right away that the issue only manifested itself when
behind Bellsouth Netopia routers.

Considering this, I can understand how that issue might have slipped
past general testing but I would have thought that SSH would be pretty
widely used compared to Opera and NX and the SSH issue manifests itself
whether you are wired, wireless, on a LAN or WAN.

Mint 8 seems faster or at least more responsive than Mint 6 or 7 and the
drivers for several of my peripherals, particularly the wireless NIC in
my personal notebook and scanner support for one of my clients scanners
that was always a little buggy under Mint 6, just seemed to work better
under Mint 8. I sure would be interested in migrating to it but this SSH
thing is a show stopper.

I'm still fairly new to Linux but I'm trying to migrate clients over to
it and one of the selling points is supposed to be my ability to provide
remote tech support and off site backup. (Which, frankly, I could do
under Windows much more easily but then I've grown tired of supporting
the OS with the worst track record for security and reliability so why
would I? :).

I guess my question is now... How can I stay in the loop so as to know
when they resolve this issue or is there anything I can do (not being a
software engineer or having any money to contribute) to help?

I was somewhat disappointed that the Mint 7 issue I was experiencing
never got resolved (to my knowledge at least). At first, I couldn't
understand why it was that several machines (6 to 8) reproduced the
problem every time on multiple sites but the bug couldn't be validated
when I reported it. It was assumed that I may have mis-configured
something but merely booting from a live CD and running "sudo apt-get
install Opera" could easily reproduce the problem in my environments.
Once I discovered that it wasn't reproducible except when behind a
Netopia router, I realized why and how such a bug could make it into the
final release and why you guys were having a hard time validating it and
assuming I might have mis-configured something. I also gave up.

Aside from the one client's buggy scanner on under Mint 6, it was
working fine. I've been using Linux Mint since Mint 5 beta was released
and Mint 6 seems to be the best version thus far. It was faster than
Mint 5 with better hardware suppo...

Husse (husse)
Changed in linuxmint:
assignee: nobody → Husse (husse)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.