similar to: ssh-keyscan hangs in close_wait state

Hi, I''m running into a strange issue where one mongrel will sometimes develop hundreds of CLOSE_WAIT TCP connections, mostly to apache (I think -- see sample lsof output below). I haven''t had a chance to get the mongrel with this behavior into USR1 debug mode yet. I didn''t catch it in time. This happens a couple times a day on average at seemingly random times.

* cross posted to the mongrel mailing list* Hi, I''m running into a strange issue where one mongrel will sometimes develop hundreds of CLOSE_WAIT TCP connections, mostly to apache (I think -- see sample lsof output below). I haven''t had a chance to get the mongrel with this behavior into USR1 debug mode yet. I wrote a little loop below that will catch it next time. This

Hello list Our central fileserver is a Samba 3.0.25b on Solaris 9 and has 10'000 users (several hundreds at the same time). This week it died on us and when I inspected the machine, it was out of 8GB Memory and 16GB Swap because thousands of smbd processes were running. netstat -na showed that many hundreds of connections to port 445 were in CLOSE_WAIT state. We first thought it could be

Hello! I can't find the cause of the above problem. Some smbd processes stuck in close_wait state and some file locks remain behind too. /any clue would be apreciated Attila /

Hi folks I know that has, to some degree, been run over the past year in different ways, but, I may have yet another instance of an issue on this. The puppetmaster system and the puppet system are both running 0.24.7-r1, on a gentoo system. Other puppet systems are running 0.24.4. The puppet system (not the puppetmaster system) that is running 0.24.7-r1 is showing multiple close_wait

https://bugzilla.mindrot.org/show_bug.cgi?id=3746 Bug ID: 3746 Summary: ssh-keyscan output format is not compatible with ssh-keygen -s Product: Portable OpenSSH Version: 9.2p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: ssh-keyscan

===== Ladies/Gents, "ssh-keyscan.c" can't be linked statically against "libssh.a". You end up with `fatal()' being doubly defined. The patch below deletes the new "ssh-keyscan.c:fatal()" function and and restores the "ssh-keyscan.c:fatal_callback()" function with modifi- cations. The problem that both attempt to alleviate is the setting of the

https://bugzilla.mindrot.org/show_bug.cgi?id=1213 --- Comment #57 from Daniel Richard G. <skunk at iSKUNK.ORG> --- Okay, rolling with git master 86936ec2. Now, ssh-keyscan isn't erroring out; instead, it's... hanging. I'm seeing this behavior crop up pretty consistently after running for several minutes. And it's wedged pretty tight, too---nothing happens even after letting

https://bugzilla.mindrot.org/show_bug.cgi?id=1213 --- Comment #50 from Daniel Richard G. <skunk at iSKUNK.ORG> --- Okay, tried again with your patch. Here's what I see: [...] # A.B.C.46 SSH-1.99-OpenSSH_4.2 # A.B.C.47 SSH-1.99-OpenSSH_4.2 # A.B.C.47 SSH-1.99-OpenSSH_4.2 # A.B.C.47 SSH-1.99-OpenSSH_4.2 # A.B.C.48 SSH-1.99-OpenSSH_4.2 # A.B.C.48

I have a network without a network connection to other networks. But a socks server is dual homed between it and other networks. I can use socks to ssh to other networks. I use ProxyCommand with the socks aware connect.c program to connect out. All works great. I discovered while trying to use the ssh-keyscan program that it does not use the ProxyCommand configuration. At least in my testing

https://bugzilla.mindrot.org/show_bug.cgi?id=3581 Bug ID: 3581 Summary: ssh-keyscan fails with `fdlim_get: bad value` with large file descriptor limit due to type confusion Product: Portable OpenSSH Version: 9.3p1 Hardware: ARM64 OS: Mac OS X Status: NEW Severity: enhancement

Hello all, Tested the latest snapshot. ssh-keyscan seems to have gone in. :) Two issues about it (patched): 1) the man pages aren't installed, only uninstalled 2) RH spec file (and the others no doubt..) won't include it. General observations: for RSA keys only?, kinda obsoletes contrib/make-ssh-known-hosts*. -- Pekka Savola "Tell me of difficulties surmounted,

http://bugzilla.mindrot.org/show_bug.cgi?id=126 Summary: ssh-keyscan hangs or crashes accessing Sun ssh host Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Miscellaneous AssignedTo: openssh-unix-dev at mindrot.org

ssh-keyscan may, under very specific circumstances, be vulnerable to something akin to a buffer overflow. It's probably impossible to exploit, though, if only because ssh-keyscan is not usually run on very large untrusted input files. ssh-keyscan uses an fgets() wrapper that uses an unsigned int to keep track of the length of a buffer holding the current line. On machines with sufficient

https://bugzilla.mindrot.org/show_bug.cgi?id=3163 Bug ID: 3163 Summary: teach ssh-keyscan to use ssh_config (plus options like ProxyJump) Product: Portable OpenSSH Version: 7.4p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component:

On Mon, 27 Feb 2023, Keine Eile wrote: > Hi ML members, > > is there a reason, why ssh-keyscan does not use Host definitions from > .ssh/config but does only relys on DNS host names? I have a quite long list of > host names and a not that well maintained name server. Mostly to keep ssh-keyscan simple. ssh_config contains a lot more options than Host/Hostname that we'd need to

http://bugzilla.mindrot.org/show_bug.cgi?id=1213 Summary: ssh-keyscan exits in mid-way Product: Portable OpenSSH Version: 4.3p2 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Miscellaneous AssignedTo: bitbucket at mindrot.org ReportedBy: tryponraj at

https://bugzilla.mindrot.org/show_bug.cgi?id=1971 Bug #: 1971 Summary: ssh-keyscan should default to ecdsa or ecdsa,rsa Classification: Unclassified Product: Portable OpenSSH Version: 5.9p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh-keyscan

hi all, I got "xmalloc: out of memory" when i used ssh-keyscan to a remote host that is using SSH protocol 2 and only protocol 2 (no fallback to SSH protocol 1). Looks to me more like ssh-keyscan doesn't talk SSH protocol 2 to the server. Please help. Here is the exact error: # /usr/local/bin/ssh-keyscan -v miad_1 # miad_1 SSH-2.0-OpenSSH_3.0.2p1 xmalloc: out of memory

https://bugzilla.mindrot.org/show_bug.cgi?id=2605 Bug ID: 2605 Summary: ssh-keyscan generates errors in /var/log/secure Product: Portable OpenSSH Version: 6.4p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh-keyscan Assignee: