![]() The command that I needed to run to successfully run something similar to what you show in your screenshot was: sudo su - -c "cat /tmp/test. ![]() Then step 2 would be testing it manually with ssh and comparing the versions of this command that you get working with the options that action offers to result in a working version of the action.īut I digress. Running it on the local machine takes ssh out of the equation - which is probably step 1. I have also tried to do it in one line like this stdin, stdout, stderr ssh. It does if I try something similar on the local machine. However, when I put touch /tmp/test/ into the add extra code here to execute a command line it looks like that /tmp/test is still owned by regular user and not root. I think the command will have a problem all by itself. I haven't tried the action with/without these sudo settings so your findings would be much appreciated.Īlso, I'm taking a closer look at the command you're running (sudo su - tar -cvf abc.tar abc/). ![]() you might be able to remove that entry based on some of the other agent fields (like force tty). you know what command to use successfully via the action andī. And the purpose of running it manually is to make sure that the command works as you expect it to work without having to parse through agent logs, etc. I have verified that using the following would work for the specific that you're using in the ssh command:īut, this may only be needed while running it manually. And an overkill that your admins don't accept. First, you need to make sure that the user account you are using is part of the sudoers list, which can be verified by displaying the content of the /etc/group file. Second, changing the default for all users might be an overkill. If the sudo su command doesn't work, the issue is usually caused by two things.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |