Error while onboarding External QR codes on Diksha #158
Replies: 4 comments 17 replies
-
@samarthtrigyn You are correct. The data is not currently available in Elasticsearch for searching. To address this, please utilize the Please use |
Beta Was this translation helpful? Give feedback.
-
Hi @Krishnaj20 and @pallakartheekreddy Yes my query is closed thank you all for all the help. Also just for information to whosoever this might help, synctool is deployed on the lerning service VM and can be run mannually by going into the path "/home/learning/sync_tool" on the lerning service VM. |
Beta Was this translation helpful? Give feedback.
-
Hi @pallakartheekreddy @Krishnaj20 @AmiableAnil, curl --location 'https://dev.oci.diksha.gov.in//api/dialcode/v1/content/link' which gives me a success response But after running the above API suyccessfully I am still not ablew to search the content with the QR code. Thanks |
Beta Was this translation helpful? Give feedback.
-
HI @pallakartheekreddy, we are getting a strange issue. I ran the sync tool from the pipeline and are getting the error as shown below. We also tried to run the job manually on the server as well and get the same error. We also tried to run the job manually after removing the Log4j2Plugins.dat from the jar that was built. That time there was no error on the console however the syncing did not happen and we were not able to search the synced dial code to attach in any book. Can you point me in the right direction? What can we be missing? ok: [10.90.14.21] => { |
Beta Was this translation helpful? Give feedback.
-
Hi @vinukumar-vs @pramodkvarma @AmiableAnil As you might now on DIKSHA we are trying to onboard the QR codes generated on epaathshaala.
So in order to do that we have done the following steps:
identifier | batchcode | channel | dialcode_index | generated_on | metadata | published_on | publisher | status
------------+---------------------------+---------------------+----------------+-------------------------+----------+--------------+----------------+--------
0125CH01 | do_3138324509461872641811 | 0125196274181898243 | -1 | 2023-10-15T10:00:00.000 | null | null | NCERTPUBLISHER | Draft
*This was done mannually where the batchcode is the do_id of the content where we want to link the dialcode.
{
"request": {
"content": {
"identifier": ["do_3138324509461872641811"],
"dialcode": ["0125CH01"]
}
}
}
But got the response:
{
"id": "api.content.link",
"ver": "1.0",
"ts": "2023-10-18T06:34:53.531Z",
"params": {
"resmsgid": "72432ab0-6d80-11ee-ba46-cde7dc95c329",
"msgid": null,
"status": "failed",
"err": "ERR_DIALCODE_LINK",
"errmsg": "DIAL Code not found with id(s):[0125CH01]"
},
"responseCode": "RESOURCE_NOT_FOUND",
"result": {}
}
We also get the error on the frontend while searching for the DIAL code as "Invalid code".
Can you please guide what are we missing, Im assuming that the syncing to the ES is not triggered as the dial reserve api is not called that's what's giving the error.
If that is the case how can we trigger the search indexer job mannually?
Beta Was this translation helpful? Give feedback.
All reactions