Chia 1.5.1 released

With a load of NFT/CAT blx.

1 Like

I’m not into CAT/NFT stuff (yet) but for just farming there are interesting new features chia db backup and chia db validate (well, new to me at least…)

db backup creates a backup from a running node, db validate … well the name is pretty clear.
I’m installing a fresh node for trying/testing. Anybody has any experiences yet?


rich@ThinkStation-P340:~$ chia db -h
Usage: chia db [OPTIONS] COMMAND [ARGS]...

Options:
  -h, --help  Show this message and exit.

Commands:
  backup    backup the blockchain database using VACUUM INTO command
  upgrade   upgrade a v1 database to v2
  validate  validate the (v2) blockchain database. Does not verify proofs
3 Likes

Well, this is a bit disappointing… it appears 1.5.1 packages a sqlite version that’s not compatible with the new 1.5.1 db backup command :thinking: Chia release/test management as we know it…?

rich@ThinkStation-P340:~$ chia db backup --backup_file ~/Downloads/db.bak
FAILED: SQLite 3.22.0 not supported. Version needed is 3.27.0
	use '--no_indexes' option to create a backup without indexes instead.
	In case of a restore, the missing indexes will be recreated during full node startup.

Try the --no_indexes option then…

1 Like

chia db backup --no-indexes produces a 65GB file from my v2 database at 94GB…
chia db validate and chia db validate --validate-blocks both result in DATABASE IS VALID.

I stopped chia client, renamed my v2 database and copied/renamed the produced backup file to blockchain_v2_mainnet.sqlite.
Restarting chia client gives a spinning circle, I’ll let it run for long time; database needs to be re-indexed due to the --no-indexes option. There’s a single core running at 100%…


rich@ThinkStation-P340:~$ chia db backup --no_indexes --backup_file ~/Downloads/db.bak
reading from blockchain database: /home/rich/.chia/mainnet/db/blockchain_v2_mainnet.sqlite
writing to backup file: /home/rich/Downloads/db.bak


Database backup finished : /home/rich/Downloads/db.bak
rich@ThinkStation-P340:~$ chia db validate  --validate-blocks --db ~/Downloads/db.bak
opening file for reading: /home/rich/Downloads/db.bak
peak hash: edb021ecd0c79d5b1e9b0b608b186115dfd8d1f23ededa1bf89d0b50b57f8235
peak height: 2448982
traversing the full chain
0 orphaned blocks: 3258       
3258 orphaned blocks


DATABASE IS VALID: /home/rich/Downloads/db.bak

Restarting the node took some 20 minutes (I7-10700 with db on nvme disk).
During which the backup-ed&restored database file grew from 65 to 89GB, so almost at original size before backup/restore.

I think it’s a great addition to be able to backup from a running client/database with v1.5.1. We’ll have to wait for v1.5.2 for the backup to include indexes I guess;-)

3 Likes

What Ubuntu version are you running? It should be installing sqlite3 from whatever OS package is available for your distro version. 3.22.0 is the current version shipped with Ubuntu 18.04. You can now safely upgrade to Ubuntu 20.04 or 22.04 LTS versions to get the newer SQLite version needed to support this option.

1 Like

Running 20.04.04 LTS on this box, only ever have used 20.04. Think I installed .04 version from scratch.
I’ll upgrade it to 22.04 tonight, see if the newer sqlite3 version comes with it (if you say so I guess it will;-)

1 Like

Hmm, 20.04 should be getting version 3.31. Try installing this package manually? https://ubuntu.pkgs.org/20.04/ubuntu-main-amd64/sqlite3_3.31.1-4_amd64.deb.html

What version does apt-cache show sqlite3 show?

1 Like

At the moment… nothing.
I started the upgrade to 22.04 from an RDP session (xrdp), no keyboard/monitor on the system…
Not the best idea I guess, seems I’ve locked myself out.
Will start from scratch with 22.04 after hooking up keyboard/monitor.
Thanks for your replies and advice;-)

Ah bummer sorry to hear that. Yeah I’d feel a bit safer doing the upgrade over an SSH connection to the box rather than an RDP session. Good luck, hope it’s easy to recover from!

Just down loaded beta 1.5.2145.0, I’m backing up my folders to a USB drive for this one. It seems to be a big reinstall, this is the first time it said

Its installed and farming so far will keep you posted…

It was :wink:
However, as you said sqlite3 version 3.37.2-2 is default installed with Ubuntu 22.04, however the chia db backup command does not seem to recognize that version ( > the one it says is needed, 3.27…).

Below my terminal output, on freshly installed Ubuntu 22.04.

