Here are the last few entries:
2025-09-02T17:44:10+01:00 2025-09-02T16:44:10Z CreateNewBlock(): total size: 1104004 block weight: 2916841 txs: 2496 fees: 3717164 sigops 11017
2025-09-02T17:44:14+01:00 2025-09-02T16:44:14Z Saw new header hash=00000000000000000001d03eb01f5fcb46147315577611b37f96785673fe00de height=912901
2025-09-02T17:44:20+01:00 2025-09-02T16:44:20Z UpdateTip: new best=00000000000000000001d03eb01f5fcb46147315577611b37f96785673fe00de height=912901 version=0x33c72000 log2_work=95.802853 tx=1236121343 date=‘2025-09-02T16:43:49Z’ progress=1.000000 cache=2.0MiB(14939txo) warning=‘Miner violated version bit protocol’
2025-09-02T17:44:20+01:00 OK2025-09-02T16:44:20Z CreateNewBlock(): total size: 182902 block weight: 443737 txs: 459 fees: 269755 sigops 1754
2025-09-02T17:45:02+01:00 2025-09-02T16:45:02Z CreateNewBlock(): total size: 320364 block weight: 871374 txs: 695 fees: 723084 sigops 4750
2025-09-02T17:45:40+01:00 2025-09-02T16:45:40Z Saw new header hash=00000000000000000000f584ccc963883814f5c46998297eb447d5160e1cea64 height=912902
2025-09-02T17:45:45+01:00 2025-09-02T16:45:45Z UpdateTip: new best=00000000000000000000f584ccc963883814f5c46998297eb447d5160e1cea64 height=912902 version=0x25912000 log2_work=95.802865 tx=1236123804 date=‘2025-09-02T16:45:27Z’ progress=1.000000 cache=3.7MiB(26566txo) warning=‘Miner violated version bit protocol’
2025-09-02T17:45:45+01:00 2025-09-02T16:45:45Z CreateNewBlock(): total size: 98463 block weight: 241023 txs: 268 fees: 156053 sigops 1042
2025-09-02T17:46:26+01:00 OK2025-09-02T16:46:26Z CreateNewBlock(): total size: 182177 block weight: 442439 txs: 497 fees: 454094 sigops 1709
2025-09-02T17:47:08+01:00 2025-09-02T16:47:08Z CreateNewBlock(): total size: 277507 block weight: 672427 txs: 720 fees: 718784 sigops 2571
2025-09-02T17:47:49+01:00 2025-09-02T16:47:49Z CreateNewBlock(): total size: 438837 block weight: 1040037 txs: 942 fees: 1021268 sigops 3486
Nothing unusual there. I usually see that error you mentioned when validating a block takes longer than expected (it resolves itself once validation is completed). That typically happens on systems with 8GB RAM or less, though, which is not applicable in your case. If your RAM usage is fairly low like it was in your earlier post, that is a bit of a head scratcher.
In addition, Bitcoin Knots is stuck in shutting down mode again, after I took a look at the config. I did not make any changes.
Do the logs indicate why it is shutting down?
Not seeing anything in the logs that suggests why.