Node won't start

I am a grin newbie. My computer is an acer c720p running galliumos 2.1, which is essentially Ubuntu 16.04 customized for the hardware.
Today I downloaded the grin v3.0.0 tar file from github and extracted it in my home folder. I also added an export PATH command in bashrc.
When I open a terminal and type “grin”, nothing happens. A new command prompt simply pops up immediately. This happens regardless of whether I am in the grin directory or elsewhere.
Searching the forum turns up a thread from one year ago with the same question.


The OP garnered a single reply, asking if there’s a grin-server.toml file anywhere.
My installation doesn’t seem to have such a file; I only see the grin file itself. Since the aforementioned thread is a year old, I don’t know if the information in it is useful, but thought that I ought to mention it.
I would really like to get my node going because I like Grin and think it’s a great coin. Is there somebody who can help?

Try

grin --help
grin server --help 
grin server config
grin server run

The config subcommand generated the .toml file and some others, e.g. /grin/chain_data/lmdb/data.mdb. But the commands “grin” or “grin server run” exit to a command prompt, as before.
Am I supposed to be doing something with the options, like specifying a port?

No; you shouldn’t need to specify any options. Can you clear the grin-server.log file, rerun and post contents here if not too long (else give link to a paste somewhere) ?

After deleting the log file contents, and then running “grin”, this is what the log file contains:

20200214 21:45:26.182 INFO grin_util::logger - log4rs is initialized, file level: Info, stdout level: Warn, min. level: Info
20200214 21:45:26.182 INFO grin - Using configuration file at /home/a/grin/grin-server.toml
20200214 21:45:26.182 INFO grin - This is Grin version 3.0.0 (git v3.0.0), built for x86_64-unknown-linux-gnu by rustc 1.39.0 (4560ea788 2019-11-04).
20200214 21:45:26.182 WARN grin::cmd::server - Starting GRIN in UI mode…
20200214 21:45:26.182 INFO grin_servers::grin::server - Starting server, genesis block: 40adad0aec27
20200214 21:45:26.183 INFO grin_store::lmdb - Resized database from 1048576 to 134217728
20200214 21:45:26.279 ERROR grin_util::logger -
thread ‘main’ panicked at 'called Result::unwrap() on an Err value: Chain(Error { inner:

Other Error: output vs rproof MMRs different sizes })’: src/libcore/result.rs:1165stack backtrace:
0: grin_util::logger::send_panic_to_log::{{closure}}::hff21834a86023c70 (0x55f22188bd21)
1: std::panicking::rust_panic_with_hook::h825f041245da8739 (0x55f2219c38ac)
at src/libstd/panicking.rs:477
2: std::panicking::continue_panic_fmt::hbe0378e33481e81b (0x55f2219c3362)
at src/libstd/panicking.rs:380
3: rust_begin_unwind (0x55f2219c3256)
at src/libstd/panicking.rs:307
4: core::panicking::panic_fmt::h527855ce0bc891f6 (0x55f2219e119a)
at src/libcore/panicking.rs:85
5: core::result::unwrap_failed::ha8b77e6004f0ba38 (0x55f2219e1297)
at src/libcore/result.rs:1165
6: grin::cmd::server::start_server_tui::h60bb15ef21638c5c (0x55f2211b5070)
7: grin::cmd::server::server_command::h489e4b6c04796d86 (0x55f2211b5c15)
8: grin::real_main::h4a47aac0e709af64 (0x55f2211e0394)
9: grin::main::h8d53dbda0218ff7d (0x55f2211deae6)
10: std::rt::lang_start::{{closure}}::h63635ad4e997182b (0x55f2211acc93)
11: std::rt::lang_start_internal::{{closure}}::ha04574f12d97cbe2 (0x55f2219c31f3)
at src/libstd/rt.rs:49
std::panicking::try::do_call::h7c2a8488f72db90c
at src/libstd/panicking.rs:292
12: __rust_maybe_catch_panic (0x55f2219c8e1a)
at src/libpanic_unwind/lib.rs:80
13: std::panicking::try::hc3a9b5da4250385d (0x55f2219c3cbd)
at src/libstd/panicking.rs:271
std::panic::catch_unwind::hf27600bf8c37809a
at src/libstd/panic.rs:394
std::rt::lang_start_internal::h409d4f2fe51133b0
at src/libstd/rt.rs:48
14: main (0x55f2211e0ab2)
15: __libc_start_main (0x7f681a428830)
16: _start (0x55f221176a39)
17: (0x0)

#################################################################

Result of the “grin server run” command:

https://pastebin.com/i8S86kGv

Does this error persist if you remove the old chain data in ~/.grin/main/chain_data/ and rerun?

I went through the entire chain_data directory structure and deleted every file (including the blockchain), while leaving the .toml file untouched and the empty folders themselves, i.e. the directory structure intact. Still doesn’t want to run. On first attempt, it says “illegal instruction” and exits to command prompt. On second attempt, it just exits to command prompt.

a@galliumos:~/grin$ grin
Illegal instruction
a@galliumos:~/grin$ grin
a@galliumos:~/grin$ grin server run
a@galliumos:~/grin$

this is the new log https://pastebin.com/YfGV8DsL

All the files that I deleted appear to have been repopulated.
By the way, the path looks a little different than what you wrote. It’s like this, with no “main” folder
/home/a/grin/chain_data/
And there is a text file, /home/a/grin/chain_data/grin.lock which is blank.

You’re running into an

Other Error: output vs rproof MMRs different sizes

That one’s unfamiliar to me. I hope someone else can shed some light on that…

Googling “output vs rproof MMRs different sizes” I see this thread


maybe this problem has something to do with chip architecture
here’s my chip info
a@galliumos:~$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 1
Core(s) per socket: 2
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 69
Model name: Intel® Celeron® 2957U @ 1.40GHz
Stepping: 1
CPU MHz: 800.000
CPU max MHz: 1400,0000
CPU min MHz: 800,0000
BogoMIPS: 2797.88
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 2048K
NUMA node0 CPU(s): 0,1
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer xsave rdrand lahf_lm abm epb tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust erms invpcid xsaveopt dtherm arat pln pts

Usually the “Illegal instruction” error means you’ll need to build from source