Not able to query list items by a key

Question

Hello, I am running a multichain chain node for the past 4 months, I have some data on a stream which has multiple keys added to it, today I added another key to the data, now I am not able to query with the new key although the key shows that items have been indexed using list stream keys.

 

recipt-chain-1: liststreamkeys btu pb-004002                      
{"method":"liststreamkeys","params":["btu","pb-004002"],"id":"12710784-1606038656","chain_name":"recipt-chain-1"}

[
    {
        "key" : "pb-004002",
        "items" : 1,
        "confirmed" : 0
    }
]
recipt-chain-1: liststreamkeyitems btu pb-004002
{"method":"liststreamkeyitems","params":["btu","pb-004002"],"id":"46023702-1606038690","chain_name":"recipt-chain-1"}

[
]

these are all the keys currently on the data, except for the current key I can query with all the other keys, even if I switch the position of the last three keys I am still not able to query with the new key.

  "keys" : [
            "6000f2",
            "01324D",
            "00002f-00106e",
            "pb",
            "00002f",
            "00106e",
            "22-11-2020",
            "pb-004002",
            "0013825_0014096"
        ],
     

however, if I switch the key to first place it works, Is this a bug or I am doing something wrong?

Node details:

"version" : "2.0.2",
"nodeversion" : 20002901,
"protocolversion" : 20010,

 

Thanks

Answer 1

This is indeed unexpected behavior. Would you be willing to stop the node and send us a copy of the blockchain directory, so we can take a look at what happened?

Comments

The blockchain contains some confidential data, let me check for any legal issues, if I send a video, showcasing the particular problem will that be of any help?

---

It won't help so much, we would need to look at MultiChain's files to understand what is going on. For a start you could also just post the output of decoderawtransaction for the problematic transaction, so we can examine that. You may also want to consider stopping the node then restarting with the -rescan option – this will reindex the subscribed streams.