Date: Wed, 7 Feb 2001 15:08:33 +0300 From: "Andrey Simonenko" <simon@comsys.ntu-kpi.kiev.ua> To: freebsd-questions@freebsd.org Subject: Re: ssh says "FATAL: Freeing block that is already freed" Message-ID: <95rhe1$2kqg$1@igloo.uran.net.ua> References: <4.3.2.7.2.20010129195433.00aa82a0@mail.cornhusker.net>
next in thread | previous in thread | raw e-mail | index | archive | help
I installed ssh-2.4.0 and can now make ssh connection to FreeBSD 4.2-STABLE, but sftp2 still gives this error. Problems was with ssh-2.1.0.pl2. Tim DeBoer <deboert@cornhusker.net> wrote in message news:4.3.2.7.2.20010129195433.00aa82a0@mail.cornhusker.net... > At 10:20 PM 1/28/01 -0800, you wrote: > >Date: Mon, 29 Jan 2001 00:06:25 +0200 > >From: Andrey Simonenko <simon@comsys.ntu-kpi.kiev.ua> > >Subject: ssh says "FATAL: Freeing block that is already freed" > > > >On my server I use FreeBSD 4.2-STABLE. When I try to connect to my server > >with ssh from another hosts (FreeBSD 3.5-STABLE and 4.0-STABLE), ssh outputs: > > > >FATAL: Freeing block that is already freed > > > >even before asking password. > > > >I can make ssh connection to any other host from my server, I can make ssh > >connection from my server to my server (i.e. ssh localhost) as well. But can't > >make ssh connection to my server from other hosts (see error message above). > > > >What is wrong with ssh/sshd? When I made upgrade to STABLE, I didn't forget > >to run mergemaster. I even recreated RSA key for host and removed keys from > >home directory. It didn't solve problem. > > > >Also I should note, that I haven't such problems when I make ssh connect from > >FreeBSD 4.2-STABLE and from OpenBSD 2.7 to FreeBSD 4.2-STABLE (not to above > >mentioned my server, to another computer). > > I'll take a SWAG at it. > Three possibilities I've experienced. > > 1) Is sshd actually running? (Don't laugh, I had this exact same problem > when I first installed FreeBSD. It disappeared after I rebooted once. For > some reason, the daemon did not start after install.) If it's not showing > up when you ps ax, then it's not running. > > 2) Your host.domain.name has changed, and the other machines can't make the > connection because the host name you're trying to connect to doesn't > resolve properly. Can you connect if you try to connect by IP address > instead of by host name? > (I run into this every time I re-do my windows machine) > > 3) I experienced a similar issue, the last time I updated the SSH server > software on my linux machines. > I needed to use a different SSH server type in my client software before I > could connect to the servers. Available choices were DataFellows, SSH > Communications, and Standard. The version of SSH produced by www.ssh.com > had been changed to require standard. > Try updating the version of SSH on your other machines maybe. (Really > shouldn't need to, but it's worth a try anyway) > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?95rhe1$2kqg$1>