Have this on two nodes - if I select a specif one I get the data
Also the payout info of may is completely missing (no data to display) - other month seems to be OK.
Known issue? - anyone else experiencing this - issue started with Version 1.5.2
Does your log show any error ?
Payout info for may will show up after payouts are done and reported back to the node.
Not sure why you’re not seeing anything for June. Try to refresh the page with CTRL+F5.
Reagrding the utilization graph - no errors. Just recognized that I cannot even select all satellites from drop down menu. Only after page refresh it show all sattelites but without any data. Selecting any individual satillite works.
Regarding payout: Never seen this empty page for a month. Is this behaviour new?
I would bet something is wrong with you mounted directory or the mount point. This screenshot is what I would expect from a node that is soon getting DQed and later finds out what the mistake was.
had same issue, but seems to be ok now.
good to hear - on one of two it looks now good as well here. One node still shows only data for selected single dedicated sats - but no summary. But since it gets 20Mbps currently (avail disc also shrinks) and no log issues it looks healthy - hopefully this is counted as well for payment…
I would like to suggest you to check your databases:
PS R:\StorJV3\storage> & ‘C:\Program Files\SQLite3\sqlite3.exe’ .\heldamount.db “PRAGMA integrity_check;”
ok
PS R:\StorJV3\storage> & ‘C:\Program Files\SQLite3\sqlite3.exe’ .\info.db “PRAGMA integrity_check;”
ok
PS R:\StorJV3\storage> & ‘C:\Program Files\SQLite3\sqlite3.exe’ .\notifications.db “PRAGMA integrity_check;”
ok
PS R:\StorJV3\storage> & ‘C:\Program Files\SQLite3\sqlite3.exe’ .\piece_expiration.db “PRAGMA integrity_check;”
ok
PS R:\StorJV3\storage> & ‘C:\Program Files\SQLite3\sqlite3.exe’ .\piece_spaced_used.db “PRAGMA integrity_check;”
ok
PS R:\StorJV3\storage> & ‘C:\Program Files\SQLite3\sqlite3.exe’ .\pricing.db “PRAGMA integrity_check;”
ok
PS R:\StorJV3\storage> & ‘C:\Program Files\SQLite3\sqlite3.exe’ .\reputation.db “PRAGMA integrity_check;”
ok
PS R:\StorJV3\storage> & ‘C:\Program Files\SQLite3\sqlite3.exe’ .\satellites.db “PRAGMA integrity_check;”
ok
PS R:\StorJV3\storage> & ‘C:\Program Files\SQLite3\sqlite3.exe’ .\storage_usage.db “PRAGMA integrity_check;”
ok
PS R:\StorJV3\storage> & ‘C:\Program Files\SQLite3\sqlite3.exe’ .\orders.db “PRAGMA integrity_check;”
ok
R:\StorJV3\storage> & ‘C:\Program Files\SQLite3\sqlite3.exe’ .\bandwidth.db “PRAGMA integrity_check;”
row 114 missing from index idx_bandwidth_usage_created
row 115 missing from index idx_bandwidth_usage_created
row 116 missing from index idx_bandwidth_usage_created
Error: database disk image is malformed
PS R:\StorJV3\storage> & ‘C:\Program Files\SQLite3\sqlite3.exe’ .\used_serial.db “PRAGMA integrity_check;”
row 1 missing from index idx_used_serial_
row 2 missing from index idx_used_serial_
row 3 missing from index idx_used_serial_
row 4 missing from index idx_used_serial_
row 5 missing from index idx_used_serial_
row 6 missing from index idx_used_serial_
…
row 84 missing from index idx_used_serial_
row 85 missing from index idx_used_serial_
row 86 missing from index idx_used_serial_
row 87 missing from index idx_used_serial_
row 88 missing from index idx_used_serial_
row 89 missing from index idx_used_serial_
row 90 missing from index idx_used_serial_
row 91 missing from index idx_used_serial_
row 92 missing from index idx_used_serial_
row 93 missing from index idx_used_serial_
row 94 missing from index idx_used_serial_
row 95 missing from index idx_used_serial_
wrong # of entries in index idx_used_serial_
PS R:\StorJV3\storage>
Bandwidth I assume can be ignored or not?
used_serial.db I have no idea about. Hopefully I checked all.
ah pieceinfo I missed but here it is:
PS R:\StorJV3\storage> & ‘C:\Program Files\SQLite3\sqlite3.exe’ .\pieceinfo.db “PRAGMA integrity_check;”
ok
somewhere I read used_serial can be removed so it gets recreated automatically?
here the schemas of both DBs
PS R:\StorJV3\storage> cat .\used_serial-schema.sql
CREATE TABLE used_serial_ (
satellite_id BLOB NOT NULL,
serial_number BLOB NOT NULL,
expiration TIMESTAMP NOT NULL
);
CREATE UNIQUE INDEX pk_used_serial_ ON used_serial_(satellite_id, serial_number);
CREATE INDEX idx_used_serial_ ON used_serial_(expiration);
PS R:\StorJV3\storage> cat .\bandwidth-schema.sql
CREATE TABLE bandwidth_usage (
satellite_id BLOB NOT NULL,
action INTEGER NOT NULL,
amount BIGINT NOT NULL,
created_at TIMESTAMP NOT NULL
);
CREATE TABLE bandwidth_usage_rollups (
interval_start TIMESTAMP NOT NULL,
satellite_id BLOB NOT NULL,
action INTEGER NOT NULL,
amount BIGINT NOT NULL,
PRIMARY KEY ( interval_start, satellite_id, action )
);
CREATE INDEX idx_bandwidth_usage_satellite ON bandwidth_usage(satellite_id);
CREATE INDEX idx_bandwidth_usage_created ON bandwidth_usage(created_at);The used_serial.db can be re-created, but bandwidth is better to recover. The web dashboard takes bandwidth usage exactly from the bandwidth.db
OK recreation of bandwidth DB is running
the used-serial I renamed to …_bak
I’m not sure that storagenode will recreate it itself. It doing so only when it doesn’t have any database.
So, please, re-create it manually.
nope did not so
PS R:\StorJV3\storage> & ‘C:\Program Files\SQLite3\sqlite3.exe’ .\used_serial.db
SQLite version 3.32.2 2020-06-04 12:58:43
Enter “.help” for usage hints.
sqlite> CREATE TABLE used_serial_ (satellite_id BLOB NOT NULL,serial_number BLOB NOT NULL,expiration TIMESTAMP NOT NULL);
sqlite> CREATE UNIQUE INDEX pk_used_serial_ ON used_serial_(satellite_id, serial_number);
sqlite> CREATE INDEX idx_used_serial_ ON used_serial_(expiration);
sqlite> .exit
back to normal display thanks for the hints. used_serial I just created an empty DB not restored the old data - in case I should export import the old one let me know
Doesn’t really matter. I’m now better understand a process, it used to store serials to protect from double spent:
