We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
查找了发现原因是auth-service的health地址监听错了,但是代码完全是按照博主的写的,不知博主是怎么让它变成up的?这个是不是和自定义了eureka的health地址有关? 我在admin里右上角显示auth-service的health地址是 http://xxx:5000/mgmt/uaa/mgmt/health,多了一个mgmt,但不知道配置错在哪里,而直接访问 http://xxx:5000/uaa/mgmt/health是可以返回health信息的,这是什么原因?求解!
The text was updated successfully, but these errors were encountered:
找到问题所在了,虽然我用的代码和博主的一样,但是我springboot和spring cloud以及springbootadmin的版本都是使用最新版本的,所以出现问题,博主的代码是没问题的。 现总结如下: 1.springboot可以使用最新版本,即1.5.10 2.spring cloud Edgware.SR1和springbootadmin 1.5.7版本冲突,可能和Edgware.SR1版本大更新有关。 3.都使用最新版的但依照博主的配置的话,auth-service会由于自定义/health路径导致springbootadmin始终读取/health路径出错,所以状态一直是“DOWN”. 希望新来的人可以从这获得一点提示,也希望博主更新一下新版本的配置,谢谢!
Sorry, something went wrong.
No branches or pull requests
查找了发现原因是auth-service的health地址监听错了,但是代码完全是按照博主的写的,不知博主是怎么让它变成up的?这个是不是和自定义了eureka的health地址有关?
我在admin里右上角显示auth-service的health地址是
http://xxx:5000/mgmt/uaa/mgmt/health,多了一个mgmt,但不知道配置错在哪里,而直接访问
http://xxx:5000/uaa/mgmt/health是可以返回health信息的,这是什么原因?求解!
The text was updated successfully, but these errors were encountered: