Let's share the difficulties we met when we compile and run nockchain

General
1

Hi everyone! I am Bruce from China. It’s nice to make friends here! I have compiled the nockchain, and I would like to share some bugs and difficulties when I compiled it. Please leave your message here to help more people run the nockchain!!!

image
image1905×1001 80.9 KB

2 Likes
2

When I make install choo, I met rm -rf .data.choo
rm -rf ~/.nockapp/choo
cargo install --locked --force --path crates/nockapp/apps/choo --bin choo
make: cargo: No such file or directory
make: *** [Makefile:20: install-choo] Error 127.

This is caused by the lack of rust and cargo in my linux. I solve it by
curl --proto ‘=https’ --tlsv1.2 -sSf https://sh.rustup.rs | sh

source $HOME/.cargo/env

sudo apt install build-essential

make install-choo

2 Likes
3

when i make build nockchain, it may fail caused by the lack of Clang and LLVM

1 Like
4

please use git clone GitHub - zorp-corp/nockchain: Nockchain protocol monorepo to clone the repository

1 Like
6

run a leader and run a follower

2 Likes
7

Hi tomdef, I have not met this issue! if you fix it, could you leave your approach to fix this issue? thx so much!

8

How did you fix this? Same here.

9

It is unclear as to whom you are asking that question, @mitnev, but @CasimirPolandZorp addressed the OP’s question.

10

Bro, have you solved your problem? I have the same problem.

11

Hello, when I run the program, the block height remains at 0 for a long time without changing. Is this normal?

12

WechatIMG875
WechatIMG875572×740 175 KB

13

Yes that is normal right now

15

I’m getting an error when I try to run make build on AWS Linux. It looks like the command that’s failing is hoonc --arbitrary hoon/trivial.hoon

2025-05-15T05:38:31.018786Z DEBUG hoonc: Dependencies directory: "hoon"
2025-05-15T05:38:31.018821Z DEBUG hoonc: Entry file: "hoon/trivial.hoon"
2025-05-15T05:38:31.018848Z  INFO nockapp::kernel::boot: kernel: starting
2025-05-15T05:38:31.018857Z DEBUG nockapp::kernel::boot: kernel: pma directory: "/home/ec2-user/.nockapp/hoonc/pma"
2025-05-15T05:38:31.018861Z DEBUG nockapp::kernel::boot: kernel: jam buffer paths: "/home/ec2-user/.nockapp/hoonc/checkpoints/0.chkjam", "/home/ec2-user/.nockapp/hoonc/checkpoints/1.chkjam"

thread 'serf' panicked at crates/nockvm/rust/nockvm/src/mem.rs:302:23:
Box<dyn Any>
stack backtrace:
   0: std::panicking::begin_panic
             at /rustc/05f9846f893b09a1be1fc8560e33fc3c815cfecb/library/std/src/panicking.rs:767:5
   1: std::panic::panic_any
             at /rustc/05f9846f893b09a1be1fc8560e33fc3c815cfecb/library/std/src/panic.rs:259:5
   2: nockvm::mem::NockStack::new
             at ./crates/nockvm/rust/nockvm/src/mem.rs:302:23
   3: nockapp::kernel::form::SerfThread::new::{{closure}}::{{closure}}
             at ./crates/nockapp/src/kernel/form.rs:125:33
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Error initializing NockApp: OneshotChannelError(RecvError(()))
1 Like
16

how much RAM does that machine have?

17

Well, now that you mention it, less than the recommended amount. I was starting small with cheap ec2 instance types to slowly increase my vcpu quota. I’ll try with 16gb and let you know how it goes!

1 Like
18

Yeah, looks like RAM was the issue, thanks! I feel dumb

1 Like
19

no worries, hard to know that ahead of time

20

I’m getting the same mem.rs error again, but only when the miner tries to actually start mining. And this is after upgrading to 64GB of ram! Either 64GB is not actually the minimum requirement or something’s messed up on my box.

21
22

Incredible, thanks man, you’re the best! This seems to have fixed things.

1 Like