[jira] [Commented] (HIVE-16769) Possible hive service startup due to the existing file /tmp/stderr

["Naveen Gangam (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032969#comment-16032969 ] 

Naveen Gangam commented on HIVE-16769:
--------------------------------------

[~aihuaxu] I think I understand what you are trying to do. So the output to STDERR from the java process/command will be redirected to the console/shell running this bash script which can then be redirected (to file overwriting or appending) at the user's discretion. However, I am not certain a shell will let you redirect  that output to a file. Can you show output from any tests you may have run? Thanks

> Possible hive service startup due to the existing file /tmp/stderr
> ------------------------------------------------------------------
>
>                 Key: HIVE-16769
>                 URL: https://issues.apache.org/jira/browse/HIVE-16769
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive
>    Affects Versions: 2.0.0
>            Reporter: Aihua Xu
>            Assignee: Aihua Xu
>         Attachments: HIVE-16769.1.patch, HIVE-16769.2.patch
>
>
> HIVE-12497 prints the ignoring errors from hadoop version, hbase mapredcp and hadoop jars to /tmp/$USER/stderr. 
> In some cases $USER is not set, then the file becomes /tmp/stderr.  If  such file preexists with different permission, it will cause the service startup to fail.
> I just tried the script without outputting to stderr file, I don't see such error any more {{"ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console."}}.
> I think we can remove such redirect to avoid possible startup failure.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)