[GitHub] [apisix] liu871009243 commented on issue #8134: help request: restart apisix, then route 404
liu871009243 commented on issue #8134: URL: https://github.com/apache/apisix/issues/8134#issuecomment-1291445248 @tzssangglass Thanks for technical support. And I hava another question: I found many files named "core.xxx" in the "/usr/local/apisix" folder. They appeare when I restart apisix.  And the "core.xxx" files are binary files. Can I delete the "core.xxx" files? Can I make them no logger appeare? -- 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
[GitHub] [apisix] liu871009243 commented on issue #8134: help request: restart apisix, then route 404
liu871009243 commented on issue #8134: URL: https://github.com/apache/apisix/issues/8134#issuecomment-1288345314 > what error? @tzssangglass  -- 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
[GitHub] [apisix] liu871009243 commented on issue #8134: help request: restart apisix, then route 404
liu871009243 commented on issue #8134: URL: https://github.com/apache/apisix/issues/8134#issuecomment-1287665175 @tzssangglass @tokers Thanks for technical support for a few days. Case wanting to promote the use of ApiSix in the team, we depolyed a new Apisix cluster, and synchronous data from the old stand-alone one. Then some problems encountered. We exported the data from old ETCD, and imported them to new ETCD cluster, then the problems no longer encounter. Now I get an idea: ETCD will callback Apisix when the data change. ETCD is the publisher, and Apisix is the subscriber. Looking forward to giving correction, convenient follow-up problem positioning. - The following is our operation process. Background: A stard-alone Apisix (old Apisix) and a local ETCD (old ETCD) in a virtual machine. It runs normally for days. Tow new Apisix (Apisix1 and Apisix2) with LB, and a new ETCD cluster (new ETCD). We want to use new Apisix and ETCD insteading of old one. Step: 1. Eported the data from old ETCD, and imported them to new ETCD. Then modified old Apisix's ETCD config to new ETCD. But old Apisix started failed with some openresty error. 2. Step 1 let us guess that we can't import data to ETCD without using Apisix. Then we using Apisix admin api to import data. However, this issue appeared. 3. The comment: `the admin API will verify the data format, but the process does not guarantee that the old and new data are the same?` We retry to import data to new ETCD. Apisix1 and Apisix2 run normally even if restarting them. Guess: In Step 1, old Apisix started failed, because old Apisix don't konw new ETCD's data changes. Then the data doesn't match. In Step 3, importing data in the same way as Step 1, but the new Apisix is running with the new ETCD all the time. So new Apisix knows the data changes. -- 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
[GitHub] [apisix] liu871009243 commented on issue #8134: help request: restart apisix, then route 404
liu871009243 commented on issue #8134: URL: https://github.com/apache/apisix/issues/8134#issuecomment-1286751808 > There is no problem with the process, the admin API will verify the data format, but the process does not guarantee that the old and new data are the same? Are there any suggestions? 1. Using Apisix admin api 2. Exporting the data from old ETCD, and importing them to new ETCD cluster 3. To do... -- 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
[GitHub] [apisix] liu871009243 commented on issue #8134: help request: restart apisix, then route 404
liu871009243 commented on issue #8134: URL: https://github.com/apache/apisix/issues/8134#issuecomment-1286690492 After deploying Apisix cluster, we imported routes, upstreams and consumers from old stand-alone apisix. We wrote a python script, using apisix admin api to do it: get the resources from old apisix, and put them to new apisix cluster. Whether it will make difference. -- 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
[GitHub] [apisix] liu871009243 commented on issue #8134: help request: restart apisix, then route 404
liu871009243 commented on issue #8134: URL: https://github.com/apache/apisix/issues/8134#issuecomment-1286505675 > it has been fixed by https://github.com/apache/apisix/pull/5558, and released in APISIX v2.12.0, pls upgrade your APISIX's version. we are using version 2.13.1，if downgrading APISIX to v2.12.0，I fear of creating new problems. Is there any other solution? before deploying the apisix cluster, we have deployed stand-alone apisix and etcd without basic auth in a virtual machine. it is running normally, even if restart apisix. -- 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
[GitHub] [apisix] liu871009243 commented on issue #8134: help request: restart apisix, then route 404
liu871009243 commented on issue #8134: URL: https://github.com/apache/apisix/issues/8134#issuecomment-1286361573 our `disable_sync_configuration_during_start` option is false. For additional, we deployed an etcd cluster, and enable basic auth. And we deployed two apisix: apisix1 and apisix2 with LB. restart apisix1, apisix1 route 404, but apisix2 run normally. restart apisix2, then apisix2 route 404. we open the route in dashboard, and save it, both apisix1 and apisix2 run normally. -- 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
[GitHub] [apisix] liu871009243 commented on issue #8134: help request: restart apisix, then route 404
liu871009243 commented on issue #8134:
URL: https://github.com/apache/apisix/issues/8134#issuecomment-1285269226
when restart apisix, error.log outputs:
` 2022/10/20 17:22:40 [warn] 28536#28536: *224 [lua] jwt-laqu.lua:18:
jwt-laqu, ngx_time:1666257760, context: ngx.timer
2022/10/20 17:22:40 [warn] 28531#28531: *223 [lua] plugin.lua:223:
load_stream(): new plugins:
{"ip-restriction":true,"limit-conn":true,"mqtt-proxy":true}, context: ngx.timer
2022/10/20 17:22:40 [warn] 28536#28536: *224 [lua] plugin.lua:223:
load_stream(): new plugins:
{"ip-restriction":true,"limit-conn":true,"mqtt-proxy":true}, context: ngx.timer
2022/10/20 17:22:40 [warn] 28530#28530: *225 [lua] jwt-laqu.lua:18:
jwt-laqu, ngx_time:1666257760, context: ngx.timer
2022/10/20 17:22:40 [warn] 28530#28530: *225 [lua] plugin.lua:223:
load_stream(): new plugins:
{"ip-restriction":true,"limit-conn":true,"mqtt-proxy":true}, context: ngx.timer
2022/10/20 17:22:40 [warn] 28530#28530: *225 [lua] init.lua:297:
sync_local_conf_to_etcd(): sync local conf to etcd, context: ngx.timer`
when i access the route, no log new in the error.log.
and when i open the route in dashboard, and save it, the route get right.
and when i access it, log get right
--
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
