Lightrun
question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error during handshake for tls auth by apache pulsar client on ubuntu server

See original GitHub issue

I have setup the apache pulsar v2.3 on Ubuntu 18.04.2 LTS from Run Pulsar locally. It sends message successfully without any authentication. But i would like to send message using tls authentication , so configuring tls certificate using security-tls-transport and security-tls-authentication.

Using above link I have created the certificates and modified following config files broker.conf,client.conf and standalone.conf. I am trying to send message by CLI with below command. bin/pulsar-client produce my-topic --messages "hello-pulsar"

But it throws the following error

[pulsar-client-io-1-1] INFO  org.apache.pulsar.client.impl.ConnectionPool -           
[[id: 0x8010c4f5, L:/127.0.0.1:42840 - R:localhost/127.0.0.1:6651]] 
Connected to server
09:47:17.686 [pulsar-client-io-1-1] WARN  
org.apache.pulsar.client.impl.ClientCnx - Error during handshake
java.nio.channels.ClosedChannelException: null
   at io.netty.handler.ssl.SslHandler.channelInactive(...)(Unknown Source) 
~[io.netty-netty-all-4.1.32.Final.jar:4.1.32.Final]
09:47:17.691 [pulsar-client-io-1-1] INFO  
org.apache.pulsar.client.impl.ClientCnx - [id: 0x8010c4f5, 
L:/127.0.0.1:42840 ! R:localhost/127.0.0.1:6651] Disconnected
09:47:17.692 [pulsar-client-io-1-1] WARN  
org.apache.pulsar.client.impl.ConnectionPool - [[id: 0x8010c4f5, 
L:/127.0.0.1:42840 ! R:localhost/127.0.0.1:6651]] Connection handshake 
failed: org.apache.pulsar.client.api.PulsarClientException: Connection 
already closed
09:47:17.692 [pulsar-client-io-1-1] WARN  
org.apache.pulsar.client.impl.PulsarClientImpl - [my-topic] Failed to get 
partitioned topic metadata: 
org.apache.pulsar.client.api.PulsarClientException: Connection already 
closed
09:47:17.692 [main] ERROR org.apache.pulsar.client.cli.PulsarClientTool - 
Error while producing messages
09:47:17.692 [main] ERROR org.apache.pulsar.client.cli.PulsarClientTool - 
Connection already closed
org.apache.pulsar.client.api.PulsarClientException: Connection already 
closed at 
org.apache.pulsar.client.impl.ClientCnx.channelInactive(ClientCnx.java:204) 
~[org.apache.pulsar-pulsar-client-original-2.3.0.jar:2.3.0]
   at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive
(AbstractChannelHandlerContext.java:245) ~[io.netty-netty-all- 
4.1.32.Final.jar:4.1.32.Final]
   at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive
(AbstractChannelHandlerContext.java:231) ~[io.netty-netty-all- 
4.1.32.Final.jar:4.1.32.Final]
   at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive
(AbstractChannelHandlerContext.java:224) ~[io.netty-netty-all- 
4.1.32.Final.jar:4.1.32.Final]
   at 
io.netty.handler.codec.ByteToMessageDecoder.channelInputClosed
(ByteToMessageDecoder.java:390) ~[io.netty-netty-all- 
4.1.32.Final.jar:4.1.32.Final]
   at 
io.netty.handler.codec.ByteToMessageDecoder.channelInactive
  (ByteToMessageDecoder.java:355) ~[io.netty-netty-all- 
 4.1.32.Final.jar:4.1.32.Final]
   at 
 io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive
  (AbstractChannelHandlerContext.java:245) ~[io.netty-netty-all- 
 4.1.32.Final.jar:4.1.32.Final]
   at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive
 (AbstractChannelHandlerContext.java:231) ~[io.netty-netty-all- 
 4.1.32.Final.jar:4.1.32.Final]
   at io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive
 (AbstractChannelHandlerContext.java:224) ~[io.netty-netty-all- 
4.1.32.Final.jar:4.1.32.Final]
   at io.netty.handler.codec.ByteToMessageDecoder.channelInputClosed
(ByteToMessageDecoder.java:390) ~[io.netty-netty-all- 
4.1.32.Final.jar:4.1.32.Final]
   at io.netty.handler.codec.ByteToMessageDecoder.channelInactive
    (ByteToMessageDecoder.java:355) ~[io.netty-netty-all- 
 4.1.32.Final.jar:4.1.32.Final]
   at io.netty.handler.ssl.SslHandler.channelInactive(SslHandler.java:1054) 
