I never had any problems with the block analysis at NIS start... And I dont think that is finnikola's problem. He is talking about synchronizing. But if that .db goes up to block ~49000, something is wrong...
Did you shut down NCC and NIS, replace your .db in ...../nis/data/ and restart NIS?
[/quote
Yes, i killed Nis and NCC process. I also deleted the other files in nis/data.
I'll try again when I return home this evening.
Then try to download "[url=http://bob.nem.ninja/nis4.h2.zip]nis4.h2.zip" from http://bob.nem.ninja/ and extract it to your nis/data directory.
I've downloaded the database from bob.nem.ninja and extracted to nis/data but....again stuck at block 38476....how it is possible?
Must i delete other files?
Can you supply the logs for NIS? They are located in c:\users\<your user>\nem\nis\logs for windows and home/nem/nis/logs for a linux based system.
I'm running on a server with Debian 7 32-bit: CPU 600MHz; 1GB RAM(512MB Swap)
I did a step by step tutorial on how to do this:
https://forum.ournem.com/beta-launch-discussion/how-to-setup-a-node-in-vps/msg11018/#msg11018
I'm trying to understand minimum memory required by NIS.
I created a new node and set -Xmx850M for NIS and CACHE_SIZE=65536 in db.properties
That was ok before block 47256 then I got java.lang.OutOfMemoryError: Java heap space
So I increased -Xmx but node was unable to synchronize:<br />03:01:22 INFO synchronizeNodeInternal -> chain inconsistent: calling undoTxesAndGetScore() (1 blocks). (org.nem.nis.sync.BlockChainUpdater c)<br />03:01:24 INFO hit failed on block 47256 gen b9a06fb199a11bb551827b2f8a83e15c09b8f868a1b1f7822fed188a73351d30 (org.nem.nis.sz a)<br />
I deleted db and now I'm trying again.
I have a backup of db and logs if devs need it.
I'm running on a server with Debian 7 32-bit: CPU 600MHz; 1GB RAM(512MB Swap)
I did a step by step tutorial on how to do this:
https://forum.ournem.com/beta-launch-discussion/how-to-setup-a-node-in-vps/msg11018/#msg11018
600 MHz single core!? And that works fine?
To synchronize the CPU is at 100%. Is now running NCC, NIS and bot.
I'm running on a server with Debian 7 32-bit: CPU 600MHz; 1GB RAM(512MB Swap)
I did a step by step tutorial on how to do this:
https://forum.ournem.com/beta-launch-discussion/how-to-setup-a-node-in-vps/msg11018/#msg11018
600 MHz single core!? And that works fine?
[img width=686 height=106]http://i.imgur.com/cVN5D7v.png[/img]
About the CPU speed, is a intel E5-2630 but i choose the minimun plan: 0.5 core
Then the CPU should come with half the processing power?
http://www.host1plus.com/vps-hosting/
I've tried running with ubuntu, but this crash for keeping CPU always 100% with NEM runing.
Ok, I guess that is not comparable to a dual core 1 GHz armv7 cpu…
Then try to download "[url=http://bob.nem.ninja/nis4.h2.zip]nis4.h2.zip" from http://bob.nem.ninja/ and extract it to your nis/data directory.
I've downloaded the database from bob.nem.ninja and extracted to nis/data but....again stuck at block 38476....how it is possible?
Must i delete other files?
Can you supply the logs for NIS? They are located in c:\users\<your user>\nem\nis\logs for windows and home/nem/nis/logs for a linux based system.
Sorry, but i deleted totally nem folder and installed again.
Now with the database on bob.nem.ninja is all ok, passed block 49000 and now is at 62765 :)
...
Im curious if NXT and NEM will run without problems at the same time.
...
Now i can say that NXT and NIS can run without any problem at the same time on the Cubietruck. They are on from 48 hours.
I use NCC from my remote PC.
I tried to activate remote harvesting, but in about 3 hours i still see "activating remote harvesting" it is normal?
NIS is synchronized.
Yes, it takes 24 hours.
Yes, it takes 24 hours.
Ok.
But when i activated it there was the field "Due by (hours)" what is this?
I understand that is maximum time for harvesting and it can not be big than 24 hours. So i must wait 24 hours for start remote harvesting and only for max 24 hours?
Yes, it takes 24 hours.
Ok.
But when i activated it there was the field "Due by (hours)" what is this?
I understand that is maximum time for harvesting and it can not be big than 24 hours. So i must wait 24 hours for start remote harvesting and only for max 24 hours?
I have the same question.
The "Due by" field is just the time after which the transaction, which activates remote harvesting, expires. The activation is done via a transaction and transactions must be included in a block before they expire. Don't wory if you use 12 (hours) then it will always have been included in a block before expiration 
first start of 0.4.48-BETA without xfce:
NIS start: 3 hours, 44 minutes, 40 seconds
Block analysis (0 till 100,0XX): 3 hours, 42 minutes, 38 seconds
NCC start: 25 seconds
What happened?
Actually i am not aware that anything changed. What was the startup time for last version?
Actually i am not aware that anything changed. What was the startup time for last version?
I can't tell you how long it took for 0.4.45 now, but for 0.4.36 it was like 22 minutes:
https://forum.ournem.com/technical-discussion/anybody-with-low-power-computer-(or-even-single-board-computer)-running-nisncc/msg10422/#msg10422
Actually i am not aware that anything changed. What was the startup time for last version?
I can't tell you how long it took for 0.4.45 now, but for 0.4.36 it was like 22 minutes:
https://forum.ournem.com/technical-discussion/anybody-with-low-power-computer-(or-even-single-board-computer)-running-nisncc/msg10422/#msg10422
I think gimre mentioned in the changelog that the latest build starts absurdly slow because of db migrations or whatever and that this will be addressed but not on the testnet.
For me this doesnt look like a db migration but a normal block analysis:
[url=http://postimg.org/image/eflaiz5r1/]
For now I've given up trying to run NIS on my RaspberryPI (B+ model) it was proving to troublesome with crashes and long sync times. For now I'm running a virtual 1GB RAM Centos 6.5 minimal install under Windows Hyper-V (I run a Windows 2012 R2 Server Essentials 24 x 7). I am hoping to return to the PI as a NIS at some point in the future.
KC