Lewisyixin opened a new issue #6401: URL: https://github.com/apache/apisix/issues/6401
### Issue description When apisix was started by the command 'apisix start', then using systemd to start apisix will cause the process to shut down. This may not be a bug exactily. But if in a production environment, one engineer starts process whth the former method, and another engineer uses systemd to execute the startup again, it may cause bad effects.  One way to avoid this problem is adding 'RemainAfterExit=yes' in apisix.service. ### Environment - apisix version (cmd: `apisix version`):2.12.1 - OS (cmd: `uname -a`): Linux apisix 3.10.0-514.26.2.el7.x86_64 #1 SMP Tue Jul 4 13:29:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux - OpenResty / Nginx version (cmd: `nginx -V` or `openresty -V`):nginx version: openresty/1.19.9.1 - etcd version, if have (cmd: run `curl http://127.0.0.1:9090/v1/server_info` to get the info from server-info API):etcd-v3.5.1 - apisix-dashboard version, if have: - the plugin runner version, if the issue is about a plugin runner (cmd: depended on the kind of runner): - luarocks version, if the issue is about installation (cmd: `luarocks --version`): ### Steps to reproduce apisix start systemctl status apisix systemctl stop apisix systemctl status apisix ### Actual result Porcess shutdown ### Error log no need ### Expected result systemctl start apisix will not cause process shutdown -- 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]