~[io.netty-netty-all-4.1.32.Final.jar:4.1.32.Final]
   at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive
 (AbstractChannelHandlerContext.java:245) ~[io.netty-netty-all- 
4.1.32.Final.jar:4.1.32.Final]
   at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive
(AbstractChannelHandlerContext.java:231) ~[io.netty-netty-all- 
4.1.32.Final.jar:4.1.32.Final]
   at io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive
(AbstractChannelHandlerContext.java:224) ~[io.netty-netty-all- 
4.1.32.Final.jar:4.1.32.Final]
   at io.netty.channel.DefaultChannelPipeline$HeadContext.channelInactive
(DefaultChannelPipeline.java:1429) ~[io.netty-netty-all- 
4.1.32.Final.jar:4.1.32.Final]
   at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive
(AbstractChannelHandlerContext.java:245) ~[io.netty-netty-all- 
4.1.32.Final.jar:4.1.32.Final]
   at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive
(AbstractChannelHandlerContext.java:231) ~[io.netty-netty-all- 
4.1.32.Final.jar:4.1.32.Final]
   at io.netty.channel.DefaultChannelPipeline.fireChannelInactive
(DefaultChannelPipeline.java:947) ~[io.netty-netty-all- 
4.1.32.Final.jar:4.1.32.Final]
   at io.netty.channel.AbstractChannel$AbstractUnsafe$8.run
(AbstractChannel.java:826) ~[io.netty-netty-all- 
4.1.32.Final.jar:4.1.32.Final]
   at io.netty.util.concurrent.AbstractEventExecutor.safeExecute
(AbstractEventExecutor.java:163) ~[io.netty-netty-all- 
4.1.32.Final.jar:4.1.32.Final]
   at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks
(SingleThreadEventExecutor.java:404) ~[io.netty-netty-all- 
4.1.32.Final.jar:4.1.32.Final]
   at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:335) ~ 
[io.netty-netty-all-4.1.32.Final.jar:4.1.32.Final]
   at io.netty.util.concurrent.SingleThreadEventExecutor$5.run
(SingleThreadEventExecutor.java:909) ~[io.netty-netty-all- 
4.1.32.Final.jar:4.1.32.Final]
   at io.netty.util.concurrent.FastThreadLocalRunnable.run
(FastThreadLocalRunnable.java:30) ~[io.netty-netty-all- 
4.1.32.Final.jar:4.1.32.Final]
   at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_201]
09:47:17.694 [main] INFO  org.apache.pulsar.client.cli.PulsarClientTool - 0 
messages successfully produced

Could anyone please help to resolve this ?

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:6 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
sijiecommented, Nov 4, 2019

@shan2015seyfert did you configure standalone to start with TLS settings?

See: http://pulsar.apache.org/docs/en/security-tls-transport/

1reaction
merlimatcommented, Apr 4, 2019

@shan2015seyfert it seems you either connecting with TLS to a cleartext port (or the reverse)

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error during handshake for tls auth by apache pulsar client on ...
3 on Ubuntu 18.04.2 LTS from Run Pulsar locally. It works fine without any authentication. I have tried configuring tls certificate using ...
Read more >
[GitHub] [pulsar] thomaeschen closed issue #12313: Error during ...
[GitHub] [pulsar] thomaeschen closed issue #12313: Error during handshake for tls auth by apache pulsar client on linux server.
Read more >
Authentication using TLS - Apache Pulsar
TLS authentication is an extension of TLS transport encryption. Not only servers have keys and certs that the client uses to verify the...
Read more >
Fix 'TLS Error: TLS handshake failed' on OpenVPN client
Am using digitalocean provider for my server and the problem was with floating ip feature. In order to fix that, you have to...
Read more >
TLS Certificate Verify Failure in paho-mqtt implementation
File "/usr/lib/python3.7/ssl.py", line 1117, in do_handshake ... have one mosquitto server implemented on a raspberry pi 3b+, an mqtt client ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found
Previous page

Pulsar standalone start failed

Next page

Error go get pulsar: fatal: unable to access 'https://gopkg.in/natefinch/lumberjack.v2/'