Re: SSH hung with an OpenSSH_6.6.1p1 -- OpenSSH_5.8p2_hpn13v11
On 3/26/2015 2:44 AM, Wu ShuKun wrote: OpenSSH_5.4p1 FreeBSD-20100308, OpenSSL 0.9.8q 2 Dec 2010 failed with Latest SSH: % ssh -V OpenSSH_6.6.1p1, OpenSSL 1.0.1l-freebsd 15 Jan 2015 Hi, The latest is 1.0.1m, no? }# ssh -V OpenSSH_6.6.1p1, OpenSSL 1.0.1m-freebsd 19 Mar 2015 What version of FreeBSD are you using ? Ssh and Openssl from the ports ? or in the base ? ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Improve your ADSL access now, breaking news from iSAT on a must have, game changing, new technology for you - MailRef#G38-1027496#
Internet Services And Technologies 26 March 2015 Improve your ADSL access now, breaking news from iSAT on a must have, game changing, new technology for you We are extremely proud to announce the release of our ADSL line monitoring and management system (ALMMS). This is a ground breaking technology that is improving ADSL access throughout South Africa. If you are using ADSL Internet access, you are relying on a Telkom ADSL line. Then there is absolutely no doubt that you need this ADSL line monitoring and management service from iSAT now. This type of product is unique in South Africa and only available from iSAT. And at only R20 a month, it really is a no-brainer. Telkom ADSL lines do not deliver a consistent performance. This is absolutely not a fault of Telkom's, it is the way that the ADSL technology works internationally, technically ADSL is known as a best effort service. And this is where ALMMS comes in, it monitors and helps keep your line stable and optimised. Your Internet connection is of course limited to the speed of your line. For example if your 10 Mbps line is only running at 1 Mbps, then your maximum Internet speed is 1 Mbps, no matter what speed connection you have. This situation is a regular occurrence on the Telkom ADSL network. If your ADSL line is not already with iSAT, get it moved today, it's an entirely painless process, and your service will not be interrupted at all. If you have other services with a different ISP, leave them as they are, they will continue working, just get the ADSL line moved now, and enable ALMMS immediately. Once ALMMS is running and it picks up any issues on your line, an email alert is sent you and a more detailed technical fault report is sent to our support team. A support incident is also automatically logged on your account in our support management system. We work directly with Telkom to get the problem resolved, and keep in touch with you along the way. Click here https://www.isat.co.za/products/adsl-line-monitoring-management-system. aspx?examples=trueMailref=G38-1027496# to see some actual examples of what ALMMS does. For an overview about ALMMS click here https://www.isat.co.za/products/adsl-line-monitoring-management-system. aspx?overview=trueMailref=G38-1027496# . For a detailed description of ALMMS click here https://www.isat.co.za/products/adsl-line-monitoring-management-system. aspx?details=trueMailref=G38-1027496# . ALMMS is making our competitors nervous, please read some common objections and our responses here https://www.isat.co.za/products/adsl-line-monitoring-management-system. aspx?objections=trueMailref=G38-1027496# For frequently asked questions about ALMMS click here https://www.isat.co.za/products/adsl-line-monitoring-management-system. aspx?faqs=trueMailref=G38-1027496# . Sign up now it will only take 5 minutes Sign up on-line (this is the quickest and easiest method, and completely secure), click here https://www.isat.co.za/ordering/adsl-line-monitoring-management-system. aspx?almms=trueMailref=G38-1027496# . Or Request a form to fill in and fax through to us, click here https://www.isat.co.za/documents/isat-almms-registration-form.pdf . It's time for change, help be part of the solution and not part of the problem. Kind Regards If you aren't using ADSL access, please forward this email on to someone who is, they will be grateful for your help. ALMMS is vital for ADSL users. And we apologise for taking up your time. Click Unsubscribe mailto:al...@isat.co.za?Subject=Unsubscribe -freebsd-stable@freebsd.org to send us a mail to remove yourself from our mailing list. If you are an ADSL user please do not unsubscribe, if you are unsure of something rather mail your questions to al...@isat.co.za ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Significant memory leak in 9.3p10?
On Thu, Mar 26, 2015 at 9:28 PM, Steven Hartland kill...@multiplay.co.uk wrote: Does vmstat -m or vmstat -z shed any light? None, as those show kernel memory usage, not user space. Looking at them anyway shows nothing unusual, consuming large amounts of memory, or disproportionate to the kernel memory shown as in-use. The list of suspects that can consume user memory without being associated with any user process is very short: some sort of anonymous, persistent shared memory object. Konstantin offered a partial list of some likely candidates in response to the initial message, including: - NO: tmpfs mounts (not used) - NO: swap-backed md disks (not used) - PROBABLY NO: sysv shared memory (believed not to be used) - MAYBE: possibly posix shared memory (unknown whether used) - MAYBE: anonymous mmap segments that have somehow got lost (i.e. file descriptor is hanging around in the kernel somewhere) -- proposed by someone off-list - MAYBE: others? Of the two remaining known possibilities, posix shared memory seems more likely than an unknown mmap bug. Unfortunately, I have not found any way to gather statistics and/or get/set limits on posix shared memory usage. Does such a method exist? Really, it would be great if there were a tool that could walk the entire list of VM blocks and generate some kind of report or statistics (like vmstat -z or vmstat -m, but for VM rather than kernel memory). As it is, we are reduced to guessing what might be going on, which is decidedly suboptimal. However, I have no idea if such a tool exists, if it is even possible to write, or (if it is) how to go about writing it. Thanks! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Significant memory leak in 9.3p10?
On 26 March 2015, at 18:02, Chris H bsd-li...@bsdforge.com wrote: On Thu, 26 Mar 2015 20:28:15 -0400 J David j.david.li...@gmail.com wrote On Thu, Mar 26, 2015 at 8:25 PM, Chris H bsd-li...@bsdforge.com wrote: As Kevin already noted; stopping firefox, and starting it again, seems the only solution. The machines in questions are servers, they do not run Firefox or any GUI. And whatever is using the memory does not show up on ps or top. Fair enough. I'm still getting caught up, on the thread. Maybe another shot in the dark. But speaking of Servers. We ran into trouble with a web server generating *enormous* error logs -- a runaway script. The result was, even tho there was far more than adequate space for the swelling log(s). Memory, and eventually Swap usage, began to climb quite steadily. Like I said; maybe a shot in the dark. But just thought I'd mention it. I just encountered the same problem on a FreeBSD 8.2-RELEASE-p3 server today. Swap was at 100% and processes were being killed. I used ps ax and killed all the processes with W status that I could. Swap usage went down to 99%. This was a production server so was forced to reboot. After the reboot, the system came back up with the same process set and zero swap used. Shortly after that a core image appeared and the root filesystem was full. The core file was about 1 GB. However, none of my processes are anywhere near that. The specific process that was dumped is only about 140 lines of C code and doesn’t have any dynamic storage used, just a couple of short character strings and one integer. The binary file is 23KB. I couldn’t take time to run gdb on it as it was affecting production. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Significant memory leak in 9.3p10?
On Thu, 26 Mar 2015 14:03:45 -0700 Kevin Oberman rkober...@gmail.com wrote On Thu, Mar 26, 2015 at 12:46 PM, J David j.david.li...@gmail.com wrote: On Mon, Mar 16, 2015 at 7:52 PM, J David j.david.li...@gmail.com wrote: On Mon, Mar 16, 2015 at 7:24 PM, Konstantin Belousov kostik...@gmail.com wrote: There are a lot of possibilities to create persistent anonymous shared memory objects. Not complete list is tmpfs mounts, swap-backed md disks, sysv shared memory, possibly posix shared memory (I do not remember which implementation is used in stable/9). If that's the explanation, how could it be detected/measured/investigated/resolved/prevented? Under ordinary circumstances, machines will go run like this for days/weeks: Mem: 549M Active, 3623M Inact, 567M Wired, 3484K Cache, 827M Buf, 3156M Free Swap: 1024M Total, 1024M Free Then, when this happens, it rapidly degrades from that to so bad that processes start getting killed for being out of swap space. These FreeBSD machines running out of swap space and dying continues to be a daily problem causing outages and unscheduled reboots. Is there really no way to even research what might be causing the problem? (Widening the cross-posting in the hopes of eliciting more help, so the brief summary of the problem orginally posted to freebsd-stable is that an unknown actor consumes all the user-space memory in the system, including swap space, to the point where processes are killed for being out of swap space, but if every process on the machine is stopped, very little of the user-space memory in use is freed. Original message with more details is here: https://lists.freebsd.org/pipermail/freebsd-stable/2015-March/081986.html .) There are no tmpfs mounts or md disks, so it would have to be one of the other causes. How can FreeBSD's use of persistent, anonymous shared memory objects be investigated, measured, or controlled so we can get a handle on this issue? This is just a shot in the dark and not a really likely one, but I have had issues with Firefox leaking memory badly. I can free the space by killing firefox and restarting it. It seems to be linked to certain web sites, probably javascript. I have not been able to confirm which one does it. It just will start growing until the system slows to a crawl as too many things are swapped out. Normally my system does not touch swap. I can confirm this -- both regular, as well as ESR. Upgrading firefox [ultimately] has little-to-no effect. I have experienced this for near 2yrs. I suspect the [firefoxes] js engine. Any one of any number of sites could/would/will cause it. As Kevin already noted; stopping firefox, and starting it again, seems the only solution. If it is in user space, top should show it under RES. -- Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org --Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Significant memory leak in 9.3p10?
On Thu, Mar 26, 2015 at 8:25 PM, Chris H bsd-li...@bsdforge.com wrote: As Kevin already noted; stopping firefox, and starting it again, seems the only solution. The machines in questions are servers, they do not run Firefox or any GUI. And whatever is using the memory does not show up on ps or top. Thanks! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: SSH hung with an OpenSSH_6.6.1p1 -- OpenSSH_5.8p2_hpn13v11
Yep. I'm upgraded via freebsd-update. and I have no idea where i'm wrong either.:-[ Is it likely I have no luck in other words? 在 2015/03/26 22:16, Mike Tancsa 写道: On 3/26/2015 2:44 AM, Wu ShuKun wrote: greeting! ssh connection failed by using a new version SSH to and old one. Below is the symptoms which on a same network. Connection is Okay with old version SSH %ssh -V OpenSSH_5.4p1 FreeBSD-20100308, OpenSSL 0.9.8q 2 Dec 2010 OpenSSH_6.6.1p1, OpenSSL 1.0.1l-freebsd 15 Jan 2015 % ssh -v 10.41.172.19 OpenSSH_6.6.1p1, OpenSSL 1.0.1l-freebsd 15 Jan 2015 Is it possible this user somehow got a package or port, or binary upgrade somehow built with OpenSSL when it was briefly broken between r280266 and r280274 ? (Trimming the other lists from this thread) ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: SSH hung with an OpenSSH_6.6.1p1 -- OpenSSH_5.8p2_hpn13v11
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 03/26/15 17:30, Wu ShuKun wrote: Yep. I'm upgraded via freebsd-update. and I have no idea where i'm wrong either.:-[ Is it likely I have no luck in other words? Can you try specifying -o KexAlgorithms diffie-hellman-group-exchange-sha1 when ssh'ing and see if that would mitigate the problem? My gut feeling is that somehow the HPN patch have broke certain key exchange negotiation steps of OpenSSH, which was not exercised in earlier versions of FreeBSD due to the lack of ECDH key exchange? Cheers, - -- Xin LI delp...@delphij.nethttps://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.1.2 (FreeBSD) iQIcBAEBCgAGBQJVFKndAAoJEJW2GBstM+ns83UQAIjsYGkaBJstCW1F/Rp1Q1mm Hg63DSYteIhOfAJ/m3M4qpfWJq3vf9ID0QjN0oPkfpKvwK35P3hgkT0y/hleRjpG YdcDqlW6Adm8ZmaI+9BdZSqga+plfXyjeyChgjXSfocT7Is+s0+zSS4km3rl91aR Jhv1uVr/gMKUTnXlCaNSDajzHpEYxaKu1ipp1OTfdwnSdoK1VpVN1dcDHFK0stts qdrFiOQWKaUXiXnfVTrGRowTBk46C429k+66YLKmYLfSj/0toiCGRlrwfCLTYFHM Uc0oGWTJbqyhd9lpf5Q90B7pvJ7sBaatvEt0i9LgyuyfZQieAX6hidgnEV5cI4nC CYfMwjXRSOChcvpBtjsC/Az+7FE0mOXN9NAmwPcQ5XO0JtipNrCKwN1oR6nG2Rk5 c1qBcc9fYZBYRwdnunEG3FlNgnzi5baoHszSoHGmkew4dbUZsTIYEknsMlP0B3BP k0RHnl/083JTDP55WR/IEJF0O0LVGnrI4UQEDq66hfNSNoLLJkMkyC95EIZpNHVo uo6TI9TP3QvJBp/iPIuIdQaux7DFD/ba1htXWwOsf4Sw2brHYyvLGfnHkFOBrFNt LkiYZf9CCsawDU+BGSn2OJCndDidLuJV4H2jtZFbJ+vo13nq0t+ZmA7ZtEOz4EMr v2DmLBOFU3jxsrAwmkhJ =HsH2 -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Significant memory leak in 9.3p10?
On Thu, 26 Mar 2015 20:28:15 -0400 J David j.david.li...@gmail.com wrote On Thu, Mar 26, 2015 at 8:25 PM, Chris H bsd-li...@bsdforge.com wrote: As Kevin already noted; stopping firefox, and starting it again, seems the only solution. The machines in questions are servers, they do not run Firefox or any GUI. And whatever is using the memory does not show up on ps or top. Fair enough. I'm still getting caught up, on the thread. Maybe another shot in the dark. But speaking of Servers. We ran into trouble with a web server generating *enormous* error logs -- a runaway script. The result was, even tho there was far more than adequate space for the swelling log(s). Memory, and eventually Swap usage, began to climb quite steadily. Like I said; maybe a shot in the dark. But just thought I'd mention it. Thanks! --Chris -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Significant memory leak in 9.3p10?
On Mon, Mar 16, 2015 at 7:52 PM, J David j.david.li...@gmail.com wrote: On Mon, Mar 16, 2015 at 7:24 PM, Konstantin Belousov kostik...@gmail.com wrote: There are a lot of possibilities to create persistent anonymous shared memory objects. Not complete list is tmpfs mounts, swap-backed md disks, sysv shared memory, possibly posix shared memory (I do not remember which implementation is used in stable/9). If that's the explanation, how could it be detected/measured/investigated/resolved/prevented? Under ordinary circumstances, machines will go run like this for days/weeks: Mem: 549M Active, 3623M Inact, 567M Wired, 3484K Cache, 827M Buf, 3156M Free Swap: 1024M Total, 1024M Free Then, when this happens, it rapidly degrades from that to so bad that processes start getting killed for being out of swap space. These FreeBSD machines running out of swap space and dying continues to be a daily problem causing outages and unscheduled reboots. Is there really no way to even research what might be causing the problem? (Widening the cross-posting in the hopes of eliciting more help, so the brief summary of the problem orginally posted to freebsd-stable is that an unknown actor consumes all the user-space memory in the system, including swap space, to the point where processes are killed for being out of swap space, but if every process on the machine is stopped, very little of the user-space memory in use is freed. Original message with more details is here: https://lists.freebsd.org/pipermail/freebsd-stable/2015-March/081986.html .) There are no tmpfs mounts or md disks, so it would have to be one of the other causes. How can FreeBSD's use of persistent, anonymous shared memory objects be investigated, measured, or controlled so we can get a handle on this issue? Thanks! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Significant memory leak in 9.3p10?
On Thu, Mar 26, 2015 at 12:46 PM, J David j.david.li...@gmail.com wrote: On Mon, Mar 16, 2015 at 7:52 PM, J David j.david.li...@gmail.com wrote: On Mon, Mar 16, 2015 at 7:24 PM, Konstantin Belousov kostik...@gmail.com wrote: There are a lot of possibilities to create persistent anonymous shared memory objects. Not complete list is tmpfs mounts, swap-backed md disks, sysv shared memory, possibly posix shared memory (I do not remember which implementation is used in stable/9). If that's the explanation, how could it be detected/measured/investigated/resolved/prevented? Under ordinary circumstances, machines will go run like this for days/weeks: Mem: 549M Active, 3623M Inact, 567M Wired, 3484K Cache, 827M Buf, 3156M Free Swap: 1024M Total, 1024M Free Then, when this happens, it rapidly degrades from that to so bad that processes start getting killed for being out of swap space. These FreeBSD machines running out of swap space and dying continues to be a daily problem causing outages and unscheduled reboots. Is there really no way to even research what might be causing the problem? (Widening the cross-posting in the hopes of eliciting more help, so the brief summary of the problem orginally posted to freebsd-stable is that an unknown actor consumes all the user-space memory in the system, including swap space, to the point where processes are killed for being out of swap space, but if every process on the machine is stopped, very little of the user-space memory in use is freed. Original message with more details is here: https://lists.freebsd.org/pipermail/freebsd-stable/2015-March/081986.html .) There are no tmpfs mounts or md disks, so it would have to be one of the other causes. How can FreeBSD's use of persistent, anonymous shared memory objects be investigated, measured, or controlled so we can get a handle on this issue? This is just a shot in the dark and not a really likely one, but I have had issues with Firefox leaking memory badly. I can free the space by killing firefox and restarting it. It seems to be linked to certain web sites, probably javascript. I have not been able to confirm which one does it. It just will start growing until the system slows to a crawl as too many things are swapped out. Normally my system does not touch swap. If it is in user space, top should show it under RES. -- Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Significant memory leak in 9.3p10?
In our case, On Thu, Mar 26, 2015 at 5:03 PM, Kevin Oberman rkober...@gmail.com wrote: This is just a shot in the dark and not a really likely one, but I have had issues with Firefox leaking memory badly. I can free the space by killing firefox and restarting it. In our case, we can log in from the console, kill every single user-mode process on the system except the init, login, and the console shell, and the memory is not recovered. Gigabytes and gigabytes user memory of it are being held by some un-findable anonymous persistent structure not linked to any process. Konstantin proposed that it was some sort of shared memory usage, but there appears to be no way to check or investigate most types of shared memory usage on FreeBSD. If it is in user space, top should show it under RES. This is definitely *not* the case. Whatever is using the memory is not associated with any user-space process, and does not show up on top or ps. It also does not appear to be SysV shared memory, as that reports: $ ipcs -m Shared Memory: T ID KEY MODEOWNERGROUP $ Also, kern.ipc.shmmax is only 512MB whereas this problem is consuming usually 8-10GB. So I guess the remaining possibilities are anonymous mmap's that are somehow not associated with any process and Posix shared memory. Are there any ways to investigate either possibility? Thanks! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Significant memory leak in 9.3p10?
On Thu, Mar 26, 2015 at 7:39 PM, The Lost Admin thelostad...@gmail.com wrote: Have you looked through the system shutdown scripts (part of init/rc) to see what happens after the uptime is printed? that might give you a lead. All of that output is printed by the kernel (see sys/kern/kern_shutdown.c), not by scripts. It happens after any shutdown scripts are run. The output from your PS seams to be much shorter than I would expect. Are you sure it included everything? For example, I would expect to see processes for cron, syslog, and normally sshd. Killed them all. Killed absolutely user process but init, login, and the shell. Memory not freed. I’ve also got a few more kernel processes that you don’t appear to have. Most notably is pagedaemon pagedaemon is on the list with pid 5. Thanks! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: SSH hung with an OpenSSH_6.6.1p1 -- OpenSSH_5.8p2_hpn13v11
Okay % ssh -v -o KexAlgorithms diffie-hellman-group-exchange-sha1 10.41.172.19 OpenSSH_6.6.1p1, OpenSSL 1.0.1l-freebsd 15 Jan 2015 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Connecting to 10.41.172.19 [10.41.172.19] port 22. debug1: Connection established. debug1: identity file /home/wsk/.ssh/id_rsa type -1 debug1: identity file /home/wsk/.ssh/id_rsa-cert type -1 debug1: identity file /home/wsk/.ssh/id_dsa type -1 debug1: identity file /home/wsk/.ssh/id_dsa-cert type -1 debug1: identity file /home/wsk/.ssh/id_ecdsa type -1 debug1: identity file /home/wsk/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/wsk/.ssh/id_ed25519 type -1 debug1: identity file /home/wsk/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.6.1_hpn13v11 FreeBSD-20140420 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p2_hpn13v11 FreeBSD-20110503 debug1: match: OpenSSH_5.8p2_hpn13v11 FreeBSD-20110503 pat OpenSSH_5* compat 0x0c00 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102430728192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP Connection closed by 10.41.172.19 % 在 2015/03/27 08:52, Xin Li 写道: On 03/26/15 17:30, Wu ShuKun wrote: Yep. I'm upgraded via freebsd-update. and I have no idea where i'm wrong either.:-[ Is it likely I have no luck in other words? Can you try specifying -o KexAlgorithms diffie-hellman-group-exchange-sha1 when ssh'ing and see if that would mitigate the problem? My gut feeling is that somehow the HPN patch have broke certain key exchange negotiation steps of OpenSSH, which was not exercised in earlier versions of FreeBSD due to the lack of ECDH key exchange? Cheers, ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Significant memory leak in 9.3p10?
On 26/03/2015 23:47, J David wrote: In our case, On Thu, Mar 26, 2015 at 5:03 PM, Kevin Oberman rkober...@gmail.com wrote: This is just a shot in the dark and not a really likely one, but I have had issues with Firefox leaking memory badly. I can free the space by killing firefox and restarting it. In our case, we can log in from the console, kill every single user-mode process on the system except the init, login, and the console shell, and the memory is not recovered. Gigabytes and gigabytes user memory of it are being held by some un-findable anonymous persistent structure not linked to any process. Konstantin proposed that it was some sort of shared memory usage, but there appears to be no way to check or investigate most types of shared memory usage on FreeBSD. Does vmstat -m or vmstat -z shed any light? Regards Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: SSH hung with an OpenSSH_6.6.1p1 -- OpenSSH_5.8p2_hpn13v11
all set are in base. and I’m using 10.1-RELEASE-p8 BTW 在 2015年3月26日，下午6:12，Mike Tancsa m...@sentex.net 写道： On 3/26/2015 2:44 AM, Wu ShuKun wrote: OpenSSH_5.4p1 FreeBSD-20100308, OpenSSL 0.9.8q 2 Dec 2010 failed with Latest SSH: % ssh -V OpenSSH_6.6.1p1, OpenSSL 1.0.1l-freebsd 15 Jan 2015 Hi, The latest is 1.0.1m, no? }# ssh -V OpenSSH_6.6.1p1, OpenSSL 1.0.1m-freebsd 19 Mar 2015 What version of FreeBSD are you using ? Ssh and Openssl from the ports ? or in the base ? ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: SSH hung with an OpenSSH_6.6.1p1 -- OpenSSH_5.8p2_hpn13v11
On 03/26/2015 21:25, Wu ShuKun wrote: Okay % ssh -v -o KexAlgorithms diffie-hellman-group-exchange-sha1 10.41.172.19 OpenSSH_6.6.1p1, OpenSSL 1.0.1l-freebsd 15 Jan 2015 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Connecting to 10.41.172.19 [10.41.172.19] port 22. debug1: Connection established. debug1: identity file /home/wsk/.ssh/id_rsa type -1 debug1: identity file /home/wsk/.ssh/id_rsa-cert type -1 debug1: identity file /home/wsk/.ssh/id_dsa type -1 debug1: identity file /home/wsk/.ssh/id_dsa-cert type -1 debug1: identity file /home/wsk/.ssh/id_ecdsa type -1 debug1: identity file /home/wsk/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/wsk/.ssh/id_ed25519 type -1 debug1: identity file /home/wsk/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.6.1_hpn13v11 FreeBSD-20140420 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p2_hpn13v11 FreeBSD-20110503 debug1: match: OpenSSH_5.8p2_hpn13v11 FreeBSD-20110503 pat OpenSSH_5* compat 0x0c00 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102430728192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP Connection closed by 10.41.172.19 % Can you try stopping sshd on the server side and run /usr/sbin/sshd -Dd then SSH in and see if the server provides a reason for disconnecting the client? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
SSH hung with an OpenSSH_6.6.1p1 -- OpenSSH_5.8p2_hpn13v11
greeting! ssh connection failed by using a new version SSH to and old one. Below is the symptoms which on a same network. Connection is Okay with old version SSH %ssh -V OpenSSH_5.4p1 FreeBSD-20100308, OpenSSL 0.9.8q 2 Dec 2010 %ssh -v 10.41.172.19 OpenSSH_5.4p1 FreeBSD-20100308, OpenSSL 0.9.8q 2 Dec 2010 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Connecting to 10.41.172.19 [10.41.172.19] port 22. debug1: Connection established. debug1: identity file /home/wsk/.ssh/id_rsa type -1 debug1: identity file /home/wsk/.ssh/id_rsa-cert type -1 debug1: identity file /home/wsk/.ssh/id_dsa type -1 debug1: identity file /home/wsk/.ssh/id_dsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p2_hpn13v11 FreeBSD-20110503 debug1: match: OpenSSH_5.8p2_hpn13v11 FreeBSD-20110503 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.4p1 FreeBSD-20100308 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY The authenticity of host '10.41.172.19 (10.41.172.19)' can't be established. RSA key fingerprint is ab:81:83:79:6a:d8:29:23:a0:51:1d:e6:f0:aa:ce:d6. Are you sure you want to continue connecting (yes/no)? --- failed with Latest SSH: % ssh -V OpenSSH_6.6.1p1, OpenSSL 1.0.1l-freebsd 15 Jan 2015 % ssh -v 10.41.172.19 OpenSSH_6.6.1p1, OpenSSL 1.0.1l-freebsd 15 Jan 2015 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Connecting to 10.41.172.19 [10.41.172.19] port 22. debug1: Connection established. debug1: identity file /home/wsk/.ssh/id_rsa type -1 debug1: identity file /home/wsk/.ssh/id_rsa-cert type -1 debug1: identity file /home/wsk/.ssh/id_dsa type -1 debug1: identity file /home/wsk/.ssh/id_dsa-cert type -1 debug1: identity file /home/wsk/.ssh/id_ecdsa type -1 debug1: identity file /home/wsk/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/wsk/.ssh/id_ed25519 type -1 debug1: identity file /home/wsk/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.6.1_hpn13v11 FreeBSD-20140420 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p2_hpn13v11 FreeBSD-20110503 debug1: match: OpenSSH_5.8p2_hpn13v11 FreeBSD-20110503 pat OpenSSH_5* compat 0x0c00 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY Connection closed by 10.41.172.19 any ideas? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: SSH hung with an OpenSSH_6.6.1p1 -- OpenSSH_5.8p2_hpn13v11
On 3/26/2015 2:44 AM, Wu ShuKun wrote: greeting! ssh connection failed by using a new version SSH to and old one. Below is the symptoms which on a same network. Connection is Okay with old version SSH %ssh -V OpenSSH_5.4p1 FreeBSD-20100308, OpenSSL 0.9.8q 2 Dec 2010 OpenSSH_6.6.1p1, OpenSSL 1.0.1l-freebsd 15 Jan 2015 % ssh -v 10.41.172.19 OpenSSH_6.6.1p1, OpenSSL 1.0.1l-freebsd 15 Jan 2015 Is it possible this user somehow got a package or port, or binary upgrade somehow built with OpenSSL when it was briefly broken between r280266 and r280274 ? (Trimming the other lists from this thread) ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
