Welcome to the Linux Foundation Forum!
ssh - execute the script remotely / File not found
cloudsuser
Posts: 7
in Command Line
ssh - execute the script remotely / File not found: ''
I am uisng amazon ec2-api-tool & ec2-ami-tool
i was unable to execute through ssh.
Getting error as
File not found: ''
The same script i can able to run directly in client machine successfully.
Through ssh i was uanble to run the script remotely
Source : myScript.sh
ec2-create-volume --size $1 --availability-zone $2
$ssh -i key.pem [email protected] ./myScript.sh 10 us-east-1a
File not found: ''
Note:
i have read write permission to my remote machine script myScript.sh
What i might have done mistake...?
0
Comments
-
You must point to the absolute position of the script on the remote machine. Currently your ssh call is looking in the root directory for your script.0
-
As you said i treid with following command,
$ssh -i key.pem [email protected]<host> -C /root/myScript.sh
Output: File not found: ''
In remote machine, $ls -rtl myScript.sh
$-rwxr--r-- 1 root root 59 May 30 12:31 myScript.sh
Source: myScript.sh
ec2-create-volume --size 10 --availability-zone us-east-1a
Note: I can able to manually execute the command "ec2-create-volume --size 10 --availability-zone us-east-1a" successfully
If i want to execute the same with ssh via script, how i should procede. Please help me on this.0 -
ssh -i key.pem [email protected]<host> -C "sh /root/myScript.sh <args>"0
-
I think mfilpot is right, you need to explain to your system how to run your script. An alternative to specifying the interpreter when you invoke the script, is to define the interpreter in the beginning of the script itself, like this:
#!/bin/sh ec2-create-volume --size 10 --availability-zone us-east-1a
If you do this, I think your command should work fine:ssh -i key.pem [email protected]<host> -C /root/myScript.sh
0 -
jabirali wrote:I think mfilpot is right, you need to explain to your system how to run your script. An alternative to specifying the interpreter when you invoke the script, is to define the interpreter in the beginning of the script itself, like this:
#!/bin/sh ec2-create-volume --size 10 --availability-zone us-east-1a
If you do this, I think your command should work fine:ssh -i key.pem [email protected]<host> -C /root/myScript.sh
I also want to note that if you are planning to add input arguments you may want to enclose the script path and arguments in quotes, although it can work without the quotes depending on the arguments.0 -
As you said i tried with following option,
1) added "#!/bin/sh" in myScript.sh
ssh -i key.pem [email protected]<host> -C "sh /root/myScript.sh"
[color=]Output: File not found: ''[/color]
2) $ssh -i key.pem [email protected]<host> -C "/bin/sh ec2-create-volume --size 10 --availability-zone us-east-1a"
Output: File not found: ''0 -
1. If you script is in the location specified then maybe ssh is not finding the specified key, either way one of the files cannot be located.
2. if ec2-create-volume is a command in $PATH then you do not need to call /bin/sh to execute it
I am leaning on the system not finding the key file that you are specifying because both command are reporting the same error.0 -
Thanks for your info.
Please note ,
1) The key is available. I can able to ssh(login) successfully with the help of key
2) ec2-create-volume is a command in $PATH
What may be the issues ?0 -
Everything seems like it should work, the only things I can think of now would be if some option is blocking you from executing scripts on the remote machine or if the user's ssh access is chrooted.0
-
Have you tried running ec2-create-volume with the full path included? I know you said it's in $PATH, but give it a whirl. I'm curious if that will work.0
-
So just for some clarification:
You are sshing from $HOST1 to $HOST2.
Obviously, your keyless auth works, however, is the script located on $HOST1 or $HOST2.
If the script isn't located on $HOST2 it won't work, once you've ssh'd over, any command you pass will be executed on $HOST2 not on $HOST1.
-Rob0 -
Another thing is that it's best practice to include the full path to the application your are running in your scripts.
#!/bin/bash
/path/to/ec2-create-volume --size 10 --availability-zone us-east-1a
The error you're seeing is probably that it cannot find the ec2-create-volume application.
If you're going to automate applications that are going to run remotely it's a good idea to define the environment variables you want for any script.
you could create a env.sh which contains PATH, etc and in every script include it.
#!/bin/bash
source /root/env.sh
/path/to/command
Check exit codes to do anything if things go wrong, and return an exit code when your script finishes.
By creating an env.sh that you can then incorporate it into all your scripts that you make afterwards and know that you've taken care of everything.
--
Patrick0
Categories
- 9K All Categories
- 15 LFX Mentorship
- 68 LFX Mentorship: Linux Kernel
- 374 Linux Foundation Boot Camps
- 233 Cloud Engineer Boot Camp
- 73 Advanced Cloud Engineer Boot Camp
- 27 DevOps Engineer Boot Camp
- 8 Cloud Native Developer Boot Camp
- 958 Training Courses
- 15 LFC110 Class Forum
- 16 LFD102 Class Forum
- 105 LFD103 Class Forum
- 5 LFD121 Class Forum
- 56 LFD201 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 19 LFD254 Class Forum
- 449 LFD259 Class Forum
- 90 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 16 LFS200 Class Forum
- 707 LFS201 Class Forum
- LFS201-JP クラス フォーラム
- 282 LFS211 Class Forum
- 50 LFS216 Class Forum
- 27 LFS241 Class Forum
- 28 LFS242 Class Forum
- 19 LFS243 Class Forum
- 6 LFS244 Class Forum
- 12 LFS250 Class Forum
- LFS250-JP クラス フォーラム
- 113 LFS253 Class Forum
- 807 LFS258 Class Forum
- 8 LFS258-JP クラス フォーラム
- 54 LFS260 Class Forum
- 81 LFS261 Class Forum
- 18 LFS262 Class Forum
- 76 LFS263 Class Forum
- 14 LFS264 Class Forum
- 10 LFS266 Class Forum
- 10 LFS267 Class Forum
- 9 LFS268 Class Forum
- 6 LFS269 Class Forum
- 182 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 191 LFW211 Class Forum
- 111 LFW212 Class Forum
- 879 Hardware
- 207 Drivers
- 74 I/O Devices
- 43 Monitors
- 115 Multimedia
- 205 Networking
- 98 Printers & Scanners
- 82 Storage
- 730 Linux Distributions
- 85 Debian
- 64 Fedora
- 12 Linux Mint
- 13 Mageia
- 22 openSUSE
- 127 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 349 Ubuntu
- 450 Linux System Administration
- 33 Cloud Computing
- 64 Command Line/Scripting
- Github systems admin projects
- 89 Linux Security
- 76 Network Management
- 105 System Management
- 45 Web Management
- 51 Mobile Computing
- 19 Android
- 19 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 501 Off Topic
- 121 Introductions
- 193 Small Talk
- 19 Study Material
- 752 Programming and Development
- 243 Kernel Development
- 475 Software Development
- 903 Software
- 247 Applications
- 178 Command Line
- 2 Compiling/Installing
- 73 Games
- 314 Installation
- 25 All In Program
- 25 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)