Hi all,
since we want to make the beta as stable as possible, the devs need your support.
If your node is stuck at a certain height, don't just delete the database and resync from scratch. The db contains valuable information for the devs, even more than the log.
Copy the db to a folder of your choice (the db is the file nis4.h2.db in the folder nem/nis/data), upload it to some file hoster and send me the link to it.
That way we hopefully are able to reproduce the behavior you experienced.
Bloody Rookie
A NIS log in addition would be good too
Stuck at block 11521.
db: https://www.dropbox.com/s/p91y8d7u2jpvoia/nis4.h2.db.tar.gz?dl=0
nis log: https://www.dropbox.com/s/0stjcyg7vsb7bkh/nis-log.tar.gz?dl=0
Edit: After restarting NIS and NCC (stopped to copy the db), it is now on block 13050 (no timeout yet, but stuck for a while now).
Was off line for some 2 days, tried again yesterday and now I am synced.
Was off line for some 2 days, tried again yesterday and now I am synced.
Can you supply a log again? Just to see who got you synced.
Was off line for some 2 days, tried again yesterday and now I am synced.
Can you supply a log again? Just to see who got you synced.
PM sent.
This weekend after running for many hours I saw that I was not synced.
Command window said NIS server not available.
Tried a re-start let it run for some hrs but no sync.
Have uploaded new logs.
PM sent.
This weekend after running for many hours I saw that I was not synced.
Command window said NIS server not available.
Tried a re-start let it run for some hrs but no sync.
Have uploaded new logs.
PM sent.
Weird after posting and being off line for some days I gave it another try.
Now NEM is synced again.
Hi there.
I posted yesterdays (03_11-14) stucked db and todays DB.
The one from today (04_11-14) I got a blockchain branch while spamming network with the bot.
I noticed I was 10 blocks in future than blockchain. I restarted the client and the ./nix.runNis.sh dont let use the db cause its corrupted and exits.
Solution: delete the DB and logs and restart everything.
https://www.dropbox.com/s/grgb85fdumtvsid/Nem%20Logs.tar.gz?dl=0
@Parana: The block chain explorer is still on the old version so when you start spamming then the block chain explorer will be behind. I asked in the original 0.4.17-beta thread not to spam before the fork to give users the chance to upgrade.
@Parana: The block chain explorer is still on the old version so when you start spamming then the block chain explorer will be behind. I asked in the original 0.4.17-beta thread not to spam before the fork to give users the chance to upgrade.
Will you see a potential fork problem arising in the future when transaction volume is high emulating a spam and users are not ready yet with a new wallet?
@Parana: The block chain explorer is still on the old version so when you start spamming then the block chain explorer will be behind. I asked in the original 0.4.17-beta thread not to spam before the fork to give users the chance to upgrade.
Will you see a potential fork problem arising in the future when transaction volume is high emulating a spam and users are not ready yet with a new wallet?
Starting with 0.4.17 I don't think that spamming the network should cause a fork. All future versions should be performant enough too.
Not sure if that answers your question.
@Parana: The block chain explorer is still on the old version so when you start spamming then the block chain explorer will be behind. I asked in the original 0.4.17-beta thread not to spam before the fork to give users the chance to upgrade.
Will you see a potential fork problem arising in the future when transaction volume is high emulating a spam and users are not ready yet with a new wallet?
Starting with 0.4.17 I don't think that spamming the network should cause a fork. All future versions should be performant enough too.
Not sure if that answers your question.
Ok. Understood. Thanks.
@bloodrookye should i stop? Its sending a transaction every 30 seconds
Enviado de meu Nexus 4 usando Tapatalk
@bloodrookye should i stop? Its sending a transaction every 30 seconds
Enviado de meu Nexus 4 usando Tapatalk
maybe it is fair to stop right now and start after block height 24244 again.
@bloodrookye should i stop? Its sending a transaction every 30 seconds
Enviado de meu Nexus 4 usando Tapatalk
maybe it is fair to stop right now and start after block height 24244 again.
@bloodyrookie I asked to turn off my notebook. I noticed I was in a branch cause I was sending a transaction every 15 seconds. Taking a look at the blockchain, lots of blocks have zero transaction. The block height was late and I saw my transactions wasnt listed. I also noticed there are new blocks sometimes in 10 seconds. Unless its an error from the blockexplorer. Thanks [emoji12]
Enviado de meu Nexus 4 usando Tapatalk
Stuck at block 36710. Have tried reboot machine / nis, not fix.
Data and Log - [url=https://mega.co.nz/#!mAEWECoT!Vg8WyiSKBcf5pmc3ImAM6AWQ_twF2BGOdfZ0HUc2fHQ]https://mega.co.nz/#!mAEWECoT!Vg8WyiSKBcf5pmc3ImAM6AWQ_twF2BGOdfZ0HUc2fHQ