daifuyang opened a new issue, #470:
URL: https://github.com/apache/apisix-docker/issues/470

   2023-05-30 08:41:18 nginx: [emerg] bind() to 
unix:/usr/local/apisix/conf/config_listen.sock failed (98: Address already in 
use)
   2023-05-30 08:41:19 nginx: [emerg] bind() to 
unix:/usr/local/apisix/conf/config_listen.sock failed (98: Address already in 
use)
   2023-05-30 08:41:19 nginx: [emerg] bind() to 
unix:/usr/local/apisix/conf/config_listen.sock failed (98: Address already in 
use)
   2023-05-30 08:41:20 nginx: [emerg] bind() to 
unix:/usr/local/apisix/conf/config_listen.sock failed (98: Address already in 
use)
   2023-05-30 08:41:20 nginx: [emerg] bind() to 
unix:/usr/local/apisix/conf/config_listen.sock failed (98: Address already in 
use)
   2023-05-30 08:41:21 nginx: [emerg] still could not bind()
   2023-05-30 08:42:21 
   2023-05-30 08:42:21 WARNING: using fixed Admin API token has security risk.
   2023-05-30 08:42:21 Please modify "admin_key" in conf/config.yaml .
   2023-05-30 08:42:21 
   2023-05-30 08:42:21 
   2023-05-30 08:42:22 nginx: [emerg] bind() to 
unix:/usr/local/apisix/conf/config_listen.sock failed (98: Address already in 
use)
   2023-05-30 08:42:22 nginx: [emerg] bind() to 
unix:/usr/local/apisix/conf/config_listen.sock failed (98: Address already in 
use)
   2023-05-30 08:42:23 nginx: [emerg] bind() to 
unix:/usr/local/apisix/conf/config_listen.sock failed (98: Address already in 
use)
   2023-05-30 08:42:23 nginx: [emerg] bind() to 
unix:/usr/local/apisix/conf/config_listen.sock failed (98: Address already in 
use)
   2023-05-30 08:42:24 nginx: [emerg] bind() to 
unix:/usr/local/apisix/conf/config_listen.sock failed (98: Address already in 
use)
   2023-05-30 08:42:24 nginx: [emerg] still could not bind()
   
   
![image](https://github.com/apache/apisix-docker/assets/19951467/3d00be13-73c2-4d7b-a711-f32bf59a3867)
   


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