wklken commented on issue #9951:
URL: https://github.com/apache/apisix/issues/9951#issuecomment-1664071816

   @kingluo when we change the prefix in `config.yaml` then start the apisix, 
the execution order is `apisix start`(`prefix=/apisix`) then `apisix 
reload`(`prefix=/custom-prefix`)?  
   
   ------
   
   change the prefix in config.yaml, then docker-compose up, put a route and 
service, the `config_etcd.lua` got the events, but still 404
   
   ```
   apisix_1  | 2023/08/03 14:14:50 [info] 51#51: *16 [lua] config_etcd.lua:117: 
produce_res(): append res: {
   apisix_1  |   result = {
   apisix_1  |     events = { {
   apisix_1  |         kv = {
   apisix_1  |           create_revision = "45",
   apisix_1  |           key = "/test-apisix/routes/100",
   apisix_1  |           mod_revision = "45",
   apisix_1  |           value = {
   apisix_1  |             create_time = 1691072090,
   apisix_1  |             id = "100",
   apisix_1  |             methods = { "GET",
   apisix_1  |               <metatable> = <1>{}
   apisix_1  |             },
   apisix_1  |             priority = 0,
   apisix_1  |             service_id = "200",
   apisix_1  |             status = 1,
   apisix_1  |             update_time = 1691072090,
   apisix_1  |             uri = "/metrics"
   apisix_1  |           },
   apisix_1  |           version = "1"
   apisix_1  |         }
   apisix_1  |       },
   apisix_1  |       <metatable> = <table 1>
   apisix_1  |     },
   apisix_1  |     header = {
   apisix_1  |       cluster_id = "14841639068965178418",
   apisix_1  |       member_id = "10276657743932975437",
   apisix_1  |       raft_term = "5",
   apisix_1  |       revision = "45"
   apisix_1  |     }
   apisix_1  |   }
   apisix_1  | }, err: nil, context: ngx.timer
   ```
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to