I played around with linux servers all day long and then just did the exact same stuff on a macbook and it just worked. I see a CPU core working hard and my RAM usage is up. Sure I see the occasional error message from a quic connection dropping, but I don’t know if that should even alarm me. When I grep for mining-on from my logs I see this; everything looks good maybe:
cat logs | grep -a mining-on
2025-05-22T19:36:03.637735Z INFO poke{src="libp2p"}:do_poke:slam:interpret: slogger: [%mining-on 16.403.360.192.242.793.373 3.729.916.137.565.976.388 4.841.179.700.730.650.850 15.348.244.770.755.086.673 692.083.285.147.958.964]
2025-05-22T19:37:31.094231Z INFO poke{src="libp2p"}:do_poke:slam:interpret: slogger: [%mining-on 7.747.443.845.271.629.095 5.660.899.446.013.130.014 16.240.482.680.428.274.828 10.632.268.164.621.327.291 10.770.059.714.026.683.921]
2025-05-22T19:38:58.104678Z INFO poke{src="libp2p"}:do_poke:slam:interpret: slogger: [%mining-on 9.123.727.458.387.341.179 1.197.520.098.285.115.729 6.224.300.754.256.307.542 2.517.191.640.729.909.646 14.926.170.594.679.154.006]
I want to fix linux. Has anyone tried this on OpenBSD?
Do you understand Rust? If so, do you have the time to try and look at the source to understand the error messages you are seeing?
Give this a shot - it may be barbaric, apoligies if I am embarssing myself
PUBKEY="..."
sudo apt install screen #maybe you don't need this step
screen -L -dmS nocknock nockchain --mining-pubkey $PUBKEY --mine
QUERY="ERROR"
cat screenlog.0 | grep -a $QUERY #search for whatever you desire
or if you’d like to look at it in real time (without the ability to scroll back)
screen -r nocknock #cltr+a then d to detach without cancelling the processes at hand
I would like to understand your error better and to try and dig into it with you. I don’t speak too much Rust and I’ve never hooned a day in my life, but necessity drives invention.
I’ve got some hoon experience, but no rust experience. Interesting. At this point, I have refined my run command to the following. I take the make file “run-nockchain” command and modify it as follows (saves me from having to delete the socket everytime):
without the -genesis options, it fails on not having the genesis hash block, so that is needed. I’ve removed the manual peers list that everyone has been passing around, as a bunch of packets get sent to those peers but a lot of handshakes just drop. Finally, its been mentioned in other places that the --bind option causes issues for some machines (such as linux). So the end result is what you see in the image
Effectively, it stops at “kernel is in init phase, can’t do non-init command”, and then gets caught in a loop where it keeps writing to the jam file - these are likely raw byte files that interface with the urbit/hoon portions of the code. The timer is a bad thing - its like its waiting for something and it keeps resetting.
Removing --fakenet from that modified command string results in: "Error: “Must specify either --btc-username or --btc-password when using genesis_watcher or genesis_leader on livenet”
"
And just for reference, running the simple command string nockchain --mining-publkey <key> --mine
Try getting rid of this flag too maybe. I don’t think you should scrap the VPS due to this. Let’s try to find a solution. It is frustrating, but together we will mine the problem until we pool towards a solution. Many of us on linux have suffered a reduction in our power of acting, and this saddens a great vortex of beings.
Mac Minis may be the Meta, but some of us are still linux users. I beseech you stay strong in the struggle.
I may have a working(as far as I, a dumb creature unworthy of claiming actual knowledge, am aware presently) mac in my lap, but I plan to run Nockchain from linux in the long run (maybe even OpenBSD/FreeBSD if Dependency Gehenna is not too deep)
