Node synchronization problems due to invalid height passed

Hey guys,

I’m quite new to the topic so please be understanding.

I have a problem with my local NIS. I’ve lost a wifi connection for a while and when it came back my node is not able to synchronize because of warning below. I can tell that chain height is not increasing. Is restart the only option? Any thoughts from you guys what is the reason of this problem?

WARNING Timer SYNC raised exception: java.lang.IllegalArgumentException: invalid height passed to addSend
java.util.concurrent.CompletionException: java.lang.IllegalArgumentException: invalid height passed to addSend
at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1629)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalArgumentException: invalid height passed to addSend
at org.nem.nis.mt.kln.d(TimeBasedVestingWeightedBalances.java:109)
at org.nem.nis.dc.odu.a(WeightedBalancesObserver.java:31)
at org.nem.nis.secret.BlockTransferObserverToBlockTransactionObserverAdapter.b(BlockTransferObserverToBlockTransactionObserverAdapter.java:68)
at org.nem.nis.secret.BlockTransferObserverToBlockTransactionObserverAdapter.a(BlockTransferObserverToBlockTransactionObserverAdapter.java:47)
at org.nem.nis.secret.BlockTransferObserverToBlockTransactionObserverAdapter.a(BlockTransferObserverToBlockTransactionObserverAdapter.java:32)
at org.nem.nis.secret.AggregateBlockTransactionObserverBuilder$AggregateBlockTransactionObserver.a(AggregateBlockTransactionObserverBuilder.java:77)
at org.nem.nis.dc.yns.notify(BlockTransactionObserverToTransactionObserverAdapter.java:28)
at java.util.ArrayList.forEach(ArrayList.java:1255)
at org.nem.core.model.TransferTransaction.transfer(TransferTransaction.java:271)
at org.nem.core.model.Transaction.execute(Transaction.java:131)
at org.nem.nis.vg.pve.c(BlockExecuteProcessor.java:34)
at org.nem.nis.dfc.a(BlockChainValidator.java:106)
at org.nem.nis.pz.gob.a(BlockChainServices.java:78)
at org.nem.nis.sync.BlockChainUpdateContext.fA(BlockChainUpdateContext.java:144)
at org.nem.nis.sync.BlockChainUpdateContext.fz(BlockChainUpdateContext.java:79)
at org.nem.nis.sync.BlockChainUpdateContext.fy(BlockChainUpdateContext.java:71)
at org.nem.nis.sync.BlockChainUpdater.a(BlockChainUpdater.java:249)
at org.nem.nis.sync.BlockChainUpdater.c(BlockChainUpdater.java:137)
at org.nem.nis.BlockChain.b(BlockChain.java:112)
at org.nem.nis.BlockChain.a(BlockChain.java:104)
at org.nem.nis.tae.a(CountingBlockSynchronizer.java:39)
at org.nem.peer.services.NodeSynchronizer.b(NodeSynchronizer.java:50)
at org.nem.peer.PeerNetwork.gt(PeerNetwork.java:141)
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1626)

I don’t have idea. @BloodyRookie do you have an idea what can cause this problem?

That looks like a corrupt db. Shut down NIS, zip the db and provide it to me via some file hoster please.
Meanwhile you can download a recent db from bob

bob.nem.ninja/nis5_mainnet.h2-1453k.db.zip

or sync from scratch whatever you like more.

2 Likes