-
Notifications
You must be signed in to change notification settings - Fork 974
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Port is missing from log messages #925
Comments
Working on something for this, the port information is available in the response. I need to modify the method that generates the |
@andrewnclark thanks, I look forward to your PR. When I merged #782 I didn't notice the change in the log. We need to be sure to provide a unit test for that. |
Do we have any progress on this? |
I have had to roll this back to the previous version. AWS elastic search does not return this parameter. I get ErrorException: Undefined index: primary_port in The element is not present in |
@lionslair can you |
Will do some point today and post. Have to switch my local env to use the aws and do the dump. |
I am still on the rolled back version but this is the dump from the fail. But I think this was because my local host wont connect to the remote now. |
Just upgraded elasticsearch to 7.5.1 and vendor 7.4.1. This casued the same issue. This field is not included in the response and causes notices. |
I have a same problem. curl can not getprimary_port. And I found something, like this https://curl.haxx.se/libcurl/c/CURLINFO_PRIMARY_PORT.html It is say PRIMARY_POR Added in 7.21.0, so I update curl version to last, but it can not working |
@limingjundawn thanks for the update, I'll investigate more on that. |
Just tested with curl 7.60 on CentOS 6 and en 7.58 on Ubuntu 18.4 and both don't return this field and are causing notices. |
@cyrnetix I find the way to solve this problem. |
What is the last curl version? |
Why can't |
@lionslair the last version is |
That would be nice, not everyone is able to upgrade the curl version on their server. |
We just used this and updated our composer file for the mean time |
Any estimate on the release of this fix? |
This has been fixed with 7.5.1 release |
I've now had to come back to this after some time and the issue doesn't seem to be fixed:
Clearly the port is still missing from the URL. It should be: This is on |
Summary of problem or feature request
I can see that in v.7 the port has disappeared from the host. After further digging I see it's been specifically requested and fixed in #548 & #782
Perhaps it is a valid use case (although I don't really understand it), but the change seems to be causing problems elsewhere - now the port is missing from the log messages too.
Code snippet of problem
Here is an example of what is sent to the logger now:
Based on this information, I should be able to type in the terminal:
But of course this doesn't work, as it's trying to reach port 80, instead of 9200
The text was updated successfully, but these errors were encountered: