Re: TcpDiscoverSpi error connection refused
Thanks Denis.
Sent from my iPhone
> On 9 Apr 2018, at 18:22, Denis Mekhanikov wrote:
>
> There are the following lines in the TcpDiscoverySpi implementation:
>
> if (log.isDebugEnabled())
> log.error("Exception on direct send: " + e.getMessage(), e);
>
> So, these exceptions are shown only when debug logging is enabled, and they
> are logged as errors.
>
> Neeraj, you probably just didn't enable debug log on the second node, so you
> don't see these exceptions on it.
>
> Denis
>
> пн, 9 апр. 2018 г. в 7:00, Neeraj Vaidya :
>> Hi Denis,
>> But this issue does not occur on node2 even if it is started before node1. I
>> feel even otherwise this message related to Discovery of level SEVERE is a
>> bit misleading. Wouldn’t it be visible when log level is anything higher
>> than DEBUG as well ? I agree this is not a functional issue as it only
>> occurs at startup when performing discovery and gets cleared when a peer is
>> discovered.
>>
>> Regards,
>> Neeraj
>>
>> Sent from my iPhone
>>
>>> On 8 Apr 2018, at 01:58, Amir Akhmedov wrote:
>>>
>>> Hi Denis,
>>>
>>> I had a similar logs before and I can confirm I got them when enabled
>>> "debug" level but the log level "severe" was really confusing.
>>>
On Fri, Apr 6, 2018, 8:52 AM Denis Mekhanikov
wrote:
Neeraj,
You probably enabled debug logging on the following package:
org.apache.ignite.spi.discovery.tcp
There is nothing wrong in these exceptions actually.
The first connection refused exception happens because there are two hosts
in the IP finder configuration, but when you start the first node, nobody
is bound to the discovery port on the second host. So, you get "Connection
refused" exception, when discovery SPI is trying to connect to the second
host.
If you see a message like this, then it means, that discovery finished its
work successfully:
Topology snapshot [ver=1, servers=1, ...]
You can disable debug logging not to see these exceptions.
The second exception is also doesn't mean anything bad.
It only means, that some object was transferred to this node, and
connection was suddenly closed.
So, none of these exceptions mean anything bad.
Denis
пт, 6 апр. 2018 г. в 2:34, Neeraj Vaidya :
> Hi,
> I have 2 virtualbox guest OS'es (CentOS7 64-bit) , each having firewalld
> stopped and disabled.
> The nodes are axlrate-node-1 and axlrate-node-2. I have updated
> default-config.xml in both servers
> My default-config.xml looks like below :
> -default-config.xml
> @ axlrate-node-1-
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xsi:schemaLocation="
>http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans.xsd";>
>
> class="org.apache.ignite.configuration.IgniteConfiguration">
>
>
>
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>
>
>
> axlrate-node-1
> axlrate-node-2
>
>
>
>
>
>
>
>
>
> ---
>
> -default-config.xml
> @ axlrate-node-2-
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xsi:schemaLocation="
>http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans.xsd";>
>
> class="org.apache.ignite.configuration.IgniteConfiguration">
>
>
>
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>
>
>
> axlrate-node-1
> axlrate-node-2
>
>
>
>
>
>
>
>
>
> ---
>
>
> When I try to start ignite on axlrate-node-1, I see the following error
> at startup.
>
Re: TcpDiscoverSpi error connection refused
There are the following lines in the TcpDiscoverySpi implementation:
if (log.isDebugEnabled())
log.error("Exception on direct send: " + e.getMessage(), e);
So, these exceptions are shown only when debug logging is enabled, and they
are logged as errors.
Neeraj, you probably just didn't enable debug log on the second node, so
you don't see these exceptions on it.
Denis
пн, 9 апр. 2018 г. в 7:00, Neeraj Vaidya :
> Hi Denis,
> But this issue does not occur on node2 even if it is started before node1.
> I feel even otherwise this message related to Discovery of level SEVERE is
> a bit misleading. Wouldn’t it be visible when log level is anything higher
> than DEBUG as well ? I agree this is not a functional issue as it only
> occurs at startup when performing discovery and gets cleared when a peer is
> discovered.
>
> Regards,
> Neeraj
>
> Sent from my iPhone
>
> On 8 Apr 2018, at 01:58, Amir Akhmedov wrote:
>
> Hi Denis,
>
> I had a similar logs before and I can confirm I got them when enabled
> "debug" level but the log level "severe" was really confusing.
>
> On Fri, Apr 6, 2018, 8:52 AM Denis Mekhanikov
> wrote:
>
>> Neeraj,
>>
>> You probably enabled debug logging on the following package:
>> *org.apache.ignite.spi.discovery.tcp*
>>
>> There is nothing wrong in these exceptions actually.
>> The first connection refused exception happens because there are two
>> hosts in the IP finder configuration, but when you start the first node,
>> nobody is bound to the discovery port on the second host. So, you get
>> *"Connection
>> refused" *exception, when discovery SPI is trying to connect to the
>> second host.
>>
>> If you see a message like this, then it means, that discovery finished
>> its work successfully:
>> *Topology snapshot [ver=1, servers=1, ...]*
>>
>> You can disable debug logging not to see these exceptions.
>>
>> The second exception is also doesn't mean anything bad.
>> It only means, that some object was transferred to this node, and
>> connection was suddenly closed.
>>
>> So, none of these exceptions mean anything bad.
>>
>> Denis
>>
>> пт, 6 апр. 2018 г. в 2:34, Neeraj Vaidya :
>>
>>> Hi,
>>> I have 2 virtualbox guest OS'es (CentOS7 64-bit) , each having firewalld
>>> stopped and disabled.
>>> The nodes are axlrate-node-1 and axlrate-node-2. I have updated
>>> default-config.xml in both servers
>>> My default-config.xml looks like below :
>>> -default-config.xml
>>> @ axlrate-node-1-
>>> http://www.springframework.org/schema/beans";
>>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>>>xsi:schemaLocation="
>>>http://www.springframework.org/schema/beans
>>>http://www.springframework.org/schema/beans/spring-beans.xsd";>
>>>
>>> >> class="org.apache.ignite.configuration.IgniteConfiguration">
>>>
>>>
>>>
>>>
>>> >> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>>>
>>>
>>>
>>> axlrate-node-1
>>> axlrate-node-2
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ---
>>>
>>> -default-config.xml
>>> @ axlrate-node-2-
>>> http://www.springframework.org/schema/beans";
>>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>>>xsi:schemaLocation="
>>>http://www.springframework.org/schema/beans
>>>http://www.springframework.org/schema/beans/spring-beans.xsd";>
>>>
>>> >> class="org.apache.ignite.configuration.IgniteConfiguration">
>>>
>>>
>>>
>>>
>>> >> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>>>
>>>
>>>
>>> axlrate-node-1
>>> axlrate-node-2
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ---
>>>
>>>
>>> When I try to start ignite on axlrate-node-1, I see the following error
>>> at startup.
>>>
>>> ---log
>>> on
>>> axlrate-node-1---
>>> [09:14:41,747][SEVERE][main][TcpDiscoverySpi] Exception on direct send:
>>> Connection refused (Connection refused)
>>> java.net.ConnectException: Connection refused (Co
Re: TcpDiscoverSpi error connection refused
Hi Denis, But this issue does not occur on node2 even if it is started before node1. I feel even otherwise this message related to Discovery of level SEVERE is a bit misleading. Wouldn’t it be visible when log level is anything higher than DEBUG as well ? I agree this is not a functional issue as it only occurs at startup when performing discovery and gets cleared when a peer is discovered. Regards, Neeraj Sent from my iPhone > On 8 Apr 2018, at 01:58, Amir Akhmedov wrote: > > Hi Denis, > > I had a similar logs before and I can confirm I got them when enabled "debug" > level but the log level "severe" was really confusing. > >> On Fri, Apr 6, 2018, 8:52 AM Denis Mekhanikov wrote: >> Neeraj, >> >> You probably enabled debug logging on the following package: >> org.apache.ignite.spi.discovery.tcp >> >> There is nothing wrong in these exceptions actually. >> The first connection refused exception happens because there are two hosts >> in the IP finder configuration, but when you start the first node, nobody is >> bound to the discovery port on the second host. So, you get "Connection >> refused" exception, when discovery SPI is trying to connect to the second >> host. >> >> If you see a message like this, then it means, that discovery finished its >> work successfully: >> Topology snapshot [ver=1, servers=1, ...] >> >> You can disable debug logging not to see these exceptions. >> >> The second exception is also doesn't mean anything bad. >> It only means, that some object was transferred to this node, and connection >> was suddenly closed. >> >> So, none of these exceptions mean anything bad. >> >> Denis >> >> пт, 6 апр. 2018 г. в 2:34, Neeraj Vaidya : >>> Hi, >>> I have 2 virtualbox guest OS'es (CentOS7 64-bit) , each having firewalld >>> stopped and disabled. >>> The nodes are axlrate-node-1 and axlrate-node-2. I have updated >>> default-config.xml in both servers >>> My default-config.xml looks like below : >>> -default-config.xml >>> @ axlrate-node-1- >>> http://www.springframework.org/schema/beans"; >>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >>>xsi:schemaLocation=" >>>http://www.springframework.org/schema/beans >>>http://www.springframework.org/schema/beans/spring-beans.xsd";> >>> >>> >> class="org.apache.ignite.configuration.IgniteConfiguration"> >>> >>> >>> >>> >>> >> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> >>> >>> >>> >>> axlrate-node-1 >>> axlrate-node-2 >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> --- >>> >>> -default-config.xml >>> @ axlrate-node-2- >>> http://www.springframework.org/schema/beans"; >>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >>>xsi:schemaLocation=" >>>http://www.springframework.org/schema/beans >>>http://www.springframework.org/schema/beans/spring-beans.xsd";> >>> >>> >> class="org.apache.ignite.configuration.IgniteConfiguration"> >>> >>> >>> >>> >>> >> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> >>> >>> >>> >>> axlrate-node-1 >>> axlrate-node-2 >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> --- >>> >>> >>> When I try to start ignite on axlrate-node-1, I see the following error at >>> startup. >>> >>> ---log >>> on >>> axlrate-node-1--- >>> [09:14:41,747][SEVERE][main][TcpDiscoverySpi] Exception on direct send: >>> Connection refused (Connection refused) >>> java.net.ConnectException: Connection refused (Connection refused) >>> at java.net.PlainSocketImpl.socketConnect(Native Method) >>> at >>> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) >>> at >>> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) >>> at >>> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) >>> at java.net.SocksSocketImpl.connect(Sock
Re: TcpDiscoverSpi error connection refused
Hi Denis, I had a similar logs before and I can confirm I got them when enabled "debug" level but the log level "severe" was really confusing. On Fri, Apr 6, 2018, 8:52 AM Denis Mekhanikov wrote: > Neeraj, > > You probably enabled debug logging on the following package: > *org.apache.ignite.spi.discovery.tcp* > > There is nothing wrong in these exceptions actually. > The first connection refused exception happens because there are two hosts > in the IP finder configuration, but when you start the first node, nobody > is bound to the discovery port on the second host. So, you get *"Connection > refused" *exception, when discovery SPI is trying to connect to the > second host. > > If you see a message like this, then it means, that discovery finished its > work successfully: > *Topology snapshot [ver=1, servers=1, ...]* > > You can disable debug logging not to see these exceptions. > > The second exception is also doesn't mean anything bad. > It only means, that some object was transferred to this node, and > connection was suddenly closed. > > So, none of these exceptions mean anything bad. > > Denis > > пт, 6 апр. 2018 г. в 2:34, Neeraj Vaidya : > >> Hi, >> I have 2 virtualbox guest OS'es (CentOS7 64-bit) , each having firewalld >> stopped and disabled. >> The nodes are axlrate-node-1 and axlrate-node-2. I have updated >> default-config.xml in both servers >> My default-config.xml looks like below : >> -default-config.xml >> @ axlrate-node-1- >> http://www.springframework.org/schema/beans"; >>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >>xsi:schemaLocation=" >>http://www.springframework.org/schema/beans >>http://www.springframework.org/schema/beans/spring-beans.xsd";> >> >> > class="org.apache.ignite.configuration.IgniteConfiguration"> >> >> >> >> >> > class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> >> >> >> >> axlrate-node-1 >> axlrate-node-2 >> >> >> >> >> >> >> >> >> >> >> --- >> >> -default-config.xml >> @ axlrate-node-2- >> http://www.springframework.org/schema/beans"; >>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >>xsi:schemaLocation=" >>http://www.springframework.org/schema/beans >>http://www.springframework.org/schema/beans/spring-beans.xsd";> >> >> > class="org.apache.ignite.configuration.IgniteConfiguration"> >> >> >> >> >> > class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> >> >> >> >> axlrate-node-1 >> axlrate-node-2 >> >> >> >> >> >> >> >> >> >> >> --- >> >> >> When I try to start ignite on axlrate-node-1, I see the following error >> at startup. >> >> ---log >> on >> axlrate-node-1--- >> [09:14:41,747][SEVERE][main][TcpDiscoverySpi] Exception on direct send: >> Connection refused (Connection refused) >> java.net.ConnectException: Connection refused (Connection refused) >> at java.net.PlainSocketImpl.socketConnect(Native Method) >> at java.net >> .AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) >> at java.net >> .AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) >> at java.net >> .AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) >> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) >> at java.net.Socket.connect(Socket.java:589) >> at >> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1386) >> at >> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1349) >> at >> org.apache.ignite.spi.discovery.tcp.ServerImpl.sendMessageDirectly(ServerImpl.java:1169) >> at >> org.apache.ignite.spi.discovery.tcp.ServerImpl.sendJoinRequestMessage(ServerImpl.java:1016) >> at >> org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:860) >> at >> org.apache.
Re: TcpDiscoverSpi error connection refused
Neeraj, You probably enabled debug logging on the following package: *org.apache.ignite.spi.discovery.tcp* There is nothing wrong in these exceptions actually. The first connection refused exception happens because there are two hosts in the IP finder configuration, but when you start the first node, nobody is bound to the discovery port on the second host. So, you get *"Connection refused" *exception, when discovery SPI is trying to connect to the second host. If you see a message like this, then it means, that discovery finished its work successfully: *Topology snapshot [ver=1, servers=1, ...]* You can disable debug logging not to see these exceptions. The second exception is also doesn't mean anything bad. It only means, that some object was transferred to this node, and connection was suddenly closed. So, none of these exceptions mean anything bad. Denis пт, 6 апр. 2018 г. в 2:34, Neeraj Vaidya : > Hi, > I have 2 virtualbox guest OS'es (CentOS7 64-bit) , each having firewalld > stopped and disabled. > The nodes are axlrate-node-1 and axlrate-node-2. I have updated > default-config.xml in both servers > My default-config.xml looks like below : > -default-config.xml > @ axlrate-node-1- > http://www.springframework.org/schema/beans"; >xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >xsi:schemaLocation=" >http://www.springframework.org/schema/beans >http://www.springframework.org/schema/beans/spring-beans.xsd";> > > class="org.apache.ignite.configuration.IgniteConfiguration"> > > > > > class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> > > > > axlrate-node-1 > axlrate-node-2 > > > > > > > > > > > --- > > -default-config.xml > @ axlrate-node-2- > http://www.springframework.org/schema/beans"; >xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >xsi:schemaLocation=" >http://www.springframework.org/schema/beans >http://www.springframework.org/schema/beans/spring-beans.xsd";> > > class="org.apache.ignite.configuration.IgniteConfiguration"> > > > > > class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> > > > > axlrate-node-1 > axlrate-node-2 > > > > > > > > > > > --- > > > When I try to start ignite on axlrate-node-1, I see the following error at > startup. > > ---log > on > axlrate-node-1--- > [09:14:41,747][SEVERE][main][TcpDiscoverySpi] Exception on direct send: > Connection refused (Connection refused) > java.net.ConnectException: Connection refused (Connection refused) > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net > .AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) > at java.net > .AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) > at java.net > .AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) > at java.net.Socket.connect(Socket.java:589) > at > org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1386) > at > org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1349) > at > org.apache.ignite.spi.discovery.tcp.ServerImpl.sendMessageDirectly(ServerImpl.java:1169) > at > org.apache.ignite.spi.discovery.tcp.ServerImpl.sendJoinRequestMessage(ServerImpl.java:1016) > at > org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:860) > at > org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:360) > at > org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:1846) > at > org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297) > at > org.apache.ignite.internal.managers.discovery.GridDiscover
