You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by "Dan Kirkwood (JIRA)" <ji...@apache.org> on 2017/06/09 16:56:18 UTC
[jira] [Updated] (TC-374) `systemctl stop traffic_ops` does not
kill all processes
[ https://issues.apache.org/jira/browse/TC-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Kirkwood updated TC-374:
----------------------------
Description:
not sure why it gets in this state, but traffic_ops processes sometimes get in a state where the parent process is the root (1) for many of the script/cdn workers. The init.d script doesn't stop them because they don't match the pid in `/var/run/traffic_ops.pid`.
This needs to be more robust.
Example: on my test VM, if I run this, I see multiple parent processes:
{quote}
ps -ef | grep script/cdn|grep -v root | awk '\{print $3\}' | sort -u
1
22713
29306
{quote}
was:
not sure why it gets in this state, but traffic_ops processes sometimes get in a state where the parent process is the root (1) for many of the script/cdn workers. The init.d script doesn't stop them because they don't match the pid in `/var/run/traffic_ops.pid`.
This needs to be more robust.
> `systemctl stop traffic_ops` does not kill all processes
> --------------------------------------------------------
>
> Key: TC-374
> URL: https://issues.apache.org/jira/browse/TC-374
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Ops
> Affects Versions: 2.1.0
> Reporter: Dan Kirkwood
> Fix For: 2.1.0
>
>
> not sure why it gets in this state, but traffic_ops processes sometimes get in a state where the parent process is the root (1) for many of the script/cdn workers. The init.d script doesn't stop them because they don't match the pid in `/var/run/traffic_ops.pid`.
> This needs to be more robust.
> Example: on my test VM, if I run this, I see multiple parent processes:
> {quote}
> ps -ef | grep script/cdn|grep -v root | awk '\{print $3\}' | sort -u
> 1
> 22713
> 29306
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)