| 2021-02-15 20:21:33 |
Rajat Jain |
description |
Issue:
When I stop designate-api service, its children workers does not get killed. It left orphaned. Same issue with designate-central and designate-worker.
Analysis:
Before Stopping service:
----------------------
```
ps -fe | grep designate-api
designa+ 2722054 1 0 17:45 ? 00:01:31 /usr/bin/python3 /usr/bin/designate-api --config-file /etc/designate/designate.conf --log-file /var/log/designate/api.log
designa+ 2722102 2722054 0 17:45 ? 00:00:03 /usr/bin/python3 /usr/bin/designate-api --config-file /etc/designate/designate.conf --log-file /var/log/designate/api.log
designa+ 2722103 2722054 0 17:45 ? 00:00:02 /usr/bin/python3 /usr/bin/designate-api --config-file /etc/designate/designate.conf --log-file /var/log/designate/api.log
```
It shows that there is one main process and 2 child process of designate-api working.
```
ss -tunlp | grep 9001
tcp LISTEN 0 128 0.0.0.0:9001 0.0.0.0:* users:(("designate-api",pid=2722103,fd=8),("designate-api",pid=2722103,fd=5),("designate-api",pid=2722102,fd=8),("designate-api",pid=2722102,fd=5),("designate-api",pid=2722054,fd=5))
```
After stopping service:
---------------------
systemctl stop designate-api
```
ps -fe | grep designate-api
designa+ 2722102 1 0 17:45 ? 00:00:03 /usr/bin/python3 /usr/bin/designate-api --config-file /etc/designate/designate.conf --log-file /var/log/designate/api.log
designa+ 2722103 1 0 17:45 ? 00:00:02 /usr/bin/python3 /usr/bin/designate-api --config-file /etc
```
We can see that child workers become orphaned. It does not get killed.
Server is still listening on port 9001.
ss -tunlp | grep 9001
tcp LISTEN 17 128 0.0.0.0:9001 0.0.0.0:* users:(("designate-api",pid=2722103,fd=5),("designate-api",pid=2722102,fd=5)) |
Issue:
When I stop designate-api service, its children workers does not get killed. It left orphaned. Same issue with designate-central and designate-worker.
Analysis:
Before Stopping service:
----------------------
```
ps -fe | grep designate-api
designa+ 2722054 1 0 17:45 ? 00:01:31 /usr/bin/python3 /usr/bin/designate-api --config-file /etc/designate/designate.conf --log-file /var/log/designate/api.log
designa+ 2722102 2722054 0 17:45 ? 00:00:03 /usr/bin/python3 /usr/bin/designate-api --config-file /etc/designate/designate.conf --log-file /var/log/designate/api.log
designa+ 2722103 2722054 0 17:45 ? 00:00:02 /usr/bin/python3 /usr/bin/designate-api --config-file /etc/designate/designate.conf --log-file /var/log/designate/api.log
```
It shows that there is one main process and 2 child process of designate-api working.
```
ss -tunlp | grep 9001
tcp LISTEN 0 128 0.0.0.0:9001 0.0.0.0:* users:(("designate-api",pid=2722103,fd=8),("designate-api",pid=2722103,fd=5),("designate-api",pid=2722102,fd=8),("designate-api",pid=2722102,fd=5),("designate-api",pid=2722054,fd=5))
```
After stopping service:
---------------------
systemctl stop designate-api
```
ps -fe | grep designate-api
designa+ 2722102 1 0 17:45 ? 00:00:03 /usr/bin/python3 /usr/bin/designate-api --config-file /etc/designate/designate.conf --log-file /var/log/designate/api.log
designa+ 2722103 1 0 17:45 ? 00:00:02 /usr/bin/python3 /usr/bin/designate-api --config-file /etc
```
We can see that child workers become orphaned. It does not get killed.
Server is still listening on port 9001.
ss -tunlp | grep 9001
tcp LISTEN 17 128 0.0.0.0:9001 0.0.0.0:* users:(("designate-api",pid=2722103,fd=5),("designate-api",pid=2722102,fd=5))
Environment Openstack / Designate version - Stable/Train |
|
