[ https://issues.apache.org/jira/browse/CASSANDRA-13211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Shuler updated CASSANDRA-13211: --------------------------------------- Fix Version/s: (was: 2.1.x) 4.0 3.11.0 3.0.11 2.2.9 2.1.17 > Use portable stderr for java error in startup > --------------------------------------------- > > Key: CASSANDRA-13211 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13211 > Project: Cassandra > Issue Type: Bug > Reporter: Max Bowsher > Assignee: Michael Shuler > Fix For: 2.1.17, 2.2.9, 3.0.11, 3.11.0, 4.0 > > Attachments: 13211_use-portable-stderr.patch > > > The cassandra startup shell script contains this line: > echo Unable to find java executable. Check JAVA_HOME and PATH environment > variables. > /dev/stderr > The problem here is the construct "> /dev/stderr". If the user invoking > Cassandra has changed user (for example, by SSHing in as a personal user, and > then sudo-ing to an application user responsible for executing the Cassandra > daemon), then the attempt to open /dev/stderr will fail, because it will > point to a PTY node under /dev/pts/ owned by the original user. > Ultimately this leads to the real problem being masked by the confusing error > message "bash: /dev/stderr: Permission denied". > The correct technique is to replace "> /dev/stderr" with ">&2" which will > write to the already open stderr file descriptor, instead of resolving the > chain of symlinks starting at /dev/stderr, and attempting to reopen the > target by name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)