# Node won't start **URL:** \ **Category:** Tech Support\ **Created:** [February 14, 2020, 8:48am UTC](https://forum.grin.mw/t/node-wont-start/7060 "2020-02-14T08:48:45Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![cheshirecat](https://avatars.discourse-cdn.com/v4/letter/c/34f0e0/32.png) [@cheshirecat](https://forum.grin.mw/u/cheshirecat)\ **Post date:** [February 14, 2020, 8:48am UTC](https://forum.grin.mw/t/node-wont-start/7060/1 "2020-02-14T08:48:45Z")
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. > [@Grin Node wont start](https://forum.grin.mw/t/grin-node-wont-start/3388): > > Hi I’m unable to run node on Ubuntu 16.04 After running ‘grin’ in terminal TUI doesn’t appear instead it gets me back to prompt Logs look like this 20190127 19:57:46.848 INFO grin\_util::logger - log4rs is initialized, file level: Debug, stdout level: Warn, min. level: Debug 20190127 19:57:46.848 INFO grin - Using configuration file at /home/cakara/grin/grin-server.toml 20190127 19:57:46.848 INFO grin - This is Grin version 1.0.0 (git v1.0.0), built for x86\_64-unknown-linux-gnu by rustc 1.3… 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? ---
**Author:** ![tromp](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/tromp/32/22_2.png) [@tromp](https://forum.grin.mw/u/tromp)\ **Post date:** [February 14, 2020, 12:41pm UTC](https://forum.grin.mw/t/node-wont-start/7060/2 "2020-02-14T12:41:14Z")
Try ``` grin --help grin server --help grin server config grin server run ``` ---
**Author:** ![cheshirecat](https://avatars.discourse-cdn.com/v4/letter/c/34f0e0/32.png) [@cheshirecat](https://forum.grin.mw/u/cheshirecat)\ **Post date:** [February 14, 2020, 2:12pm UTC](https://forum.grin.mw/t/node-wont-start/7060/3 "2020-02-14T14:12:21Z")
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? ---
**Author:** ![tromp](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/tromp/32/22_2.png) [@tromp](https://forum.grin.mw/u/tromp)\ **Post date:** [February 14, 2020, 2:24pm UTC](https://forum.grin.mw/t/node-wont-start/7060/4 "2020-02-14T14:24:12Z")
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) ? ---
**Author:** ![cheshirecat](https://avatars.discourse-cdn.com/v4/letter/c/34f0e0/32.png) [@cheshirecat](https://forum.grin.mw/u/cheshirecat)\ **Post date:** [February 14, 2020, 2:48pm UTC](https://forum.grin.mw/t/node-wont-start/7060/5 "2020-02-14T14:48:04Z")
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:😁: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: > **["grin server run" log - Pastebin.com](https://pastebin.com/i8S86kGv)** > > Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time. ---
**Author:** ![tromp](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/tromp/32/22_2.png) [@tromp](https://forum.grin.mw/u/tromp)\ **Post date:** [February 14, 2020, 4:35pm UTC](https://forum.grin.mw/t/node-wont-start/7060/6 "2020-02-14T16:35:53Z")
Does this error persist if you remove the old chain data in ~/.grin/main/chain\_data/ and rerun? ---
**Author:** ![cheshirecat](https://avatars.discourse-cdn.com/v4/letter/c/34f0e0/32.png) [@cheshirecat](https://forum.grin.mw/u/cheshirecat)\ **Post date:** [February 14, 2020, 4:53pm UTC](https://forum.grin.mw/t/node-wont-start/7060/7 "2020-02-14T16:53:29Z")
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](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. ---
**Author:** ![tromp](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/tromp/32/22_2.png) [@tromp](https://forum.grin.mw/u/tromp)\ **Post date:** [February 14, 2020, 7:27pm UTC](https://forum.grin.mw/t/node-wont-start/7060/8 "2020-02-14T19:27:32Z")
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… ---
**Author:** ![cheshirecat](https://avatars.discourse-cdn.com/v4/letter/c/34f0e0/32.png) [@cheshirecat](https://forum.grin.mw/u/cheshirecat)\ **Post date:** [February 15, 2020, 3:30am UTC](https://forum.grin.mw/t/node-wont-start/7060/9 "2020-02-15T03:30:30Z")
Googling “output vs rproof MMRs different sizes” I see this thread > > > Describe the bug > I installed Grin node as usual, but the grin can't be started in my new VPS. It seems issue... 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 ---
**Author:** ![david](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/david/32/660_2.png) [@david](https://forum.grin.mw/u/david)\ **Post date:** [February 16, 2020, 9:18pm UTC](https://forum.grin.mw/t/node-wont-start/7060/10 "2020-02-16T21:18:19Z")
Usually the “Illegal instruction” error means you’ll need to build from source ---
**Author:** ![Rabinovitch](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/rabinovitch/32/1019_2.png) [@Rabinovitch](https://forum.grin.mw/u/Rabinovitch)\ **Post date:** [March 24, 2020, 3:03pm UTC](https://forum.grin.mw/t/node-wont-start/7060/11 "2020-03-24T15:03:16Z")
The same problem (can’t start the node) I met today: > 20200324 21:59:33.315 INFO grin\_util::logger - log4rs is initialized, file level: Info, stdout level: Warn, min. level: Info > 20200324 21:59:33.315 INFO grin - Using configuration file at /home/rabinovitch/Grin/grin-server.toml > 20200324 21:59:33.315 INFO grin - This is Grin version 3.1.0 (git v3.1.0), built for x86\_64-unknown-linux-gnu by rustc 1.41.0 (5e1a79984 2020-01-27). > 20200324 21:59:33.315 WARN grin::cmd::server - Starting GRIN in UI mode… > 20200324 21:59:33.315 INFO grin\_servers:😁:server - Starting server, genesis block: 40adad0aec27 > 20200324 21:59:33.315 INFO grin\_store::lmdb - Resized database from 1048576 to 134217728 > 20200324 21:59:33.363 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:1188stack backtrace: > 0: grin\_util::logger::send\_panic\_to\_log::{{closure}} > 1: std::panicking::rust\_panic\_with\_hook > at src/libstd/panicking.rs:475 > 2: rust\_begin\_unwind > at src/libstd/panicking.rs:375 > 3: core::panicking::panic\_fmt > at src/libcore/panicking.rs:84 > 4: core::result::unwrap\_failed > at src/libcore/result.rs:1188 > 5: grin::cmd::server::start\_server\_tui > 6: grin::cmd::server::server\_command > 7: grin::real\_main > 8: grin::main > 9: std::rt::lang\_start::{{closure}} > 10: std::rt::lang\_start\_internal::{{closure}} > at src/libstd/rt.rs:52 > std::panicking::try::do\_call > at src/libstd/panicking.rs:292 > 11: \_\_rust\_maybe\_catch\_panic > at src/libpanic\_unwind/lib.rs:78 > 12: std::panicking::try > at src/libstd/panicking.rs:270 > std::panic::catch\_unwind > at src/libstd/panic.rs:394 > std::rt::lang\_start\_internal > at src/libstd/rt.rs:51 > 13: main > 14: \_\_libc\_start\_main > 15: \_start ---
**Author:** ![david](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/david/32/660_2.png) [@david](https://forum.grin.mw/u/david)\ **Post date:** [March 24, 2020, 5:20pm UTC](https://forum.grin.mw/t/node-wont-start/7060/12 "2020-03-24T17:20:47Z")
You can use this version for now: [https://github.com/jaspervdm/grin/releases/tag/v3.1.1-test](https://github.com/jaspervdm/grin/releases/tag/v3.1.1-test) It’s not an official release, but it’s a more portable build of the same code. It should fix this isue, I believe. ---
**Author:** ![Rabinovitch](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/rabinovitch/32/1019_2.png) [@Rabinovitch](https://forum.grin.mw/u/Rabinovitch)\ **Post date:** [March 25, 2020, 1:30am UTC](https://forum.grin.mw/t/node-wont-start/7060/13 "2020-03-25T01:30:00Z")
No success at all. > 20200325 08:28:47.728 INFO grin\_util::logger - log4rs is initialized, file level: Info, stdout level: Warn, min. level: Info > 20200325 08:28:47.728 INFO grin - Using configuration file at /home/rabinovitch/Grin/grin-server.toml > 20200325 08:28:47.728 INFO grin - This is Grin version 4.0.0-alpha.1 (git v3.1.1-test\_no\_compat.2), built for x86\_64-unknown-linux-gnu by rustc 1.41.1 (f3e1a954d 2020-02-24). > 20200325 08:28:47.728 WARN grin::cmd::server - Starting GRIN in UI mode… > 20200325 08:28:47.728 INFO grin\_servers:😁:server - Starting server, genesis block: 40adad0aec27 > 20200325 08:28:47.728 INFO grin\_store::lmdb - Resized database from 1048576 to 134217728 > 20200325 08:28:47.817 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:1188stack backtrace: > 0: grin\_util::logger::send\_panic\_to\_log::{{closure}} > 1: std::panicking::rust\_panic\_with\_hook > at src/libstd/panicking.rs:475 > 2: rust\_begin\_unwind > at src/libstd/panicking.rs:375 > 3: core::panicking::panic\_fmt > at src/libcore/panicking.rs:84 > 4: core::result::unwrap\_failed > at src/libcore/result.rs:1188 > 5: grin::cmd::server::start\_server\_tui > 6: grin::cmd::server::server\_command > 7: grin::real\_main > 8: grin::main > 9: std::rt::lang\_start::{{closure}} > 10: std::rt::lang\_start\_internal::{{closure}} > at src/libstd/rt.rs:52 > std::panicking::try::do\_call > at src/libstd/panicking.rs:292 > 11: \_\_rust\_maybe\_catch\_panic > at src/libpanic\_unwind/lib.rs:78 > 12: std::panicking::try > at src/libstd/panicking.rs:270 > std::panic::catch\_unwind > at src/libstd/panic.rs:394 > std::rt::lang\_start\_internal > at src/libstd/rt.rs:51 > 13: main > 14: \_\_libc\_start\_main > 15: \_start