Kernel is in init phase, can't do non-init command

Something goes wrong. Running on mac mini m4.

I get something similar:

DEBUG run: nockapp::nockapp: Action channel received
 INFO poke{src="timer"}:do_poke:slam:interpret: slogger: command: timer
DEBUG next_effect: nockapp::nockapp::driver: Waiting for recv on next effect
DEBUG next_effect: nockapp::nockapp::driver: Waiting for recv on next effect
DEBUG next_effect: nockapp::nockapp::driver: Waiting for recv on next effect
DEBUG next_effect: nockapp::nockapp::driver: Waiting for recv on next effect
TRACE nockapp::nockapp: Write to "./.data.nockchain/checkpoints/0.chkjam" successful, checksum: 9f457d961820ba38e0b61c3a4aca687d200eb2c0357f6b36d54fedfd5e9ff054, event: 43
DEBUG run: nockapp::nockapp: Action channel received
 INFO poke{src="timer"}:do_poke:slam:interpret: slogger: command: timer
DEBUG next_effect: nockapp::nockapp::driver: Waiting for recv on next effect
DEBUG next_effect: nockapp::nockapp::driver: Waiting for recv on next effect
DEBUG next_effect: nockapp::nockapp::driver: Waiting for recv on next effect
DEBUG next_effect: nockapp::nockapp::driver: Waiting for recv on next effect
TRACE nockapp::nockapp: Write to "./.data.nockchain/checkpoints/1.chkjam" successful, checksum: 80b3b88136c98cbb49b5fb7b93726708eda47af0901ec880fe248686a1bd470e, event: 44
DEBUG run: nockapp::nockapp: Action channel received
 INFO poke{src="timer"}:do_poke:slam:interpret: slogger: command: timer
DEBUG next_effect: nockapp::nockapp::driver: Waiting for recv on next effect
DEBUG next_effect: nockapp::nockapp::driver: Waiting for recv on next effect
DEBUG next_effect: nockapp::nockapp::driver: Waiting for recv on next effect
DEBUG next_effect: nockapp::nockapp::driver: Waiting for recv on next effect
TRACE nockapp::nockapp: Write to "./.data.nockchain/checkpoints/0.chkjam" successful, checksum: 68f1913e61a7855c8209332f378746d7f7b4ca1e77a37ef41da2fd9b9c1c92f5, event: 45
1 Like

Same with me. I’ve installed everything with no issues. Tried running in --mine mode with the list of suggested peers that has been drifting around. Now I am just running it with --mine only, and it keeps iterating events and trying to write to one of the jam files with checksums.