Bitcoin Forum

J'ai installé le version v0.15.0.1 et cela fait plus de 4 heures qu'il affiche le message "Rebobinage des blocs..." . J'ai essayé de l'arrêter, et j'obtiens le fenêtre qui dit de ne pas fermer avant que ce ne soit terminé. Il consomme de plus en plus de mémoire et va finir par planter de toutes les façons. Si j'arrête le PC brutalement, je suis partie pour 15 jours de chargement de la blockchain...

Est-ce que quelqu'un peut m'aider ?

@hbou, il suffit de lire le français

---

Very few reading this in this section will be able to understand what you're saying, you might want to post this in your local board instead.

I cannot work out what language you are using to be able to convert your post into English.

EDIT AHA it's french!

My Post Translated:

Your post in English

In response to this:
The client needs to scan the whole blockchain, if you are after something that takes up much less memory then you can look for something like www.electrum.org/#download (An alternative to bitcoin core), otherwise, you'll just have to keep downloading the blockchain.
Wait out the 15 days if you haven't already and repost your findings if you wish to continue using core.

Translation:

I am sorry, I thougt it was in french. I don not know where to post it elsewhere.

I install the last release of bitcoin core, the 15.0.1. For the last 4 hours, it is on the first windows saying "rewinding the blocs". I try to stop it but I got the window saying I have to wait (if I stop it violently, it takes me 15 days to reload the blockchain). I do not know what to do.

Is this the first time you have done a violent shutdown on it and got to wait 15 days?

In the folder where your blocks are stored, can you open a file called debug.log and paste it in here?

Here's the French board: https://bitcointalk.org/index.php?board=13.0 they might be able to help you better (especially if the debug.log is in french)

I did not do a violent shutdown. But I know that to reload the blockchain takes something like 15 days.
The log is in english...  and very big.
Here is the first and last lines. It seems it freed memory, so for that it will be OK.
What I would like to know is :

- Is it normal ?
- how long can it takes ?
- what happen it I shutdown the PC (I have electricity's cut where I live).

2017-10-27 03:52:34 Bitcoin version v0.15.0.1
2017-10-27 03:52:34 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-10-27 03:52:35 Assuming ancestors of block 0000000000000000003b9ce759c2a087d52abc4266f8f4ebd6d768b89defa50a have valid signatures.
2017-10-27 03:52:35 Using the 'standard' SHA256 implementation
2017-10-27 03:52:40 Default data directory C:\Users\Hervé\AppData\Roaming\Bitcoin
2017-10-27 03:52:40 Using data directory C:\Hervé\Bitcoin
2017-10-27 03:52:40 Using config file C:\Hervé\Bitcoin\bitcoin.conf
2017-10-27 03:52:40 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core ne s'est pas encore arrêté en toute sécurité..."
2017-10-27 03:52:40 Using at most 125 automatic connections (2048 file descriptors available)
2017-10-27 03:52:40 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2017-10-27 03:52:40 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2017-10-27 03:52:40 Using 2 threads for script verification
2017-10-27 03:52:40 scheduler thread start
2017-10-27 03:52:40 init message: Verifying wallet(s)...
2017-10-27 03:52:40 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2017-10-27 03:52:40 Using wallet wallet.dat
2017-10-27 03:52:40 CDBEnv::Open: LogDir=C:\Hervé\Bitcoin\database ErrorFile=C:\Hervé\Bitcoin\db.log
2017-10-27 03:52:40 Cache configuration:
2017-10-27 03:52:40 * Using 2.0MiB for block index database
2017-10-27 03:52:40 * Using 8.0MiB for chain state database
2017-10-27 03:52:40 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-10-27 03:52:40 init message: Chargement de l'index des blocs...
2017-10-27 03:52:40 Opening LevelDB in C:\Hervé\Bitcoin\blocks\index
2017-10-27 03:52:40 Opened LevelDB successfully
2017-10-27 03:52:40 Using obfuscation key for C:\Hervé\Bitcoin\blocks\index: 0000000000000000
2017-10-27 03:53:16 LoadBlockIndexDB: last block file = 1040
2017-10-27 03:53:16 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=40, size=33034385, heights=491783...491931, time=2017-10-26...2017-10-27)
2017-10-27 03:53:16 Checking all blk files are present...
2017-10-27 03:53:17 LoadBlockIndexDB: transaction index disabled
2017-10-27 03:53:17 Opening LevelDB in C:\Hervé\Bitcoin\chainstate
2017-10-27 03:53:22 Opened LevelDB successfully
2017-10-27 03:53:22 Using obfuscation key for C:\Hervé\Bitcoin\chainstate: 59b47d3a5ab915db
2017-10-27 03:53:22 Upgrading utxo-set database...
2017-10-27 03:53:22 [0%]...[10%]...[20%]...[30%]...[40%]...[50%]...[60%]...[70%]...[80%]...[90%]...[100%]...[DONE].
2017-10-27 04:55:08 Loaded best chain: hashBestChain=000000000000000000ad05148004a90841a1c26b0a079d3a25f57ebdb72c70bb height=491825 date=2017-10-26 08:58:27 progress=0.999163
2017-10-27 04:55:08 init message: Rebobinage des blocs...
2017-10-27 04:57:35 Leaving InitialBlockDownload (latching to false)
2017-10-27 04:57:41 UpdateTip: new best=00000000000000000064eecb358aea18cc749adf8a631a0d4b6e2d871b7e3773 height=491824 version=0x20000000 log2_work=87.3564 tx=265757012 date='2017-10-26 08:49:30' progress=0.999155 cache=1.4MiB(10820txo)

