storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthew Lowe <githubpoi...@gmail.com>
Subject Re: Netty-Client - Returned channel was actually not established
Date Fri, 03 Jun 2016 20:58:21 GMT
I will look into it and get back to you!

Best Regards
Matthew Lowe

> On 03 Jun 2016, at 22:24, Jacob Johansen <johansenjuwp@gmail.com> wrote:
> 
> Is the server the client is trying to connect to listening on the
> port. (netstat command)
> 
> Is your DNS or host file correct?
> Jacob Johansen
> 
> 
>> On Fri, Jun 3, 2016 at 3:13 PM, Matthew Lowe <githubpoixen@gmail.com> wrote:
>> Giving this a bump, as its rather important.
>> 
>> To be more specific, no traffic ever goes through the topology. As soon as
>> it it started, the error will start.
>> One time I left it overnight and it connected, but I am unsure how long this
>> took to happen.
>> 
>> And ideas would be great, thanks!
>> 
>> On 03 Jun 2016, at 15:52, Matthew Lowe <githubpoixen@gmail.com> wrote:
>> 
>> Hello all,
>> 
>> I have just updated my cluster.xml to use some appenders that I made.
>> 
>> I am now getting items like the following in the logs.
>> I seems like given enough time (hours), it will eventually resolve and start
>> to work.
>> 
>> I am running storm 0.9.4
>> 
>> 2016-06-03T13:46:28.825+0000 b.s.m.n.Client [ERROR] connection attempt 1 to
>> Netty-Client-ip-xx.x.xx.xxx.eu-west-1.compute.internal/xx.x.xx.xxx:6700
>> failed: java.lang.RuntimeException: Returned channel was actually not
>> established
>> 2016-06-03T13:46:28.826+0000 b.s.m.n.Client [INFO] connection attempt 2 to
>> Netty-Client-ip-xx.x.xx.xxx.eu-west-1.compute.internal/xx.x.xx.xxx:6700
>> scheduled to run in 103 ms
>> 
>> 

Mime
View raw message