And now I'm getting the same error again.
I deleted it many times, trying to resync , delete watchman database, and still have this problem, and my node is PRE_ENABLED on my node, and other nodes listed it as WATCHDOG_EXPIRED
also I see many WATCHDOG_EXPIRED (about 24)
Just tested mine. No problem found.
ok I try to debug this..
1996fe78ce9efd7a3b6deefbcd2e120b75f850909ad8f702062a517b1cb27ae1 have problem with data:
"DataString": "[[\"trigger\",{\"event_block_height\":24600,\"payment_addresses\":\"BC99kkb2mvz6SRdAVYRsgKaoWeuYavYLUT|BNKh6Z8tKaEToFyQzcffgsR9gssjeCMZLW|BNKh6Z8tKaEToFyQzcffgsR9gssjeCMZLW|BNKh6Z8tKaEToFyQzcffgsR9gssjeCMZLW|BNKh6Z8tKaEToFyQzcffgsR9gssjeCMZLW|BNKh6Z8tKaEToFyQzcffgsR9gssjeCMZLW|BGdV31j9w9yM5CrCnsUsUyFZkwhAsDyDP3|BAqBZkMieZfES9LkVgcMmMPv3E68tZt9G8|BKPGxUJvi82hi7RA3gmPUT8a9tASjtrsMF|BP8BCkDc411a25KjsD2k9tRCWKLjGQFCGz|BAqBZkMieZfES9LkVgcMmMPv3E68tZt9G8|BB57LvFhNhYAeD8JSHTnQTmiKRYx4DkxG7|BB2BwSbDCqCqNsfc7FgWFJn4sRgnUt4tsM|BNKh6Z8tKaEToFyQzcffgsR9gssjeCMZLW\",\"payment_amounts\":\"250.0000|135000.0000|23171.0000|47203.0000|517000.0000|89320.0000|2894609.0000|867333.0000|16692.0000|312500.0000|125000.0000|186493.0000|400000.0000|42272.0000\",\"proposal_hashes\":\"8aee1d9574677f7c5030571d6244769ff17e9c1c91d3c36bcdfc883a817dc0d7|e6ff30af51064a281752a6b5fdc03bd9d2fa457af89e1a0021a93661a726c96e|664f6ebfb9de9c448f986dd266db259bf89d5b6ca1ca82af7d37eee4212a3f98|13d938defec6e110ef0df251654c544d5dc9c57cf015a1ea8bb60538899b5643|46e3ee892800b272a8fa44cf4eda13506c73c297c1bc4773a0b718e7f200b4d3|9b9b0c95d2390dcf8f6bdb3f30bb02a3bf8b8e2c83bf3ccf154cd337345e8835|23f3af5b2b93d57bb5319d6c01ec98c9b2f5ca40628311c5054841295360c679|5ec1b8496385159ae913b6341719ebab199c680305a02d87a3a69dc7b84a0563|3629e6cce8a71ade8fcd9a83e9566efce479f0a3562314aa71ae5446497e07cc|da0c60fd9de6aac40b1425aca56c200f4b0665f3196c060fe443c00061dbd4ab|fbdde6d5297525ea2f9732df0858068b1a76f953a7f3d68873c298bf5d6afd20|df3815d09091445c1ce839e7cd29f995abf117837d74525da866b51bbdb7bc16|ab354293e413459c42d52a1511d5351a7a900c2c97cd4c81b6bbf261a196d0c2|ed9ec4a65237b7d54f1766dffe39f1fb18cbc99783c3495fb927610f3c3620a1\",\"type\":2,}]]",
at end is ...\"type\":
2,}]]"
this "comma" breaking python json decoder.
ok ... I add replace to this string to fix json, but also I have many errors like this:
2018-01-02 21:53:06 Invalid Proposal name [First Prod Proposal] (does not match regex), returning False
2018-01-02 21:53:06 No proposals, cannot create an empty superblock.
2018-01-02 21:53:06 No superblock created, sorry. Returning.
this is normal ?
I today try to run first time masternode, and everythings looks ok
biblepay-cli masternode status
{
"vin": "CTxIn(COutPoint(f96df9063af005b942f5cb62844d0360567930d145bde7430c740b8a6c221fe3, 1), scriptSig=)",
"service": "137.74.0.113:40000",
"payee": "BBauqhusvhQJcjBZHgrC6r1eN5xc4DHqy7",
"status": "Masternode successfully started"
}
I don't know how to make watchman working :/
Was working in slack on this last night, and we have come to the conclusion that some nodes still contain a remnant of the bad gobject. Note that the python error you receive will definitely go away when this object is deleted:
1996fe78ce9efd7a3b6deefbcd2e120b75f850909ad8f702062a517b1cb27ae1
So please gobject vote-many 1996fe78ce9efd7a3b6deefbcd2e120b75f850909ad8f702062a517b1cb27ae1 funding no, then delete yes, then delete *.dat files except wallet.dat then resync. I believe this object is now fleeced out of the supermajority, as I see 90% of the sanctuaries are now staying in ENABLED state again. We just need to clear it out of the minority now.
I did double check that its not on any of my seed nodes also on windows - its gone.
Superblock, block 24600 coming sometime Friday, Im excited!