Negative held amount

node1 · October 4, 2020, 4:32am

Is this my node problem? Or something global?

Alexey · October 4, 2020, 9:02am

Could you please check it with an

node1 · October 5, 2020, 8:28am

Hello,
earnings.py also show the same negative (overpaid) amount.

Alexey · October 5, 2020, 8:49am

Then your databases got corrupted. Or you used them from the other node.

node1 · October 6, 2020, 8:45am

Screen Shot 2020-10-06 at 11.37.37 AM

I have 2nd node on the same machine, but have no idea how it could mix together and use other then needed db.

Alexey · October 6, 2020, 7:13pm

It’s enough to configure it with a wrong path once.

node1 · October 7, 2020, 7:38am

I can’t rember i’ve made such a mistake. But let’s assume i did.
Is there any way to fix it?

Alexey · October 9, 2020, 9:50pm

Let’s try to move the current version of heldamount.db to the backup and create an empty one:

Stop the storagenode
Move the heldamount.db to heldamount.db.bak
Execute either with a local installed sqlite3 or with a docker version (you can take an example from https://support.storj.io/hc/en-us/articles/360029309111), replace the /path/to with your actual path:

sqlite3 /path/to/heldamount.db

When you see a sqlite> prompt execute this script:

CREATE TABLE versions (version int, commited_at text);
CREATE TABLE paystubs (
                                                  period text NOT NULL,
                                                  satellite_id bytea NOT NULL,
                                                  created_at timestamp NOT NULL,
                                                  codes text NOT NULL,
                                                  usage_at_rest double precision NOT NULL,
                                                  usage_get bigint NOT NULL,
                                                  usage_put bigint NOT NULL,
                                                  usage_get_repair bigint NOT NULL,
                                                  usage_put_repair bigint NOT NULL,
                                                  usage_get_audit bigint NOT NULL,
                                                  comp_at_rest bigint NOT NULL,
                                                  comp_get bigint NOT NULL,
                                                  comp_put bigint NOT NULL,
                                                  comp_get_repair bigint NOT NULL,
                                                  comp_put_repair bigint NOT NULL,
                                                  comp_get_audit bigint NOT NULL,
                                                  surge_percent bigint NOT NULL,
                                                  held bigint NOT NULL,
                                                  owed bigint NOT NULL,
                                                  disposed bigint NOT NULL,
                                                  paid bigint NOT NULL,
                                                  PRIMARY KEY ( period, satellite_id )
                                );
CREATE TABLE payments (
                                                id bigserial NOT NULL,
                                                created_at timestamp NOT NULL,
                                                satellite_id bytea NOT NULL,
                                                period text,
                                                amount bigint NOT NULL,
                                                receipt text,
                                                notes text,
                                                PRIMARY KEY ( id )
                                        );
.exit

Start the storagenode
Check logs
If all ok, check the dashboard

node1 · October 14, 2020, 7:42am

Thank you, tried, but:

sqlite3 heldamount.db
SQLite version 3.29.0 2019-07-10 17:32:03
Enter “.help” for usage hints.
sqlite> CREATE TABLE versions (version int, commited_at text);
t NOT NULL,
comp_put bigint NOT NULL,
comp_get_repair bigint NOT NULL,
comp_put_repair bigint NOT NULL,
comp_get_audit bigint NOT NULL,
surge_percent bigint NOT NULL,
held bigint NOT NULL,
owed bigint NOT NULL,
disposed bigint NOT NULL,
paid bigint NOT NULL,
PRIMARY KEY ( period, satellite_id )
);
CREATE TABLE payments (
id bigserial NOT NULL,
created_at timestamp NOT NULL,
satellite_id bytea NOT NULL,
period text,
amount bigint NOT NULL,
receipt text,
notes text,
PRIMARY KEY ( id )
);
.exitsqlite> CREATE TABLE paystubs (
…> period text NOT NULL,
…> satellite_id bytea NOT NULL,
…> created_at timestamp NOT NULL,
…> codes text NOT NULL,
…> usage_at_rest double precision NOT NULL,
…> usage_get bigint NOT NULL,
…> usage_put bigint NOT NULL,
…> usage_get_repair bigint NOT NULL,
…> usage_put_repair bigint NOT NULL,
…> usage_get_audit bigint NOT NULL,
…> comp_at_rest bigint NOT NULL,
…> comp_get bigint NOT NULL,
…> comp_put bigint NOT NULL,
…> comp_get_repair bigint NOT NULL,
…> comp_put_repair bigint NOT NULL,
…> comp_get_audit bigint NOT NULL,
…> surge_percent bigint NOT NULL,
…> held bigint NOT NULL,
…> owed bigint NOT NULL,
…> disposed bigint NOT NULL,
…> paid bigint NOT NULL,
…> PRIMARY KEY ( period, satellite_id )
…> );
sqlite> CREATE TABLE payments (
…> id bigserial NOT NULL,
…> created_at timestamp NOT NULL,
…> satellite_id bytea NOT NULL,
…> period text,
…> amount bigint NOT NULL,
…> receipt text,
…> notes text,
…> PRIMARY KEY ( id )
…> );
sqlite> .exit

When restarted node, it won’t start. Logs show this:

Alexey · October 14, 2020, 8:17am

Stop the storagenode
Execute with a sqlite3

sqlite3 heldamount.db

When you see a sqlite> prompt, execute:

insert into versions select 32, datetime() where not exists(select 1 from versions where "version" = 32);
insert into versions select 33, datetime() where not exists(select 1 from versions where "version" = 33);
insert into versions select 37, datetime() where not exists(select 1 from versions where "version" = 37);
insert into versions select 43, datetime() where not exists(select 1 from versions where "version" = 43);
.exit

Start the storagenode
Check logs

node1 · October 14, 2020, 8:21am

As the first suggestion did not worked out and the node could not run at all, i’ve moved heldamaunt.db back from and restartard node. So should i do this second suggestion on the orginial (corrupted) db, or on the new one, after making a BAK?

Alexey · October 14, 2020, 8:27am

The second is solution for the error with a new empty database when the storagenode trying to apply migrations, which already applied.

node1 · October 14, 2020, 8:32am

Alexey. Node is running, log’s looks nice. I don’t have currently access to it’s web dashboard so i could not see the held amount, but will check later today, and let you know.

As always - thank you for your help! : )

P.S. Checked, everything is fine!!