Bug#409531: nbd-server: timeout option not very useful

2008-10-10 Thread Vagrant Cascadian
over the last year on several occasions, i've seen folks spend a couple
of hours debugging this option and coming to the same results ... it
times out weather it's being used or not.

the -a timeout option is just plain broken.

would it be possible to either disable this option entirely, or at the
very least, document that it's broken and recommend using keepalive
timeouts instead in the man page?

thanks for maintaining nbd!

live well,
  vagrant



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#409531: nbd-server: timeout option not very useful

2007-05-28 Thread Petter Reinholdtsen

According to
https://sourceforge.net/tracker/index.php?func=detail&aid=819235&group_id=13229&atid=113229
 >
and the tcp(7) manual page, the nbd server should disconnect the
connection after 2 hours 11 minutes if the client fail to respond to
tcp keepalive requests.  The keepalive feature was implemented in
2003, and is present in the Debian package.

Is the keepalive feature not working as it should?  I guess the
timeout should be removed if it isn't working, and we should get the
keepalive feature working instead.

Happy hacking,
-- 
Petter Reinholdtsen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#409531: nbd-server: timeout option not very useful

2007-05-27 Thread Ronny Aasen

the workaround is just to have the machine running an nbd-client make
nbd accesses periodically just to keep the connection alive... but
that's kind of ugly.


I have tried this. 
basicaly i ran nbd-server using  -a 600  so it would timeout after 10 minutes
The nbd-client connects and working, sitting idle. 


then i had a script running on the client that did a   dd if=/dev/nbd0 
of=/dev/null every 30 second.
so it read the whole device once every 30 secs.

it still did timeout after 600 sec.

must the device be written to for the timeout to reset ? 


Regards
Ronny Aasen






--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#409531: nbd-server: timeout option not very useful

2007-02-04 Thread Vagrant Cascadian
On Sun, Feb 04, 2007 at 08:45:15PM +0100, Wouter Verhelst wrote:
> On Sat, Feb 03, 2007 at 11:54:49AM -0800, Vagrant Cascadian wrote:
> > when using nbd-server with the "-a timeout" option, it will often
> > disconnect running nbd-client instances that have merely been inactive
> > for a while. it would be much, much more useful if it implemented some
> > sort of "ping" to determine if the nbd-client instance is still there,
> > just not very active.
> > 
> > the workaround is just to have the machine running an nbd-client make
> > nbd accesses periodically just to keep the connection alive... but
> > that's kind of ugly.
> 
> Or just do not use it at all. nbd-server does set the SO_KEEPALIVE
> socket option, which will do such keepalive requests every once in a
> while.  However, for that to kick in, it takes two hours (by default),
> and then you still need a number of probes before it is actually
> disconnected and the server killed.

hmmm... i'm not sure i understand you here.

are you saying that nbd-server instances disconnect if there is no
nbd-client process connecting to it after some period of time? i've seen
nbd-server instances run for days without an nbd-client connected to
them.

i would like for some sort of idle timeout mechanism, so that an
nbd-server instance doesn't indefinitely consume resources to no
purpose. if there's a way to get behavior like that without using the
"-a timeout", please let me know.
 
> Anyhow, if you want to write a patch that makes the -a option more
> useful, feel free... but that would probably also require a kernel
> patch, which I don't maintain.

and well over my head...

thanks for your work and time.

live well,
  vagrant


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#409531: nbd-server: timeout option not very useful

2007-02-04 Thread Wouter Verhelst
On Sat, Feb 03, 2007 at 11:54:49AM -0800, Vagrant Cascadian wrote:
> Package: nbd-server
> Version: 1:2.8.7-3
> Severity: normal
> 
> when using nbd-server with the "-a timeout" option, it will often
> disconnect running nbd-client instances that have merely been inactive
> for a while. it would be much, much more useful if it implemented some
> sort of "ping" to determine if the nbd-client instance is still there,
> just not very active.
> 
> the workaround is just to have the machine running an nbd-client make
> nbd accesses periodically just to keep the connection alive... but
> that's kind of ugly.

Or just do not use it at all. nbd-server does set the SO_KEEPALIVE
socket option, which will do such keepalive requests every once in a
while.  However, for that to kick in, it takes two hours (by default),
and then you still need a number of probes before it is actually
disconnected and the server killed.

Anyhow, if you want to write a patch that makes the -a option more
useful, feel free... but that would probably also require a kernel
patch, which I don't maintain.

-- 
 Home is where you have to wash the dishes.
  -- #debian-devel, Freenode, 2004-09-22


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#409531: nbd-server: timeout option not very useful

2007-02-03 Thread Vagrant Cascadian
Package: nbd-server
Version: 1:2.8.7-3
Severity: normal

when using nbd-server with the "-a timeout" option, it will often
disconnect running nbd-client instances that have merely been inactive
for a while. it would be much, much more useful if it implemented some
sort of "ping" to determine if the nbd-client instance is still there,
just not very active.

the workaround is just to have the machine running an nbd-client make
nbd accesses periodically just to keep the connection alive... but
that's kind of ugly.

live well,
  vagrant

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-vserver-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages nbd-server depends on:
ii  debconf [debconf-2.0]   1.5.11   Debian configuration management sy
ii  libc6   2.3.6.ds1-10 GNU C Library: Shared libraries
ii  libglib2.0-02.12.4-2 The GLib library of C routines

nbd-server recommends no packages.

-- debconf information excluded


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]