Troubleshooting Guide For Quantexa Developers
To ensure we are able to help you quickly when troubleshooting, you should follow the below steps in the order they are presented.
Following these will allow you to get resolutions and responses much faster if you end up getting to the stage where you are reaching out for support, and it will also help you to build your own knowledge to avoid further issues in future.
Check out our article Troubleshooting Guide for Quantexa Developers for a detailed step-by-step in each of the stages: independent troubleshooting, researching relevant information & reaching out for support in the appropriate channel.
Comments
-
Hi Team ,
Please find the details
Description: App-Search giving 500 error on UI and boxed error in logs
Support type: Call or Email
Version: 2.0.4
Components: App-Search
Please find the attached files & the issue with detailed way.
Debugging: App-Search , After the changes for batch in for UID attribute where data type was string and we changed it to struct after this we have tried to rebuild the app images and deployed which is not working and getting app-search 500 error on UI and in logs its grps transform error as ( Boxed Error )
"java.lang.RuntimeException: Boxed Error\n\tat com.quantexa.clustering.grpc.client.Utils$.$anonfun$transformException$1(Utils.scala:62)\n\tat scala.Option.fold(Option.scala:251)\n\tat com.quantexa.clustering.grpc.client.Utils$.transformException(Utils.scala:62)\n\tat com.quantexa.search.client.SearchClientGrpcImpl$$anon$1.onError(SearchClientGrpcImpl.scala:35)\n\tat io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:478)\n\tat io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)\n\tat io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)\n\tat io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)\n\tat io.opentracing.contrib.grpc.TracingClientInterceptor$1$2.onClose(TracingClientInterceptor.java:228)\n\tat io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:616)",
When the UDI attribute was of data type string, was everything working fine as expected?
We have restarted /rebuild all the apps like (App resolve, App Security, App Scoring, App investigate, App search, config server, etcd, explorer-ui, gateway)
After build and re-deploy all the apps restarted successfully, but when trying to get app-search functionality on Quantexa app UI then encountering error on UI and in logs and dev tool window.1Q. In your search service yaml config, please can you make sure that the search.config configuration parameter correctly points to the search "profile" to be used? I.e. this needs to match the profile given in searchDefinitions in your resolver config:
"searchDefinitions": {
"<profile>": {
"dataSources": {
...
},
"entities": {
...
}
}
}
A We have verified and the profile is same as per suggestion in search config file.2Q. Please can you also make sure that your Elasticsearch is connected? If you are in a non prod environment, you can run sudo systemctl restart elasticsearch.service in a terminal window to restart your elastic service.
A.We modified few fields in Document Data Model (DDM) as part of resolution enhancement and batch process ran fine after this change.
But Quantexa apps broke after this change since the data in elastic search have different DDM schema now.
In order to fix this (2), we recreated Quantexa App jars on top of change (1) so that Apps would also have updated DDM reflected, and deployed them. But unfortunately apps are not working.3Q. In your search service yaml config, please make sure that the search.config configuration parameter correctly points to the search "profile" to be used. I.e. this needs to match the profile given in searchDefinitions in your resolver config. (A more in depth explanation of where to locate this parameter can be found in my comment on March 19th) ::
A . We have verified and the profile is same as per suggestion in search config file.
4Q. Make sure elasticsearch is connected. If in a non prod environment, you can run sudo systemctl restart elasticsearch.service in a terminal window to restart your elastic service.
Yes we did this activity and can see elastic search is connected with application and still getting encounter with boxed error.
Please could you also:
- Share your k8s.yml file for app-search :: Attached the file
5Q. Increase logging for gateway and app-search at the following packages (please share logs with us):
logging:
level:
com.quantexa.gateway.zuul: DEBUG
org.springframework.cloud: DEBUGlogging.level.com.quantexa.gateway.service: DEBUG
logging.level.com.quantexa.security.service: DEBUG
logging.level.org.apache.http: DEBUG
logging.level.com.quantexa.gateway.auth: DEBUG
logging.level.com.quantexa.search.service: TRACEAbove logging config added for app-search.yml file, Please find the error logs .
6Q. Try disabling APM by setting tracer.elasticApm.enabled: false to ensure the issue you are facing is not related to a known bug, originally raised in this similar community post (although not known to affect the version you are using).
A.We have checked with devops team, did not find the above setting on elastic side /config side as well, could you please provide more details where exactly this setting located.Please find the attached screenshot and complete dev tools log as txt file for app-search function .
Please find the screenshots of the UI error on Dev Tools.
Please find the app search error log file in txt format.
0 -
Hi @AparnaGR
I hope you're well 😊
Please can you repost your question in the Quantexa Platform Topic to ensure it gets the support required. For more information on Quantexa's support offerings and how to raise a good support request check out our 'Support' section of the Community Library.
If you need any further guidance please let me know!
Thanks,
Sophie1
