Searching with the DKG client returns bad result when searching the handler id

[CosmiCloud]

Issue description

Unable to search for any keyword without getting a critical error

Expected behavior

The search result on the entity does not fault and instead tells me if there are results or not.

Actual behavior

Searching for any keyword causes the search result on the handler id to error.

Steps to reproduce the problem

1. Attempt to use dkg.search with any keyword. Console log: console log.txt

Specifications

• Node version: v6.0.0-beta.1.21
• Platform: Ubuntu
• Node wallet: 0xC3edFfF56E2BBf0B6439576938E0d8c213e0bEf6
• Node libp2p identity: QmPoKaAowLLS6cRrBUiB783hv9uqPzNhhU6TV5uJWnHwXT

Contact details

• Email:

Error logs

Node log: out.log

Disclaimer

Please be aware that the issue reported on a public repository allows everyone to see your node logs, node details, and contact details. If you have any sensitive information, feel free to share it by sending an email to [email protected].

[zeroxbt]

For more context, this is the error we get when searching for a certain keyword.

Bad request. Unexpected error at getting results: Error: File doesn't exist on file path: data/handler_id_cache/a3f24722-475b-4d4d-8744-e4f99a29aba8

[Baddooo14]

I had the same errors as zeroxbt described above. However, for me the handler_id's were the same for the publish and search action, so the correct entity was trying to be queried. It still gave the same errors though.

I reinstalled my graphDB and rebooted my VPS, which seems to have fixed the issue. I can now search (and get correct results) again.

It also doesn't seem to make sense that the node returns an error and stop the entire search process if the file has not been found. It should then query the network and create the file, or not require the file to be in the cache at all.

[Baddooo14]

Searching seems to be failing on my end again. Have not changed any settings. Keep getting error searching the network. Error: Request failed with status code 400 when searching via the dkg-client

[NZT48]

This issue is being closed as inactive due to the date of the last activity on it. If you believe this is still a problem, please create a new issue and confirm that it is reproducible in the current ot-node release version. We are working towards closing open issues that meet specific criteria and ask you to create a new one for those that that are truly bugs in current release. We'll be monitoring those issues so that they are properly managed.

Thank you, OriginTrail Team