hi,
Type sudo systemctl | grep cncli
and check the status of cncli sync service with sudo systemctl status
Cheers,
Checking for script updatesā¦
thread āmainā panicked at ācalled Result::unwrap()
on an Err
value: SqliteFailure(Error { code: DatabaseBusy, extended_code: 5 }, Some(ādatabase is lockedā))ā, src/nodeclient/sync.rs:407:65
note: run with RUST_BACKTRACE=1
environment variable to display a backtrace
can you check output? still no access
I believe is something related with the db from guild-db folder. Can u restart/stop/start the service or try to sync it manually with ./cncli.sh sync
./cncli.sh sync
gives me this output:
Checking for script updatesā¦
thread āmainā panicked at ācalled Result::unwrap()
on an Err
value: SqliteFailure(Error { code: DatabaseBusy, extended_code: 5 }, Some(ādatabase is lockedā))ā, src/nodeclient/sync.rs:407:65
note: run with RUST_BACKTRACE=1
environment variable to display a backtrace
I donāt have this problem on my relay.
then u can delete the cncli db and resync it again⦠inside guild-db folder u should have the cncli db⦠delete it and try to re-sync
Checking for script updatesā¦
thread āmainā panicked at ācalledResult::unwrap()
on anErr
value: SqliteFa ilure(Error { code: DatabaseBusy, extended_code: 5 }, Some(ādatabase is lockedā) )ā, src/nodeclient/sync.rs:407:65
note: run withRUST_BACKTRACE=1
environment variable to display a backtrace
getting same error after deleting cncli.db
never mind it seems to be working now
Looks good now
Does cncli.sh being out of sync affect blocks? My pool hasnt had a block in 8 epochs.
GG
No! Itās only about forecasting up-coming block schedules.