Bitcoin Forum>Bitcoin>Bitcoin Technical Support
Pages:
Author

Topic: Crash without error during IBD (Read 292 times)

ABCbits
legendary
Activity: 2870
Merit: 7490
Crypto Swap Exchange
Crash without error during IBD
July 15, 2022, 04:46:57 AM
#24
Quote from: kemist on July 14, 2022, 05:25:11 PM
It says that it passed the overall-health self-assessment. Here's the part with the lines you referred to. I don't know what I'm looking for, but it appears that it's not finding anything wrong (?)

Code:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       2079785102
193 Load_Cycle_Count        0x0012   001   001   000    Old_age   Always       -       1579884

SMART Error Log Version: 1
No Errors Logged

At a glance S.M.A.R.T. information doesn't mention anything wrong with your HDD. But value of ID# 192 and 193 are abnormally high and could shorten your HDD lifespan. Ubuntu Wiki has page about it at https://wiki.ubuntu.com/DanielHahler/Bug59695, although it's written 12 years ago.
ABCbits
legendary
Activity: 2870
Merit: 7490
Crypto Swap Exchange
Re: Crash without error during IBD
July 14, 2022, 06:38:52 AM
#21
Quote from: kemist on July 13, 2022, 01:05:27 PM
Code:
$ sudo dmesg --level=warn
[    1.257330] acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    1.259352] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\_SB.PCI0.LPC.PMIO) (20210730/utaddress-204)
[    1.259371] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPC.LPIO) (20210730/utaddress-204)
[    1.259381] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPC.LPIO) (20210730/utaddress-204)
[    1.259389] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPC.LPIO) (20210730/utaddress-204)
[    1.259396] lpc_ich: Resource conflict(s) found affecting gpio_ich

This could be safely ignored[1]. I also see similar warning message on my own device.

Quote from: kemist on July 13, 2022, 01:05:27 PM
Code:
$ sudo dmesg --level=err,crit,alert,emerg
[241386.467654] ACPI: \_SB_.PCI0.LPC_.EC__.BAT1: Unable to dock!

It's related with suspend feature[2-3] which shouldn't be relevant in this case.

Quote from: kemist on July 13, 2022, 01:05:27 PM
Code:
$ sudo dmesg --level=warn
[241387.735718] ata1.00: ATA Identify Device Log not supported
[241387.738884] ata1.00: ATA Identify Device Log not supported

Honestly i'm not sure what this one means.

Quote from: kemist on July 13, 2022, 01:11:30 PM
How do I confirm that the HDD is the problem

Aside from testing which could take some time, you could check S.M.A.R.T. status of your HDD. Ubuntu website has detailed guide about it using smartmontools[4]. Usually i just run command sudo smartctl -a /dev/sda and check raw value of those two attributes for quick check.

Code:
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   
197 Current_Pending_Sector 

[1] https://unix.stackexchange.com/a/99550
[2] https://patchwork.kernel.org/project/linux-acpi/patch/1406670374.2406.27.camel@x220/
[3] https://lists.archlinux.org/pipermail/arch-general/2013-July/033839.html
[4] https://help.ubuntu.com/community/Smartmontools
kemist
newbie
Activity: 11
Merit: 4
Re: Crash without error during IBD
July 14, 2022, 05:25:11 PM
#20
It says that it passed the overall-health self-assessment. Here's the part with the lines you referred to. I don't know what I'm looking for, but it appears that it's not finding anything wrong (?)

Code:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   062    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   040    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0007   225   225   033    Pre-fail  Always       -       1
  4 Start_Stop_Count        0x0012   092   092   000    Old_age   Always       -       13749
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   040    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   075   075   000    Old_age   Always       -       11296
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   098   098   000    Old_age   Always       -       4349
191 G-Sense_Error_Rate      0x000a   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       2079785102
193 Load_Cycle_Count        0x0012   001   001   000    Old_age   Always       -       1579884
194 Temperature_Celsius     0x0002   176   176   000    Old_age   Always       -       34 (Min/Max 13/48)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0
223 Load_Retry_Count        0x000a   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

Quote from: ABCbits on July 14, 2022, 06:38:52 AM

Aside from testing which could take some time, you could check S.M.A.R.T. status of your HDD. Ubuntu website has detailed guide about it using smartmontools[4]. Usually i just run command sudo smartctl -a /dev/sda and check raw value of those two attributes for quick check.

Code:
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   
197 Current_Pending_Sector 

[1] https://unix.stackexchange.com/a/99550
[2] https://patchwork.kernel.org/project/linux-acpi/patch/1406670374.2406.27.camel@x220/
[3] https://lists.archlinux.org/pipermail/arch-general/2013-July/033839.html
[4] https://help.ubuntu.com/community/Smartmontools
kemist
newbie
Activity: 11
Merit: 4
Re: Crash without error during IBD
July 14, 2022, 12:43:58 PM
#19
Thanks!

I did check the temp during another run, and it was not over-heating, at least for the first 6 or so hours (about 50C). I also took the time to properly open up the machine and clean out remaining dust, but it looked quite clean already, so I guess I did a good job last time.

I need to think about how much to spend on this... so far it's been about what I can do for free.

Quote from: NotATether on July 13, 2022, 11:20:14 PM
Quote from: kemist on July 13, 2022, 01:11:30 PM
I would like to narrow this down to what specific hardware failure I am dealing with before investing money. Someone else has been suggesting I get an external SSD. How do I confirm that the HDD is the problem, and, if it is, then will an external SSD (most likely) solve it?
There are a number of tools for testing hard disks for problems.
If a CPU overheats, then the entire computer powers off (a "halt", not a graceful shutdown), from my experience. Misbehaving fans can cause the CPU to get hot, which is not happening in your case according to the sensors output. Your CPU temperature is in fact quite normal.

But basically, the internal hard disk (hence the "ata" in the messages) is the problematic part, and you should swap it with a newer internal hard disk - HDD or SSD - whatever your PC supports, doesn't make a difference in stablity really - make sure the new disk is not like 5 years old though Smiley.

Plugging external disks will not make the problem with the internal hard disk go away.

NotATether
legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
Re: Crash without error during IBD
July 13, 2022, 11:20:14 PM
#18
Quote from: kemist on July 13, 2022, 01:11:30 PM
I would like to narrow this down to what specific hardware failure I am dealing with before investing money. Someone else has been suggesting I get an external SSD. How do I confirm that the HDD is the problem, and, if it is, then will an external SSD (most likely) solve it?
There are a number of tools for testing hard disks for problems.
If a CPU overheats, then the entire computer powers off (a "halt", not a graceful shutdown), from my experience. Misbehaving fans can cause the CPU to get hot, which is not happening in your case according to the sensors output. Your CPU temperature is in fact quite normal.

But basically, the internal hard disk (hence the "ata" in the messages) is the problematic part, and you should swap it with a newer internal hard disk - HDD or SSD - whatever your PC supports, doesn't make a difference in stablity really - make sure the new disk is not like 5 years old though Smiley.

Plugging external disks will not make the problem with the internal hard disk go away.
LoyceV
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
Re: Crash without error during IBD
July 13, 2022, 02:14:15 PM
#17
Quote from: kemist on July 13, 2022, 12:56:14 PM
Code:
Package id 0:  +51.0°C  (high = +86.0°C, crit = +100.0°C)
Core 0:        +47.0°C  (high = +86.0°C, crit = +100.0°C)
Core 1:        +47.0°C  (high = +86.0°C, crit = +100.0°C)
I forgot to add: this should be during syncing, not while idle. If you checked while syncing, the temperature isn't the problem.

Quote from: kemist on July 13, 2022, 01:11:30 PM
How do I confirm that the HDD is the problem
I've used fdwrite and f3read to test SD cards. If this gives an error on your hard drive (which should be empty to test all sectors), you know for sure it's the problem. But I doubt you'll get an error on a HDD this way.
kemist
newbie
Activity: 11
Merit: 4
Re: Crash without error during IBD
July 13, 2022, 01:11:30 PM
#16
I would like to narrow this down to what specific hardware failure I am dealing with before investing money. Someone else has been suggesting I get an external SSD. How do I confirm that the HDD is the problem, and, if it is, then will an external SSD (most likely) solve it?

To be clear - I don't plan on mining with this set up. Just participate in blockchain integrity and create wallets once in awhile. I am hoping that if I can get through the IBD, then I can keep bitcoin core running on this machine a little while.

Quote from: NotATether on July 13, 2022, 11:37:44 AM
Quote from: kemist on July 12, 2022, 01:55:51 PM
Code:
Jul 12 11:15:40 ThinkPad kernel: ata1.00: ATA Identify Devi>
Jul 12 11:15:40 ThinkPad kernel: ata1.00: ATA Identify Devi>

It is 100% a hardware failure. Kernel prints out ata1.xx messages when there is a problem reading data from the filesystem (due to an underlying hardware error). Sympthoms also include extremely high load times for no apparent reason - caused by a bottleneck while read(2)'ing data from the disk.

The hard disk can fail independently of the fan and CPU temperature.

