Error in SSH output.

Shell Programming and Scripting
1

Hi All,

I am using below command in a shell script.

ssh -q RemoteUser@RemoteServer "/export/sctipt/test.ksh"

It is executing succesfully but the below is the output getting displayed.

tset: standard error: Invalid argument

Can you please help me in understanding below.

  • Why that optput is comming. And basic explanation on the o/p.
  • What is the solution to avoid that.

Thanks in advance.

2

Considering the orthography in your post, are you sure you ran test or tset in lieu? That would make a serious difference.

3

Below is the complete error.

tset: standard error: Invalid argument
4

That output is appearing because you have misused the tset command. If you would show us how you invoked tset , we might be able to help you fix it.

What operating system are you using?

What shell are you using?

What terminal characteristics are you trying to set with tset ?

5

Please find the details.

$ ssh -q gcidev@nygsmartp01 "/gci/support/bin/BonyCash.ksh"
tset: standard error: Invalid argument

$ uname -a
Linux nygsmartp01 2.6.32-504.16.2.el6.x86_64 #1 SMP Tue Mar 10 17:01:00 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
$
$ tty
/dev/pts/1
6

That output is not too helpful, as it does not show the tset invocation. Yet I suspect that it is missing a terminal to output to - you might want to try the ssh -t option.

7

the cause of the problem can be in:

a. profile of the user gcidev on the server nygsmartp01
b. script BonyCash.ksh on the server nygsmartp01
c. misconfigured server nygsmartp01

from your output it is impossible to understand the problem.

Can you login on the server without executing the script?

ssh gcidev@nygsmartp01

Can you execute some other programs on the server?

ssh gcidev@nygsmartp01 "date"

Which operating system has the server?

ssh gcidev@nygsmartp01 "uname -a"
8 
$ ssh gcidev@nygsmartp01 "date"

WARNING. You have accessed a private computer system.
Unauthorized access,use,connection,or entry is not permitted
and constitutes a crime punishable by law. We reserve the
right to fully pursue criminal and civil legal penalties.
All individuals using this computer system with or without proper
authority are subject to having all their activities monitored
and recorded. Anyone using this system implicitly consents to
this monitoring. Any evidence of suspected criminal activity
revealed by such monitoring may be provided to law enforcement officials.

Fri Jul 10 07:17:52 EDT 2015
$
$
$ ssh gcidev@nygsmartp01 "uname -a"

WARNING. You have accessed a private computer system.
Unauthorized access,use,connection,or entry is not permitted
and constitutes a crime punishable by law. We reserve the
right to fully pursue criminal and civil legal penalties.
All individuals using this computer system with or without proper
authority are subject to having all their activities monitored
and recorded. Anyone using this system implicitly consents to
this monitoring. Any evidence of suspected criminal activity
revealed by such monitoring may be provided to law enforcement officials.

Linux nygsmartp01 2.6.32-504.16.2.el6.x86_64 #1 SMP Tue Mar 10 17:01:00 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
9

OK. We don't see the error when you run other commands on that server. So, that leaves us the assumption that the shell script /gci/support/bin/BonyCash.ksh on the server nygsmartp01 is incorrectly invoking tset or invoking something else that is incorrectly invoking tset .

Have you tried using the ssh -t option as RudiC suggested?

Do you think we can guess at what is wrong with the way you're using tset if you won't show us how you're using tset ? Our crystal balls aren't nearly as clear as your crystal ball. You can look at /gci/support/bin/BonyCash.ksh on nygsmartp01 in your crystal ball and show it to us (and then we can try to help you fix it); or you can continue to refuse to show us how tset is invoked and not tell us what terminal characteristics you're are trying to set with it (and you're on your own to fix it). Your choice.