Hello,
When I run grin via command line on ubuntu. It just go to the next line. The Grin TUI (Text-User-Interface) does not display?
Does anyone know how to fix this ?
Did you build the copy of grin that you are using yourself or did you download it? If the latter, where did you download it from?
What are the contents of ~/.grin/main/grin-server.log ? You can find these by using the command:
cat ~/.grin/main/grin-server.log
What is the model of CPU on the system?
cat /proc/cpuinfo
By default in Linux the grin executable is not available from wherever you run it so you need to call the grin directory first before running the command.
However, for future ref. you can make it run from anywhere by running the following commands in the directory to which you downloaded grin:
mkdir -p ~/grin
tar xzf grin-v1.0.0-479973573-linux-amd64.tgz -C ~/grin
echo export 'PATH=~/grin:$PATH' >> ~/.bashrc
source ~/.bashrc
Why did my post get hidden? Op wants a “tui” which I assume they mean cli
Its doesn’t sound like they got an error message, or theres a bug with the grin software it just is something they weren’t expecting so nothing impactful happens
your post was off topic. he was asking how to get the official TUI running.
it looks really cool and everyone should see it 
1 Like
Change to Debug
#whether to log to stdout
log_to_stdout = true
#log level for stdout: Error, Warning, Info, Debug, Trace
stdout_log_level = "Warning"
#whether to log to a file
log_to_file = true
#log level for file: Error, Warning, Info, Debug, Trace
file_log_level = "Info"
#log file path
log_file_path = "/root/.grin/main/grin-server.log"Shrug in for a penny in for a pound.
Op am I at least correct that your litterally typing “grin” and hitting enter?
20190227 13:27:29.590 INFO grin - This is Grin version 1.0.2 (git v1.0.2-3-gfe9fa51), built for x86_64-unknown-linux-gn$20190227 13:27:29.590 WARN grin::cmd::server - Starting GRIN in UI mode…
20190227 13:27:29.626 INFO grin_servers:
:server - Starting server, genesis block: 40adad0aec27
20190227 13:27:29.991 ERROR grin_util::logger -
thread ‘main’ panicked at 'called Result::unwrap() on an Err value: Chain(Error { inner:
Store Error: chain init load head, reason: LMDB error })’: src/libcore/result.rs:1009stack backtrace:
0: grin_util::logger::send_panic_to_log::{{closure}}::h4b7ede3e7432d241 (0x7f299268b8c0)
1: std::panicking::rust_panic_with_hook::h8cbdfe43764887be (0x7f29927c6159)
at src/libstd/panicking.rs:495
2: std::panicking::continue_panic_fmt::h3d3c5a833c00a5e1 (0x7f29927c5c01)
at src/libstd/panicking.rs:398
3: rust_begin_unwind (0x7f29927c5ae5)
at src/libstd/panicking.rs:325
4: core::panicking::panic_fmt::h4d67173bc68f6d5a (0x7f29927e241c)
at src/libcore/panicking.rs:95
5: core::result::unwrap_failed::ha3b6d28e2c27cf9e (0x7f2991f2db49)
6: grin::cmd::server::start_server::h067c5f88ceecc92f (0x7f2991f2369b)
7: grin::cmd::server::server_command::h6c6aa04c5da5fbb1 (0x7f2991f2401e)
8: grin::real_main::h2ab25ccf59433f48 (0x7f2991f7dfdc)
9: grin::main::h469d63eef75c4821 (0x7f2991f7c485)
10: std::rt::lang_start::{{closure}}::h9fb037da8f4b23ba (0x7f2991f6d092)
11: std::rt::lang_start_internal::{{closure}}::hdfc28107b5be47c9 (0x7f29927c5a82)
I rebooted the server and now it started working! : - )
It say: Current Status : Waiting for peers
?
How is your connectivity between the server and the Internet? (Server has to be able to connect to the Internet in order to connect to peers.)
If that is not the issue try closing grin (with ‘q’, always with ‘q’), renaming the ~/.grin/main/chain_data directory to something else in order to allow grin to sync the blockchain from scratch, and restarting grin.
mv ~/.grin/main/chain_data ~/.grin/main/chain_data.old
Run ‘rustup update’ in current user without sudo
hi, @dwayne
I now get the following message in my log file:
20190228 16:34:10.697 ERROR grin_servers::dandelion_monitor - dand_mon: Problem with stem phase.
20190228 16:34:10.697 ERROR grin_servers::dandelion_monitor - dand_mon: Problem with fluff phase.
I renamed the chain_data file as suggested. I also then cleared the log file to see the exact issue.
I get the following message:
20190228 17:47:09.552 ERROR grin_p2p::peers - Could not save received peer address: Store(LmdbErr(Error::Code(-30796, ‘MDB_CORRUPTED: Located page was wrong type’)))
This is the full Log file results:
20190228 18:08:12.332 INFO grin - This is Grin version 1.0.2 (git v1.0.2-3-gfe9fa51), built for x86_64-unknown-linux-gnu by rustc 1.32.0 (9fda7c223 2019-01-16).
20190228 18:08:12.333 WARN grin::cmd::server - Starting GRIN in UI mode…
20190228 18:08:12.395 INFO grin_servers::server - Starting server, genesis block: 40adad0aec27
20190228 18:08:15.342 INFO grin_servers::server - Starting rest apis at: 127.0.0.1:3413
20190228 18:08:15.595 INFO grin_api::handlers - Starting HTTP API server at 127.0.0.1:3413.
20190228 18:08:15.602 INFO grin_servers::server - Starting dandelion monitor: 127.0.0.1:3413
20190228 18:08:15.602 WARN grin_servers::server - Grin server started.
20190228 18:08:15.602 INFO grin_servers::mining::stratumserver - (Server ID: 0) Starting stratum server with edge_bits = 31, proof_size = 42
20190228 18:08:15.602 WARN grin_servers::mining::stratumserver - Stratum server started on 127.0.0.1:3416
20190228 18:08:31.787 ERROR grin_p2p::peers - Could not save received peer address: Store(LmdbErr(Error::Code(-30796, ‘MDB_CORRUPTED: Located page was wrong type’)))
20190228 18:08:31.787 ERROR grin_p2p::peers - Could not save received peer address: Store(LmdbErr(Error::Code(-30796, ‘MDB_CORRUPTED: Located page was wrong type’)))
20190228 18:08:31.787 ERROR grin_p2p::peers - Could not save received peer address: Store(LmdbErr(Error::Code(-30796, ‘MDB_CORRUPTED: Located page was wrong type’)))
RAM issue? Run an memtest
My TUI looked like this on v1.0.0. Yesterday I navigated to my grin folder and ran git pull and then cargo build --release and now it looks like this (below). Any idea how to fix this? My wallet commands are working fine
sudo sed -i -e ‘s/# en_US.UTF-8 UTF-8/en_US.UTF-8 UTF-8/’ /etc/locale.gen &&
sudo dpkg-reconfigure --frontend=noninteractive locales &&
sudo update-locale LANG=en_US.UTF-8
LANG=en_US.UTF-8
export LANG
Another person suggested this to me as well. But it didnt fix TUI. Maybe it’s important to note that the first time I compiled it failed. I went and updated all my packages and dependencies and compiled again and it worked.
Looks like this is fixed in the latest master:
Worked for me anyway
My TUI is fixed on v1.0.3