Bug 763736 (GLUSTER-2004)

Summary: Cannot run gluster comands through SSH
Product: [Community] GlusterFS Reporter: Jacob Shucart <jacob>
Component: coreAssignee: shishir gowda <sgowda>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 3.1.0CC: gluster-bugs, joe, nsathyan, vijay
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jacob Shucart 2010-10-22 12:59:51 UTC
Just so you know, I can run the command like:

[root@jacob-centos-client ~]# ssh jacobgfs31-s1 "gluster volume info distribute 2> /tmp/txt.txt"


And it works, but I shouldn't have to do that.

Comment 1 Joe Julian 2010-10-22 14:00:27 UTC
The following will also produce that error. This is an openssh client "feature".

ssh 192.168.1.4 bash -l <<EOF
> echo foo >/dev/stderr
> EOF

a reasonable workaround may be:

ssh jacobgfs31-s1 "gluster volume info distribute 2>&1"

Comment 2 Jacob Shucart 2010-10-22 15:54:37 UTC
If I login to a GlusterFS 3.1.0 server, I can do:

[root@jacobgfs31-s1 bricks]# gluster volume info distribute

Volume Name: distribute
Type: Distribute
Status: Started
Number of Bricks: 4
Transport-type: tcp
Bricks:
Brick1: jacobgfs31-s1:/data/distribute
Brick2: jacobgfs31-s2:/data/distribute
Brick3: jacobgfs31-s3:/data/distribute
Brick4: jacobgfs31-s4:/data/distribute

If I am on a remote server, and I want to run this command over SSH, I should be able to, but instead I get:

[root@jacob-centos-client ~]# ssh jacobgfs31-s1 gluster volume info distribute
gf_log_init: failed to open logfile "/dev/stderr" (No such device or address)
failed to open logfile /dev/stderr.  exiting

Are we logging things in a non-standard way?  This is all on CentOS 5.5 in bash shells.  This method for executing commands remotely is pretty common.

Comment 3 shishir gowda 2010-11-15 01:18:15 UTC

*** This bug has been marked as a duplicate of bug 2081 ***