rich@rich-ThinkStation-P340:~$ chia db backup --backup_file ~/Downloads/db.bak
FAILED: SQLite 3.22.0 not supported. Version needed is 3.27.0
	use '--no_indexes' option to create a backup without indexes instead.
	In case of a restore, the missing indexes will be recreated during full node startup.

rich@rich-ThinkStation-P340:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.1 LTS
Release:	22.04
Codename:	jammy

rich@rich-ThinkStation-P340:~$ apt-cache show sqlite3
Package: sqlite3
Architecture: amd64
Version: 3.37.2-2
Multi-Arch: foreign
Priority: optional
Section: misc
Origin: Ubuntu
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: Laszlo Boszormenyi (GCS) <gcs@debian.org>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 1829
Depends: libc6 (>= 2.34), libreadline8 (>= 6.0), zlib1g (>= 1:1.2.0), libsqlite3-0 (= 3.37.2-2)
Suggests: sqlite3-doc
Filename: pool/main/s/sqlite3/sqlite3_3.37.2-2_amd64.deb
Size: 768254
MD5sum: fcc571f514a4a151ddefeca4ec388f94
SHA1: 6a2a6eb3b2006aec673177c8726617dfbdfe4966
SHA256: 36acb5bab68fef79648ba9ef3d90e97238bca23ae772cf444b144aaadc5638b8
SHA512: 0439a9e03b38b5d88d08ee47476478b9a0cdc2d20980f261181abd70f349b53730c9eaee336e847dd371884840cc512c11d24e9093de4acf02917b3cfca28c40
Homepage: https://www.sqlite.org/
Description-en: Command line interface for SQLite 3
 SQLite is a C library that implements an SQL database engine.
 Programs that link with the SQLite library can have SQL database
 access without running a separate RDBMS process.
Description-md5: 60cd5a660be500525f955c43bd7981cf

The Debian installer doesn’t include sqlite so it must be finding one on the system. Maybe from some time ago you installed a custom one or it’s finding another copy besides the OS managed version.

Try whereis sqlite3 from the command line and it’ll list every one it finds in your path.

Or, run /usr/bin/sqlite3 --version (the OS managed version) and see if that’s different than 3.22.0 which would indicate there’s an older, rogue sqlite3 binary that got installed from something.

Hopefully this is happening because of a standalone version that got installed a while back which can simply be deleted at this point.

There’s no ‘while back’ at this system, installed freshly downloaded Ubuntu 22.04.01LTS and had the installer erase and use the entire nvme.

rich@rich-ThinkStation-P340:~$ /usr/bin/sqlite3 --version
3.37.2 2022-01-06 13:25:41 872ba256cbf61d9290b571c0e6d82a20c224ca3ad82971edc46b29818d5dalt1

but still…

rich@rich-ThinkStation-P340:~$ chia db backup --backup_file ~/Downloads/db.bak
FAILED: SQLite 3.22.0 not supported. Version needed is 3.27.0
	use '--no_indexes' option to create a backup without indexes instead.
	In case of a restore, the missing indexes will be recreated during full node startup.

1.5.1 is pretty new and maybe not many have tried the new db backup command on Ubuntu yet.
No big thing because the --no_indexes option works and indexes will be recreated after restoring the backup, but I’ll keep an eye out for others that may report similar issue.
Thanks for your help!

Yeah that could be.

The version number is coming back from the Python sqlite3 object, which isn’t necessarily the same as the OS installed binary. It looks like whatever versions Python3 use has nothing to do with the installed sqlite package version. Didn’t know that!

I guess the Python distribution needs an update in order to get the newer version :frowning:

1 Like
farmer chia.plot_sync.receiver    : ERROR    reset: node_id ...

got few of new kind of log entry.

Hi, if your farm is > ~500TB do not update or you will only be able to submit ~ 500TB worth of partials to the pool.

There is a major issue w/ this one. Please wait for 1.5.2

There are a few “fixes” to what is broken w/ this update.

  1. plot a k34 and this will change your difficulty to 4 instead of 1.
  2. go to config.yaml and set outbound_rate_limit_percent to something like 999999999999999999

There are other crypto farms that are over 100k in hdds who are basically dead in the water after this update.

2 Likes

and that message was directed to whom?

This is what the quote function is for…select the text so he knows what you have… a … beef… with…or whatever

The quote is a bit hit and miss in this software

1 Like

@rallbright do you have a source for this? just asking as i have 1PB farm on spacepool and havent seen any change to number of partials and getting the expected daily payout amounts on 1.5.1 Linux.

1 Like

what about my warning message, also does it affect solo mining?