Since upgrading from 5.5.4 to 5.5.5 my NIS server seems to be having problems. I have cleared the work directory a number of times to re-download the database but without joy. The machine seems to be behind on blocks and not catching up and http://nembex.nem.ninja/#nodes is showing me as offline.
After a while my NIS interactive display starts showing the followingion: remote node is evil: REMOTE_RETURNED_INVALID_HASHES (org.nem.nis.BlockChain a)<br />2015-02-14 12:02:24.900 INFO synchronizing with Node [alice6 <TALICE6I3KE36ECAQVGBYAD3FENZPVWJEC6HTZK4>] @ [108.61.168.86] finished (org.nem.peer.services.NodeSynchronizer a)<br />2015-02-14 12:02:24.900 INFO Updating experience with Node [alice6 <TALICE6I3KE36ECAQVGBYAD3FENZPVWJEC6HTZK4>] @ [108.61.168.86]: FAILURE (org.nem.peer.PeerNetworkState a)<br />2015-02-14 12:02:27.903 INFO synchronizing with Node [alice4 <TALICE4AQNH5TE7O43RZ5FPJ3AC6HCFTSOO7B3GF>] @ [199.217.112.135] (org.nem.peer.services.NodeSynchronizer a)<br />2015-02-14 12:02:28.515 INFO failed to synchronize with Node [alice4 <TALICE4AQNH5TE7O43RZ5FPJ3AC6HCFTSOO7B3GF>] @ [199.217.112.135]: org.nem.core.connect.FatalPeerException: remote node is evil: REMOTE_RETURNED_INVALID_HASHES (org.nem.nis.BlockChain a)<br />2015-02-14 12:02:28.515 INFO synchronizing with Node [alice4 <TALICE4AQNH5TE7O43RZ5FPJ3AC6HCFTSOO7B3GF>] @ [199.217.112.135] finished (org.nem.peer.services.NodeSynchronizer a)<br />2015-02-14 12:02:28.515 INFO Updating experience with Node [alice4 <TALICE4AQNH5TE7O43RZ5FPJ3AC6HCFTSOO7B3GF>] @ [199.217.112.135]: FAILURE (org.nem.peer.PeerNetworkState a)<br />2015-02-14 12:02:31.516 INFO synchronizing with Node [alice5 <TALICE55LWXDCL4CHBQH2BFTP3AQZBR4VE6ZYRUM>] @ [108.61.182.27] (org.nem.peer.services.NodeSynchronizer a)<br />2015-02-14 12:02:32.948 INFO failed to synchronize with Node [alice5 <b><TALICE55LWXDCL4CHBQH2BFTP3AQZBR4VE6ZYRUM>] @ [108.61.182.27]: org.nem.core.connect.FatalPeerException: remote node is evil: REMOTE_RETURNED_INVALID_HASHES (org.nem.nis.BlockChain a)<br /></b>2015-02-14 12:02:32.948 INFO synchronizing with Node [alice5 <TALICE55LWXDCL4CHBQH2BFTP3AQZBR4VE6ZYRUM>] @ [108.61.182.27] finished (org.nem.peer.services.NodeSynchronizer a)<br />2015-02-14 12:02:32.948 INFO Updating experience with Node [alice5 <TALICE55LWXDCL4CHBQH2BFTP3AQZBR4VE6ZYRUM>] @ [108.61.182.27]: FAILURE (org.nem.peer.PeerNetworkState a)<br />2015-02-14 12:02:35.949 INFO synchronizing with Node [alice5 <TALICE55LWXDCL4CHBQH2BFTP3AQZBR4VE6ZYRUM>] @ [108.61.182.27] (org.nem.peer.services.NodeSynchronizer a)<br />2015-02-14 12:02:37.097 INFO failed to synchronize with Node [alice5 <TALICE55LWXDCL4CHBQH2BFTP3AQZBR4VE6ZYRUM>] @ [108.61.182.27]: org.nem.core.connect.FatalPeerException: remote node is evil: REMOTE_RETURNED_INVALID_HASHES (org.nem.nis.BlockChain a)<br />2015-02-14 12:02:37.097 INFO synchronizing with Node [alice5 <TALICE55LWXDCL4CHBQH2BFTP3AQZBR4VE6ZYRUM>] @ [108.61.182.27] finished (org.nem.peer.services.NodeSynchronizer a)<br />2015-02-14 12:02:37.097 INFO Updating experience with Node [alice5 <TALICE55LWXDCL4CHBQH2BFTP3AQZBR4VE6ZYRUM>] @ [108.61.182.27]: FAILURE (org.nem.peer.PeerNetworkState a)<br />2015-02-14 12:02:40.098 INFO synchronizing with Node [rtstrx <TB45EHCTHEAVI675Z6KRMNMOJ3LPS7BHERY63GM4>] @ [95.16.180.62] (org.nem.peer.services.NodeSynchronizer a)<br />2015-02-14 12:02:40.475 INFO entering /time-sync/network-time [192.168.10.104] (org.nem.nis.controller.interceptors.AuditInterceptor preHandle)<br />2015-02-14 12:02:40.476 INFO exiting /time-sync/network-time [192.168.10.104] (org.nem.nis.controller.interceptors.AuditInterceptor afterCompletion)<br />2015-02-14 12:02:40.743 INFO failed to synchronize with Node [rtstrx <TB45EHCTHEAVI675Z6KRMNMOJ3LPS7BHERY63GM4>] @ [95.16.180.62]: org.nem.core.connect.FatalPeerException: remote node is evil: REMOTE_RETURNED_INVALID_HASHES (org.nem.nis.BlockChain a)<br />2015-02-14 12:02:40.744 INFO synchronizing with Node [rtstrx <TB45EHCTHEAVI675Z6KRMNMOJ3LPS7BHERY63GM4>] @ [95.16.180.62] finished (org.nem.peer.services.NodeSynchronizer a)<br />2015-02-14 12:02:40.744 INFO Updating experience with Node [rtstrx <TB45EHCTHEAVI675Z6KRMNMOJ3LPS7BHERY63GM4>] @ [95.16.180.62]: FAILURE (org.nem.peer.PeerNetworkState a)<br />2015-02-14 12:02:43.746 INFO synchronizing with Node [nijuichi <TBNIJUIKOWXU6P2TY4JO2ZYF32Z4CCMIDD5K3ZPF>] @ [nijuichi.nem.ninja] (org.nem.peer.services.NodeSynchronizer a)<br />2015-02-14 12:02:43.909 INFO failed to synchronize with Node [nijuichi <TBNIJUIKOWXU6P2TY4JO2ZYF32Z4CCMIDD5K3ZPF>] @ [nijuichi.nem.ninja]: org.nem.core.connect.FatalPeerException: remote node is evil: REMOTE_RETURNED_INVALID_HASHES (org.nem.nis.BlockChain a)<br />2015-02-14 12:02:43.909 INFO synchronizing with Node [nijuichi <TBNIJUIKOWXU6P2TY4JO2ZYF32Z4CCMIDD5K3ZPF>] @ [nijuichi.nem.ninja] finished (org.nem.peer.services.NodeSynchronizer a)<br />2015-02-14 12:02:43.909 INFO Updating experience with Node [nijuichi <TBNIJUIKOWXU6P2TY4JO2ZYF32Z4CCMIDD5K3ZPF>] @ [nijuichi.nem.ninja]: FAILURE (org.nem.peer.PeerNetworkState a)<br />
NIS is running on CentOS Linux and NCC is running remote on Windows 8.1
Any thoughts or suggestions?
KC
Seems to me that your database is corrupt.
btw. your node is not visible from the outside, port 7890 is probably closed.
I uploaded a recent db to bo: [url=http://bob.nem.ninja/nis5.h2.zip]bob.nem.ninja/nis5.h2.zip
Download it and try again 
Thanks a lot.
I deleted an old wallet file and created a new wallet.
And "ERROR 121. The address book file does not exist" does not show up again.
Then I downloaded a recent db and re-started software,
and escaped from a fork and fully synchronized.
My node is visible from outside now?
P.S. Please send me some nem(xem) to my new wallet address.
TC2PHE-K5DT34-MRZ6SK-PT6G2S-6CCOQS-KC7X4D-NF5H
(Because of "ERROR 709
The account is unknown. An account needs to be part of at least one transaction (sender or recipient) to be known to the network.")
Seems to me that your database is corrupt.
btw. your node is not visible from the outside, port 7890 is probably closed.
I uploaded a recent db to bo: [url=http://bob.nem.ninja/nis5.h2.zip]bob.nem.ninja/nis5.h2.zip
Download it and try again :)
BloodyRookie,
Followed your advice and all seems to be well now. Not sure why my database was getting corrupt over and over.
KC
@KingCole: your node seems to be behind again. Can you supply the NIS log?
@BloodyRookie
The log file from my server is too large to attach so I've placed it on OneDrive and shared it - link is : http://1drv.ms/1FefJBN
KC
@KingCole: your database is corrupt again ^^ But I think the issue you are experiencing will be fixed in the next release.
@KingCole: your database is corrupt again ^^ But I think the issue you are experiencing will be fixed in the next release.
:'( thanks for looking BR, should I wait for 5.5.6 or go back to 5.5.4?
KC
Interesting as the [url=http://nembex.nem.ninja/#stats]accounts have difference in the amount of forged blocks, but the difference is small for the total amount of fees received by each account. Apparently consider the amount contained in the block to calculate the chance of account be able to forge drawing on the blocks already collected by it?
The amount a account already collected with harvesting has no influence on the chance to harvest the next block.
Is somewhere in the configuration files where I can change my IP to use a domain name? That neither nxt.myAddress= in NXT
I have this problem when i use port fwd fireSSH and sometimes with Putty, there are problems with nem and nfd.
I have found two issues.
With the latest release it is very difficult to access the client over an ssh tunnel. 95% of the time it will start loading the webpage and stop with a blank page or just a green bar at the top.
I cannot get nis to run properly on 524M nodes. Even if I tweak the java command line and swap space, it will stop loading blocks greater than 6750.
But the Linux terminal client works perfectly with nem, nxt and nfd clients.
@KingCole: your database is corrupt again ^^ But I think the issue you are experiencing will be fixed in the next release.
BR - my node is looking better on the latest version of NIS
@KingColde: good to hear.