How to view details for error message "Bad Request" for Query API - vespa

Is there a way to see error details for debugging requests to the Query API?
I am using OkHttpClient to make POST calls to the search endpoint.
I am getting the following error message:
Bad Request
However, there are no other details in the error message returned by Vespa for trying to debug the error.
I also tried using the vespa-logfmt CLI tool, but there were no other error messages on in the server logs indicating what went wrong with the request.

Sorry, I was able to figure this out on my own. It ended up being an issue with OkHttp rather than Vespa.
I was using Response.message, but I needed to actually use Response.body().string() to see the full error output.
Apologies for the confusion.

Related

Google Error Reporting does not correlate to parent http request

I'm using Google App Engine Standard with Python 3. When i click on an error in Google Error Reporting and then click "View Logs", I get taken to Google Logs Viewer/Explorer with something like this error_group("CObpg_HTfjskb6GA") as a search filter.
I see the individual log line with the stacktrace but not any logs for the parent request for which this occurred.
In the docs, they have a screenshot where it does look like we should be able to see the parent http request in which the error occurred: https://cloud.google.com/error-reporting/docs/viewing-errors#view_associated_log_entries
Right now when I need to look into an error, I have to do a separate search in logs explorer with part of the error message (in the case of the above example I'd search for "KeyError: 'c'") to find a duplicate log that has a trace id set. Then I'd be able to 'show all logs for trace' and be able to finally see all the logs that lead up to this error.
This feels related to this other issue from before, where logs in general in python3 were not getting correlated like they were in python2: How to group related request log entries GAE python 3.7 standard env
Logs now get grouped together via trace, but as far as I can tell, I cannot set trace on error report logs.
I have my logging setup by doing:
client = google.cloud.logging.Client()
client.setup_logging()
For error reporting I was just getting error reports from google.cloud.logging's integration with the python logger:
try:
# code where an error occurs
except Exception as exc:
logging.exception(exc)
raise
I've now started trying to use google-cloud-error-reporting to see if maybe there are some options in there that I can set to get it to correlate, but I seem to only be able to set a HttpContext & ReportingLocation. There isnt a spot for me to set trace or anything like that.

delete_model() error when cleaning up AWS sagemaker

I followed the tutorial on https://aws.amazon.com/getting-started/hands-on/build-train-deploy-machine-learning-model-sagemaker/
I got an error when trying to clean up with the following code.
xgb_predictor.delete_endpoint()
xgb_predictor.delete_model()
ClientError: An error occurred (ValidationException) when calling the DescribeEndpointConfig operation: Could not find the endpoint configuration.
Does it mean I need to delete the model first instead?
I checked on the console and deleted the model manually.
No, you don't need to delete the model prior to deleting the endpoint. From the error logs looks like its not able to find the endpoint configuration. Can you verify if you are setting delete_endpoint_config to True
xgb_predictor.delete_endpoint(delete_endpoint_config=True)
Additionally, you can verify if the endpoint_config is still avaiable on the AWS console.

Wordpress PHP Warning: Error while sending QUERY packet. PID=7350

“Warning: Error while sending QUERY packet.”
I am getting this error again and again. i contact to my host and they set all configuration according to need but still getting same error and my website is not work properly because of this error.
Please let me know if you have any solution regarding this error.
Thanks

Moodle Global Search issue

I want Global Search in Moodle. I have configured Solr Server
But i am getting the below error message.
Solr client error: Unsuccessful system request : Response Code 404.
HTTP ERROR 404
Problem accessing /solr/moodle/admin/system/. Reason:
I am new to Moodle and dont know much about it.
First of all check that you installed php solr2 extension, see doc here :
https://docs.moodle.org/31/en/Global_search#How_to_install_Solr
Also to understand Moodle errors you need to enable debug, see doc here :
https://docs.moodle.org/31/en/Debugging

HTTP Error 405 Method not allowed error in admin log

I'm getting a strange error in my newly deployed application in appengine. In the error log it tells me that PageRank, TwitterBot and a couple of others. I would guess this is due to these try to get data using ajax or another async service resulting in "same origin policy"-problem.
My question is does anyone know what these bots are trying to get? For example if pagerank (google page rank I would guess) can't get any info about my application would this effect my page rank. And anyone know what the twitterbot does? And if there is away to handle to provide a proper response?
Most likely, your RequestHandlers (I'm assuming you're using python with webapp from the tags on your earlier questions) aren't implementing a method for whichever request method the bots are using. I'd guess they're HEAD requests, and you have no head() methods defined.

Resources