[...]

2017-10-27 16:41:19 UpdateTip: new best=0000000000000000006c614f43d9282f725821fb420be4da00d0f67afc78ce45 height=490042 version=0x20000000 log2_work=87.288102 tx=262426042 date='2017-10-15 23:31:25' progress=0.988184 cache=99.0MiB(257540txo)
2017-10-27 16:41:57 UpdateTip: new best=000000000000000000d818e093a22f44ac55d6f6728e3bb6a1db675c8e12ffe4 height=490041 version=0x20000000 log2_work=87.288063 tx=262423963 date='2017-10-15 23:05:25' progress=0.988166 cache=99.6MiB(262799txo)
2017-10-27 16:42:44 UpdateTip: new best=0000000000000000001efd3bea78bf4f5a05e38857433fda6a8106f7d681e12c height=490040 version=0x20000000 log2_work=87.288024 tx=262422229 date='2017-10-15 22:53:11' progress=0.988157 cache=100.3MiB(268444txo)
2017-10-27 16:43:14 UpdateTip: new best=000000000000000000a4e772f7195a9f2617a2e74cb05b85b4c7f967d87b26ca height=490039 version=0x20000000 log2_work=87.287984 tx=262421039 date='2017-10-15 22:46:30' progress=0.988152 cache=100.8MiB(272415txo)
2017-10-27 16:44:12 UpdateTip: new best=0000000000000000006f47f9bacb00d7b41db297a10def2596a10e03b6473192 height=490038 version=0x20000000 log2_work=87.287945 tx=262419072 date='2017-10-15 22:32:51' progress=0.988142 cache=101.5MiB(278325txo)
2017-10-27 16:45:10 UpdateTip: new best=00000000000000000024407d580e4fcc34458a6a3ade8905a3cfa41dff4a61ef height=490037 version=0x20000000 log2_work=87.287906 tx=262417509 date='2017-10-15 22:22:10' progress=0.988133 cache=102.2MiB(284307txo)
2017-10-27 16:45:56 UpdateTip: new best=00000000000000000037901da7b8fb76ee050b1ae084f2d3984eb0ebf730e159 height=490036 version=0x20000000 log2_work=87.287867 tx=262415385 date='2017-10-15 22:02:49' progress=0.988119 cache=103.1MiB(291012txo)
2017-10-27 16:46:54 UpdateTip: new best=000000000000000000c07451897e9cc9e561e7e2788eeb8c9e893b302ab813d5 height=490035 version=0x20000000 log2_work=87.287827 tx=262413648 date='2017-10-15 21:51:30' progress=0.988111 cache=104.0MiB(298651txo)
2017-10-27 16:48:05 UpdateTip: new best=00000000000000000010dcf2eada6521cafc4aa9f0b3c87ccc39d0e4a4545d53 height=490034 version=0x20000000 log2_work=87.287788 tx=262412564 date='2017-10-15 21:43:24' progress=0.988104 cache=105.1MiB(307425txo)
2017-10-27 16:49:06 UpdateTip: new best=0000000000000000002864427cd469926b3fbf0b8bf113da4113ffeb238c781a height=490033 version=0x20000000 log2_work=87.287749 tx=262409620 date='2017-10-15 21:13:58' progress=0.988083 cache=105.7MiB(312321txo)

