Karaf客户端和SSH都无法连接到Karaf Shell

时间:2019-08-14 17:50:55

标签: linux apache-karaf apache-servicemix

我在Linux VM上运行Karaf shell,然后尝试使用apache提供的客户端脚本或ssh工具连接到它,在两种情况下都关闭连接。

我按如下所示启动karaf外壳:

[scfuser@europa-16 bin]$ ./karaf
karaf: Ignoring predefined value for KARAF_HOME
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=16M; 
support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option 
MaxPermSize=128M; support was removed in 8.0

Apache ServiceMix (4.4.1-fuse-07-11)

Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.

karaf@root>

然后在一个单独的窗口中按如下方式运行客户端:

[scfuser@europa-16 bin]$ ./client
Session is closed

还尝试打开ssh的调试选项:

[scfuser@europa-16 bin]$ ssh -vvv -p 8101 karaf@localhost -vvv -p 8101 
karaf@localhost
OpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to localhost [::1] port 8101.
debug1: Connection established.
debug1: identity file /home/scfuser/.ssh/identity type -1
debug1: identity file /home/scfuser/.ssh/identity-cert type -1
debug1: identity file /home/scfuser/.ssh/id_rsa type -1
debug1: identity file /home/scfuser/.ssh/id_rsa-cert type -1
debug1: identity file /home/scfuser/.ssh/id_dsa type -1
debug1: identity file /home/scfuser/.ssh/id_dsa-cert type -1
debug1: identity file /home/scfuser/.ssh/id_ecdsa type -1
debug1: identity file /home/scfuser/.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 2.0, remote software version SSHD-CORE-0.5.0
debug1: no match: SSHD-CORE-0.5.0
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.3
debug2: fd 3 setting O_NONBLOCK
debug1: SSH2_MSG_KEXINIT sent
debug3: Wrote 960 bytes for a total of 981
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-dss-cert-v00@openssh.com,ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit: diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,aes192-cbc,aes256-cbc
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,aes192-cbc,aes256-cbc
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-md5-96,hmac-sha1-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-md5-96,hmac-sha1-96
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_setup: found hmac-md5
debug1: kex: server->client aes128-cbc hmac-md5 none
debug2: mac_setup: found hmac-md5
debug1: kex: client->server aes128-cbc hmac-md5 none
debug2: dh_gen_key: priv key bits set: 126/256
debug2: bits set: 508/1024
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug3: Wrote 144 bytes for a total of 1125
Connection closed by ::1

更多信息:Java 1.8似乎会发生这种情况,只要此应用程序与Java 1.7一起安装,它就可以正常工作。到目前为止,我注意到的唯一区别是,在java 1.8安装中,servicemix似乎使用了/ etc下的jre.properties文件,它为jre 1.8提供了一个额外的条目,如下所示:

jre-1.8= \ com.sun.org.apache.xalan.internal.xsltc.trax, \ com.sun.org.apache.xerces.internal.dom, \ ... etc.etc.

0 个答案:

没有答案