Temporary Tron Fullnode Issue Resolved
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-shkeepersqlite3 /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-shkeeperIf you encounter any difficulties or have questions, please contact our support team for assistance.
Latest News & Announcements
-
SHKeeper Now Supports Lightning Network!
#announcementsWe are thrilled to announce the addition of Lightning Network support to SHKeeper, making transactions faster, cheaper, and more efficient than ever before! Why Use Lightning Network? Important to Note: While SHKeeper fully supports Lightning Network payments, the setup of payment channels and management...
-
External Node Capability for Monero
#announcementsWe are thrilled to announce the release of the capability to utilize an external node for Monero transactions. This powerful new feature enables users to streamline operations by reducing server requirements and optimizing the overall performance of their SHKeeper setup. Here’s What This Release Brings:...
-
Temporary Tron Fullnode Issue Resolved
#announcementsThe 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,...