Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #12014
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Newsgroups | comp.os.linux.misc |
| Subject | weirdness with TCP timeouts? |
| Date | 2014-09-08 11:25 +0100 |
| Organization | albasani.net |
| Message-ID | <luk078$pfl$1@news.albasani.net> (permalink) |
I have googled my socks off, but cant find this exact problem mentioned anywhere. So here goes with a summary. For multifarious reasons I am bringing up a new desktop based on MINT 17 MATE Qiana. Nice release. But that's bye the bye. Most stuff works well - better than 14 - and what was obscure was sorted by googling .. I ended up with three problems two solved by workarounds and one I cant get a handle on. (the "I have an active printjob icon gets stuck in the notification area if a networked printer is in use. Solved by not having the print monitor daemon running at all) The second issue was that ssh sessions to my remote server were timing out. They never used to, but I pulled the ssh keepalive down to a couple of minutes and now the session stays up. The third issue I cant get around is that when accessing news.albanasi.net/119 as I do to chat here, Thunderbird is ALSO experiencing some weirdness. IF I leave Thunderbird alone, it collects all the headers automatically, and then I click on an article to retrieve the actual post. Except that it nearly always fails on the first attempt, and never on any subsequent ones. The message is 'connection refused'.. Now I may be guilty of some leap of conclusions that the data doesn't warrant, but it seems to me that perhaps all of these issues are related to a new kernel with maybe a different way of handling sockets than the old. That is in some way sockets are being closed inside the kernel in ways they shouldn't be. And applications are not being notified that they have closed. IN short my fevered imagination is considering the possibility that TCP timeouts in the kernel have changed in unexpected ways, so that connections that used to exist, have been silently dropped. 3.13.0-24 is the current kernel version. (I did have one other massively irritating issue with networking, and that was unbelievably slow NFS mounting, but that proved to be an NFS4 connections being attempted against an NFS3 server. Solved by adding -o nfsvers=3 to the mount scripts.) Any light that can be shed on this gratefully appreciated The problem is of course that with the jump from mint 14 to 17, not only has the kernel changed, but my hardware and the applications, so it's hard to know where to look. I would remark that apart from this and a few other issues that are understood and accepted and are down to hardware limitations (being addressed with a credit card) and a few things that are getting a bit too 'make it simple for noobs' for my taste, that this is the best linux distro I have ever loaded up. In terms of 'all the tools I need for the work I do, and no eye candy that I didn't pick myself'. So I am keen to get it tuned up to my taste. -- Everything you read in newspapers is absolutely true, except for the rare story of which you happen to have first-hand knowledge. – Erwin Knoll
Back to comp.os.linux.misc | Previous | Next — Next in thread | Find similar | Unroll thread
weirdness with TCP timeouts? The Natural Philosopher <tnp@invalid.invalid> - 2014-09-08 11:25 +0100
Re: weirdness with TCP timeouts? Tim Watts <tw_usenet@dionic.net> - 2014-09-08 17:35 +0100
Re: weirdness with TCP timeouts? The Natural Philosopher <tnp@invalid.invalid> - 2014-09-08 17:54 +0100
Re: weirdness with TCP timeouts? The Natural Philosopher <tnp@invalid.invalid> - 2014-09-08 18:06 +0100
Re: weirdness with TCP timeouts? Johnny <johnny@invalid.net> - 2014-09-08 13:25 -0500
Re: weirdness with TCP timeouts? The Natural Philosopher <tnp@invalid.invalid> - 2014-09-08 19:27 +0100
Re: weirdness with TCP timeouts? Chick Tower <c.tower@deadspam.com> - 2014-09-19 02:33 +0000
Re: weirdness with TCP timeouts? The Natural Philosopher <tnp@invalid.invalid> - 2014-09-19 06:30 +0100
csiph-web