Ignite Startup Failures

classic Classic list List threaded Threaded
4 messages Options
pragmaticbigdata pragmaticbigdata
Reply | Threaded
Open this post in threaded view
|

Ignite Startup Failures

I am using ignite 1.6 and trying to build up a cluster of multiple servers. While starting different nodes on my linux vm's through the ignite.sh conf.xml command, I get a NPE. The complete console and server.logs are shared here.

The configuration file used to start up ignite is the one which comes with the package - examples/config/example-ignite.xml.

The server startup was working a few days ago. Nothing seems to have changed in the configuration. Kindly let me know your inputs on what could possibly be wrong.
vdpyatkov vdpyatkov
Reply | Threaded
Open this post in threaded view
|

Re: Ignite Startup Failures

Hello,

Unfortunately I was not able to get access to logs files.
I think you need to check IGNITE_HOME environment variable.

You can find information about in the article https://apacheignite.readme.io/docs/getting-started in Installation topic.

If the exception persists, please send log files.


On Sun, Jun 5, 2016 at 7:04 AM, pragmaticbigdata <[hidden email]> wrote:
I am using ignite 1.6 and trying to build up a cluster of multiple servers.
While starting different nodes on my linux vm's through the ignite.sh
conf.xml command, I get a NPE. The complete console and server.logs are
shared  here <http://pastebin.com/rPp837fU>  .

The configuration file used to start up ignite is the one which comes with
the package - examples/config/example-ignite.xml.

The server startup was working a few days ago. Nothing seems to have changed
in the configuration. Kindly let me know your inputs on what could possibly
be wrong.



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Startup-Failures-tp5427.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.



--
Vladislav Pyatkov
vdpyatkov vdpyatkov
Reply | Threaded
Open this post in threaded view
|

Re: Ignite Startup Failures

vdpyatkov wrote
Hello,

Unfortunately I was not able to get access to logs files.
I think you need to check IGNITE_HOME environment variable.

You can find information about in the article
https://apacheignite.readme.io/docs/getting-started in *Installation* topic.

If the exception persists, please send log files.


On Sun, Jun 5, 2016 at 7:04 AM, pragmaticbigdata <[hidden email]> wrote:

> I am using ignite 1.6 and trying to build up a cluster of multiple servers.
> While starting different nodes on my linux vm's through the ignite.sh
> conf.xml command, I get a NPE. The complete console and server.logs are
> shared  here <http://pastebin.com/rPp837fU>  .
>
> The configuration file used to start up ignite is the one which comes with
> the package - examples/config/example-ignite.xml.
>
> The server startup was working a few days ago. Nothing seems to have
> changed
> in the configuration. Kindly let me know your inputs on what could possibly
> be wrong.
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-Startup-Failures-tp5427.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>



--
Vladislav Pyatkov
Hello,

I read your log in detail and found the message:

[09:28:29,498][WARNING][disco-event-worker-#44%null%][GridDiscoveryManager] Local node SEGMENTED: TcpDiscoveryNode [id=18232186-3a75-4911-9b89-29b0b8446db5, addrs=[0:0:0:0:0:0:0:1%lo, 10.210.26.97, 127.0.0.1], sockAddrs=[v-in-sd-hack-02.synygy.net/10.210.26.97:47500, /0:0:0:0:0:0:0:1%lo:47500, /10.210.26.97:47500, /127.0.0.1:47500], discPort=47500, order=275, intOrder=149, lastExchangeTime=1465099109477, loc=true, ver=1.6.0#20160518-sha1:0b22c45b, isClient=false]

It likely means problem in network.
You need check availability ports for DiscoverySPI and CommunicationSPI.
If the problem continues to appear, please attach XML configuration.
vdpyatkov vdpyatkov
Reply | Threaded
Open this post in threaded view
|

Re: Ignite Startup Failures

In addition a long pause GC can lead to error.
You can get GC log and analyze it [1].
If this does not help, then add GC log in this thread.


On Tue, Jun 7, 2016 at 6:35 PM, vdpyatkov <[hidden email]> wrote:
vdpyatkov wrote
> Hello,
>
> Unfortunately I was not able to get access to logs files.
> I think you need to check IGNITE_HOME environment variable.
>
> You can find information about in the article
> https://apacheignite.readme.io/docs/getting-started in *Installation*
> topic.
>
> If the exception persists, please send log files.
>
>
> On Sun, Jun 5, 2016 at 7:04 AM, pragmaticbigdata &lt;

> amits.84@

> &gt; wrote:
>
>> I am using ignite 1.6 and trying to build up a cluster of multiple
>> servers.
>> While starting different nodes on my linux vm's through the ignite.sh
>> conf.xml command, I get a NPE. The complete console and server.logs are
>> shared  here &lt;http://pastebin.com/rPp837fU&gt;  .
>>
>> The configuration file used to start up ignite is the one which comes
>> with
>> the package - examples/config/example-ignite.xml.
>>
>> The server startup was working a few days ago. Nothing seems to have
>> changed
>> in the configuration. Kindly let me know your inputs on what could
>> possibly
>> be wrong.
>>
>>
>>
>> --
>> View this message in context:
>> http://apache-ignite-users.70518.x6.nabble.com/Ignite-Startup-Failures-tp5427.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>
>
> --
> Vladislav Pyatkov

Hello,

I read your log in detail and found the message:

[09:28:29,498][WARNING][disco-event-worker-#44%null%][GridDiscoveryManager]
Local node SEGMENTED: TcpDiscoveryNode
[id=18232186-3a75-4911-9b89-29b0b8446db5, addrs=[0:0:0:0:0:0:0:1%lo,
10.210.26.97, 127.0.0.1],
sockAddrs=[v-in-sd-hack-02.synygy.net/10.210.26.97:47500,
/0:0:0:0:0:0:0:1%lo:47500, /10.210.26.97:47500, /127.0.0.1:47500],
discPort=47500, order=275, intOrder=149, lastExchangeTime=1465099109477,
loc=true, ver=1.6.0#20160518-sha1:0b22c45b, isClient=false]

It likely means problem in network.
You need check availability ports for DiscoverySPI and CommunicationSPI.
If the problem continues to appear, please attach XML configuration.



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Startup-Failures-tp5427p5503.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.



--
Vladislav Pyatkov