kemist
newbie
Activity: 11
Merit: 4
Re: Crash without error during IBD
July 13, 2022, 01:05:27 PM
#15
Code:
$ sudo dmesg --level=warn
[sudo] password:
[    0.157708] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[    0.157782]  #2
[    0.161743]  #3
[    0.166408] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.243206] pnp 00:00: disabling [mem 0x000c0000-0x000c3fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[    0.243212] pnp 00:00: disabling [mem 0x000c4000-0x000c7fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[    0.243214] pnp 00:00: disabling [mem 0x000c8000-0x000cbfff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[    0.243217] pnp 00:00: disabling [mem 0x000cc000-0x000cffff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[    0.243219] pnp 00:00: disabling [mem 0x000d0000-0x000d3fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[    0.243221] pnp 00:00: disabling [mem 0x000d4000-0x000d7fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[    0.243223] pnp 00:00: disabling [mem 0x000d8000-0x000dbfff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[    0.243225] pnp 00:00: disabling [mem 0x000dc000-0x000dffff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[    0.384632] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
[    0.384775] platform eisa.0: EISA: Cannot allocate resource for mainboard
[    0.384776] platform eisa.0: Cannot allocate resource for EISA slot 1
[    0.384778] platform eisa.0: Cannot allocate resource for EISA slot 2
[    0.384779] platform eisa.0: Cannot allocate resource for EISA slot 3
[    0.384781] platform eisa.0: Cannot allocate resource for EISA slot 4
[    0.384782] platform eisa.0: Cannot allocate resource for EISA slot 5
[    0.384784] platform eisa.0: Cannot allocate resource for EISA slot 6
[    0.384785] platform eisa.0: Cannot allocate resource for EISA slot 7
[    0.384787] platform eisa.0: Cannot allocate resource for EISA slot 8
[    1.257330] acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    1.259352] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\_SB.PCI0.LPC.PMIO) (20210730/utaddress-204)
[    1.259371] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPC.LPIO) (20210730/utaddress-204)
[    1.259381] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPC.LPIO) (20210730/utaddress-204)
[    1.259389] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPC.LPIO) (20210730/utaddress-204)
[    1.259396] lpc_ich: Resource conflict(s) found affecting gpio_ich
[    1.659456] ata1.00: ATA Identify Device Log not supported
[    1.662039] ata1.00: ATA Identify Device Log not supported
[   18.959770] iwlwifi 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[   19.018011] at24 0-0050: supply vcc not found, using dummy regulator
[   46.572446] kauditd_printk_skb: 28 callbacks suppressed
[241385.357572] unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0000000000000000) at rIP: 0xffffffffb9090b34 (native_write_msr+0x4/0x20)
[241385.357587] Call Trace:
[241385.357589]  
[241385.357590]  ? __restore_processor_state.constprop.0+0x179/0x200
[241385.357598]  restore_processor_state+0x9/0x10
[241385.357602]  x86_acpi_suspend_lowlevel+0x133/0x1a0
[241385.357605]  acpi_suspend_enter+0x56/0x1c0
[241385.357609]  suspend_enter+0x28f/0x340
[241385.357613]  suspend_devices_and_enter+0x12b/0x240
[241385.357617]  enter_state+0x1d2/0x430
[241385.357620]  pm_suspend+0x4e/0xc0
[241385.357623]  state_store+0x81/0xe0
[241385.357628]  kobj_attr_store+0x12/0x20
[241385.357631]  sysfs_kf_write+0x3e/0x50
[241385.357635]  kernfs_fop_write_iter+0x137/0x1c0
[241385.357638]  new_sync_write+0x117/0x1a0
[241385.357644]  vfs_write+0x1cd/0x260
[241385.357647]  ksys_write+0x67/0xe0
[241385.357649]  __x64_sys_write+0x19/0x20
[241385.357651]  do_syscall_64+0x5c/0xc0
[241385.357654]  ? exit_to_user_mode_prepare+0x37/0xb0
[241385.357658]  ? syscall_exit_to_user_mode+0x27/0x50
[241385.357661]  ? __x64_sys_sendmsg+0x1d/0x20
[241385.357665]  ? do_syscall_64+0x69/0xc0
[241385.357667]  ? do_user_addr_fault+0x1e3/0x670
[241385.357670]  ? exit_to_user_mode_prepare+0x37/0xb0
[241385.357673]  ? syscall_exit_to_user_mode+0x27/0x50
[241385.357675]  ? __do_sys_gettid+0x1b/0x20
[241385.357678]  ? do_syscall_64+0x69/0xc0
[241385.357680]  ? asm_exc_page_fault+0x8/0x30
[241385.357684]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[241385.357688] RIP: 0033:0x7f2d9e2e0a37
[241385.357692] Code: 10 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24
[241385.357694] RSP: 002b:00007fff8e6b6c28 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
[241385.357697] RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007f2d9e2e0a37
[241385.357699] RDX: 0000000000000004 RSI: 00007fff8e6b6ce0 RDI: 0000000000000004
[241385.357700] RBP: 00007fff8e6b6ce0 R08: 0000000000000004 R09: 000000007fffffff
[241385.357701] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
[241385.357703] R13: 000055b1b723f2d0 R14: 00007f2d9e3e1a00 R15: 0000000000000004
[241385.357705]  
[241386.469659] done.
[241387.735718] ata1.00: ATA Identify Device Log not supported
[241387.738884] ata1.00: ATA Identify Device Log not supported

Code:
$ sudo dmesg --level=err,crit,alert,emerg
[    0.148658] x86/cpu: VMX (outside TXT) disabled by BIOS
[    0.877661] ima: Error Communicating to TPM chip
[    0.885649] ima: Error Communicating to TPM chip
[    0.889733] ima: Error Communicating to TPM chip
[    0.897746] ima: Error Communicating to TPM chip
[    0.905752] ima: Error Communicating to TPM chip
[    0.913732] ima: Error Communicating to TPM chip
[    0.921730] ima: Error Communicating to TPM chip
[    0.929731] ima: Error Communicating to TPM chip
[   12.923495] mtd device must be supplied (device name is empty)
[   23.295269] mtd device must be supplied (device name is empty)
[   27.902828] mtd device must be supplied (device name is empty)
[241386.467654] ACPI: \_SB_.PCI0.LPC_.EC__.BAT1: Unable to dock!

Quote from: ?? on ??
Quote from: kemist on July 12, 2022, 01:55:51 PM
Here are the journalctl results.

That doesn't tell much, but at least we know it's not crashed/closed due to OOM Killer. Could you check result of this dmesg command since i agree with others it might be hardware failure.

Code:
sudo dmesg --level=warn
sudo dmesg --level=err,crit,alert,emerg

Quote from: kemist on July 12, 2022, 01:55:51 PM
Note that I tried to re-run it last night with slightly different parameters:

Code:
$ bitcoind -prune=20000 -maxmempool=500 -reindex -daemon

FYI, the default maxmempool is only 300 (300 MB) and it's not used during sync/reindex.

Quote from: kemist on July 12, 2022, 01:55:51 PM
Code:
Jul 12 11:15:40 ThinkPad kernel: ata1.00: ATA Identify Devi>
Jul 12 11:15:40 ThinkPad kernel: ata1.00: ATA Identify Devi>

kemist
newbie
Activity: 11
Merit: 4
Re: Crash without error during IBD
July 13, 2022, 12:56:14 PM
#14
Code:
$ sensors
thinkpad-isa-0000
Adapter: ISA adapter
fan1:        3126 RPM

BAT0-acpi-0
Adapter: ACPI interface
in0:          12.55 V 
curr1:         0.00 A 

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +51.0°C  (high = +86.0°C, crit = +100.0°C)
Core 0:        +47.0°C  (high = +86.0°C, crit = +100.0°C)
Core 1:        +47.0°C  (high = +86.0°C, crit = +100.0°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +49.0°C  (crit = +99.0°C)

Quote from: LoyceV on July 13, 2022, 11:15:24 AM
Quote from: kemist on July 13, 2022, 10:47:45 AM
so there could still be dust in there.
Check the CPU temperature. Command:
Code:
sensors
NotATether
legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
Re: Crash without error during IBD
July 13, 2022, 11:37:44 AM
#13
Quote from: kemist on July 12, 2022, 01:55:51 PM
Code:
Jul 12 11:15:40 ThinkPad kernel: ata1.00: ATA Identify Devi>
Jul 12 11:15:40 ThinkPad kernel: ata1.00: ATA Identify Devi>

It is 100% a hardware failure. Kernel prints out ata1.xx messages when there is a problem reading data from the filesystem (due to an underlying hardware error). Sympthoms also include extremely high load times for no apparent reason - caused by a bottleneck while read(2)'ing data from the disk.

The hard disk can fail independently of the fan and CPU temperature.
LoyceV
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
Re: Crash without error during IBD
July 13, 2022, 11:15:24 AM
#12
Quote from: kemist on July 13, 2022, 10:47:45 AM
so there could still be dust in there.
Check the CPU temperature. Command:
Code:
sensors
kemist
newbie
Activity: 11
Merit: 4
Re: Crash without error during IBD
July 13, 2022, 10:47:45 AM
#11
Yes, actually. At some point when I was trying to get the linux install going, it was not booting due to a fan error. I did my best to take apart what I could and blow out some dust. Again, hardware is not my thing, so I was never able to take the case apart completely, so there could still be dust in there.

Quote from: LoyceV on July 12, 2022, 03:31:54 PM
It could be hardware failure. With just 4 GB RAM, you're asking a lot from your old HDD. I recently saw a case in which an incorrect CPU voltage setting caused problems syncing.

Quote from: LoyceV on June 05, 2022, 03:26:36 AM
So that's why Bitcoin Core gives a warning when started for the first time:
Quote
This initial synchronisation is very demanding, and may expose hardware problems with your computer that had previously gone unnoticed.
Memtest won't expose all possible problems.

Any chance the laptop cooling system is filled with dust?
kemist
newbie
Activity: 11
Merit: 4
Re: Crash without error during IBD
July 13, 2022, 10:19:59 AM
#10
This is a huge file, obviously. Here is the very first part:

Code:
2022-07-12T19:01:43Z Bitcoin Core version v22.0.0 (release build)
2022-07-12T19:01:43Z Assuming ancestors of block 00000000000000000008a89e854d57e5667df88f1cdef6fde2fbca1de5b639ad have valid signatures.
2022-07-12T19:01:43Z Setting nMinimumChainWork=00000000000000000000000000000000000000001fa4663bbbe19f82de910280
2022-07-12T19:01:43Z Prune configured to target 20000 MiB on disk for block and undo files.
2022-07-12T19:01:43Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation
2022-07-12T19:01:43Z Default data directory /home/kathryn/.bitcoin
2022-07-12T19:01:43Z Using data directory /home/kathryn/.bitcoin
2022-07-12T19:01:43Z Config file: /home/kathryn/.bitcoin/bitcoin.conf (not found, skipping)
2022-07-12T19:01:43Z Command-line arg: daemon=""
2022-07-12T19:01:43Z Command-line arg: debug="1"
2022-07-12T19:01:43Z Command-line arg: prune="20000"
2022-07-12T19:01:43Z Command-line arg: reindex=""
2022-07-12T19:01:43Z Using at most 125 automatic connections (1024 file descriptors available)
2022-07-12T19:01:43Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2022-07-12T19:01:43Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2022-07-12T19:01:43Z Script verification uses 3 additional threads
2022-07-12T19:01:43Z scheduler thread start
2022-07-12T19:01:43Z Allowing HTTP connections from: 127.0.0.0/8 ::1/128
2022-07-12T19:01:43Z Binding RPC on address ::1 port 8332
2022-07-12T19:01:43Z Binding RPC on address 127.0.0.1 port 8332
2022-07-12T19:01:43Z Initialized HTTP server
2022-07-12T19:01:43Z HTTP: creating work queue of depth 16
2022-07-12T19:01:43Z Starting RPC
2022-07-12T19:01:43Z Starting HTTP RPC server
2022-07-12T19:01:43Z Using random cookie authentication.
2022-07-12T19:01:43Z Generated RPC authentication cookie /home/kathryn/.bitcoin/.cookie
2022-07-12T19:01:43Z Registering HTTP handler for / (exactmatch 1)
2022-07-12T19:01:43Z Registering HTTP handler for /wallet/ (exactmatch 0)
2022-07-12T19:01:43Z Starting HTTP server
2022-07-12T19:01:43Z HTTP: starting 4 worker threads
2022-07-12T19:01:43Z Entering http event loop
2022-07-12T19:01:43Z Using wallet directory /home/kathryn/.bitcoin/wallets
2022-07-12T19:01:43Z init message: Verifying wallet(s)…
2022-07-12T19:01:43Z init message: Loading banlist…
2022-07-12T19:01:43Z Loaded 0 banned node addresses/subnets  27ms
2022-07-12T19:01:43Z net: setting try another outbound peer=false
2022-07-12T19:01:43Z SetNetworkActive: true
2022-07-12T19:01:43Z Reading estimates: 190 buckets counting confirms up to 48 blocks
2022-07-12T19:01:43Z Reading estimates: 190 buckets counting confirms up to 12 blocks
2022-07-12T19:01:43Z Reading estimates: 190 buckets counting confirms up to 1008 blocks
2022-07-12T19:01:43Z Using /16 prefix for IP bucketing
2022-07-12T19:01:43Z Cache configuration:
2022-07-12T19:01:43Z * Using 2.0 MiB for block index database
2022-07-12T19:01:43Z * Using 8.0 MiB for chain state database
2022-07-12T19:01:43Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2022-07-12T19:01:43Z init message: Loading block index…
2022-07-12T19:01:43Z Switching active chainstate to Chainstate [ibd] @ height -1 (null)
2022-07-12T19:01:43Z LevelDB using max_open_files=1000 (default=1000)
2022-07-12T19:01:43Z Wiping LevelDB in /home/kathryn/.bitcoin/blocks/index
2022-07-12T19:01:44Z Opening LevelDB in /home/kathryn/.bitcoin/blocks/index
2022-07-12T19:01:44Z leveldb: Delete type=3 #1
2022-07-12T19:01:44Z Opened LevelDB successfully
2022-07-12T19:01:44Z Using obfuscation key for /home/kathryn/.bitcoin/blocks/index: 0000000000000000
2022-07-12T19:01:44Z WriteBatch memory usage: db=index, before=0.0MiB, after=0.0MiB
2022-07-12T19:01:44Z Removing unusable blk?????.dat and rev?????.dat files for -reindex with -prune
2022-07-12T19:01:49Z Initializing databases...
2022-07-12T19:01:49Z LevelDB using max_open_files=1000 (default=1000)
2022-07-12T19:01:49Z Wiping LevelDB in /home/kathryn/.bitcoin/chainstate
2022-07-12T19:01:49Z Opening LevelDB in /home/kathryn/.bitcoin/chainstate
2022-07-12T19:01:50Z leveldb: Delete type=3 #1
2022-07-12T19:01:50Z Opened LevelDB successfully
2022-07-12T19:01:50Z WriteBatch memory usage: db=chainstate, before=0.0MiB, after=0.0MiB
2022-07-12T19:01:50Z Wrote new obfuscate key for /home/kathryn/.bitcoin/chainstate: af84563ad38d42b4
2022-07-12T19:01:50Z Using obfuscation key for /home/kathryn/.bitcoin/chainstate: af84563ad38d42b4
2022-07-12T19:01:50Z  block index            6156ms
2022-07-12T19:01:50Z Unsetting NODE_NETWORK on prune mode
2022-07-12T19:01:50Z loadblk thread start
2022-07-12T19:01:50Z WriteBatch memory usage: db=index, before=0.0MiB, after=0.0MiB
2022-07-12T19:01:50Z Reindexing finished
2022-07-12T19:01:50Z Pre-allocating up to position 0x1000000 in blk00000.dat
2022-07-12T19:01:50Z   - Load block from disk: 0.09ms [0.00s]
2022-07-12T19:01:50Z BlockChecked: block hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f state=Valid
2022-07-12T19:01:50Z   - Connect total: 0.08ms [0.00s (0.08ms/blk)]
2022-07-12T19:01:50Z   - Flush: 0.03ms [0.00s (0.03ms/blk)]
2022-07-12T19:01:50Z FlushStateToDisk: find files to prune started
2022-07-12T19:01:50Z FlushStateToDisk: find files to prune completed (0.00ms)
2022-07-12T19:01:50Z   - Writing chainstate: 0.07ms [0.00s (0.07ms/blk)]
2022-07-12T19:01:50Z UpdateTip: new best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 version=0x00000001 log2_work=32.000022 tx=1 date='2009-01-03T18:15:05Z' progress=0.000000 cache=0.0MiB(0txo)
2022-07-12T19:01:50Z   - Connect postprocess: 0.06ms [0.00s (0.06ms/blk)]
2022-07-12T19:01:50Z - Connect block: 0.32ms [0.00s (0.32ms/blk)]
2022-07-12T19:01:50Z Enqueuing BlockConnected: block hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f block height=0
2022-07-12T19:01:50Z Enqueuing UpdatedBlockTip: new block hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f fork block hash=null (in IBD=true)
2022-07-12T19:01:50Z Failed to open mempool file from disk. Continuing anyway.
2022-07-12T19:01:50Z loadblk thread exit
2022-07-12T19:01:50Z block tree size = 1
2022-07-12T19:01:50Z nBestHeight = 0
2022-07-12T19:01:50Z BlockConnected: block hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f block height=0
2022-07-12T19:01:50Z UpdatedBlockTip: new block hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f fork block hash=null (in IBD=true)
2022-07-12T19:01:50Z AddLocal([2600:1700:d980:8c70::15]:8333,1)
2022-07-12T19:01:50Z Discover: IPv6 wlp3s0: 2600:1700:d980:8c70::15
2022-07-12T19:01:50Z AddLocal([2600:1700:d980:8c70:5485:b1bc:2ad:584c]:8333,1)
2022-07-12T19:01:50Z Discover: IPv6 wlp3s0: 2600:1700:d980:8c70:5485:b1bc:2ad:584c
2022-07-12T19:01:50Z AddLocal([2600:1700:d980:8c70:9fbf:2d00:dec8:95c]:8333,1)
2022-07-12T19:01:50Z Discover: IPv6 wlp3s0: 2600:1700:d980:8c70:9fbf:2d00:dec8:95c
2022-07-12T19:01:50Z Bound to 127.0.0.1:8334
2022-07-12T19:01:50Z torcontrol thread start
2022-07-12T19:01:50Z Bound to [::]:8333
2022-07-12T19:01:50Z Bound to 0.0.0.0:8333
2022-07-12T19:01:50Z tor: Error connecting to Tor control socket
2022-07-12T19:01:50Z tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect
2022-07-12T19:01:50Z init message: Loading P2P addresses…
2022-07-12T19:01:50Z IP 203.132.93.250 mapped to AS0 belongs to tried bucket 184
2022-07-12T19:01:50Z IP 54.79.89.2 mapped to AS0 belongs to tried bucket 212
2022-07-12T19:01:50Z IP 94.130.141.83 mapped to AS0 belongs to tried bucket 86
2022-07-12T19:01:50Z IP 199.47.254.80 mapped to AS0 belongs to tried bucket 248
2022-07-12T19:01:50Z IP 95.217.145.249 mapped to AS0 belongs to tried bucket 134
2022-07-12T19:01:50Z IP 78.47.106.229 mapped to AS0 belongs to tried bucket 238
2022-07-12T19:01:50Z IP 52.78.60.35 mapped to AS0 belongs to tried bucket 12
2022-07-12T19:01:50Z IP 178.154.197.5 mapped to AS0 belongs to tried bucket 47
2022-07-12T19:01:50Z IP 5.145.14.121 mapped to AS0 belongs to tried bucket 6
2022-07-12T19:01:50Z IP 213.239.219.86 mapped to AS0 belongs to tried bucket 178
2022-07-12T19:01:50Z IP 62.171.154.78 mapped to AS0 belongs to tried bucket 104
2022-07-12T19:01:50Z IP 3.208.33.179 mapped to AS0 belongs to tried bucket 198
2022-07-12T19:01:50Z IP 173.76.123.173 mapped to AS0 belongs to tried bucket 234
2022-07-12T19:01:50Z IP 82.64.162.213 mapped to AS0 belongs to tried bucket 35
2022-07-12T19:01:50Z IP 165.232.99.140 mapped to AS0 belongs to tried bucket 225
2022-07-12T19:01:50Z IP 74.193.71.239 mapped to AS0 belongs to tried bucket 106
2022-07-12T19:01:50Z IP 145.239.103.151 mapped to AS0 belongs to tried bucket 45
2022-07-12T19:01:50Z IP 136.32.25.25 mapped to AS0 belongs to tried bucket 153
2022-07-12T19:01:50Z IP 35.244.103.240 mapped to AS0 belongs to tried bucket 246
2022-07-12T19:01:50Z IP 88.99.1.244 mapped to AS0 belongs to tried bucket 38
2022-07-12T19:01:50Z IP 35.236.40.20 mapped to AS0 belongs to tried bucket 94
2022-07-12T19:01:50Z IP 77.32.121.162 mapped to AS0 belongs to tried bucket 150
2022-07-12T19:01:50Z IP 104.155.12.33 mapped to AS0 belongs to tried bucket 20
2022-07-12T19:01:50Z IP 78.47.218.143 mapped to AS0 belongs to tried bucket 216
2022-07-12T19:01:50Z IP 168.119.89.118 mapped to AS0 belongs to tried bucket 234
2022-07-12T19:01:50Z IP 45.79.192.236 mapped to AS0 belongs to tried bucket 215
2022-07-12T19:01:50Z IP 35.173.47.113 mapped to AS0 belongs to tried bucket 34
2022-07-12T19:01:50Z IP 95.216.245.175 mapped to AS0 belongs to tried bucket 29
2022-07-12T19:01:50Z IP 2.138.162.3 mapped to AS0 belongs to tried bucket 194
2022-07-12T19:01:50Z IP 15.206.146.144 mapped to AS0 belongs to tried bucket 233
2022-07-12T19:01:50Z IP 112.118.188.50 mapped to AS0 belongs to tried bucket 28
2022-07-12T19:01:50Z IP 188.134.6.84 mapped to AS0 belongs to tried bucket 114
2022-07-12T19:01:50Z IP 3.0.209.114 mapped to AS0 belongs to tried bucket 247
2022-07-12T19:01:50Z IP 34.87.252.166 mapped to AS0 belongs to tried bucket 105
2022-07-12T19:01:50Z IP 176.126.167.10 mapped to AS0 belongs to tried bucket 56
2022-07-12T19:01:50Z IP 173.249.7.254 mapped to AS0 belongs to tried bucket 15
2022-07-12T19:01:50Z IP 192.99.6.223 mapped to AS0 belongs to tried bucket 250
2022-07-12T19:01:50Z IP 44.192.128.241 mapped to AS0 belongs to tried bucket 140
2022-07-12T19:01:50Z IP 13.232.38.92 mapped to AS0 belongs to tried bucket 156
2022-07-12T19:01:50Z IP 75.57.118.175 mapped to AS0 belongs to tried bucket 203
2022-07-12T19:01:50Z IP 54.37.110.90 mapped to AS0 belongs to tried bucket 121
2022-07-12T19:01:50Z IP 75.119.140.109 mapped to AS0 belongs to tried bucket 32
2022-07-12T19:01:50Z IP 100.14.66.54 mapped to AS0 belongs to tried bucket 199
2022-07-12T19:01:50Z IP 77.72.144.198 mapped to AS0 belongs to tried bucket 195
2022-07-12T19:01:50Z IP 35.215.2.174 mapped to AS0 belongs to tried bucket 182
2022-07-12T19:01:50Z IP 35.212.237.223 mapped to AS0 belongs to tried bucket 218
2022-07-12T19:01:50Z IP 176.143.107.60 mapped to AS0 belongs to tried bucket 64
2022-07-12T19:01:50Z IP 71.120.3.68 mapped to AS0 belongs to tried bucket 49
2022-07-12T19:01:50Z IP 174.4.81.41 mapped to AS0 belongs to tried bucket 216
2022-07-12T19:01:50Z IP 54.232.29.198 mapped to AS0 belongs to tried bucket 76
2022-07-12T19:01:50Z IP 95.96.3.114 mapped to AS0 belongs to tried bucket 165
2022-07-12T19:01:50Z IP 47.206.64.163 mapped to AS0 belongs to tried bucket 223
2022-07-12T19:01:50Z IP 54.65.201.164 mapped to AS0 belongs to tried bucket 182
2022-07-12T19:01:50Z IP 23.120.34.179 mapped to AS0 belongs to tried bucket 54
2022-07-12T19:01:50Z IP 206.196.145.143 mapped to AS0 belongs to tried bucket 0
2022-07-12T19:01:50Z IP 104.54.215.47 mapped to AS0 belongs to tried bucket 49
2022-07-12T19:01:50Z IP 141.95.222.162 mapped to AS0 belongs to tried bucket 90
2022-07-12T19:01:50Z IP 76.69.213.152 mapped to AS0 belongs to tried bucket 64
2022-07-12T19:01:50Z IP 143.110.240.87 mapped to AS0 belongs to tried bucket 75
2022-07-12T19:01:50Z IP 34.237.15.134 mapped to AS0 belongs to tried bucket 151
2022-07-12T19:01:50Z IP 52.59.10.197 mapped to AS0 belongs to tried bucket 65
2022-07-12T19:01:50Z IP 35.242.205.19 mapped to AS0 belongs to tried bucket 53
2022-07-12T19:01:50Z IP 84.73.8.104 mapped to AS0 belongs to tried bucket 181
2022-07-12T19:01:50Z IP 54.173.97.189 mapped to AS0 belongs to tried bucket 86
2022-07-12T19:01:50Z IP 73.94.10.105 mapped to AS0 belongs to tried bucket 31
2022-07-12T19:01:50Z IP 1.13.7.12 mapped to AS0 belongs to tried bucket 166
2022-07-12T19:01:50Z IP 78.125.82.240 mapped to AS0 belongs to tried bucket 95
2022-07-12T19:01:50Z IP 34.139.161.222 mapped to AS0 belongs to tried bucket 172
2022-07-12T19:01:50Z IP 68.129.26.244 mapped to AS0 belongs to tried bucket 219
2022-07-12T19:01:50Z IP 50.101.120.109 mapped to AS0 belongs to tried bucket 145
2022-07-12T19:01:50Z IP 74.79.123.203 mapped to AS0 belongs to tried bucket 122
2022-07-12T19:01:50Z IP 15.161.90.31 mapped to AS0 belongs to tried bucket 102
2022-07-12T19:01:50Z IP 137.25.38.108 mapped to AS0 belongs to tried bucket 47
2022-07-12T19:01:50Z IP 134.209.247.91 mapped to AS0 belongs to tried bucket 46
2022-07-12T19:01:50Z IP 144.76.1.155 mapped to AS0 belongs to tried bucket 84
2022-07-12T19:01:50Z IP 85.208.69.13 mapped to AS0 belongs to tried bucket 42
2022-07-12T19:01:50Z IP 207.158.15.91 mapped to AS0 belongs to tried bucket 39
2022-07-12T19:01:50Z IP 24.55.2.25 mapped to AS0 belongs to tried bucket 163
2022-07-12T19:01:50Z IP 168.119.68.66 mapped to AS0 belongs to tried bucket 86
2022-07-12T19:01:50Z IP 107.191.116.103 mapped to AS0 belongs to tried bucket 170
2022-07-12T19:01:50Z IP 192.99.8.31 mapped to AS0 belongs to tried bucket 250
2022-07-12T19:01:50Z IP 51.15.165.173 mapped to AS0 belongs to tried bucket 23
2022-07-12T19:01:50Z IP 103.163.225.51 mapped to AS0 belongs to tried bucket 107
2022-07-12T19:01:50Z IP 93.95.88.13 mapped to AS0 belongs to tried bucket 191
2022-07-12T19:01:50Z IP 75.133.52.91 mapped to AS0 belongs to tried bucket 240
2022-07-12T19:01:50Z IP 84.172.89.202 mapped to AS0 belongs to tried bucket 193
2022-07-12T19:01:50Z IP 72.89.98.24 mapped to AS0 belongs to tried bucket 235
2022-07-12T19:01:50Z IP 54.180.137.207 mapped to AS0 belongs to tried bucket 144
2022-07-12T19:01:50Z IP 143.110.178.161 mapped to AS0 belongs to tried bucket 167
2022-07-12T19:01:50Z IP 34.87.70.59 mapped to AS0 belongs to tried bucket 25
2022-07-12T19:01:50Z IP 193.169.244.188 mapped to AS0 belongs to tried bucket 95
2022-07-12T19:01:50Z IP 98.128.243.142 mapped to AS0 belongs to tried bucket 21
2022-07-12T19:01:50Z IP 95.105.186.195 mapped to AS0 belongs to tried bucket 167
2022-07-12T19:01:50Z IP 89.27.79.172 mapped to AS0 belongs to tried bucket 215
2022-07-12T19:01:50Z IP 199.48.92.184 mapped to AS0 belongs to tried bucket 191
2022-07-12T19:01:50Z IP 85.173.165.66 mapped to AS0 belongs to tried bucket 124
2022-07-12T19:01:50Z IP 146.70.49.38 mapped to AS0 belongs to tried bucket 46
2022-07-12T19:01:50Z IP 184.144.87.224 mapped to AS0 belongs to tried bucket 42
2022-07-12T19:01:50Z IP 165.22.237.13 mapped to AS0 belongs to tried bucket 93

Then, jumping ahead to where it is almost done updating headers:

Code:
2022-07-12T19:05:38Z more getheaders (236000) to end to peer=3 (startheight:744739)
2022-07-12T19:05:38Z sending getheaders (965 bytes) peer=3
2022-07-12T19:05:38Z received: headers (162003 bytes) peer=5
2022-07-12T19:05:38Z more getheaders (334000) to end to peer=5 (startheight:744739)
2022-07-12T19:05:38Z sending getheaders (997 bytes) peer=5
2022-07-12T19:05:38Z received: headers (162003 bytes) peer=0
2022-07-12T19:05:38Z more getheaders (246000) to end to peer=0 (startheight:744739)
2022-07-12T19:05:38Z sending getheaders (965 bytes) peer=0
2022-07-12T19:05:38Z received: headers (162003 bytes) peer=4
2022-07-12T19:05:38Z Synchronizing blockheaders, height: 688000 (~92.46%)
2022-07-12T19:05:38Z more getheaders (688000) to end to peer=4 (startheight:744739)
2022-07-12T19:05:38Z sending getheaders (1029 bytes) peer=4
2022-07-12T19:05:38Z received: headers (162003 bytes) peer=4
2022-07-12T19:05:38Z Synchronizing blockheaders, height: 690000 (~92.82%)
2022-07-12T19:05:38Z more getheaders (690000) to end to peer=4 (startheight:744739)
2022-07-12T19:05:38Z sending getheaders (1029 bytes) peer=4
2022-07-12T19:05:38Z received: headers (162003 bytes) peer=12
2022-07-12T19:05:38Z more getheaders (292000) to end to peer=12 (startheight:744739)
2022-07-12T19:05:38Z sending getheaders (997 bytes) peer=12
2022-07-12T19:05:39Z received: headers (162003 bytes) peer=11
2022-07-12T19:05:39Z more getheaders (326000) to end to peer=11 (startheight:744739)
2022-07-12T19:05:39Z sending getheaders (997 bytes) peer=11
2022-07-12T19:05:39Z sending addrv2 (16 bytes) peer=4
2022-07-12T19:05:39Z received: headers (162003 bytes) peer=7
2022-07-12T19:05:39Z more getheaders (322000) to end to peer=7 (startheight:744739)
2022-07-12T19:05:39Z sending getheaders (997 bytes) peer=7
2022-07-12T19:05:39Z received: headers (162003 bytes) peer=10
2022-07-12T19:05:39Z more getheaders (238000) to end to peer=10 (startheight:744739)
2022-07-12T19:05:39Z sending getheaders (965 bytes) peer=10
2022-07-12T19:05:39Z received: headers (162003 bytes) peer=4
2022-07-12T19:05:39Z Synchronizing blockheaders, height: 692000 (~93.10%)
2022-07-12T19:05:39Z more getheaders (692000) to end to peer=4 (startheight:744739)
2022-07-12T19:05:39Z sending getheaders (1029 bytes) peer=4
2022-07-12T19:05:39Z Requesting block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 (1) peer=4
2022-07-12T19:05:39Z Requesting block 000000006a625f06636b8bb6ac7b960a8d03705d1ace08b1a19da3fdcc99ddbd (2) peer=4
2022-07-12T19:05:39Z Requesting block 0000000082b5015589a3fdf2d4baff403e6f0be035a5d9742c1cae6295464449 (3) peer=4
2022-07-12T19:05:39Z Requesting block 000000004ebadb55ee9096c9a2f8880e09da59c0d68b1c228da88e48844a1485 (4) peer=4
2022-07-12T19:05:39Z Requesting block 000000009b7262315dbf071787ad3656097b892abffd1f95a1a022f896f533fc (5) peer=4
2022-07-12T19:05:39Z Requesting block 000000003031a0e73735690c5a1ff2a4be82553b2a12b776fbd3a215dc8f778d (6) peer=4
2022-07-12T19:05:39Z Requesting block 0000000071966c2b1d065fd446b1e485b2c9d9594acd2007ccbd5441cfc89444 (7) peer=4
2022-07-12T19:05:39Z Requesting block 00000000408c48f847aa786c2268fc3e6ec2af68e8468a34a28c61b7f1de0dc6 (8) peer=4
2022-07-12T19:05:39Z Requesting block 000000008d9dc510f23c2657fc4f67bea30078cc05a90eb89e84cc475c080805 (9) peer=4
2022-07-12T19:05:39Z Requesting block 000000002c05cc2e78923c34df87fd108b22221ac6076c18f3ade378a4d915e9 (10) peer=4
2022-07-12T19:05:39Z Requesting block 0000000097be56d606cdd9c54b04d4747e957d3608abe69198c661f2add73073 (11) peer=4
2022-07-12T19:05:39Z Requesting block 0000000027c2488e2510d1acf4369787784fa20ee084c258b58d9fbd43802b5e (12) peer=4
2022-07-12T19:05:39Z Requesting block 000000005c51de2031a895adc145ee2242e919a01c6d61fb222a54a54b4d3089 (13) peer=4
2022-07-12T19:05:39Z Requesting block 0000000080f17a0c5a67f663a9bc9969eb37e81666d9321125f0e293656f8a37 (14) peer=4
2022-07-12T19:05:39Z Requesting block 00000000b3322c8c3ef7d2cf6da009a776e6a99ee65ec5a32f3f345712238473 (15) peer=4
2022-07-12T19:05:39Z Requesting block 00000000174a25bb399b009cc8deff1c4b3ea84df7e93affaaf60dc3416cc4f5 (16) peer=4
2022-07-12T19:05:39Z sending getdata (577 bytes) peer=4
2022-07-12T19:05:40Z received: headers (162003 bytes) peer=5
2022-07-12T19:05:40Z more getheaders (336000) to end to peer=5 (startheight:744739)
2022-07-12T19:05:40Z sending getheaders (997 bytes) peer=5
2022-07-12T19:05:41Z received: headers (162003 bytes) peer=4
2022-07-12T19:05:41Z Synchronizing blockheaders, height: 694000 (~93.35%)
2022-07-12T19:05:41Z more getheaders (694000) to end to peer=4 (startheight:744739)
2022-07-12T19:05:41Z sending getheaders (1029 bytes) peer=4
2022-07-12T19:05:41Z received: block (215 bytes) peer=4
2022-07-12T19:05:41Z received block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 peer=4
2022-07-12T19:05:41Z   - Load block from disk: 0.00ms [0.00s]
2022-07-12T19:05:41Z     - Sanity checks: 0.03ms [0.00s (0.02ms/blk)]
2022-07-12T19:05:41Z     - Fork checks: 0.10ms [0.00s (0.05ms/blk)]
2022-07-12T19:05:41Z       - Connect 1 transactions: 0.04ms (0.038ms/tx, 0.000ms/txin) [0.00s (0.02ms/blk)]
2022-07-12T19:05:41Z     - Verify 0 txins: 0.07ms (0.000ms/txin) [0.00s (0.04ms/blk)]
2022-07-12T19:05:41Z Pre-allocating up to position 0x100000 in rev00000.dat
2022-07-12T19:05:41Z     - Index writing: 0.32ms [0.00s (0.16ms/blk)]
2022-07-12T19:05:41Z     - Callbacks: 0.04ms [0.00s (0.02ms/blk)]
2022-07-12T19:05:41Z BlockChecked: block hash=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 state=Valid
2022-07-12T19:05:41Z   - Connect total: 0.70ms [0.00s (0.39ms/blk)]
2022-07-12T19:05:41Z   - Flush: 0.08ms [0.00s (0.05ms/blk)]
2022-07-12T19:05:41Z FlushStateToDisk: find files to prune started
2022-07-12T19:05:41Z FlushStateToDisk: find files to prune completed (0.00ms)
2022-07-12T19:05:41Z   - Writing chainstate: 0.09ms [0.00s (0.08ms/blk)]
2022-07-12T19:05:41Z Blockpolicy estimates updated by 0 of 0 block txs, since last block 0 of 0 tracked, mempool map size 0, max target 0 from current
2022-07-12T19:05:41Z UpdateTip: new best=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 height=1 version=0x00000001 log2_work=33.000022 tx=2 date='2009-01-09T02:54:25Z' progress=0.000000 cache=0.0MiB(1txo)
2022-07-12T19:05:41Z   - Connect postprocess: 0.33ms [0.00s (0.20ms/blk)]
2022-07-12T19:05:41Z - Connect block: 1.20ms [0.00s (0.76ms/blk)]
2022-07-12T19:05:41Z Enqueuing BlockConnected: block hash=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 block height=1
2022-07-12T19:05:41Z Enqueuing UpdatedBlockTip: new block hash=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 fork block hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f (in IBD=true)
2022-07-12T19:05:41Z Requesting block 000000003ff1d0d70147acfbef5d6a87460ff5bcfce807c2d5b6f0a66bfdf809 (17) peer=4
2022-07-12T19:05:41Z sending getdata (37 bytes) peer=4
2022-07-12T19:05:41Z BlockConnected: block hash=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 block height=1
2022-07-12T19:05:41Z UpdatedBlockTip: new block hash=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 fork block hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f (in IBD=true)
2022-07-12T19:05:41Z received: block (215 bytes) peer=4
2022-07-12T19:05:41Z received block 000000006a625f06636b8bb6ac7b960a8d03705d1ace08b1a19da3fdcc99ddbd peer=4
2022-07-12T19:05:41Z   - Load block from disk: 0.00ms [0.00s]
2022-07-12T19:05:41Z     - Sanity checks: 0.03ms [0.00s (0.02ms/blk)]
2022-07-12T19:05:41Z     - Fork checks: 0.04ms [0.00s (0.05ms/blk)]
2022-07-12T19:05:41Z       - Connect 1 transactions: 0.03ms (0.032ms/tx, 0.000ms/txin) [0.00s (0.02ms/blk)]
2022-07-12T19:05:41Z     - Verify 0 txins: 0.06ms (0.000ms/txin) [0.00s (0.04ms/blk)]
2022-07-12T19:05:41Z     - Index writing: 0.09ms [0.00s (0.14ms/blk)]
2022-07-12T19:05:41Z     - Callbacks: 0.03ms [0.00s (0.02ms/blk)]
2022-07-12T19:05:41Z BlockChecked: block hash=000000006a625f06636b8bb6ac7b960a8d03705d1ace08b1a19da3fdcc99ddbd state=Valid
2022-07-12T19:05:41Z   - Connect total: 0.38ms [0.00s (0.39ms/blk)]
2022-07-12T19:05:41Z   - Flush: 0.03ms [0.00s (0.05ms/blk)]
2022-07-12T19:05:41Z   - Writing chainstate: 0.03ms [0.00s (0.06ms/blk)]
2022-07-12T19:05:41Z Blockpolicy estimates updated by 0 of 0 block txs, since last block 0 of 0 tracked, mempool map size 0, max target 0 from current
2022-07-12T19:05:41Z UpdateTip: new best=000000006a625f06636b8bb6ac7b960a8d03705d1ace08b1a19da3fdcc99ddbd height=2 version=0x00000001 log2_work=33.584985 tx=3 date='2009-01-09T02:55:44Z' progress=0.000000 cache=0.0MiB(2txo)
2022-07-12T19:05:41Z   - Connect postprocess: 0.24ms [0.00s (0.21ms/blk)]
2022-07-12T19:05:41Z - Connect block: 0.67ms [0.00s (0.73ms/blk)]
2022-07-12T19:05:41Z Enqueuing BlockConnected: block hash=000000006a625f06636b8bb6ac7b960a8d03705d1ace08b1a19da3fdcc99ddbd block height=2
2022-07-12T19:05:41Z Enqueuing UpdatedBlockTip: new block hash=000000006a625f06636b8bb6ac7b960a8d03705d1ace08b1a19da3fdcc99ddbd fork block hash=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 (in IBD=true)
2022-07-12T19:05:41Z Requesting block 000000008693e98cf893e4c85a446b410bb4dfa129bd1be582c09ed3f0261116 (18) peer=4
2022-07-12T19:05:41Z sending getdata (37 bytes) peer=4
2022-07-12T19:05:41Z BlockConnected: block hash=000000006a625f06636b8bb6ac7b960a8d03705d1ace08b1a19da3fdcc99ddbd block height=2
2022-07-12T19:05:41Z received: block (215 bytes) peer=4
2022-07-12T19:05:41Z received block 0000000082b5015589a3fdf2d4baff403e6f0be035a5d9742c1cae6295464449 peer=4
2022-07-12T19:05:41Z UpdatedBlockTip: new block hash=000000006a625f06636b8bb6ac7b960a8d03705d1ace08b1a19da3fdcc99ddbd fork block hash=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 (in IBD=true)
2022-07-12T19:05:41Z   - Load block from disk: 0.00ms [0.00s]
2022-07-12T19:05:41Z     - Sanity checks: 0.04ms [0.00s (0.02ms/blk)]
2022-07-12T19:05:41Z     - Fork checks: 0.06ms [0.00s (0.05ms/blk)]
2022-07-12T19:05:41Z       - Connect 1 transactions: 0.03ms (0.032ms/tx, 0.000ms/txin) [0.00s (0.03ms/blk)]
2022-07-12T19:05:41Z     - Verify 0 txins: 0.06ms (0.000ms/txin) [0.00s (0.05ms/blk)]
2022-07-12T19:05:41Z     - Index writing: 0.09ms [0.00s (0.12ms/blk)]
2022-07-12T19:05:41Z     - Callbacks: 0.03ms [0.00s (0.02ms/blk)]
2022-07-12T19:05:41Z BlockChecked: block hash=0000000082b5015589a3fdf2d4baff403e6f0be035a5d9742c1cae6295464449 state=Valid
2022-07-12T19:05:41Z   - Connect total: 0.38ms [0.00s (0.38ms/blk)]
2022-07-12T19:05:41Z   - Flush: 0.03ms [0.00s (0.04ms/blk)]
2022-07-12T19:05:41Z   - Writing chainstate: 0.03ms [0.00s (0.05ms/blk)]
2022-07-12T19:05:41Z Blockpolicy estimates updated by 0 of 0 block txs, since last block 0 of 0 tracked, mempool map size 0, max target 0 from current
2022-07-12T19:05:41Z UpdateTip: new best=0000000082b5015589a3fdf2d4baff403e6f0be035a5d9742c1cae6295464449 height=3 version=0x00000001 log2_work=34.000022 tx=4 date='2009-01-09T03:02:53Z' progress=0.000000 cache=0.0MiB(3txo)
2022-07-12T19:05:41Z   - Connect postprocess: 0.24ms [0.00s (0.22ms/blk)]
2022-07-12T19:05:41Z - Connect block: 0.67ms [0.00s (0.72ms/blk)]
2022-07-12T19:05:41Z Enqueuing BlockConnected: block hash=0000000082b5015589a3fdf2d4baff403e6f0be035a5d9742c1cae6295464449 block height=3
2022-07-12T19:05:41Z Enqueuing UpdatedBlockTip: new block hash=0000000082b5015589a3fdf2d4baff403e6f0be035a5d9742c1cae6295464449 fork block hash=000000006a625f06636b8bb6ac7b960a8d03705d1ace08b1a19da3fdcc99ddbd (in IBD=true)
2022-07-12T19:05:41Z Requesting block 00000000841cb802ca97cf20fb9470480cae9e5daa5d06b4a18ae2d5dd7f186f (19) peer=4
2022-07-12T19:05:41Z sending getdata (37 bytes) peer=4
2022-07-12T19:05:41Z BlockConnected: block hash=0000000082b5015589a3fdf2d4baff403e6f0be035a5d9742c1cae6295464449 block height=3
2022-07-12T19:05:41Z received: block (215 bytes) peer=4
2022-07-12T19:05:41Z received block 000000004ebadb55ee9096c9a2f8880e09da59c0d68b1c228da88e48844a1485 peer=4
2022-07-12T19:05:41Z UpdatedBlockTip: new block hash=0000000082b5015589a3fdf2d4baff403e6f0be035a5d9742c1cae6295464449 fork block hash=000000006a625f06636b8bb6ac7b960a8d03705d1ace08b1a19da3fdcc99ddbd (in IBD=true)
2022-07-12T19:05:41Z   - Load block from disk: 0.00ms [0.00s]
2022-07-12T19:05:41Z     - Sanity checks: 0.03ms [0.00s (0.02ms/blk)]
2022-07-12T19:05:41Z     - Fork checks: 0.04ms [0.00s (0.05ms/blk)]
2022-07-12T19:05:41Z       - Connect 1 transactions: 0.03ms (0.031ms/tx, 0.000ms/txin) [0.00s (0.03ms/blk)]
2022-07-12T19:05:41Z     - Verify 0 txins: 0.06ms (0.000ms/txin) [0.00s (0.05ms/blk)]
2022-07-12T19:05:41Z     - Index writing: 0.08ms [0.00s (0.12ms/blk)]
2022-07-12T19:05:41Z     - Callbacks: 0.03ms [0.00s (0.03ms/blk)]
2022-07-12T19:05:41Z BlockChecked: block hash=000000004ebadb55ee9096c9a2f8880e09da59c0d68b1c228da88e48844a1485 state=Valid
2022-07-12T19:05:41Z   - Connect total: 0.34ms [0.00s (0.37ms/blk)]
2022-07-12T19:05:41Z   - Flush: 0.03ms [0.00s (0.04ms/blk)]
2022-07-12T19:05:41Z   - Writing chainstate: 0.03ms [0.00s (0.05ms/blk)]
2022-07-12T19:05:41Z Blockpolicy estimates updated by 0 of 0 block txs, since last block 0 of 0 tracked, mempool map size 0, max target 0 from current
2022-07-12T19:05:41Z UpdateTip: new best=000000004ebadb55ee9096c9a2f8880e09da59c0d68b1c228da88e48844a1485 height=4 version=0x00000001 log2_work=34.321950 tx=5 date='2009-01-09T03:16:28Z' progress=0.000000 cache=0.0MiB(4txo)
2022-07-12T19:05:41Z   - Connect postprocess: 0.26ms [0.00s (0.22ms/blk)]
2022-07-12T19:05:41Z - Connect block: 0.65ms [0.00s (0.70ms/blk)]
2022-07-12T19:05:41Z Enqueuing BlockConnected: block hash=000000004ebadb55ee9096c9a2f8880e09da59c0d68b1c228da88e48844a1485 block height=4
2022-07-12T19:05:41Z Enqueuing UpdatedBlockTip: new block hash=000000004ebadb55ee9096c9a2f8880e09da59c0d68b1c228da88e48844a1485 fork block hash=0000000082b5015589a3fdf2d4baff403e6f0be035a5d9742c1cae6295464449 (in IBD=true)
2022-07-12T19:05:41Z Requesting block 0000000067a97a2a37b8f190a17f0221e9c3f4fa824ddffdc2e205eae834c8d7 (20) peer=4
2022-07-12T19:05:41Z sending getdata (37 bytes) peer=4
2022-07-12T19:05:41Z BlockConnected: block hash=000000004ebadb55ee9096c9a2f8880e09da59c0d68b1c228da88e48844a1485 block height=4
2022-07-12T19:05:41Z received: block (215 bytes) peer=4
2022-07-12T19:05:41Z UpdatedBlockTip: new block hash=000000004ebadb55ee9096c9a2f8880e09da59c0d68b1c228da88e48844a1485 fork block hash=0000000082b5015589a3fdf2d4baff403e6f0be035a5d9742c1cae6295464449 (in IBD=true)
2022-07-12T19:05:41Z received block 000000009b7262315dbf071787ad3656097b892abffd1f95a1a022f896f533fc peer=4
2022-07-12T19:05:41Z   - Load block from disk: 0.00ms [0.00s]
2022-07-12T19:05:41Z     - Sanity checks: 0.03ms [0.00s (0.02ms/blk)]
2022-07-12T19:05:41Z     - Fork checks: 0.04ms [0.00s (0.04ms/blk)]
2022-07-12T19:05:41Z       - Connect 1 transactions: 0.03ms (0.030ms/tx, 0.000ms/txin) [0.00s (0.03ms/blk)]
2022-07-12T19:05:41Z     - Verify 0 txins: 0.06ms (0.000ms/txin) [0.00s (0.05ms/blk)]
2022-07-12T19:05:41Z     - Index writing: 0.08ms [0.00s (0.11ms/blk)]
2022-07-12T19:05:41Z     - Callbacks: 0.03ms [0.00s (0.03ms/blk)]
2022-07-12T19:05:41Z BlockChecked: block hash=000000009b7262315dbf071787ad3656097b892abffd1f95a1a022f896f533fc state=Valid
2022-07-12T19:05:41Z   - Connect total: 0.34ms [0.00s (0.37ms/blk)]
2022-07-12T19:05:41Z   - Flush: 0.03ms [0.00s (0.04ms/blk)]
2022-07-12T19:05:41Z   - Writing chainstate: 0.03ms [0.00s (0.05ms/blk)]
2022-07-12T19:05:41Z Blockpolicy estimates updated by 0 of 0 block txs, since last block 0 of 0 tracked, mempool map size 0, max target 0 from current
2022-07-12T19:05:41Z UpdateTip: new best=000000009b7262315dbf071787ad3656097b892abffd1f95a1a022f896f533fc height=5 version=0x00000001 log2_work=34.584985 tx=6 date='2009-01-09T03:23:48Z' progress=0.000000 cache=0.0MiB(5txo)
2022-07-12T19:05:41Z   - Connect postprocess: 0.23ms [0.00s (0.23ms/blk)]
2022-07-12T19:05:41Z - Connect block: 0.62ms [0.00s (0.69ms/blk)]
2022-07-12T19:05:41Z Enqueuing BlockConnected: block hash=000000009b7262315dbf071787ad3656097b892abffd1f95a1a022f896f533fc block height=5
2022-07-12T19:05:41Z Enqueuing UpdatedBlockTip: new block hash=000000009b7262315dbf071787ad3656097b892abffd1f95a1a022f896f533fc fork block hash=000000004ebadb55ee9096c9a2f8880e09da59c0d68b1c228da88e48844a1485 (in IBD=true)
2022-07-12T19:05:41Z Requesting block 000000006f016342d1275be946166cff975c8b27542de70a7113ac6d1ef3294f (21) peer=4
2022-07-12T19:05:41Z sending getdata (37 bytes) peer=4
2022-07-12T19:05:41Z BlockConnected: block hash=000000009b7262315dbf071787ad3656097b892abffd1f95a1a022f896f533fc block height=5
2022-07-12T19:05:41Z UpdatedBlockTip: new block hash=000000009b7262315dbf071787ad3656097b892abffd1f95a1a022f896f533fc fork block hash=000000004ebadb55ee9096c9a2f8880e09da59c0d68b1c228da88e48844a1485 (in IBD=true)
2022-07-12T19:05:41Z received: block (215 bytes) peer=4
2022-07-12T19:05:41Z received block 000000003031a0e73735690c5a1ff2a4be82553b2a12b776fbd3a215dc8f778d peer=4
2022-07-12T19:05:41Z   - Load block from disk: 0.00ms [0.00s]
2022-07-12T19:05:41Z     - Sanity checks: 0.03ms [0.00s (0.03ms/blk)]
2022-07-12T19:05:41Z     - Fork checks: 0.04ms [0.00s (0.04ms/blk)]
2022-07-12T19:05:41Z       - Connect 1 transactions: 0.03ms (0.031ms/tx, 0.000ms/txin) [0.00s (0.03ms/blk)]
2022-07-12T19:05:41Z     - Verify 0 txins: 0.07ms (0.000ms/txin) [0.00s (0.05ms/blk)]
2022-07-12T19:05:41Z     - Index writing: 0.13ms [0.00s (0.11ms/blk)]
2022-07-12T19:05:41Z     - Callbacks: 0.03ms [0.00s (0.03ms/blk)]
2022-07-12T19:05:41Z BlockChecked: block hash=000000003031a0e73735690c5a1ff2a4be82553b2a12b776fbd3a215dc8f778d state=Valid
2022-07-12T19:05:41Z   - Connect total: 0.41ms [0.00s (0.37ms/blk)]
2022-07-12T19:05:41Z   - Flush: 0.03ms [0.00s (0.03ms/blk)]
2022-07-12T19:05:41Z   - Writing chainstate: 0.03ms [0.00s (0.04ms/blk)]
2022-07-12T19:05:41Z Blockpolicy estimates updated by 0 of 0 block txs, since last block 0 of 0 tracked, mempool map size 0, max target 0 from current
2022-07-12T19:05:41Z UpdateTip: new best=000000003031a0e73735690c5a1ff2a4be82553b2a12b776fbd3a215dc8f778d height=6 version=0x00000001 log2_work=34.807377 tx=7 date='2009-01-09T03:29:49Z' progress=0.000000 cache=0.0MiB(6txo)
2022-07-12T19:05:41Z   - Connect postprocess: 0.24ms [0.00s (0.23ms/blk)]
2022-07-12T19:05:41Z - Connect block: 0.71ms [0.00s (0.69ms/blk)]
2022-07-12T19:05:41Z Enqueuing BlockConnected: block hash=000000003031a0e73735690c5a1ff2a4be82553b2a12b776fbd3a215dc8f778d block height=6
2022-07-12T19:05:41Z Enqueuing UpdatedBlockTip: new block hash=000000003031a0e73735690c5a1ff2a4be82553b2a12b776fbd3a215dc8f778d fork block hash=000000009b7262315dbf071787ad3656097b892abffd1f95a1a022f896f533fc (in IBD=true)
2022-07-12T19:05:41Z Requesting block 0000000098b58d427a10c860335a21c1a9a7639e96c3d6f1a03d8c8c885b5e3b (22) peer=4
2022-07-12T19:05:41Z sending getdata (37 bytes) peer=4
2022-07-12T19:05:41Z BlockConnected: block hash=000000003031a0e73735690c5a1ff2a4be82553b2a12b776fbd3a215dc8f778d block height=6
2022-07-12T19:05:41Z received: block (215 bytes) peer=4
2022-07-12T19:05:41Z UpdatedBlockTip: new block hash=000000003031a0e73735690c5a1ff2a4be82553b2a12b776fbd3a215dc8f778d fork block hash=000000009b7262315dbf071787ad3656097b892abffd1f95a1a022f896f533fc (in IBD=true)
2022-07-12T19:05:41Z received block 0000000071966c2b1d065fd446b1e485b2c9d9594acd2007ccbd5441cfc89444 peer=4
2022-07-12T19:05:41Z   - Load block from disk: 0.00ms [0.00s]
2022-07-12T19:05:41Z     - Sanity checks: 0.03ms [0.00s (0.03ms/blk)]
2022-07-12T19:05:41Z     - Fork checks: 0.04ms [0.00s (0.04ms/blk)]
2022-07-12T19:05:41Z       - Connect 1 transactions: 0.03ms (0.032ms/tx, 0.000ms/txin) [0.00s (0.03ms/blk)]
2022-07-12T19:05:41Z     - Verify 0 txins: 0.06ms (0.000ms/txin) [0.00s (0.06ms/blk)]
2022-07-12T19:05:41Z     - Index writing: 0.08ms [0.00s (0.11ms/blk)]
2022-07-12T19:05:41Z     - Callbacks: 0.03ms [0.00s (0.03ms/blk)]
2022-07-12T19:05:41Z BlockChecked: block hash=0000000071966c2b1d065fd446b1e485b2c9d9594acd2007ccbd5441cfc89444 state=Valid
2022-07-12T19:05:41Z   - Connect total: 0.36ms [0.00s (0.37ms/blk)]
2022-07-12T19:05:41Z   - Flush: 0.03ms [0.00s (0.03ms/blk)]
2022-07-12T19:05:41Z   - Writing chainstate: 0.03ms [0.00s (0.04ms/blk)]
2022-07-12T19:05:41Z Blockpolicy estimates updated by 0 of 0 block txs, since last block 0 of 0 tracked, mempool map size 0, max target 0 from current
2022-07-12T19:05:41Z UpdateTip: new best=0000000071966c2b1d065fd446b1e485b2c9d9594acd2007ccbd5441cfc89444 height=7 version=0x00000001 log2_work=35.000022 tx=8 date='2009-01-09T03:39:29Z' progress=0.000000 cache=0.0MiB(7txo)
2022-07-12T19:05:41Z   - Connect postprocess: 0.29ms [0.00s (0.24ms/blk)]
2022-07-12T19:05:41Z - Connect block: 0.70ms [0.01s (0.69ms/blk)]
2022-07-12T19:05:41Z Enqueuing BlockConnected: block hash=0000000071966c2b1d065fd446b1e485b2c9d9594acd2007ccbd5441cfc89444 block height=7
2022-07-12T19:05:41Z Enqueuing UpdatedBlockTip: new block hash=0000000071966c2b1d065fd446b1e485b2c9d9594acd2007ccbd5441cfc89444 fork block hash=000000003031a0e73735690c5a1ff2a4be82553b2a12b776fbd3a215dc8f778d (in IBD=true)
2022-07-12T19:05:41Z Requesting block 000000000cd339982e556dfffa9de94744a4135c53eeef15b7bcc9bdeb9c2182 (23) peer=4
2022-07-12T19:05:41Z sending getdata (37 bytes) peer=4
2022-07-12T19:05:41Z BlockConnected: block hash=0000000071966c2b1d065fd446b1e485b2c9d9594acd2007ccbd5441cfc89444 block height=7
2022-07-12T19:05:41Z received: block (215 bytes) peer=4
2022-07-12T19:05:41Z UpdatedBlockTip: new block hash=0000000071966c2b1d065fd446b1e485b2c9d9594acd2007ccbd5441cfc89444 fork block hash=000000003031a0e73735690c5a1ff2a4be82553b2a12b776fbd3a215dc8f778d (in IBD=true)
2022-07-12T19:05:41Z received block 00000000408c48f847aa786c2268fc3e6ec2af68e8468a34a28c61b7f1de0dc6 peer=4
2022-07-12T19:05:41Z   - Load block from disk: 0.00ms [0.00s]
2022-07-12T19:05:41Z     - Sanity checks: 0.03ms [0.00s (0.03ms/blk)]
2022-07-12T19:05:41Z     - Fork checks: 0.04ms [0.00s (0.04ms/blk)]
2022-07-12T19:05:41Z       - Connect 1 transactions: 0.03ms (0.031ms/tx, 0.000ms/txin) [0.00s (0.03ms/blk)]
2022-07-12T19:05:41Z     - Verify 0 txins: 0.06ms (0.000ms/txin) [0.00s (0.06ms/blk)]
2022-07-12T19:05:41Z     - Index writing: 0.09ms [0.00s (0.11ms/blk)]
2022-07-12T19:05:41Z     - Callbacks: 0.03ms [0.00s (0.03ms/blk)]
2022-07-12T19:05:41Z BlockChecked: block hash=00000000408c48f847aa786c2268fc3e6ec2af68e8468a34a28c61b7f1de0dc6 state=Valid
2022-07-12T19:05:41Z   - Connect total: 0.34ms [0.00s (0.37ms/blk)]
2022-07-12T19:05:41Z   - Flush: 0.03ms [0.00s (0.03ms/blk)]
2022-07-12T19:05:41Z   - Writing chainstate: 0.03ms [0.00s (0.04ms/blk)]
2022-07-12T19:05:41Z Blockpolicy estimates updated by 0 of 0 block txs, since last block 0 of 0 tracked, mempool map size 0, max target 0 from current
2022-07-12T19:05:41Z UpdateTip: new best=00000000408c48f847aa786c2268fc3e6ec2af68e8468a34a28c61b7f1de0dc6 height=8 version=0x00000001 log2_work=35.169947 tx=9 date='2009-01-09T03:45:43Z' progress=0.000000 cache=0.0MiB(8txo)
2022-07-12T19:05:41Z   - Connect postprocess: 0.23ms [0.00s (0.24ms/blk)]
2022-07-12T19:05:41Z - Connect block: 0.63ms [0.01s (0.69ms/blk)]
2022-07-12T19:05:41Z Enqueuing BlockConnected: block hash=00000000408c48f847aa786c2268fc3e6ec2af68e8468a34a28c61b7f1de0dc6 block height=8
2022-07-12T19:05:41Z Enqueuing UpdatedBlockTip: new block hash=00000000408c48f847aa786c2268fc3e6ec2af68e8468a34a28c61b7f1de0dc6 fork block hash=0000000071966c2b1d065fd446b1e485b2c9d9594acd2007ccbd5441cfc89444 (in IBD=true)
2022-07-12T19:05:41Z Requesting block 00000000fc051fbbce89a487e811a5d4319d209785ea4f4b27fc83770d1e415f (24) peer=4
2022-07-12T19:05:41Z sending getdata (37 bytes) peer=4
2022-07-12T19:05:41Z BlockConnected: block hash=00000000408c48f847aa786c2268fc3e6ec2af68e8468a34a28c61b7f1de0dc6 block height=8
2022-07-12T19:05:41Z received: block (215 bytes) peer=4
2022-07-12T19:05:41Z received block 000000008d9dc510f23c2657fc4f67bea30078cc05a90eb89e84cc475c080805 peer=4
2022-07-12T19:05:41Z UpdatedBlockTip: new block hash=00000000408c48f847aa786c2268fc3e6ec2af68e8468a34a28c61b7f1de0dc6 fork block hash=0000000071966c2b1d065fd446b1e485b2c9d9594acd2007ccbd5441cfc89444 (in IBD=true)
2022-07-12T19:05:41Z   - Load block from disk: 0.00ms [0.00s]
2022-07-12T19:05:41Z     - Sanity checks: 0.03ms [0.00s (0.03ms/blk)]
2022-07-12T19:05:41Z     - Fork checks: 0.04ms [0.00s (0.04ms/blk)]
2022-07-12T19:05:41Z       - Connect 1 transactions: 0.05ms (0.050ms/tx, 0.000ms/txin) [0.00s (0.03ms/blk)]
2022-07-12T19:05:41Z     - Verify 0 txins: 0.08ms (0.000ms/txin) [0.00s (0.06ms/blk)]
2022-07-12T19:05:41Z     - Index writing: 0.08ms [0.00s (0.10ms/blk)]
2022-07-12T19:05:41Z     - Callbacks: 0.03ms [0.00s (0.03ms/blk)]
2022-07-12T19:05:41Z BlockChecked: block hash=000000008d9dc510f23c2657fc4f67bea30078cc05a90eb89e84cc475c080805 state=Valid
2022-07-12T19:05:41Z   - Connect total: 0.36ms [0.00s (0.37ms/blk)]
2022-07-12T19:05:41Z   - Flush: 0.03ms [0.00s (0.03ms/blk)]
2022-07-12T19:05:41Z   - Writing chainstate: 0.03ms [0.00s (0.04ms/blk)]
2022-07-12T19:05:41Z Blockpolicy estimates updated by 0 of 0 block txs, since last block 0 of 0 tracked, mempool map size 0, max target 0 from current
2022-07-12T19:05:41Z UpdateTip: new best=000000008d9dc510f23c2657fc4f67bea30078cc05a90eb89e84cc475c080805 height=9 version=0x00000001 log2_work=35.321950 tx=10 date='2009-01-09T03:54:39Z' progress=0.000000 cache=0.0MiB(9txo)

And then, the last moments before closing:

Code:
2022-07-13T06:20:55Z UpdateTip: new best=000000000000000001e9428ec647b3d8b30379352543c45fa01c2b99cd3951f8 height=372873 version=0x00000003 log2_work=83.298292 tx=82269190 date='2015-09-03T20:16:13Z' progress=0.112440 cache=599.2MiB(4425823txo)
2022-07-13T06:20:55Z   - Connect postprocess: 0.38ms [114.68s (0.31ms/blk)]
2022-07-13T06:20:55Z - Connect block: 1.35ms [5987.85s (16.06ms/blk)]
2022-07-13T06:20:55Z Enqueuing BlockConnected: block hash=000000000000000001e9428ec647b3d8b30379352543c45fa01c2b99cd3951f8 block height=372873
2022-07-13T06:20:55Z Enqueuing UpdatedBlockTip: new block hash=000000000000000001e9428ec647b3d8b30379352543c45fa01c2b99cd3951f8 fork block hash=0000000000000000042dac60c35089341d9a2d9541744fd466dca4c999f5dfff (in IBD=true)
2022-07-13T06:20:55Z   - Load block from disk: 11.04ms [1079.85s]
2022-07-13T06:20:55Z     - Sanity checks: 3.76ms [297.57s (0.80ms/blk)]
2022-07-13T06:20:55Z     - Fork checks: 0.08ms [63.54s (0.17ms/blk)]
2022-07-13T06:20:56Z       - Connect 618 transactions: 179.37ms (0.290ms/tx, 0.132ms/txin) [3390.92s (9.09ms/blk)]
2022-07-13T06:20:56Z     - Verify 1362 txins: 179.56ms (0.132ms/txin) [3408.98s (9.14ms/blk)]
2022-07-13T06:20:56Z     - Index writing: 4.38ms [372.71s (1.00ms/blk)]
2022-07-13T06:20:56Z     - Callbacks: 0.07ms [11.66s (0.03ms/blk)]
2022-07-13T06:20:56Z BlockChecked: block hash=0000000000000000054d9213ee43cd7a7b353b3322a15848cfefe36b88ec37fe state=Valid
2022-07-13T06:20:56Z   - Connect total: 188.19ms [4204.79s (11.28ms/blk)]
2022-07-13T06:20:56Z   - Flush: 6.07ms [433.70s (1.16ms/blk)]
2022-07-13T06:20:56Z   - Writing chainstate: 0.10ms [155.04s (0.42ms/blk)]
2022-07-13T06:20:56Z Blockpolicy estimates updated by 0 of 0 block txs, since last block 0 of 0 tracked, mempool map size 0, max target 0 from current
2022-07-13T06:20:56Z UpdateTip: new best=0000000000000000054d9213ee43cd7a7b353b3322a15848cfefe36b88ec37fe height=372874 version=0x00000003 log2_work=83.298321 tx=82269808 date='2015-09-03T20:22:09Z' progress=0.112441 cache=599.2MiB(4426021txo)
2022-07-13T06:20:56Z   - Connect postprocess: 0.96ms [114.68s (0.31ms/blk)]
2022-07-13T06:20:56Z - Connect block: 206.35ms [5988.05s (16.06ms/blk)]
2022-07-13T06:20:56Z Enqueuing BlockConnected: block hash=0000000000000000054d9213ee43cd7a7b353b3322a15848cfefe36b88ec37fe block height=372874
2022-07-13T06:20:56Z Enqueuing UpdatedBlockTip: new block hash=0000000000000000054d9213ee43cd7a7b353b3322a15848cfefe36b88ec37fe fork block hash=000000000000000001e9428ec647b3d8b30379352543c45fa01c2b99cd3951f8 (in IBD=true)
2022-07-13T06:20:56Z UpdatedBlockTip: new block hash=00000000000000000602d31aaef66ed1871b18c22f5661cebbbad6a8ad7e81c0 fork block hash=000000000000000000a652bf1a3a6e589e257f36ecbc1df92167aeef3a88fa67 (in IBD=true)
2022-07-13T06:20:56Z BlockConnected: block hash=000000000000000009545b77c35ba8a956ca4ae54f1fbab5c0efa9c530399bc6 block height=372870
2022-07-13T06:20:56Z UpdatedBlockTip: new block hash=000000000000000009545b77c35ba8a956ca4ae54f1fbab5c0efa9c530399bc6 fork block hash=00000000000000000602d31aaef66ed1871b18c22f5661cebbbad6a8ad7e81c0 (in IBD=true)
2022-07-13T06:20:56Z BlockConnected: block hash=0000000000000000026bb4e8d71b4cd5dcaae262a15080973f509384ec290893 block height=372871
2022-07-13T06:20:56Z UpdatedBlockTip: new block hash=0000000000000000026bb4e8d71b4cd5dcaae262a15080973f509384ec290893 fork block hash=000000000000000009545b77c35ba8a956ca4ae54f1fbab5c0efa9c530399bc6 (in IBD=true)
2022-07-13T06:20:56Z BlockConnected: block hash=0000000000000000042dac60c35089341d9a2d9541744fd466dca4c999f5dfff block height=372872
2022-07-13T06:20:56Z UpdatedBlockTip: new block hash=0000000000000000042dac60c35089341d9a2d9541744fd466dca4c999f5dfff fork block hash=0000000000000000026bb4e8d71b4cd5dcaae262a15080973f509384ec290893 (in IBD=true)
2022-07-13T06:20:56Z BlockConnected: block hash=000000000000000001e9428ec647b3d8b30379352543c45fa01c2b99cd3951f8 block height=372873
2022-07-13T06:20:56Z UpdatedBlockTip: new block hash=000000000000000001e9428ec647b3d8b30379352543c45fa01c2b99cd3951f8 fork block hash=0000000000000000042dac60c35089341d9a2d9541744fd466dca4c999f5dfff (in IBD=true)
2022-07-13T06:20:56Z BlockConnected: block hash=0000000000000000054d9213ee43cd7a7b353b3322a15848cfefe36b88ec37fe block height=372874
2022-07-13T06:20:56Z UpdatedBlockTip: new block hash=0000000000000000054d9213ee43cd7a7b353b3322a15848cfefe36b88ec37fe fork block hash=000000000000000001e9428ec647b3d8b30379352543c45fa01c2b99cd3951f8 (in IBD=true)
2022-07-13T06:20:56Z   - Load block from disk: 11.98ms [1079.86s]
2022-07-13T06:20:56Z     - Sanity checks: 2.00ms [297.57s (0.80ms/blk)]
2022-07-13T06:20:56Z     - Fork checks: 0.09ms [63.54s (0.17ms/blk)]
2022-07-13T06:20:56Z       - Connect 264 transactions: 146.01ms (0.553ms/tx, 0.196ms/txin) [3391.07s (9.09ms/blk)]
2022-07-13T06:20:56Z     - Verify 746 txins: 146.20ms (0.196ms/txin) [3409.13s (9.14ms/blk)]
2022-07-13T06:20:56Z     - Index writing: 2.33ms [372.71s (1.00ms/blk)]
2022-07-13T06:20:56Z     - Callbacks: 0.06ms [11.66s (0.03ms/blk)]
2022-07-13T06:20:56Z BlockChecked: block hash=000000000000000006011628b874f7619bbe7da444ead0450d531b7cc51ef357 state=Valid
2022-07-13T06:20:56Z   - Connect total: 151.01ms [4204.94s (11.28ms/blk)]
2022-07-13T06:20:56Z   - Flush: 2.95ms [433.70s (1.16ms/blk)]
2022-07-13T06:20:56Z   - Writing chainstate: 0.08ms [155.04s (0.42ms/blk)]
2022-07-13T06:20:56Z Blockpolicy estimates updated by 0 of 0 block txs, since last block 0 of 0 tracked, mempool map size 0, max target 0 from current
2022-07-13T06:20:56Z UpdateTip: new best=000000000000000006011628b874f7619bbe7da444ead0450d531b7cc51ef357 height=372875 version=0x00000003 log2_work=83.298349 tx=82270072 date='2015-09-03T20:24:40Z' progress=0.112441 cache=599.3MiB(4426184txo)
2022-07-13T06:20:56Z   - Connect postprocess: 0.62ms [114.68s (0.31ms/blk)]
2022-07-13T06:20:56Z - Connect block: 166.65ms [5988.22s (16.06ms/blk)]
2022-07-13T06:20:56Z Enqueuing BlockConnected: block hash=000000000000000006011628b874f7619bbe7da444ead0450d531b7cc51ef357 block height=372875
2022-07-13T06:20:56Z Enqueuing UpdatedBlockTip: new block hash=000000000000000006011628b874f7619bbe7da444ead0450d531b7cc51ef357 fork block hash=0000000000000000054d9213ee43cd7a7b353b3322a15848cfefe36b88ec37fe (in IBD=true)
2022-07-13T06:20:56Z BlockConnected: block hash=000000000000000006011628b874f7619bbe7da444ead0450d531b7cc51ef357 block height=372875
2022-07-13T06:20:56Z   - Load block from disk: 35.67ms [1079.90s]
2022-07-13T06:20:56Z     - Sanity checks: 11.59ms [297.58s (0.80ms/blk)]
2022-07-13T06:20:56Z     - Fork checks: 0.10ms [63.54s (0.17ms/blk)]


Quote from: nc50lc on July 12, 2022, 03:28:08 AM
Quote from: kemist on July 11, 2022, 01:25:37 PM
I am not at the computer, so can't paste debug.log right now, but the only error is about not finding mempool, but continuing anyway. The last line is never an error.
Without the logs or error message, this is just going to be a guessing game.
Try starting Core with -debug=1 parameter to enable all log categories.

Perhaps it's the same as this (open) issue: Bitcoind repeatedly crashing at UpdateTip with no error message #24483?
NotATether
legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
Re: Crash without error during IBD
July 13, 2022, 02:21:22 AM
#9
Crash on an old laptop? Chances are you're using an old HDD too. Please note that if the HDD has failed any SMART checks, you should not be surprised if the crash was because of an Input/Output Error (EIO) or Structure Needs Cleaning kind of error values (of errno) which are causing Bitcoin Core to abort, as there is no logic inside the program t handle these type of errors which do not occur normally.
LoyceV
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
Re: Crash without error during IBD
July 12, 2022, 03:31:54 PM
#8
It could be hardware failure. With just 4 GB RAM, you're asking a lot from your old HDD. I recently saw a case in which an incorrect CPU voltage setting caused problems syncing.

Quote from: LoyceV on June 05, 2022, 03:26:36 AM
So that's why Bitcoin Core gives a warning when started for the first time:
Quote
This initial synchronisation is very demanding, and may expose hardware problems with your computer that had previously gone unnoticed.
Memtest won't expose all possible problems.

Any chance the laptop's cooling system is filled with dust?
kemist
newbie
Activity: 11
Merit: 4
Re: Crash without error during IBD
July 12, 2022, 01:55:51 PM
#7
Here are the journalctl results. Note that I tried to re-run it last night with slightly different parameters:

Code:
$ bitcoind -prune=20000 -maxmempool=500 -reindex -daemon

It crashed at just before 8AM this morning (that's the timestamp of the last update in debug.log).

So, first, I looked at the most recent journalctl logs for just today to see what happened at that time. Here's just before, during and after:

Code:
Jul 12 07:42:41 ThinkPad systemd[1]: NetworkManager-dispatc>
Jul 12 07:56:05 ThinkPad systemd-oomd[702]: Killed /user.sl>
Jul 12 07:56:06 ThinkPad systemd[975]: vte-spawn-25f26153-0>
Jul 12 07:56:06 ThinkPad systemd[975]: vte-spawn-25f26153-0>
Jul 12 07:56:19 ThinkPad systemd[975]: gnome-terminal-serve>
Jul 12 08:17:02 ThinkPad CRON[21339]: pam_unix(cron:session>

option -p 3:

Code:
$ sudo journalctl -p 3 -x -b -0
Jul 09 14:08:33 ThinkPad kernel: x86/cpu: VMX (outside TXT)>
Jul 09 14:08:34 ThinkPad kernel: ima: Error Communicating t>
Jul 09 14:08:34 ThinkPad kernel: ima: Error Communicating t>
Jul 09 14:08:34 ThinkPad kernel: ima: Error Communicating t>
Jul 09 14:08:34 ThinkPad kernel: ima: Error Communicating t>
Jul 09 14:08:34 ThinkPad kernel: ima: Error Communicating t>
Jul 09 14:08:34 ThinkPad kernel: ima: Error Communicating t>
Jul 09 14:08:34 ThinkPad kernel: ima: Error Communicating t>
Jul 09 14:08:34 ThinkPad kernel: ima: Error Communicating t>
Jul 09 14:08:34 ThinkPad kernel: mtd device must be supplie>
Jul 09 14:08:44 ThinkPad kernel: mtd device must be supplie>
Jul 09 14:08:49 ThinkPad kernel: mtd device must be supplie>
Jul 09 14:09:27 ThinkPad systemd[975]: Failed to start Appl>
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 229 and the job result is failed.
Jul 09 14:09:27 ThinkPad systemd[975]: Failed to start Appl>
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 225 and the job result is failed.
Jul 09 14:09:56 ThinkPad systemd[975]: Failed to start Trac>
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 25 and the job result is failed.
Jul 09 19:15:57 ThinkPad systemd[1]: Failed to start Refres>
░░ Subject: A start job for unit fwupd-refresh.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit fwupd-refresh.service has finished with a failure.
░░
░░ The job identifier is 3062 and the job result is failed.
Jul 10 12:01:42 ThinkPad systemd[1]: Failed to start Refres>
░░ Subject: A start job for unit fwupd-refresh.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit fwupd-refresh.service has finished with a failure.
░░
░░ The job identifier is 7345 and the job result is failed.
Jul 11 02:45:43 ThinkPad systemd[1]: Failed to start Refres>
░░ Subject: A start job for unit fwupd-refresh.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit fwupd-refresh.service has finished with a failure.
░░
░░ The job identifier is 11391 and the job result is failed.
Jul 11 14:31:40 ThinkPad systemd[1]: Failed to start Refres>
░░ Subject: A start job for unit fwupd-refresh.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit fwupd-refresh.service has finished with a failure.
░░
░░ The job identifier is 13567 and the job result is failed.
Jul 12 04:59:42 ThinkPad systemd[1]: Failed to start Refres>
░░ Subject: A start job for unit fwupd-refresh.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit fwupd-refresh.service has finished with a failure.
░░
░░ The job identifier is 16523 and the job result is failed.
Jul 12 06:09:38 ThinkPad systemd[1]: Failed to start Refres>
░░ Subject: A start job for unit fwupd-refresh.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit fwupd-refresh.service has finished with a failure.
░░
░░ The job identifier is 16833 and the job result is failed.
Jul 12 11:15:40 ThinkPad kernel: ACPI: \_SB_.PCI0.LPC_.EC__>
lines 63-85/85 (END)

option -p 4:

Code:
$ sudo journalctl -p 4 -x -b -0
Jul 09 14:08:33 ThinkPad kernel: x86/cpu: VMX (outside TXT)>
Jul 09 14:08:33 ThinkPad kernel: MDS CPU bug present and SM>
Jul 09 14:08:33 ThinkPad kernel:  #2
Jul 09 14:08:33 ThinkPad kernel:  #3
Jul 09 14:08:33 ThinkPad kernel: ENERGY_PERF_BIAS: Set to '>
Jul 09 14:08:34 ThinkPad kernel: pnp 00:00: disabling [mem >
Jul 09 14:08:34 ThinkPad kernel: pnp 00:00: disabling [mem >
Jul 09 14:08:34 ThinkPad kernel: pnp 00:00: disabling [mem >
Jul 09 14:08:34 ThinkPad kernel: pnp 00:00: disabling [mem >
Jul 09 14:08:34 ThinkPad kernel: pnp 00:00: disabling [mem >
Jul 09 14:08:34 ThinkPad kernel: pnp 00:00: disabling [mem >
Jul 09 14:08:34 ThinkPad kernel: pnp 00:00: disabling [mem >
Jul 09 14:08:34 ThinkPad kernel: pnp 00:00: disabling [mem >
Jul 09 14:08:34 ThinkPad kernel: device-mapper: core: CONFI>
Jul 09 14:08:34 ThinkPad kernel: platform eisa.0: EISA: Can>
Jul 09 14:08:34 ThinkPad kernel: platform eisa.0: Cannot al>
Jul 09 14:08:34 ThinkPad kernel: platform eisa.0: Cannot al>
Jul 09 14:08:34 ThinkPad kernel: platform eisa.0: Cannot al>
Jul 09 14:08:34 ThinkPad kernel: platform eisa.0: Cannot al>
Jul 09 14:08:34 ThinkPad kernel: platform eisa.0: Cannot al>
Jul 09 14:08:34 ThinkPad kernel: platform eisa.0: Cannot al>
Jul 09 14:08:34 ThinkPad kernel: platform eisa.0: Cannot al>
Jul 09 14:08:34 ThinkPad kernel: platform eisa.0: Cannot al>
Jul 09 14:08:34 ThinkPad kernel: ima: Error Communicating t>
Jul 09 14:08:34 ThinkPad kernel: ima: Error Communicating t>
Jul 09 14:08:34 ThinkPad kernel: ima: Error Communicating t>
Jul 09 14:08:34 ThinkPad kernel: ima: Error Communicating t>
Jul 09 14:08:34 ThinkPad kernel: ima: Error Communicating t>
Jul 09 14:08:34 ThinkPad kernel: ima: Error Communicating t>
Jul 09 14:08:34 ThinkPad kernel: ima: Error Communicating t>
Jul 09 14:08:34 ThinkPad kernel: ima: Error Communicating t>
Jul 09 14:08:34 ThinkPad kernel: acpi PNP0C14:01: duplicate>
Jul 09 14:08:34 ThinkPad kernel: ACPI Warning: SystemIO ran>
Jul 09 14:08:34 ThinkPad kernel: ACPI Warning: SystemIO ran>
Jul 09 14:08:34 ThinkPad kernel: ACPI Warning: SystemIO ran>
Jul 09 14:08:34 ThinkPad kernel: ACPI Warning: SystemIO ran>
Jul 09 14:08:34 ThinkPad kernel: lpc_ich: Resource conflict>
Jul 09 14:08:34 ThinkPad kernel: ata1.00: ATA Identify Devi>
Jul 09 14:08:34 ThinkPad kernel: ata1.00: ATA Identify Devi>
Jul 09 14:08:34 ThinkPad kernel: mtd device must be supplie>
Jul 09 14:08:40 ThinkPad kernel: iwlwifi 0000:03:00.0: can'>
Jul 09 14:08:40 ThinkPad kernel: at24 0-0050: supply vcc no>
Jul 09 14:08:40 ThinkPad systemd-udevd[342]: sda: Process '>
Jul 09 14:08:42 ThinkPad systemd-udevd[355]: video4linux: P>
Jul 09 14:08:42 ThinkPad systemd-udevd[355]: video4linux: P>
Jul 09 14:08:44 ThinkPad systemd-udevd[348]: sda2: Process >
Jul 09 14:08:44 ThinkPad kernel: mtd device must be supplie>
Jul 09 14:08:44 ThinkPad systemd-udevd[334]: sda1: Process >
Jul 09 14:08:49 ThinkPad kernel: mtd device must be supplie>
Jul 09 14:09:00 ThinkPad udisksd[786]: failed to load modul>
Jul 09 14:09:01 ThinkPad udisksd[786]: Failed to load the '>
Jul 09 14:09:07 ThinkPad kernel: kauditd_printk_skb: 28 cal>
Jul 09 14:09:08 ThinkPad gdm-autologin][931]: gkr-pam: no p>
Jul 09 14:09:12 ThinkPad systemd[1]: kerneloops.service: Fo>
Jul 09 14:09:12 ThinkPad systemd[1]: This usually indicates>
Jul 09 14:09:27 ThinkPad gnome-session-binary[1188]: GnomeD>
Jul 09 14:09:27 ThinkPad systemd[975]: app-gnome-gnome\x2dk>
Jul 09 14:09:27 ThinkPad systemd[975]: app-gnome-gnome\x2dk>
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit UNIT has entered the 'failed' state with result 'resources'.
Jul 09 14:09:27 ThinkPad systemd[975]: Failed to start Appl>
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 229 and the job result is failed.
Jul 09 14:09:27 ThinkPad systemd[975]: app-gnome-gnome\x2dk>
Jul 09 14:09:27 ThinkPad systemd[975]: app-gnome-gnome\x2dk>
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit UNIT has entered the 'failed' state with result 'resources'.
Jul 09 14:09:27 ThinkPad systemd[975]: Failed to start Appl>
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 225 and the job result is failed.
Jul 09 14:09:27 ThinkPad systemd[975]: org.gnome.Shell@x11.>
Jul 09 14:09:39 ThinkPad snapd-desktop-i[1036]: cannot open>
Jul 09 14:09:40 ThinkPad systemd[975]: snap.snapd-desktop-i>
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit UNIT has entered the 'failed' state with result 'exit-code'.
Jul 09 14:09:40 ThinkPad snapd-desktop-i[1288]: cannot open>
Jul 09 14:09:40 ThinkPad systemd[975]: snap.snapd-desktop-i>
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit UNIT has entered the 'failed' state with result 'exit-code'.
Jul 09 14:09:54 ThinkPad at-spi-dbus-bus.desktop[1222]: dbu>
Jul 09 14:09:54 ThinkPad systemd[975]: Dependency failed fo>
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 184 and the job result is dependency.
Jul 09 14:09:54 ThinkPad at-spi-dbus-bus.desktop[1222]: dbu>
Jul 09 14:09:54 ThinkPad at-spi2-registr[1545]: Failed to r>
Jul 09 14:09:54 ThinkPad at-spi2-registr[1545]: Unable to r>
Jul 09 14:09:55 ThinkPad tracker-extract[1037]: Could not c>
Jul 09 14:09:56 ThinkPad systemd[975]: tracker-extract-3.se>
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit UNIT has entered the 'failed' state with result 'exit-code'.
Jul 09 14:09:56 ThinkPad systemd[975]: Failed to start Trac>
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 25 and the job result is failed.
Jul 09 14:10:03 ThinkPad gsd-media-keys[1563]: Failed to gr>
Jul 09 14:10:03 ThinkPad gsd-media-keys[1563]: Failed to gr>
Jul 09 14:10:38 ThinkPad org.freedesktop.FileManager1[1882]>
Jul 09 14:10:42 ThinkPad gnome-shell[1214]: ATK Bridge is d>
Jul 09 14:11:01 ThinkPad [email protected][12>
Jul 09 14:11:02 ThinkPad [email protected][12>
Jul 09 19:15:57 ThinkPad systemd[1]: fwupd-refresh.service:>
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit fwupd-refresh.service has entered the 'failed' state with result 'e>
Jul 09 19:15:57 ThinkPad systemd[1]: Failed to start Refres>
░░ Subject: A start job for unit fwupd-refresh.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit fwupd-refresh.service has finished with a failure.
░░
░░ The job identifier is 3062 and the job result is failed.
Jul 10 01:17:37 ThinkPad gnome-shell[1214]: clutter_actor_i>
Jul 10 07:29:43 ThinkPad gnome-shell[1214]: meta_window_set>
Jul 10 07:41:16 ThinkPad gnome-shell[1214]: clutter_actor_s>
Jul 10 07:41:16 ThinkPad gnome-shell[1214]: ../clutter/clut>
Jul 10 07:41:16 ThinkPad gnome-shell[1214]: ../clutter/clut>
Jul 10 07:45:45 ThinkPad nautilus[1532]: g_object_ref: asse>
Jul 10 07:45:45 ThinkPad nautilus[1532]: g_object_unref: as>
Jul 10 07:46:43 ThinkPad gnome-shell[1214]: Could not creat>
Jul 10 07:52:34 ThinkPad gnome-shell[1214]: meta_window_set>
Jul 10 08:15:09 ThinkPad gnome-shell[1214]: meta_window_set>
Jul 10 08:29:41 ThinkPad gnome-shell[1214]: meta_window_set>
Jul 10 08:33:43 ThinkPad gedit[4510]: Error querying file i>
Jul 10 12:01:42 ThinkPad systemd[1]: fwupd-refresh.service:>
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit fwupd-refresh.service has entered the 'failed' state with result 'e>
Jul 10 12:01:42 ThinkPad systemd[1]: Failed to start Refres>
░░ Subject: A start job for unit fwupd-refresh.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit fwupd-refresh.service has finished with a failure.
░░
░░ The job identifier is 7345 and the job result is failed.
Jul 11 02:45:43 ThinkPad systemd[1]: fwupd-refresh.service:>
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit fwupd-refresh.service has entered the 'failed' state with result 'e>
Jul 11 02:45:43 ThinkPad systemd[1]: Failed to start Refres>
░░ Subject: A start job for unit fwupd-refresh.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit fwupd-refresh.service has finished with a failure.
░░
░░ The job identifier is 11391 and the job result is failed.
Jul 11 07:48:14 ThinkPad io.snapcraft.Settings[8609]: userd>
Jul 11 14:31:40 ThinkPad systemd[1]: fwupd-refresh.service:>
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit fwupd-refresh.service has entered the 'failed' state with result 'e>
Jul 11 14:31:40 ThinkPad systemd[1]: Failed to start Refres>
░░ Subject: A start job for unit fwupd-refresh.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit fwupd-refresh.service has finished with a failure.
░░
░░ The job identifier is 13567 and the job result is failed.
Jul 11 22:28:20 ThinkPad gedit[4510]: Error querying file i>
Jul 12 04:59:42 ThinkPad systemd[1]: fwupd-refresh.service:>
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit fwupd-refresh.service has entered the 'failed' state with result 'e>
Jul 12 04:59:42 ThinkPad systemd[1]: Failed to start Refres>
░░ Subject: A start job for unit fwupd-refresh.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit fwupd-refresh.service has finished with a failure.
░░
░░ The job identifier is 16523 and the job result is failed.
Jul 12 06:09:38 ThinkPad systemd[1]: fwupd-refresh.service:>
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit fwupd-refresh.service has entered the 'failed' state with result 'e>
Jul 12 06:09:38 ThinkPad systemd[1]: Failed to start Refres>
░░ Subject: A start job for unit fwupd-refresh.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit fwupd-refresh.service has finished with a failure.
░░
░░ The job identifier is 16833 and the job result is failed.
Jul 12 09:11:19 ThinkPad update-notifier[1942]: gtk_widget_>
Jul 12 09:11:19 ThinkPad update-notifier[1942]: gtk_widget_>
Jul 12 11:15:34 ThinkPad kernel: unchecked MSR access error>
Jul 12 11:15:36 ThinkPad kernel: Call Trace:
Jul 12 11:15:36 ThinkPad kernel: 
Jul 12 11:15:36 ThinkPad kernel:  ? __restore_processor_sta>
Jul 12 11:15:36 ThinkPad kernel:  restore_processor_state+0>
Jul 12 11:15:36 ThinkPad kernel:  x86_acpi_suspend_lowlevel>
Jul 12 11:15:36 ThinkPad kernel:  acpi_suspend_enter+0x56/0>
Jul 12 11:15:36 ThinkPad kernel:  suspend_enter+0x28f/0x340
Jul 12 11:15:36 ThinkPad kernel:  suspend_devices_and_enter>
Jul 12 11:15:37 ThinkPad kernel:  enter_state+0x1d2/0x430
Jul 12 11:15:37 ThinkPad kernel:  pm_suspend+0x4e/0xc0
Jul 12 11:15:37 ThinkPad kernel:  state_store+0x81/0xe0
Jul 12 11:15:37 ThinkPad kernel:  kobj_attr_store+0x12/0x20
Jul 12 11:15:37 ThinkPad kernel:  sysfs_kf_write+0x3e/0x50
Jul 12 11:15:37 ThinkPad kernel:  kernfs_fop_write_iter+0x1>
Jul 12 11:15:37 ThinkPad kernel:  new_sync_write+0x117/0x1a0
Jul 12 11:15:37 ThinkPad kernel:  vfs_write+0x1cd/0x260
Jul 12 11:15:37 ThinkPad kernel:  ksys_write+0x67/0xe0
Jul 12 11:15:37 ThinkPad kernel:  __x64_sys_write+0x19/0x20
Jul 12 11:15:37 ThinkPad kernel:  do_syscall_64+0x5c/0xc0
Jul 12 11:15:37 ThinkPad kernel:  ? exit_to_user_mode_prepa>
Jul 12 11:15:37 ThinkPad kernel:  ? syscall_exit_to_user_mo>
Jul 12 11:15:37 ThinkPad kernel:  ? __x64_sys_sendmsg+0x1d/>
Jul 12 11:15:37 ThinkPad kernel:  ? do_syscall_64+0x69/0xc0
Jul 12 11:15:37 ThinkPad kernel:  ? do_user_addr_fault+0x1e>
Jul 12 11:15:37 ThinkPad kernel:  ? exit_to_user_mode_prepa>
Jul 12 11:15:37 ThinkPad kernel:  ? syscall_exit_to_user_mo>
Jul 12 11:15:37 ThinkPad kernel:  ? __do_sys_gettid+0x1b/0x>
Jul 12 11:15:37 ThinkPad kernel:  ? do_syscall_64+0x69/0xc0
Jul 12 11:15:37 ThinkPad kernel:  ? asm_exc_page_fault+0x8/>
Jul 12 11:15:37 ThinkPad kernel:  entry_SYSCALL_64_after_hw>
Jul 12 11:15:37 ThinkPad kernel: RIP: 0033:0x7f2d9e2e0a37
Jul 12 11:15:37 ThinkPad kernel: Code: 10 00 f7 d8 64 89 02>
Jul 12 11:15:37 ThinkPad kernel: RSP: 002b:00007fff8e6b6c28>
Jul 12 11:15:37 ThinkPad kernel: RAX: ffffffffffffffda RBX:>
Jul 12 11:15:37 ThinkPad kernel: RDX: 0000000000000004 RSI:>
Jul 12 11:15:37 ThinkPad kernel: RBP: 00007fff8e6b6ce0 R08:>
Jul 12 11:15:37 ThinkPad kernel: R10: 0000000000000000 R11:>
Jul 12 11:15:37 ThinkPad kernel: R13: 000055b1b723f2d0 R14:>
Jul 12 11:15:37 ThinkPad kernel: 
Jul 12 11:15:40 ThinkPad kernel: ACPI: \_SB_.PCI0.LPC_.EC__>
Jul 12 11:15:40 ThinkPad kernel: done.
Jul 12 11:15:40 ThinkPad kernel: ata1.00: ATA Identify Devi>
Jul 12 11:15:40 ThinkPad kernel: ata1.00: ATA Identify Devi>
Jul 12 11:15:49 ThinkPad gnome-shell[1214]: JS ERROR: Faile>
                                                                asyncCallback@r>
Jul 12 11:16:10 ThinkPad gnome-shell[1214]: JS ERROR: Faile>
                                                                asyncCallback@r>
Jul 12 11:16:18 ThinkPad [email protected][12>
Jul 12 11:16:18 ThinkPad [email protected][12>
Jul 12 11:40:39 ThinkPad gnome-shell[1214]: meta_window_set>


Quote from: ?? on ??
Quote from: kemist on July 11, 2022, 01:25:37 PM
I have tried running the GUI and it closed unexpectedly and without any error message. I thought it was an issue with the power controls, so I have turned off all power controls so the computer does not hibernate, or even turn off the screen.

As @nc50lc said, without any log/error message we only can guess or list all possible problems. Aside from debug.log, please check your journalctl and see any relevant message (such as I/O error, OOM killer is triggered or other hardware error). Usually i would this parameter,

Code:
sudo journalctl -p 3 -x -b -0

Where -p 3 show error message (use -p 4 to also see warning message), -x is extra message and -b -0 to show log from current boot.
nc50lc
legendary
Activity: 2618
Merit: 6452
Self-proclaimed Genius
Re: Crash without error during IBD
July 12, 2022, 03:28:08 AM
#6
Quote from: kemist on July 11, 2022, 01:25:37 PM
I am not at the computer, so can't paste debug.log right now, but the only error is about not finding mempool, but continuing anyway. The last line is never an error.
Without the logs or error message, this is just going to be a guessing game.
Try starting Core with -debug=1 parameter to enable all log categories.

Perhaps it's the same as this (open) issue: Bitcoind repeatedly crashing at UpdateTip with no error message #24483?
kemist
newbie
Activity: 11
Merit: 4
Re: Crash without error during IBD
July 12, 2022, 12:16:13 AM
#5
Quote from: DireWolfM14 on July 11, 2022, 04:20:04 PM
I ran into an issue once where a new install of Ubuntu wanted to partition my drive to no more than 200GB.  From the command terminal run "sudo df -h" to show your diskspace allocations.

Code:
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           381M  2.0M  379M   1% /run
/dev/sda2       292G   54G  224G  20% /
tmpfs           1.9G     0  1.9G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
/dev/sda1       511M  5.3M  506M   2% /boot/efi
tmpfs           381M  2.4M  379M   1% /run/user/1000

Quote from: DireWolfM14 on July 11, 2022, 04:20:04 PM
Another issue you may have is that bitcoind may already be running in the background.  If so you won't be able to run bitcoin-qt, nor will you be able to start bitcoind from the terminal.  Did you set up a systemd file so bitcoind will start on machine startup?

No, I didn't set it up to start on machine startup. I also just checked to see what processes are running, and it's not listed. To be clear, I ran the GUI first right after install. I only tried bitcoind after the GUI crashed.
kemist
newbie
Activity: 11
Merit: 4
Re: Crash without error during IBD
July 12, 2022, 12:07:33 AM
#4
(Looks like I forgot to hit submit on this yesterday) I followed those instructions to install (except I didn't verify signatures). The GUI started up and ran for quite awhile before shutting down. Didn't seem like libraries were missing.

Quote from: BitMaxz on July 11, 2022, 05:38:13 PM
How did you install Bitcoin core?

If you didn't install it properly it will end up like this so I suggest try to reinstall the Bitcoin core and make sure that you install the necessary components under this directory /usr/local/bin and use sudo install to install bitcoin core.

I suggest you read this below and carefully follow the instruction on how to install it properly through Terminal commands

- https://bitcoin.org/en/full-node#linux-instructions

About the GUI you will need the required libraries to install to make the Bitcoin core GUI work properly. Follow the instruction from this link below
- https://bitcoin.org/en/full-node#other-linux-gui
BitMaxz
legendary
Activity: 3472
Merit: 3217
Playbet.io - Crypto Casino and Sportsbook
Re: Crash without error during IBD
July 11, 2022, 05:38:13 PM
#3
How did you install Bitcoin core?

If you didn't install it properly it will end up like this so I suggest try to reinstall the Bitcoin core and make sure that you install the necessary components under this directory /usr/local/bin and use sudo install to install bitcoin core.

I suggest you read this below and carefully follow the instruction on how to install it properly through Terminal commands

- https://bitcoin.org/en/full-node#linux-instructions

About the GUI you will need the required libraries to install to make the Bitcoin core GUI work properly. Follow the instruction from this link below
- https://bitcoin.org/en/full-node#other-linux-gui
Pages:
Bitcoin Forum>Bitcoin>Bitcoin Technical Support
Jump to: