ckb-light-client exits immediately after start.

[yanguoyu]

Question and Logs:

After the program starts, it prints the 'Run...' log and then exits immediately. Version 0.4.1 runs normally, but this issue occurs in version 0.5.0.

0.5.0 screenshot

0.4.1 screenshot

System:

[eval-exec]

@yanguoyu Hello, could you provide the last TRACE level log before ckb-light-client exit? (RUST_LOG=TRACE ./ckb-light-client.exe run --config-file)
I can't reproduce this on windows-server 2019 with ckb-light-client@v0.5.0

vagrant@VAGRANT-K51B6U3 MINGW64 ~/ckb-light-client-release
$ ./ckb-light-client.exe --version
CKB Light Client 0.5.0
vagrant@VAGRANT-K51B6U3 MINGW64 ~/ckb-light-client-release
$ RUST_LOG=INFO ./ckb-light-client.exe run --config-file config/testnet.toml
[2025-06-27T12:06:10Z INFO  ckb_light_client] Starting ...
[2025-06-27T12:06:10Z INFO  ckb_light_client::cli] Executing ...
[2025-06-27T12:06:10Z INFO  ckb_light_client::subcmds] Run ...
[2025-06-27T12:06:10Z INFO  ckb_network::network] Loading the peer store. This process may take a few seconds to complete.
[2025-06-27T12:06:11Z INFO  ckb_network::network] Listen on address: /ip4/0.0.0.0/tcp/8118
[2025-06-27T12:06:11Z INFO  ckb_network::network] Listen on address: /ip4/0.0.0.0/tcp/8118/ws
[2025-06-27T12:06:11Z INFO  ckb_network::network] p2p service event: ListenStarted { address: "/ip4/0.0.0.0/tcp/8118" }
[2025-06-27T12:06:11Z INFO  ckb_network::network] p2p service event: ListenStarted { address: "/ip4/0.0.0.0/tcp/8118/ws" }
[2025-06-27T12:06:11Z INFO  ckb_light_client_lib::protocols::light_client] LightClient.protocol initialized
[2025-06-27T12:06:11Z INFO  ckb_stop_handler::stop_register] Waiting exit signal...
[2025-06-27T12:06:11Z INFO  ckb_light_client_lib::protocols::light_client] LightClient(3).connected peer=SessionId(1)
[2025-06-27T12:06:11Z INFO  ckb_light_client_lib::protocols::synchronizer] SyncProtocol(3).connected peer=SessionId(1)
[2025-06-27T12:06:12Z INFO  ckb_light_client_lib::protocols::synchronizer] SyncProtocol(3).connected peer=SessionId(2)
[2025-06-27T12:06:12Z INFO  ckb_light_client_lib::protocols::light_client] LightClient(3).connected peer=SessionId(2)
[2025-06-27T12:06:13Z INFO  ckb_light_client_lib::protocols::synchronizer] SyncProtocol(3).connected peer=SessionId(3)
[2025-06-27T12:06:13Z INFO  ckb_light_client_lib::protocols::light_client] LightClient(3).connected peer=SessionId(3)
[2025-06-27T12:06:13Z INFO  ckb_light_client_lib::protocols::synchronizer] SyncProtocol(3).connected peer=SessionId(4)
[2025-06-27T12:06:13Z INFO  ckb_light_client_lib::protocols::light_client] LightClient(3).connected peer=SessionId(4)
[2025-06-27T12:06:43Z INFO  ckb_light_client_lib::protocols::light_client] finalize 3998 new check points, stop at index 3998, value 0x5c3fd10e6d130456aeaf247485f0f0ad782b9c5d891f6a0db526dc93030a225e
[2025-06-27T12:06:51Z INFO  ckb_light_client_lib::protocols::light_client] finalize 4832 new check points, stop at index 8830, value 0xb956224b4b9419a24ac887dad6cb0d751604021ea630fb988ed6a81f7f2a4b2a
[2025-06-27T12:06:56Z INFO  ckb_light_client_lib::protocols::light_client] LightClient(3).connected peer=SessionId(20)
[2025-06-27T12:06:56Z INFO  ckb_light_client_lib::protocols::synchronizer] SyncProtocol(3).connected peer=SessionId(20)
[2025-06-27T12:06:56Z INFO  ckb_light_client_lib::protocols::synchronizer] SyncProtocol(3).connected peer=SessionId(21)
[2025-06-27T12:06:56Z INFO  ckb_light_client_lib::protocols::light_client] LightClient(3).connected peer=SessionId(21)
[2025-06-27T12:06:57Z INFO  ckb_light_client_lib::protocols::light_client] LightClient(3).connected peer=SessionId(22)
[2025-06-27T12:06:57Z INFO  ckb_light_client_lib::protocols::synchronizer] SyncProtocol(3).connected peer=SessionId(22)
[2025-06-27T12:06:57Z INFO  ckb_light_client_lib::protocols::synchronizer] SyncProtocol(3).connected peer=SessionId(23)
[2025-06-27T12:06:57Z INFO  ckb_light_client_lib::protocols::light_client] LightClient(3).connected peer=SessionId(23)
[2025-06-27T12:08:03Z WARN  ckb_light_client_lib::protocols::light_client] peer SessionId(22): reach timeout
[2025-06-27T12:08:03Z WARN  ckb_light_client_lib::protocols::light_client] peer SessionId(20): reach timeout
[2025-06-27T12:08:03Z INFO  ckb_light_client_lib::protocols::light_client] LightClient.disconnected peer=SessionId(22)
[2025-06-27T12:08:03Z INFO  ckb_light_client_lib::protocols::synchronizer] SyncProtocol.disconnected peer=SessionId(22)
[2025-06-27T12:08:03Z INFO  ckb_light_client_lib::protocols::light_client] LightClient.disconnected peer=SessionId(20)
[2025-06-27T12:08:03Z INFO  ckb_light_client_lib::protocols::synchronizer] SyncProtocol.disconnected peer=SessionId(20)
[2025-06-27T12:08:11Z INFO  ckb_light_client_lib::protocols::synchronizer] SyncProtocol(3).connected peer=SessionId(25)
[2025-06-27T12:08:11Z INFO  ckb_light_client_lib::protocols::light_client] LightClient(3).connected peer=SessionId(25)
[2025-06-27T12:08:13Z INFO  ckb_light_client_lib::protocols::synchronizer] SyncProtocol(3).connected peer=SessionId(27)
[2025-06-27T12:08:13Z INFO  ckb_light_client_lib::protocols::light_client] LightClient(3).connected peer=SessionId(27)
[2025-06-27T12:08:13Z INFO  ckb_stop_handler::stop_register] All ckb threads have been stopped
[2025-06-27T12:08:13Z INFO  ckb_network::network] NetworkService receive exit signal, start shutdown...
[2025-06-27T12:08:13Z INFO  ckb_network::network] NetworkService shutdown now
[2025-06-27T12:08:13Z INFO  ckb_network::network] p2p service event: ListenClose { address: "/ip4/0.0.0.0/tcp/8118" }
[2025-06-27T12:08:13Z INFO  ckb_network::network] p2p service event: ListenClose { address: "/ip4/0.0.0.0/tcp/8118/ws" }
[2025-06-27T12:08:13Z INFO  ckb_light_client] Done.


vagrant@VAGRANT-K51B6U3 MINGW64 ~/ckb-light-client-release
$ uname -a
MINGW64_NT-10.0-17763 VAGRANT-K51B6U3 3.6.3-086201ea.x86_64 2025-06-05 13:51 UTC x86_64 Msys

vagrant@VAGRANT-K51B6U3 MINGW64 ~/ckb-light-client-release
$ systeminfo

Host Name:                 VAGRANT-K51B6U3
OS Name:                   Microsoft Windows Server 2019 Standard Evaluation
OS Version:                10.0.17763 N/A Build 17763
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Server
OS Build Type:             Multiprocessor Free
Registered Owner:          Vagrant
Registered Organization:   Vagrant
Product ID:                00431-10000-00000-AA648
Original Install Date:     3/21/2020, 8:25:14 PM
System Boot Time:          6/27/2025, 12:01:07 PM
System Manufacturer:       innotek GmbH
System Model:              VirtualBox
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 183 Stepping 1 GenuineIntel ~3187 Mhz
BIOS Version:              innotek GmbH VirtualBox, 12/1/2006
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC) Coordinated Universal Time
Total Physical Memory:     4,096 MB
Available Physical Memory: 3,274 MB
Virtual Memory: Max Size:  5,504 MB
Virtual Memory: Available: 4,794 MB
Virtual Memory: In Use:    710 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    WORKGROUP
Logon Server:              N/A
Hotfix(s):                 6 Hotfix(s) Installed.
                           [01]: KB4537490
                           [02]: KB4486153
                           [03]: KB4512577
                           [04]: KB4537759
                           [05]: KB4539571
                           [06]: KB4538461
Network Card(s):           1 NIC(s) Installed.
                           [01]: Intel(R) PRO/1000 MT Desktop Adapter
                                 Connection Name: Ethernet
                                 DHCP Enabled:    Yes
                                 DHCP Server:     10.0.2.2
                                 IP address(es)
                                 [01]: 10.0.2.15
Hyper-V Requirements:      A hypervisor has been detected. Features required for Hyper-V will not be displayed.

[eval-exec]

@yanguoyu Hello, could you provide the ckb-light-client's data/store/LOG file too. I suspect that the DB is corrupted in RocksDB.

[Keith-CY]

I received a user report describing the same error message.
It's on

{
  "platform":"win32",
  "arch":"x64",
  "release":"10.0.17134",
}

I will contact the user to provide the data/store/LOG if @yanguoyu hasn't submitted it later.

[yanguoyu]

The issue occurs because ckb-light-client runs on Windows Server 2019, which is no longer supported by GitHub's minimum Windows version requirement, leading to failure. It works fine on Windows Server 2022.

[Keith-CY]

I confirmed with the Light Client developer that Light Client requires Windows Server 2022 or later to run. Since Windows Server 2022 is known to correspond to Windows 10 21H2, I advised the user to upgrade system.

However, even after upgrading to Windows 10 22H2, the issue persists -- the Light Client still restarts on launch. The logs also show the same output as previously uploaded.

Ref:
Windows Server 2022 & Windows 10 21H2: https://www.wikiwand.com/en/articles/Microsoft_Windows_Server_2022

[Keith-CY]

I received a user report describing the same error message. It's on

{
"platform":"win32",
"arch":"x64",
"release":"10.0.17134",
}
I will contact the user to provide the data/store/LOG if @yanguoyu hasn't submitted it later.

The LOG from users
light_client_mainnet - 副本.log.zip

[eval-exec]

I think we may need to install latest Microsoft Visual C++ Redistributable
https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

After installation and a reboot, ckb-light-client v0.5.1 successfully ran on Windows Server 2019.

[Keith-CY]

I think we may need to install latest Microsoft Visual C++ Redistributable learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

After installation and a reboot, ckb-light-client v0.5.1 successfully ran on Windows Server 2019.

Yes this is the go-to solution.