CNCLI.SH error

image

image

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

1 Like

Checking for script updates…
thread ‘main’ panicked at ‘called Result::unwrap() on an Err value: SqliteFa ilure(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

getting same error after deleting cncli.db

never mind it seems to be working now

Looks good now

image

Does cncli.sh being out of sync affect blocks? My pool hasnt had a block in 8 epochs.

GG

image

No! It’s only about forecasting up-coming block schedules.

1 Like