My Client’s NIS is synchronizing VERY slow. It now stands for hours block 222159, 139 day behind.
This is not normal, is it?
I also sent some XEM to my wallet, that don’t show up yet. Will they only show up, when my Client is synchronized 100 %?
Hoping for answers.
I have the same problem. Tried to reinstall NEM and different broweser but didn’t help also I upgrade my Java but still the same problem. Any other idea?
Yeah, I also did reinstall. Didn’t make a difference…
@scheffelchef: if it stays at block 222159 for hours without any progress, something is wrong. So either restart NIS and see if it helps or supply the most recent nis log file (located in c:>your user>\nem\nis\logs. And yes, only once your node is synced the transaction you made will appear in your wallet.
You can also try using a remote nis. There are reliable nodes available in germany like alic2.nem.ninja and alice3.nem.ninja.
@svktips: your nis stuck too at some block? then try one of the above.
After reinstall it is hanging at 222160. Which of the logfiles (nis-0.log, nis-0.log.lck, nis-1.log) do I have to “supply” and where? What does supply mean in this context? Sorryfor my rookie-questions 
.
I’m at 222235 block now but 2 days ago it was 222159. How I see there is a progress but very slow.
Alice3.nem.ninja worked for me “NIS is synchronized! (at block 423392)”
WORKED FOR ME TOO: Thanks!!!
Is there anyother solution? Because I can’t local harvesting on remote server so I turned back to localhost and again behind 139 days to sync
Edit: (As a new user can’t do more than 3 replay)
Where should I send the log file?
Still i am interested in the your most recent nis log file, scheffelchef. only 76 blocks progress in 2 days means that your node was stuck.
Hello, if you can tell ME how I can tell YOU (or send?) the recent log file, I will be glad to do so .
The most recent file in the folder c:<your user>\nem\nis\logs is the one i am interested in (if you restarted nis after you changed your setting to use alice3.nem.ninja then it is the second most recend file, so i want the log file with the sync attempt in it). You can upload it to any file hoster and paste the link here.
There is the newest log file
https://drive.google.com/file/d/0B47QgVT2D3G8Mm1JXzFCLWFjczQ/view?usp=sharing
Thx for the logs. In both cases the NIS seems to be on a fork that is too deep to resolve, hard to tell why that happened.
if you want to try again with your local NIS you can download the current blockchain from bob:
bob.nem.ninja/nis5_mainnet.h2.db.zip
you would have to stop NIS, delete the db in the folder c:<your user>\nem\nis\data and put the unzipped db there and then restart nis (and switch back from alice3 to local).
Another thing i see is that all my alice server are blacklisted by your NIS. Did you change anything in the file peers-config_mainnet.json?
Haha, no I have no clue what that is. Didn’t change anything.
With this database it is working for me.
I didn’t change anything but I haven’t run NIS since 4 months. When I started to run NIS 4 day ago the sync was fast at the begining but near 222159 block it was slow down.
Anyway, thanks for your help BloodyRookie.