There deosn't seem to be anything in the log that is erroneous.

The 15 days depends on how good your computer is, I assume it's a low spec as I have a low spec (old) one that's faster.

It'll probably restart, if you can get something lie a battery that it can use or keep safely shutting it down every 1000 blocks it might be OK.
Sometimes, I shut mine down from the power button (so it doesn't safely shutdown) and 80% of the time it's fine, 20% it's corrupted...

OK. I restore the release 13 and a backup of my wallet.
Everything is now OK.

I notice that I had the 32 bit release of the release 13 and I had installed the 64 bits release of the 15.0.1.
Do you think that can be my problem ?

Yes that can cause issues as the amount of memory (RAM) access is different between the two which can also effect other things. If your computer is not 64 bit then running a 64 bit will cause lag (if it runs at all).

OK. Thank you very much. I will try another day with the 32 bits release.

By the way, it seems that now we can shut bitcoin core. I think it was a problem with older release.
My computer is an Intel i5, 3 years old. I think the performance problem is the disk access. 149Go is a lot of data.

Ah yes it might be a hard drive issue.

If you want advice, you can try defragmenting the drive and you can use software already build into windows (if it is windows you're using). Just right click>properties>tools>defragment on the disk in windows explorer.

I though to be on a french forum... ???

Yes, you are. ..

 ;D

Ahhh. Oops. That's me for not noticing the board had changed (its the same thread link so it still comes up with it). Haha

So, I do understand better, now! :D Thx...

Réflexion de débutant : pour télécharger la blockchain, il faut donc prévoir : :)
- une place disponible suffisante sur le disque dur,
- un PC équipé d'un onduleur,
- un période favorable pour que le PC puisse rester en marche ininterrompue le temps nécessaire.
Question : y a-t-il une commande pour suspendre ou interrompre proprement ce rebobinage ?...

I am sorry, I thougt it was in french. I don not know where to post it elsewhere.

I install the last release of bitcoin core, the 15.0.1. For the last 4 hours, it is on the first windows saying "rewinding the blocs". I try to stop it but I got the window saying I have to wait (if I stop it violently, it takes me 15 days to reload the blockchain). I do not know what to do.

OK. I restore the release 13 and a backup of my wallet.
Everything is now OK.

I notice that I had the 32 bit release of the release 13 and I had installed the 64 bits release of the 15.0.1.
Do you think that can be my problem ?

OK. I restore the release 13 and a backup of my wallet.
Everything is now OK.

I notice that I had the 32 bit release of the release 13 and I had installed the 64 bits release of the 15.0.1.
Do you think that can be my problem ?

Ah yes that'll probably have been the issue. Anyway hopefully you can try putting a 32 bit version of 0.15.0.1 instead to see if that solves the issue and it works. I'm not sure bitcoin core 13 is compatible with segwit2x but it should be compatible with segwit.

J'ai installé le version v0.15.0.1 et cela fait plus de 4 heures qu'il affiche le message "Rebobinage des blocs..." . J'ai essayé de l'arrêter, et j'obtiens le fenêtre qui dit de ne pas fermer avant que ce ne soit terminé. Il consomme de plus en plus de mémoire et va finir par planter de toutes les façons. Si j'arrête le PC brutalement, je suis partie pour 15 jours de chargement de la blockchain...

Est-ce que quelqu'un peut m'aider ?

I did not do a violent shutdown. But I know that to reload the blockchain takes something like 15 days.
The log is in english...  and very big.
Here is the first and last lines. It seems it freed memory, so for that it will be OK

I think you may have forgotten toadd the log there?

Did you try it with the 32 bit version?