Temporary Tron Fullnode Issue Resolved

December 11, 2024

#announcements

The Tron fullnode experienced a short-term unavailability yesterday. While it is now back online, there was a period when the fullnode returned an incorrect “last block” number before eventually providing the correct one.
If SHKeeper queried the fullnode during this period of incorrect data, it may have overwritten the “last block” number in its database with the incorrect value. As a result, SHKeeper cannot automatically update to the correct block number.

Action Required

To resolve this issue, you need to manually correct the “last block” number in the database to the value recorded before the fullnode downtime. Please execute the following commands:

kubectl -n shkeeper scale --replicas=0 deploy tron-shkeeper

sqlite3 /var/lib/rancher/k3s/storage/pvc-*_shkeeper_tron-shkeeper-data/database.db 'update settings set value=67724176 where name="last_seen_block_num"'

kubectl -n shkeeper scale --replicas=1 deploy tron-shkeeper

If you encounter any difficulties or have questions, please contact our support team for assistance.