You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2017/11/06 20:33:00 UTC
[jira] [Created] (UIMA-5639) UIMA-DUCC: Agent rogue process
detector not working
Jerry Cwiklik created UIMA-5639:
-----------------------------------
Summary: UIMA-DUCC: Agent rogue process detector not working
Key: UIMA-5639
URL: https://issues.apache.org/jira/browse/UIMA-5639
Project: UIMA
Issue Type: Bug
Components: DUCC
Reporter: Jerry Cwiklik
Assignee: Jerry Cwiklik
Fix For: 2.2.2-Ducc
Even though a user id is added to the user exclusion filter the agent keeps marking this processes as rogue.
Identified the following user to be excluded:
ducc.agent.rogue.process.user.exclusion.filter =xxxxxxxxxxxxxx
But it continues to be labeled as alien:
01 Nov 2017 17:17:12,644 INFO Agent.NodeAgent - J[N/A ] T[60] RogueProcessReaper.submitRogueProcessForKill Ducc Not Configured to Kill Rogue Proces (PID:)876 Owner:xxxxxxxxxx+. Change (or define) ducc.agent.rogue.process.reaper.script property in ducc.properties if you want rogue processes to be cleaned up.
Looks like a bug with long user names. Agent seems to truncate id's when quering the OS for user processes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)