liu ming created TRAFODION-3182:
-----------------------------------

             Summary: clean useless Monitor log ERROR information
                 Key: TRAFODION-3182
                 URL: https://issues.apache.org/jira/browse/TRAFODION-3182
             Project: Apache Trafodion
          Issue Type: Improvement
            Reporter: liu ming
            Assignee: liu ming


In mornitor log, there are a lot of error messages:

2018-04-19 14:29:41,708, ERROR, MON, Node Number: 0,, PIN: 18578 , Process 
Name: $MONITOR,,, TID: 18650, Message ID: 101130601, [CRedirector::stdinFd], 
unable to obtain file info for stdin file, file=pipe:[469099]. Closing stdin 
pipe fd=59
2018-04-19 14:29:46,492, ERROR, MON, Node Number: 0,, PIN: 18578 , Process 
Name: $MONITOR,,, TID: 18650, Message ID: 101130601, [CRedirector::stdinFd], 
unable to obtain file info for stdin file, file=pipe:[469099]. Closing stdin 
pipe fd=64
2018-04-19 14:30:46,340, ERROR, MON, Node Number: 0,, PIN: 18578 , Process 
Name: $MONITOR,,, TID: 18650, Message ID: 101130601, [CRedirector::stdinFd], 
unable to obtain file info for stdin file, file=pipe:[469099]. Closing stdin 
pipe fd=67
2018-04-19 14:31:51,340, ERROR, MON, Node Number: 0,, PIN: 18578 , Process 
Name: $MONITOR,,, TID: 18650, Message ID: 101130601, [CRedirector::stdinFd], 
unable to obtain file info for stdin file, file=pipe:[498421]. Closing stdin 
pipe fd=55
2018-04-19 14:31:55,358, ERROR, MON, Node Number: 0,, PIN: 18578 , Process 
Name: $MONITOR,,, TID: 18650, Message ID: 101130601, [CRedirector::stdinFd], 
unable to obtain file info for stdin file, file=pipe:[498421]. Closing stdin 
pipe fd=59
2018-04-19 14:32:07,891, ERROR, MON, Node Number: 0,, PIN: 18578 , Process 
Name: $MONITOR,,, TID: 18650, Message ID: 101130601, [CRedirector::stdinFd], 
unable to obtain file info for stdin file, file=pipe:[500714]. Closing stdin 
pipe fd=55

 

These are harmless ERRORs, but it will flood the log file and make the 
administrator very confusing, we should remove them.

 

 

 

 

 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to