View Issue Details

IDProjectCategoryView StatusLast Update
0000004Timekoin ServerGeneral Issuepublic2012-06-20 16:23
ReporterKnightMB Assigned ToKnightMB  
PriorityhighSeveritymajorReproducibilityrandom
Status resolvedResolutionfixed 
Product Version1.0 
Target Version1.1Fixed in Version1.1 
Summary0000004: Malformed Attributes in Transactions can stall a Block check or repair
DescriptionIf a new (or shutdown) Timekoin server is coming online and needs to catch up with the network peers, a malformed attribute is not filtered properly. This causes Timekoin to hang with an error message that there is "too much peer conflict" many times in the logs (more than normal)
Steps To ReproduceAny server that is trying to sync up with it's peers that either gets a corrupt response or a malformed response on purpose, becomes stored in the database as "H-" or "G-" for example instead of "H" or "G".
Additional InformationThis relates to the transaction clerk module that is responsible for keeping transaction records up to date.
TagsNo tags attached.

Activities

KnightMB

2012-06-19 22:39

administrator   ~0000003

Last edited: 2012-06-19 22:41

A missing "?" in the string check was letting more than a single character bleed through. So instead of an Attribute being tagged as "T" transaction for example, it would be tagged as "T-" which when it works it way through transaction verification process fails because Timekoin thinks this is a bogus transaction ( T != T- basically) and should be ignored/deleted.

The next version will also apply a fix to the database to remove any corrupt attributes the next time Timekoin is started. This will insure that even after the new fix is applied, old, malformed attributes don't remain in the database.

Issue History

Date Modified Username Field Change
2012-06-19 21:33 KnightMB New Issue
2012-06-19 21:33 KnightMB Status new => assigned
2012-06-19 21:33 KnightMB Assigned To => KnightMB
2012-06-19 22:39 KnightMB Note Added: 0000003
2012-06-19 22:39 KnightMB Status assigned => closed
2012-06-19 22:39 KnightMB Resolution open => fixed
2012-06-19 22:39 KnightMB Fixed in Version 2.41 => 1.1
2012-06-19 22:41 KnightMB Note Edited: 0000003
2012-06-20 16:23 KnightMB Status closed => resolved