[ 
https://issues.apache.org/jira/browse/YARN-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jon Bringhurst updated YARN-3344:
---------------------------------
    Description: 
Although this doesn't appear to be causing any functional issues, it is 
spamming our log files quite a bit. :)

It appears that the regex in ProcfsBasedProcessTree doesn't work for all 
/proc/<pid>/stat files.

Here's the error I'm seeing:

{noformat}
    "source_host": "asdf",
    "method": "constructProcessInfo",
    "level": "WARN",
    "message": "Unexpected: procfs stat file is not in the expected format for 
process with pid 6953"
    "file": "ProcfsBasedProcessTree.java",
    "line_number": "514",
    "class": "org.apache.hadoop.yarn.util.ProcfsBasedProcessTree",
{noformat}

And here's the basic info on process with pid 6953:

{noformat}
[asdf ~]$ cat /proc/6953/stat
6953 (python2.6 /expo) S 1871 1871 1871 0 -1 4202496 9364 1080 0 0 25 3 0 0 20 
0 1 0 144918696 205295616 5856 18446744073709551615 1 1 0 0 0 0 0 16781312 2 
18446744073709551615 0 0 17 13 0 0 0 0 0
[asdf ~]$ ps aux|grep 6953
root      6953  0.0  0.0 200484 23424 ?        S    21:44   0:00 python2.6 
/export/apps/salt/minion-scripts/module-sync.py
jbringhu 13481  0.0  0.0 105312   872 pts/0    S+   22:13   0:00 grep -i 6953
[asdf ~]$ 
{noformat}



  was:
Although this doesn't appear to be causing any functional issues, it is 
spamming our log files quite a bit. :)

It appears that the regex in ProcfsBasedProcessTree doesn't work for all 
/proc/<pid>/stat files.

Here's the error I'm seeing (sorry about the janky json formatted log message):

{noformat}
    "source_host": "asdf",
    "method": "constructProcessInfo",
    "level": "WARN",
    "message": "Unexpected: procfs stat file is not in the expected format for 
process with pid 6953"
    "file": "ProcfsBasedProcessTree.java",
    "line_number": "514",
    "class": "org.apache.hadoop.yarn.util.ProcfsBasedProcessTree",
{noformat}

And here's the basic info on process with pid 6953:

{noformat}
[asdf ~]$ cat /proc/6953/stat
6953 (python2.6 /expo) S 1871 1871 1871 0 -1 4202496 9364 1080 0 0 25 3 0 0 20 
0 1 0 144918696 205295616 5856 18446744073709551615 1 1 0 0 0 0 0 16781312 2 
18446744073709551615 0 0 17 13 0 0 0 0 0
[asdf ~]$ ps aux|grep 6953
root      6953  0.0  0.0 200484 23424 ?        S    21:44   0:00 python2.6 
/export/apps/salt/minion-scripts/module-sync.py
jbringhu 13481  0.0  0.0 105312   872 pts/0    S+   22:13   0:00 grep -i 6953
[asdf ~]$ 
{noformat}




> procfs stat file is not in the expected format warning
> ------------------------------------------------------
>
>                 Key: YARN-3344
>                 URL: https://issues.apache.org/jira/browse/YARN-3344
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: Jon Bringhurst
>
> Although this doesn't appear to be causing any functional issues, it is 
> spamming our log files quite a bit. :)
> It appears that the regex in ProcfsBasedProcessTree doesn't work for all 
> /proc/<pid>/stat files.
> Here's the error I'm seeing:
> {noformat}
>     "source_host": "asdf",
>     "method": "constructProcessInfo",
>     "level": "WARN",
>     "message": "Unexpected: procfs stat file is not in the expected format 
> for process with pid 6953"
>     "file": "ProcfsBasedProcessTree.java",
>     "line_number": "514",
>     "class": "org.apache.hadoop.yarn.util.ProcfsBasedProcessTree",
> {noformat}
> And here's the basic info on process with pid 6953:
> {noformat}
> [asdf ~]$ cat /proc/6953/stat
> 6953 (python2.6 /expo) S 1871 1871 1871 0 -1 4202496 9364 1080 0 0 25 3 0 0 
> 20 0 1 0 144918696 205295616 5856 18446744073709551615 1 1 0 0 0 0 0 16781312 
> 2 18446744073709551615 0 0 17 13 0 0 0 0 0
> [asdf ~]$ ps aux|grep 6953
> root      6953  0.0  0.0 200484 23424 ?        S    21:44   0:00 python2.6 
> /export/apps/salt/minion-scripts/module-sync.py
> jbringhu 13481  0.0  0.0 105312   872 pts/0    S+   22:13   0:00 grep -i 6953
> [asdf ~]$ 
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to