search for: keepalives

According to the mongrel_cluster.yml file you provided, you''re starting only 14 mongrels, but in your proxy balancer config you have 30 mongrels listed on ports 21000 - 21029. In this scenario, if apache tries to proxy to any ports higher than 21014 then you''ll get a proxy error as a mongrel doesn''t exist on that port. Or am I missing something? -----Original

I''ve posted this to rails-deployment as well. I have to administer a medium size rails app (1''5 million requests each day), recently I''ve switched from lighttpd + fcgi to apache + mongrel. In the following lines I am going to describe the platform: All machines are running Debian Etch, with 4 gb ram and dual core intel32 processors. Web server runs debian''s

Hi, I got selected for beta testing SW:TOR and managed to get the installer to work on wine but it keeps crashing when I try with the launcher. It opens for a smidgen then crashes. Here's all the script I get; fixme:iphlpapi:NotifyAddrChange (Handle 0x32e604, overlapped 0x8f8d58): stub fixme:threadpool:RtlQueueWorkItem Flags 0x4 not supported fixme:winsock:WSALookupServiceBeginW (0x32e628

...ways seemed to correspond time-wise with an NBT keepalive sent by a server-level server to a connected Windows client, with the keepalive apparently correctly acknowledged by the client. First issue: The smb.conf man page states that the "keepalive=" parameter defaults to zero, and that keepalives should, in general, only be required if you are having problems. Keepalives actually default to 300 seconds (in both 2.0.7 and CVS HEAD), and the spacing between keepalives is actually typically 360 seconds (presumably smbd/process.c:timeout_processing() gets called once per minute?). Second issue...

...en when request in the config files. Furthermore (for either protocol), keepalive is only set for "interactive" connections -- it should be set (when requested) for any sort of connection. ----------------------- As an aside (as information for anyone else with the same problem), I need keepalives to keep my connections from hanging after thirty minutes due to an ISP (Cox at work) router that is masquerading IP addresses for my local network. This router apparently drops the masquerade table entries after 30 minutes of inactivity. (Then, in response to any further activity from the client...

...as of 3/14/01. Please consider this patch for inclusion in the OpenSSH main tree. This patch is based upon and includes code from the Chris Lightfoot (chris at ex-parrot.com) patch posted 2/23. The original patch from Chris is at: http://www.ex-parrot.com/~chris/openssh-patches/openssh-2.5.1p1-keepalives.patch Description: In order to keep a session active across a firewall or similar device that times out stateful connections, the client sends a SSH_MSG_NONE after X number of seconds of inactivity. Chris' original patch set this frequency to 3 minutes in the source. My patch allows this...

My expectations are probably wrong, but I had to manually kill a process to unlock a file when I think it should have killed itself. I have deadtime set to 15 and keepalive at default (300). I opened a file on my server in Excel, then shut down the machine. Hours later someone tells me the file is locked. Shouldn't keepalive have detected that the machine was off in 5 minutes?

On Tue, Nov 01, 2016 at 05:09:34PM -0700, Jeremy Allison via samba wrote: > On Tue, Nov 01, 2016 at 05:16:47PM -0500, Ed Siefker via samba wrote: > > My expectations are probably wrong, but I had to manually kill a process > > to unlock a file when I think it should have killed itself. > > > > I have deadtime set to 15 and keepalive at default (300). I opened a file on

Apologies, this may be off-topic. I''ve been wrestling with upload issues and Apache 2.2.2 / mod_proxy_balanacer / mongrel_cluster / Mongrel on Mac OS X Server 10.4.5. Typically the first upload would be fine but the next would make the mongrel instance remain running (ps state = "R") essentially locking up that instance. Apache would then eventually do: [Fri Jun 16 16:45:54

...ent: ssh AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: danfuzz at milk.com I currently have to deal with a (arguably broken) firewall which likes to drop connections that have been idle for more than a couple minutes. Unfortunately, while ssh gives me the option of using keepalives, it doesn't give me a way to set the keepalive time, and, since the default is 3 hours, it doesn't do me much good. What I'd love to see is either a KeepAliveTime option indicating a number of seconds between keepalives if KeepAlive is "on", or make KeepAlive itself take a nu...

I have set /etc/ssh/sshd_config with: KeepAlive yes ClientAliveInterval 3 However, no KeepAlive type messages seem to be sent. I've verified this by looking at the network lights, which don't flicker every 3 seconds. I am attempting to keep interactive ssh sessions alive longer. If don't type anything for about 2 minutes, the sessions close. If I run a "idle"

Hi! I am about to migrate a perdition-based IMAP/POP3 proxy to Dovecot. Unfortunately some users are behind a firewall/NAT setup which throws away seemingly idle TCP connections sooner than the established default of 24 hours (more likely after 30 minutes ...) resulting in all kinds of weird client behavior. And unfortunately? this firewall/NAT setup is outside of my control and I have no means

Hi Nithya, GlusterFS version is 3.11.0, and we use the native client of GlusterFS. Please see the below information. $gluster v info vol Volume Name: vol Type: Distributed-Replicate Volume ID: d59bd014-3b8b-411a-8587-ee36d254f755 Status: Started Snapshot Count: 0 Number of Bricks: 90 x 2 = 180 Transport-type: tcp,rdma Bricks: ... Options Reconfigured: performance.force-readdirp: false

The default for the keepalive param in 2.0.4b is 300 although the docs. suggest that the default is 0. Does anyone know why the default changed? I need to change the keepalive value to 0 as I have some users connecting via isdn and this keepalive setting will initiate an undesired phone call. I have 100+ users on the local LAN connecting to samba on HP-UX 11 and have not experience any problems

http://bugzilla.mindrot.org/show_bug.cgi?id=1307 Summary: client disconnects if ServerAlive enabled but not implemented Product: Portable OpenSSH Version: 4.3p2 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: bitbucket at

I'm not sure keepalive is working the way I think it's supposed to. Here's my test. I've got a large file (approx 1 gig) on the rsync server, and I append a character on the end to make it slightly different. I fire up rsync on the client side and everything works fine until I hit the timeout value. I have this problems when I have a timeout of below 90 seconds. I've tried

Attached is a patch to allow a user to turn on TCP keepalives for port forwarded connections. It's mainly useful when the connections to the ssh listener are coming from many different boxes, some of which crash, leaving the service on the other side of the port forwarder waiting on connections indefinitely. It creates a new option named "KeepAliveF...

Hello, I'm trying to set up a SAMBA server serving a GlusterFS volume. Everything works fine if I locally mount the GlusterFS volume (`mount -t glusterfs ...`) and then serve the mounted FS through SAMBA, but the performance is slower by a 2x/3x compared to a SAMBA server with a local ext4 filesystem. I gather that SAMBA vfs_glusterfs module can give better performance. However, as soon as I

Grandstream GXP-2000 with firmware 1.1.4.18 (beta) fixes an issue where the phone did not send rtp keepalives when on mute (resulting in disconnect from tech support hold and concalls) A side effect seems to be that Asterisk pops the following warning on the console... Jul 26 14:06:35 WARNING[31654]: rtp.c:463 ast_rtp_read: RTP Read too short Grandstream say they are not sure what it is but "it s...

https://bugzilla.mindrot.org/show_bug.cgi?id=1404 Summary: Make keepalive work properly with Cisco PIX/ASA boxes Classification: Unclassified Product: Portable OpenSSH Version: 4.7p1 Platform: Other OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: sshd AssignedTo: