NIS crashed, log message included

Anyone know why this happen? Nothing changed from previous run, after restart computer, it won’t boot anymore. :confused:

I have tried to delete db, change hostname to ip, disable autoharvest on boot. Where else should I look?

2016-02-17 14:01:37.689 SEVERE e[0;31msomething really bad happened: java.util.concurrent.CompletionException: org.nem.core.node.InvalidNodeEndpointException: host is unknowne[0m (org.nem.nis.NisMain b)

I would say something must have changed ^^ Check config.properties and peers-config_mainnet.json, really untouched?

I have restart from scratch, disable iptables, still get same message. Only change I can think is with the machine, from 4cpu decrease to 1cpu…

spec
1cpu, 1gb ram, 25gb hdd

Look like 1cpu not enough. ssh / ftp won’t response also. :disappointed_relieved:

1 cpu or more has nothing to do with the error you above i think.
Can you supply the 2 files i mentioned above?

Where is peers-config_mainnet.json located? :grin:

Java version

opt]# java -version
java version "1.8.0_45"
Java™ SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot™ 64-Bit Server VM (build 25.45-b02, mixed mode)

hmm…seems that it is only supplied in the nis jar, so forget it ^^
That leaves only the config.properties as cause of trouble which should be in the NIS folder.

Btw. your java version is rather old :wink:

Upgraded java and reinstalled everything again. Seems to be working now. :joy:

Probably something corrupted when shutdown previously.

Hello

My NIS has not crashed but after about 38 days went under heavy load.
I mean my Ubuntu 14.04 VPS cpu is under heavy load right now.

Here are my cpu info:

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 8
Vendor ID: AuthenticAMD
CPU family: 21
Model: 0
Stepping: 2
CPU MHz: 2800.000
BogoMIPS: 5600.00
Hypervisor vendor: VMware
Virtualization type: full

The server has 2GB memory
I see NIS is taking about about 170% CPU
This is 2 core processor.

Is the NEM network under heavy load lately or what?!

I would simply restart NIS. The network is surely not under heavy load.

I had the same on my server. Same configuration (VPS Server) as freigeist. A restart of NIS and it was solved.

I have done it! It works now for 2 days without problems.
Thanks.