-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
help request: After restarting, the Apisix routing configuration does not take effect #9847
Comments
docker-compose.yml
my config.yaml
Route information obtained from the admin API
Access Results
apisix access.log
the error.log no records for this request. |
docker info
docker-compose verison
|
@ShuLian1984 Is there any error log like |
steps to reproduce: not have error.log
like 469259980801835758 is my route id |
@ShuLian1984 are you sure that the And could you please share how you restart the container? |
Nothing, only executing the route data obtained in the admin API is correct and not lost. reapply the routes, and it works again. this is OS log when I restart apisix container
|
take a look |
@ShuLian1984 Can you confirm that when you are not able to access the route, the routes are present in your etcd? You can use etcdctl to GET the keys to figure out. |
@ShuLian1984 When you are not able to access route, can you also check in the control API at |
@ShuLian1984 I also see your image tag doesn't have the suffix of distro like centos or debian. Is the image locally built or Have you tagged the original image with removed suffix? What's the distro of the image? |
I could not reproduce this issue using the docker-compose example provided here: |
I can read data through the etcd manager tool, or admin api. etcd image from
docker history
|
how to fix it? |
@ShuLian1984, we are unable to reproduce this issue. |
Thank you everyone. This issue cannot be reproduced on other servers, |
OK, I will close this issue, |
@ShuLian1984 hello, we suffered such a situation as you metioned above, when we use apisix-dashboard modify the route config, we found that in etcd, the config is the same as we modified(and the update_time is correct), but when I invoke /v1/route/{route id}, it is old config, and the update_time is very long before since I modified recently, error log like below:
` I want to know why such situation could happen, and if community has resolved it, thanks use apisix 2.15.0 etcd 3.5.0 |
After restarting, the routing rules do not take effect on a properly running apixis container, and the routing configuration information is not lost. It can be obtained through the admin API and no error messages were found in the logs.
I Need to resubmit for each route rule to take effect
apisix version
):uname -a
):openresty -V
ornginx -V
):curl http://127.0.0.1:9090/v1/server_info
):The text was updated successfully, but these errors were encountered: