Hide Forgot
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.
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"
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.
*** This bug has been marked as a duplicate of bug 2081 ***