GitLab

User has been syncing for since jan 28th and is still 1 year + behind.

Excerpts from his debug.log / db.log which he posted in the ticket

(requested the files waiting for a reply):

• 2018-02-01 18:37:34 Systemnode dump finished 63ms
• 2018-02-01 18:37:34 Verifying snpayments.dat format...
• 2018-02-01 18:37:34 Loaded info from snpayments.dat 16ms
• 2018-02-01 18:37:34 Votes: 0, Blocks: 0
• 2018-02-01 18:37:34 Writting info to snpayments.dat...
• 2018-02-01 18:37:35 Written info to snpayments.dat 31ms
• 2018-02-01 18:37:35 Budget dump finished 47ms
• 2018-02-01 18:37:35 *** System error while flushing: CDB : Error -30974, can't open database
• 2018-02-01 18:37:37 CDBEnv::EnvShutdown : Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery
• 2018-02-01 18:37:37 Shutdown: done

The error is: (from the debug log)

• date=2015-03-06 11:55:32 progress=0.034821 cache=2.6MiB(13079tx)
• 2018-02-01 14:18:24 *** System error while flushing: CDB : Error -30974, can't open database
• 2018-02-01 14:37:37 ping timeout: 1200.057009s
• 2018-02-01 14:38:19 ping timeout: 1200.077018s
• 2018-02-01 14:38:22 socket sending timeout: 1201s
• 2018-02-01 14:38:23 socket sending timeout: 1201s
• 2018-02-01 16:01:39 ERROR: ProcessNewBlock : ActivateBestChain failed
• 2018-02-01 16:01:39 socket recv error An established connection was aborted by the software in your host machine. (10053)
• 2018-02-01 16:01:39 addcon thread interrupt
• 2018-02-01 16:01:39 dumpaddr thread stop
• 2018-02-01 16:01:39 opencon thread interrupt
• 2018-02-01 16:01:39 msghand thread interrupt
• 2018-02-01 16:01:39 net thread interrupt
• 2018-02-01 16:01:39 PrepareShutdown: In progress...

he db.log has these messages:

• DB_ENV->log_flush: LSN of 1/7628 past current end-of-log of 1/476
• Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
• PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
• wallet.dat: unable to flush page: 7
• PANIC: fatal region error detected; run recovery
• PANIC: fatal region error detected; run recovery
• PANIC: fatal region error detected; run recovery
• PANIC: fatal region error detected; run recovery
• PANIC: fatal region error detected; run recovery
• PANIC: fatal region error detected; run recovery
• PANIC: fatal region error detected; run recovery
• PANIC: fatal region error detected; run recovery
• PANIC: fatal region error detected; run recovery
• File handles still open at environment close
• Open file handle: C:\Users\Tester\AppData\Roaming\Crown\database\log.0000000001
• PANIC: fatal region error detected; run recovery
• file wallet.dat has LSN 1/7628, past end of log at 1/476
• Commonly caused by moving a database from one database environment to another without clearing the database LSNs, or by removing all of the log files from a database environment

The wallet I am using is:

Crown Core version v0.12.3.0-da38c363 (64-bit)

Copyright (C) 2009-2017 The Bitcoin Core Developers

Copyright (C) 2014-2017 The Crown Core Developers

================================

my system specs

OS Name Microsoft Windows 10 Pro Version 10.0.16299 Build 16299 System Model HP Pavilion 15 Notebook PC System Type x64-based PC Processor AMD A8-6410 APU with AMD Radeon R5 Graphics, 2000 Mhz, 4 Core(s), 4 Logical Processor(s)