Synchronizations were hard works

Tech Support
1

Environment: VirtualBox + Linux mint 22

I create two virtual linux mint machine

VA: only install grin++

VB: install tor, and grin++, wm/grin

  1. wm/grin

Sync step 1/7 was smoothly succeeded with 8 peers connecting. But in Sync step 2/7, sync stopped sometimes, so I had to quit the node and start again. After 4-5 times quitting and starting again, I finally got into step 3-7/7 and succeeded in downloading the whole blockchain.

Using grin-wallet listen command, succeeded withdraw from gate.io

2.grin++

a)got a error

(node:2440) electron: The default of contextIsolation is deprecated and will be changing from false to true in a future release of Electron. See [Discussion] Changing the defaults for nodeIntegration and contextIsolation to improve the default security posture of Electron applications · Issue #23506 · electron/electron · GitHub for more information

[2440:0107/162333.902404:FATAL:gpu_data_manager_impl_private.cc(445)] GPU process isn’t usable. Goodbye.

After google, solved by ./GrinPlusPlus-1.2.8.AppImage --no-sandbox

b)Always got waiting for peers in VB. But in VA it ran smoothly and succeeded in downloading the whole blockchain.

Using Slatepack, withdrawl and deposit with tradeorge.com all succeeded.

2 Likes
2

Didn’t use the nodes for more than a weeks.
Today start wm/grin, stuck at 2/7:99%.
So I start grin++. It Sync ¼ succeed. But it reSyn tx states from 0%, after about a hour, it reach to 99% and enter step 3/7. A few seconds later return to 2/7 with 0%.

Griners, have any suggestion.
Do I have to delete all the data everytime?

3

For grin node, just restart it if stucked. It should continue further without issues.

For grin++, it’s not maintained for quite some time and has known peering issues.

4

restart more than 10+ times.
every time get different tx state number:
21566635
21566632
21566629
21566626
21566623
21566620
21566617
look like last tx state - 3

5

That is probably to remove potential partly written data and as such avoid errors from forcefull interuptions. Did you shutdown with ‘Q’ or forced shutdown? Avoid forced shutdown. Also check the log tab. For example, if it says it cannot write to a certain file, remove the file .grin/main/chain_data/grin.lock

6

i always quit with ‘Q’, but maybe forget sometimes.

dit got error in logs, when everytime restart grin node.
WARN grin_chain::txhashset::txhashset - rewind_single_block: 1 output_pos entries missing for: 000214e0b112 at 3153136

ERROR grin_util::logger -
thread ‘sync’ panicked at ‘prune list append only - pos=16220390 bitmap.maximum=16224234’: store/src/prune_list.rs:295 0: grin_util::logger::send_panic_to_log::{{closure}}
1: std::panicking::rust_panic_with_hook
2: std::panicking::begin_panic_handler::{{closure}}
3: std::sys::backtrace::__rust_end_short_backtrace
4: rust_begin_unwind
5: core::panicking::panic_fmt
6: grin_store::prune_list::PruneList::append
7: <grin_store::pmmr::PMMRBackend as grin_core::core::pmmr::backend::Backend>::append_pruned_subtree
8: grin_core::core::pmmr::pmmr::PMMR<T,B>::push_pruned_subtree
9: grin_chain::txhashset::txhashset::Extension::apply_output_segment
10: grin_chain::txhashset::txhashset::extending
11: grin_chain::txhashset::desegmenter::Desegmenter::apply_output_segment
12: grin_chain::txhashset::desegmenter::Desegmenter::apply_next_segments
13: grin_servers::grin::sync::state_sync::StateSync::check_run
14: std::sys::backtrace::__rust_begin_short_backtrace
15: core::ops::function::FnOnce::call_once{{vtable.shim}}
16: std::sys::pal::unix::thread::thread::new::thread_start
17: start_thread
at ./nptl/pthread_create.c:447:8
18: __GI___clone3
at ./misc/…/sysdeps/unix/sysv/linux/x86_64/clone3.S:78