An-DJ opened a new issue, #9571:
URL: https://github.com/apache/apisix/issues/9571

   ### Current Behavior
   
   Admin & control API ip cannot be changed and reloaded if its port is 
unchanged.
   
   ### Expected Behavior
   
   Admin & control API ip can be changed and hot reloaded successfully if its 
port is unchanged.
   
   ### Error Logs
   
   _No response_
   
   ### Steps to Reproduce
   
   Take Admin API as an example:
   
   1. Start APISIX with default configuration (Admin API ip 0.0.0.0, port 9180)
   2. Change Admin API ip to `127.0.0.1` in `conf/config.yaml`
   ```
   deployment:
     admin:
       admin_listen:
           ip: 127.0.0.1
   ```
   3. Reload APISIX configure by the command `apisix reload`
   4. Failed with error.log
   ```
   2023/05/29 19:41:49 [notice] 10743#10743: signal process started
   2023/05/29 19:41:49 [emerg] 10653#10653: bind() to 127.0.0.1:9180 failed 
(98: Address already in use)
   2023/05/29 19:41:49 [emerg] 10653#10653: bind() to 127.0.0.1:9180 failed 
(98: Address already in use)
   2023/05/29 19:41:49 [emerg] 10653#10653: bind() to 127.0.0.1:9180 failed 
(98: Address already in use)
   2023/05/29 19:41:49 [emerg] 10653#10653: bind() to 127.0.0.1:9180 failed 
(98: Address already in use)
   2023/05/29 19:41:49 [emerg] 10653#10653: bind() to 127.0.0.1:9180 failed 
(98: Address already in use)
   2023/05/29 19:41:49 [emerg] 10653#10653: still could not bind()
   
   ```
   
   ### Environment
   
   - APISIX version (run `apisix version`): 3.3.0
   - Operating system (run `uname -a`): Ubuntu 18.04
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`):  
openresty/1.21.4.1
   - etcd version, if relevant (run `curl 
http://127.0.0.1:9090/v1/server_info`):
   - APISIX Dashboard version, if relevant:
   - Plugin runner version, for issues related to plugin runners:
   - LuaRocks version, for installation issues (run `luarocks --version`):
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to