Processblock not accepted, leveldb batch commit failure: IO error: unsufficient space #20327

1. 
   RagnarLothbrok25 commented at 8:40 am on November 6, 2020: none

   Fatal error has occurred, BAD_Alloc runaway exception error when starting bitcoin core

   Debug log says error on processblock Then creates orphanblocks and finally ends with:

   LevelDB batch commit failure: IO error: winmapfile.append::unmapcurrent region or mapnewregion : unsufficient memory available to process this task

   Error AcceptBlock : Addtoblockindex failed Error ProcessBlock : Acceptblock failed Processblock, block not accepted

   Orphanblock

   Can anyone help me with this issue?

   I did fix the bad alloc runaway error with this memory issue before by configuring the configuration file adding the following:

   Listen=1 Bind=0.0.0.0 Port=8333 Maxconnections=64 Maxmempool=32 Upnp=1 Dnsseed=1 Discover=1

   Dbcache=18 Dblogsize=50 Par=1 Checkblocks=2000 Checklevel=6

   Disablewallet=0

   Rpcbind= 127.0.0.1 Rpcport=8333 Rpcallowip=127.0.0.1

   Maxuploadtargets=32 Rescan=1

   Maxorphanblocksmib=80

   Testnet=0

   Can anyone help me solve the issue?

   It keeps coming back at the memory issue as the underlying problem but why does it not accept the block?

   I think I need to fix the memory issue first. This is done on the latest bitcoin core wallet

2. RagnarLothbrok25 added the label Bug on Nov 6, 2020
3. MarcoFalke removed the label Bug on Nov 6, 2020
4. MarcoFalke added the label Questions and Help on Nov 6, 2020
5. 
   MarcoFalke commented at 8:46 am on November 6, 2020: member

   What hardware/OS are you running on?
6. MarcoFalke added the label Data corruption on Nov 6, 2020
7. MarcoFalke added the label Resource usage on Nov 6, 2020
8. 
   RagnarLothbrok25 commented at 8:51 am on November 6, 2020: none

   Windows 10 latest version, 8 gig Ram, also did chkdsk through command prompt
9. 
   MarcoFalke commented at 9:19 am on November 6, 2020: member

   Does the error happen when you remove this line?

   Checkblocks=2000

10. 
    RagnarLothbrok25 commented at 9:33 am on November 6, 2020: none

    Bad alloc error still occurs when removing that line
11. 
    MarcoFalke commented at 10:22 am on November 6, 2020: member

    Without a debug log this is hard to debug

    Please check your debug.log for possible causes; Alternatively you can upload it here.

    You can find the debug.log in your data dir.

    Please be aware that the debug log might contain personally identifying information.

12. MarcoFalke closed this on Nov 8, 2020

    ---

13. 
    MarcoFalke commented at 5:38 pm on November 8, 2020: member

    Regardless of the issue here, I suggest you clear you config of settings that aren’t applicable. There is at least one setting misspelled and another one long removed from Bitcoin Core anyway.
14. DrahtBot locked this on Feb 15, 2022

Contributors
RagnarLothbrok25 MarcoFalke

Labels
Data corruption Resource usage Questions and Help