Re: problem with ssh3.1 on solaris 2.7
From: Betty (betty_cross@mapinfo.com)Date: 05/09/02
- Next message: Julian White: "IPSEC for certain traffic"
- Previous message: Phil Camus: "Kerberos support"
- In reply to: Richard E. Silverman: "Re: problem with ssh3.1 on solaris 2.7"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: betty_cross@mapinfo.com (Betty) Date: 9 May 2002 05:50:36 -0700
slade@shore.net (Richard E. Silverman) wrote in message news:<m1lznzafowb.fsf@syrinx.oankali.net>...
> >>>>> "BC" == Betty <betty_cross@mapinfo.com> writes:
>
> BC> I installed and had it working. Then I edited the sshd_config
> BC> file to attempt to get sftp working - I changed the path to the
> BC> sftp-server. I did a kill -HUP on sshd after the edit and can no
> BC> longer ssh in ...
>
> BC> ssh: connect to address 198.242.23.194 port 22: Connection refused
>
> sshd is not running.
>
> BC> nor does sftp work.
>
> Of course not, since sftp runs over SSH and that's not working.
>
> You may have messed up the sshd_config file format when editing it, so
> that sshd would not restart. Another possible problem is that if you
> start sshd without the full pathname on the command line, it cannot
> restart via SIGHUP since it doesn't know where its executable is to
> re-exec it.
I don't think I messed up the sshd_config file. When I do sshd -d,
I get the message: ld.so.1: rpm: fatal: relocation error: file
/usr/local/lib/libz.so:
symbol __register_frame_info: referenced symbol not found
Strangely enough, I posted about the same message when I installed
on a Solaris 2.6 machine. A search around the web found the following
in the FAQ of http://www.gzip.org/zlib
1. Problem with register_frame_info on Solaris
After installing zlib 1.1.4 on Solaris 2.6, running applications using
zlib generates an error such as:
ld.so.1: rpm: fatal: relocation error: file /usr/local/lib/libz.so:
symbol __register_frame_info: referenced symbol not found
The symbol __register_frame_info is not part of zlib, it is generated
by the C compiler (cc or gcc). You must recompile applications using
zlib which have this problem. This problem is specific to Solaris. See
Sunfreeware for Solaris versions of zlib 1.1.4 and applications using
zlib.
So, I'm guessing I need to somehow get the opensssh souce code to
this machine that I can no longer sftp or ssh to and try to compile
it. I've installed on serveral Solaris 8 machines and have not had
this problem -so I can't help but wonder if it isn't a problem with
the openssh3.1 packages for Solaris 6 and Solaris 7 from the
sunfreeware site - although, I don't see where anyone else has had
this problem.
- Next message: Julian White: "IPSEC for certain traffic"
- Previous message: Phil Camus: "Kerberos support"
- In reply to: Richard E. Silverman: "Re: problem with ssh3.1 on solaris 2.7"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|