Problem node no generate


#10

It seemed to you…
Ok now I’m running.


#11

Done, as soon as we update, let’s see.


#12

Now how long is it to wait to see blocks again?


#13

Not seeing signs I destroyed the knot and I rebuilt it from scratch.
When will I be able to see it?
ScudoNode


#14

*Check if the node is running and syncing the last blocks with:

journalctl -u waves.service -f


#15

Now we also see in dev.pywaves.
It is 5 hours and 30 minutes that it is synchronizing.
How much is still needed?


#16

First not synced, which means that it was synchronizing.
Now forked at 1033312
What it means?
The node has synchronized to that height?
Or do I still have to worry about the anomalous forked node?


#17

Like I said what does the log say when you issue the journalctl -u waves.service -f command?


#18

Now it seems synchronized.
The registry tells me nothing.
The question is after using journalctl -u waves.service -f, to me it never worked, the terminal seems to stop and you never see anything.
Since I have the knot, I have always had to wait for it to see in dev.pywaves, and to see them is synchronized.
However misery are already 2 days for synchronization?


#19

I do not know what to say, the node of new not synced.
DigitalOcean sent me a message saying they have network connectivity problems and my droplet may be affected.
I guess that until they solve, I will not be able to come up with it myself.


#20

Nobody is able to give me other suggestions?


#21

Here you can download a recent valid state from wavesplatform site: http://blockchain.wavesnodes.com

I use on the fly downloading + unpacking (stop waves and rm -r your data dir):

wget -qO- http://blockchain.wavesnodes.com/blockchain_last.tar | tar xv -C /your/waves/dir/with/data/dir

The syncing from the genesis is a pain.


#22

without tar’s v switch it will be a bit faster:)


#23

Thanks ikardanov.
Thanks Hoshingen.
Thanks deemru.
Thanks brox.

It seems to work.
Now who knows when the weather for the next block …


#25

How long does it take to get a block?
The others have already started to get the blocks, after switching to 0.16.2
I do not understand.


#26

Consider to read: How long until founding a block


#27

thank you
So my node should produce 18 blocks.
In reality, before the fork, the production was 10 - 14 blocks.
Then the fork stopped my knot for 30 days.
Now the node is updated to 0.16.2 and as required “rebuild the state database. Node will not run on the old state”.
My expectation is now 8 days, I guess I’ll have to wait again.
With 8 days it should have been at least 3 - 2 blocks.


#28

In probabilities world, there is no “should”. You can have zero in several months and can have 10 blocks in a single day


#29

Yes I understand the world of probalilities but, there is a node that has 607 waves and has produced a block in the last 24 hours. Am I wrong or to start a node, do we need 1000 waves?
I have 21000 and the desert has been behind me for 6 weeks.
Others with this budget are already in production.
Did I realize the wrong steps for my node without realizing it?


#30

This is my waves.conf
Did I do something wrong?
wavesconf_scudonode.pdf (20.3 KB)