解决把办法;
Key exchange failed. No compatible key exchange method. The server supports these methods: Kerberos
No compatible hostkey. The server supports these methods: null
root@N2000Server # svcadm disable ssh
root@N2000Server # /usr/lib/ssh/sshd -ddd
debug1: sshd version Sun_SSH_1.1.4
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: UNPROTECTED PRIVATE KEY FILE! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions 0711 for '/etc/ssh/ssh_host_rsa_key' are too open.
It is recommended that your private key files are NOT accessible by others.
This private key will be ignored.
bad permissions: ignore key: /etc/ssh/ssh_host_rsa_key
Could not load host key: /etc/ssh/ssh_host_rsa_key
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: UNPROTECTED PRIVATE KEY FILE! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions 0711 for '/etc/ssh/ssh_host_dsa_key' are too open.
It is recommended that your private key files are NOT accessible by others.
This private key will be ignored.
bad permissions: ignore key: /etc/ssh/ssh_host_dsa_key
Could not load host key: /etc/ssh/ssh_host_dsa_key
debug1: Bind to port 22 on ::.
Server listening on :: port 22.
debug1: Server will not fork when running in debugging mode.
Connection from 192.168.8.99 port 4810
debug1: Client protocol version 2.0; client software version nsssh2_4.0.0021 NetSarang Computer, Inc.
debug1: no match: nsssh2_4.0.0021 NetSarang Computer, Inc.
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-Sun_SSH_1.1.4
monitor debug2: Monitor pid 3130, unprivileged child pid 3131
monitor debug1: list_hostkey_types:
debug2: Waiting for monitor
monitor debug2: Monitor pid 3130, unprivileged child pid 3131
debug2: Monitor signalled readiness
debug1: use_engine is 'yes'
monitor debug1: reading the context from the child
debug1: pkcs11 engine initialized, now setting it as default for RSA, DSA, and symmetric ciphers
debug1: pkcs11 engine initialization complete
debug1: list_hostkey_types:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: aes128-ctr,aes128-cbc,arcfour,3des-cbc,blowfish-cbc,aes192-ctr,aes192-cbc,aes256-ctr,aes256-cbc
debug2: kex_parse_kexinit: aes128-ctr,aes128-cbc,arcfour,3des-cbc,blowfish-cbc,aes192-ctr,aes192-cbc,aes256-ctr,aes256-cbc
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit: en-CA,en-US,es-MX,fr-CA,zh,zh-CN,es,fr,i-default
debug2: kex_parse_kexinit: en-CA,en-US,es-MX,fr-CA,zh,zh-CN,es,fr,i-default
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: GSS-API Mechanism encoded as toWM5Slw5Ew8Mqkay+al2g==
debug1: SSH2_MSG_KEXINIT sent
debug3: kex_reset_dispatch -- should we dispatch_set(KEXINIT) here? 0 && !0
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==
debug2: kex_parse_kexinit: null
debug2: kex_parse_kexinit: aes128-ctr,aes128-cbc,arcfour,3des-cbc,blowfish-cbc,aes192-ctr,aes192-cbc,aes256-ctr,aes256-cbc
debug2: kex_parse_kexinit: aes128-ctr,aes128-cbc,arcfour,3des-cbc,blowfish-cbc,aes192-ctr,aes192-cbc,aes256-ctr,aes256-cbc
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit: en-CA,en-US,es-MX,fr-CA,zh,zh-CN,es,fr,i-default
debug2: kex_parse_kexinit: en-CA,en-US,es-MX,fr-CA,zh,zh-CN,es,fr,i-default
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit: diffie-hellman-group14-sha1,diffie-hellman-group1-sha1,diffie-hellman-group-exchange-sha1
debug2: kex_parse_kexinit: ssh-dss,ssh-rsa
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: hmac-sha1,hmac-sha1-96,hmac-md5,hmac-md5-96,hmac-ripemd160,hmac-ripemd160@openssh.com,none
debug2: kex_parse_kexinit: hmac-sha1,hmac-sha1-96,hmac-md5,hmac-md5-96,hmac-ripemd160,hmac-ripemd160@openssh.com,none
debug2: kex_parse_kexinit: none
debug2: kex_parse_kexinit: none
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: mac_init: found hmac-sha1
debug1: kex: client->server aes128-cbc hmac-sha1 none
debug2: mac_init: found hmac-sha1
debug1: kex: server->client aes128-cbc hmac-sha1 none
no common kex alg: client 'diffie-hellman-group14-sha1,diffie-hellman-group1-sha1,diffie-hellman-group-exchange-sha1', server 'gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g=='
debug1: Calling cleanup 0x405f0(0x0)
monitor debug1: child closed the communication pipe before user auth was finished
monitor debug1: Calling cleanup 0x405f0(0x0)
monitor debug1: Calling cleanup 0x405f0(0x0)
root@N2000Server # cd /etc/ssh
root@N2000Server # ls -l
total 208
-rwxr-xr-x 1 root sys 88301 Jan 22 2005 moduli
-rwxr-xr-x 1 root sys 861 Jan 22 2005 ssh_config
-rwx--x--x 1 root root 668 Mar 27 18:46 ssh_host_dsa_key
-rwxr-xr-x 1 root root 601 Mar 27 18:46 ssh_host_dsa_key.pub
-rwx--x--x 1 root root 883 Mar 27 18:46 ssh_host_rsa_key
-rwxr-xr-x 1 root root 221 Mar 27 18:46 ssh_host_rsa_key.pub
-rwxr-xr-x 1 root sys 5203 Sep 11 2009 sshd_config
-rwxr-xr-x 1 root sys 5202 Jan 22 2005 sshd_config.fcs
root@N2000Server # ls -l
total 208
-rwxr-xr-x 1 root sys 88301 Jan 22 2005 moduli
-rwxr-xr-x 1 root sys 861 Jan 22 2005 ssh_config
-rwx--x--x 1 root root 668 Mar 27 18:46 ssh_host_dsa_key
-rwxr-xr-x 1 root root 601 Mar 27 18:46 ssh_host_dsa_key.pub
-rwx--x--x 1 root root 883 Mar 27 18:46 ssh_host_rsa_key
-rwxr-xr-x 1 root root 221 Mar 27 18:46 ssh_host_rsa_key.pub
-rwxr-xr-x 1 root sys 5203 Sep 11 2009 sshd_config
-rwxr-xr-x 1 root sys 5202 Jan 22 2005 sshd_config.fcs
root@N2000Server # ls -al
total 220
drwxr-xr-x 2 root sys 512 Mar 27 18:46 .
drwxr-xr-x 77 root sys 4608 Mar 29 22:52 ..
-rwxr-xr-x 1 root sys 88301 Jan 22 2005 moduli
-rwxr-xr-x 1 root sys 861 Jan 22 2005 ssh_config
-rwx--x--x 1 root root 668 Mar 27 18:46 ssh_host_dsa_key
-rwxr-xr-x 1 root root 601 Mar 27 18:46 ssh_host_dsa_key.pub
-rwx--x--x 1 root root 883 Mar 27 18:46 ssh_host_rsa_key
-rwxr-xr-x 1 root root 221 Mar 27 18:46 ssh_host_rsa_key.pub
-rwxr-xr-x 1 root sys 5203 Sep 11 2009 sshd_config
-rwxr-xr-x 1 root sys 5202 Jan 22 2005 sshd_config.fcs
root@N2000Server # chmod 600 /etc/ssh/ssh_host_rsa_key
root@N2000Server # chmod 600 /etc/ssh/ssh_host_dsa_key
root@N2000Server # ls -al
total 220
drwxr-xr-x 2 root sys 512 Mar 27 18:46 .
drwxr-xr-x 77 root sys 4608 Mar 29 22:52 ..
-rwxr-xr-x 1 root sys 88301 Jan 22 2005 moduli
-rwxr-xr-x 1 root sys 861 Jan 22 2005 ssh_config
-rw------- 1 root root 668 Mar 27 18:46 ssh_host_dsa_key
-rwxr-xr-x 1 root root 601 Mar 27 18:46 ssh_host_dsa_key.pub
-rw------- 1 root root 883 Mar 27 18:46 ssh_host_rsa_key
-rwxr-xr-x 1 root root 221 Mar 27 18:46 ssh_host_rsa_key.pub
-rwxr-xr-x 1 root sys 5203 Sep 11 2009 sshd_config
-rwxr-xr-x 1 root sys 5202 Jan 22 2005 sshd_config.fcs
root@N2000Server # svcadm enable ssh
root@N2000Server # svcadm refresh ssh
root@N2000Server # ssh 192.168.8.11
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
6d:64:ce:f3:90:bb:77:72:fd:33:1f:07:c0:16:eb:f3.
Please contact your system administrator.
Add correct host key in /.ssh/known_hosts to get rid of this message.
Offending key in /.ssh/known_hosts:1
RSA host key for 192.168.8.11 has changed and you have requested strict checking.
Host key verification failed.
root@N2000Server # su - sybase -c showserver
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
UID PID PPID C STIME TTY TIME CMD
sybase 1138 1137 0 22:54:28 ? 0:00 /opt/sybase/ASE-15_0/bin/backupserver -SN2000DBServer_back -e/opt/sybase/ASE-15
sybase 1045 1044 0 22:52:28 ? 1:35 /opt/sybase/ASE-15_0/bin/dataserver -sN2000DB
如果修改IP地址不完善，请按照以下步骤重新修改N2000 UMS服务器的IP地址：
- 停止N2000 UMS服务，请参见如何手工关闭N2000
UMS服务。 - 停止Sybase数据库，请参见如何手工关闭数据库服务。
- 在N2000 UMS服务器中修改IP地址。
原因
处理措施
如果只修改服务器的IP地址- 执行vi /etc/hosts命令，打开vi编辑器。
- 按“Insert”键，进入编辑模式。
- 修改文件中N2000 UMS的IP地址为新的IP地址。
- 按“Esc”键，退出编辑模式。
- 使用“Shift+；”组合键，输入wq，保存退出vi编辑器。
如果修改服务器的IP地址和子网掩码- 执行vi /etc/hosts命令，打开vi编辑器。
- 按“Insert”键，进入编辑模式。
- 修改文件中N2000 UMS的IP地址为新的IP地址。
- 按“Esc”键，退出编辑模式。
- 使用“Shift+；”组合键，输入wq，保存退出vi编辑器。
- 执行vi /etc/netmasks命令，打开vi编辑器。
- 按“Insert”键，进入编辑模式。
- 修改文件中的子网掩码为新的N2000 UMS服务器子网掩码。
- 按“Esc”键，退出编辑模式。
- 使用“Shift+；”组合键，输入wq，保存退出vi编辑器。
如果修改服务器的IP地址、子网掩码和网关- 执行vi /etc/hosts命令，打开vi编辑器。
- 按“Insert”键，进入编辑模式。
- 修改文件中N2000 UMS的IP地址为新的IP地址。
- 按“Esc”键，退出编辑模式。
- 使用“Shift+；”组合键，输入wq，保存退出vi编辑器。
- 执行vi /etc/netmasks命令，打开vi编辑器。
- 按“Insert”键，进入编辑模式。
- 修改文件中的子网掩码为新的N2000 UMS服务器子网掩码。
- 按“Esc”键，退出编辑模式。
- 使用“Shift+；”组合键，输入wq，保存退出vi编辑器。
- 用vi编辑器，修改“/etc/defaultrouter”文件、“/etc/rc3”文件和“/etc/rc3.d”目录下路由文件中的路由信息。
说明：vi命令的详细介绍，请参见vi命令。
- 修改数据库的IP地址，具体操作请参见如何正确设置数据库网络传输参数。
- 启动Sybase数据库和N2000 UMS服务。
说明：
启动Sybase数据库，请参见如何手工启动数据库服务。
启动N2000 UMS服务，请参见如何手工启动N2000
UMS服务。
如何解决UMS sybase数据库启动不成功问题
|
下载 |
推荐给好友 意见反馈
|
|
|||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||