[SOLVED] Problem restarting service via ssh

[humbletech99]

I am trying to ssh into a server to fix it. When I ssh in I can restart the rsyncd dameon just fine via the command

Code: Select all

/etc/init.d/rsyncd restart

But I am trying to do this from a central location via ssh in a script like so

Code: Select all

ssh root@hostname "/etc/init.d/rsyncd restart"
 * Starting rsyncd ...@RSYNCD: 29

@ERROR: protocol startup error
                                                    [ !! ]

and this always fails!

I can't get this to work or even understand why it doesn't. There aren't a lot of env vars in the shell and the script uses only one which shouldn't matter at all if it's present or not (it's at the end of the line so if it's blank it's ok)

Can anybody help out on this?

[xoomix]

Works fine for me without the quotes like so:

ssh root@hostname.com /etc/init.d/rsyncd restart


/shrug

Maybe a previous line in your script is horking something up?

[James Wells]

Greetings,

There aren't a lot of env vars in the shell and the script uses only one which shouldn't matter at all if it's present or not (it's at the end of the line so if it's blank it's ok)

Right off the bat, this sounds like the issue. When you use ssh for remote execution like that, the remote shell will not read in the users environment, as such, if you require these variables be set, which you make it sound as being required, it will fail unless you force it to read those envrionment settings.

[Will Scarlet]

I find it important when writing scripts to try using the commands within the script from command line. This way you know if the command will even work. Of course there are exceptions to this rule, like branch logic (ie if, case, while, etc...).

Anyway after trying your command from the command line and from within a script, I found that the command works. So, I'm in agreeance with xoomix and James Wells in that something is not right with your script

Hope this helps...

[humbletech99]

I've just tried it without quotes as well. same result.

I've added a command to the ssh string which shows all set vars. This is what the ssh has:

Code: Select all

BASH=/bin/bash
BASH_ARGC=()
BASH_ARGV=()
BASH_EXECUTION_STRING='set ; /etc/init.d/rsyncd restart'
BASH_LINENO=()
BASH_SOURCE=()
BASH_VERSINFO=([0]="3" [1]="1" [2]="16" [3]="1" [4]="release" [5]="i686-pc-linux-gnu")
BASH_VERSION='3.1.16(1)-release'
DIRSTACK=()
EUID=0
GROUPS=()
HOME=/root
HOSTNAME=somename
HOSTTYPE=i686
IFS=$' \t\n'
LOGNAME=root
MACHTYPE=i686-pc-linux-gnu
MAIL=/var/mail/root
OPTERR=1
OPTIND=1
OSTYPE=linux-gnu
PATH=/usr/bin:/bin:/usr/sbin:/sbin
PPID=21531
PS4='+ '
PWD=/root
SHELL=/bin/bash
SHELLOPTS=braceexpand:hashall:interactive-comments
SHLVL=1
SSH_CLIENT='x.x.x.x 53821 22'
SSH_CONNECTION='x.x.x.x 53821 x.x.x.x 22'
TERM=dumb
UID=0
USER=root
_=bash

and here is what I get from a full ssh shell session

Code: Select all

BASH=/bin/bash
BASH_ARGC=()
BASH_ARGV=()
BASH_LINENO=()
BASH_SOURCE=()
BASH_VERSINFO=([0]="3" [1]="1" [2]="16" [3]="1" [4]="release" [5]="i686-pc-linux-gnu")
BASH_VERSION='3.1.16(1)-release'
COLUMNS=182
CONFIG_PROTECT_MASK='/etc/terminfo /etc/revdep-rebuild'
CVS_RSH=ssh
DIRSTACK=()
EDITOR=/usr/bin/vim
EUID=0
GCC_SPECS=
GROUPS=()
HISTFILE=/root/.bash_history
HISTFILESIZE=500
HISTSIZE=500
HOME=/root
HOSTNAME=somename
HOSTTYPE=i686
IFS=$' \t\n'
INFOPATH=/usr/share/info:/usr/share/binutils-data/i686-pc-linux-gnu/2.16.1/info::/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/info:/usr/share/info/emacs-21
LESS='-R -M --shift 5'
LESSOPEN='|lesspipe.sh %s'
LINES=69
LOGNAME=root
MACHTYPE=i686-pc-linux-gnu
MAIL=/var/mail/root
MAILCHECK=60
MANPATH=/usr/local/share/man:/usr/share/man:/usr/share/binutils-data/i686-pc-linux-gnu/2.16.1/man::/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/man
OPTERR=1
OPTIND=1
OSTYPE=linux-gnu
PAGER=/usr/bin/less
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/4.1.1:/usr/i686-pc-linux-gnu/gcc-bin/4.1.1
PIPESTATUS=([0]="0" [1]="0")
PPID=18490
PS1='\[\033[01;31m\]\h\[\033[01;34m\] \W \$\[\033[00m\] '
PS2='> '
PS4='+ '
PWD=/root
PYTHONPATH=/usr/lib/portage/pym
SHELL=/bin/bash
SHELLOPTS=braceexpand:emacs:hashall:histexpand:history:interactive-comments:monitor
SHLVL=1
SSH_CLIENT='x.x.x.x 55991 22'
SSH_CONNECTION='x.x.x.x 55991 x.x.x.x 22'
SSH_TTY=/dev/pts/1
TERM=rxvt
UID=0
USER=root
_=

[Will Scarlet]

After further research, I found a computer I have that has this issue on. I haven't found the differences as of yet, but I'm still looking.

In the mean time I found this option for ssh:

-t Force pseudo-tty allocation. This can be used to execute arbitrary screen-
based programs on a remote machine, which can be very useful, e.g. when
implementing menu services. Multiple -t options force tty allocation, even
if ssh has no local tty

And it worked quite well.

Something else I found is I can restart many different services from that computer with ssh without issue. In fact rsyncd is the only service tested that has the issue. I find that very odd.

Hope this helps...

[humbletech99]

this did indeed fix it. Thanks!