bzp2010 opened a new pull request, #12546:
URL: https://github.com/apache/apisix/pull/12546

   ### Description
   
   If the container exits abnormally, Nginx cannot properly clean up the unix 
domain socket files it is listening on. When the container is restarted, the 
startup will fail because the files still exist, preventing the container from 
starting.  
   Therefore, we check and delete the files in the entrypoint script of the 
Docker container. This includes the conf server and event broker.
   However, this overlooks the event broker UDS file used by the stream 
subsystem, so when using TCP/UDP proxies, startup may still fail.
   
   This PR fixes the issue by checking whether the file exists and deleting it 
if it does.
   
   ### Checklist
   
   - [x] I have explained the need for this PR and the problem it solves
   - [x] I have explained the changes or the new features added to this PR
   - [ ] I have added tests corresponding to this change
   - [ ] I have updated the documentation to reflect this change
   - [x] I have verified that this change is backward compatible (If not, 
please discuss on the [APISIX mailing 
list](https://github.com/apache/apisix/tree/master#community) first)
   
   <!--
   
   Note
   
   1. Mark the PR as draft until it's ready to be reviewed.
   2. Always add/update tests for any changes unless you have a good reason.
   3. Always update the documentation to reflect the changes made in the PR.
   4. Make a new commit to resolve conversations instead of `push -f`.
   5. To resolve merge conflicts, merge master instead of rebasing.
   6. Use "request review" to notify the reviewer after making changes.
   7. Only a reviewer can mark a conversation as resolved.
   
   -->
   


-- 
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