unable to run command as sudo in php (CentOS 7)

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












I need to run a sudo command from a PHP script in CentOS 7, but I am getting an error:




sudo: no tty present and no askpass program specified




I have edited my sudoers file with the following lines, as others have advised:




  1. don't require tty:



    Defaults:apache !requiretty




  2. Set no password for apache user:



    apache  ALL=(root) NOPASSWD: /path/to/app, /path/to/app2



(I have double-checked that these paths are correct). My errors persist. Any thoughts?






centos sudo php







share|improve this question



















  • 1




    Is that the only sudoers line for apache? Could it be hitting another rule?
    – Jeff Schaller
    Sep 25 at 20:17










  • It is the only line, yes
    – Michael Riordan
    Sep 26 at 8:46










  • You would better find another way of doing that. Apache has another user for security reasons, giving sudo to Apache is a very bad idea.
    – Rui F Ribeiro
    Sep 26 at 11:39










  • apache = NOPASSWD: /path/2/app, /path/2/app2 could you try this?
    – Diogo Jesus
    Sep 26 at 12:17














up vote
0
down vote

favorite












I need to run a sudo command from a PHP script in CentOS 7, but I am getting an error:




sudo: no tty present and no askpass program specified




I have edited my sudoers file with the following lines, as others have advised:




  1. don't require tty:



    Defaults:apache !requiretty




  2. Set no password for apache user:



    apache  ALL=(root) NOPASSWD: /path/to/app, /path/to/app2



(I have double-checked that these paths are correct). My errors persist. Any thoughts?






centos sudo php







share|improve this question



















  • 1




    Is that the only sudoers line for apache? Could it be hitting another rule?
    – Jeff Schaller
    Sep 25 at 20:17










  • It is the only line, yes
    – Michael Riordan
    Sep 26 at 8:46










  • You would better find another way of doing that. Apache has another user for security reasons, giving sudo to Apache is a very bad idea.
    – Rui F Ribeiro
    Sep 26 at 11:39










  • apache = NOPASSWD: /path/2/app, /path/2/app2 could you try this?
    – Diogo Jesus
    Sep 26 at 12:17












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I need to run a sudo command from a PHP script in CentOS 7, but I am getting an error:




sudo: no tty present and no askpass program specified




I have edited my sudoers file with the following lines, as others have advised:




  1. don't require tty:



    Defaults:apache !requiretty




  2. Set no password for apache user:



    apache  ALL=(root) NOPASSWD: /path/to/app, /path/to/app2



(I have double-checked that these paths are correct). My errors persist. Any thoughts?






centos sudo php







share|improve this question















I need to run a sudo command from a PHP script in CentOS 7, but I am getting an error:




sudo: no tty present and no askpass program specified




I have edited my sudoers file with the following lines, as others have advised:




  1. don't require tty:



    Defaults:apache !requiretty




  2. Set no password for apache user:



    apache  ALL=(root) NOPASSWD: /path/to/app, /path/to/app2



(I have double-checked that these paths are correct). My errors persist. Any thoughts?






centos sudo php




centos sudo php






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Sep 26 at 8:38

























asked Sep 25 at 19:29









Michael Riordan

386




386







  • 1




    Is that the only sudoers line for apache? Could it be hitting another rule?
    – Jeff Schaller
    Sep 25 at 20:17










  • It is the only line, yes
    – Michael Riordan
    Sep 26 at 8:46










  • You would better find another way of doing that. Apache has another user for security reasons, giving sudo to Apache is a very bad idea.
    – Rui F Ribeiro
    Sep 26 at 11:39










  • apache = NOPASSWD: /path/2/app, /path/2/app2 could you try this?
    – Diogo Jesus
    Sep 26 at 12:17












  • 1




    Is that the only sudoers line for apache? Could it be hitting another rule?
    – Jeff Schaller
    Sep 25 at 20:17










  • It is the only line, yes
    – Michael Riordan
    Sep 26 at 8:46










  • You would better find another way of doing that. Apache has another user for security reasons, giving sudo to Apache is a very bad idea.
    – Rui F Ribeiro
    Sep 26 at 11:39










  • apache = NOPASSWD: /path/2/app, /path/2/app2 could you try this?
    – Diogo Jesus
    Sep 26 at 12:17







1




1




Is that the only sudoers line for apache? Could it be hitting another rule?
– Jeff Schaller
Sep 25 at 20:17




Is that the only sudoers line for apache? Could it be hitting another rule?
– Jeff Schaller
Sep 25 at 20:17












It is the only line, yes
– Michael Riordan
Sep 26 at 8:46




It is the only line, yes
– Michael Riordan
Sep 26 at 8:46












You would better find another way of doing that. Apache has another user for security reasons, giving sudo to Apache is a very bad idea.
– Rui F Ribeiro
Sep 26 at 11:39




You would better find another way of doing that. Apache has another user for security reasons, giving sudo to Apache is a very bad idea.
– Rui F Ribeiro
Sep 26 at 11:39












apache = NOPASSWD: /path/2/app, /path/2/app2 could you try this?
– Diogo Jesus
Sep 26 at 12:17




apache = NOPASSWD: /path/2/app, /path/2/app2 could you try this?
– Diogo Jesus
Sep 26 at 12:17










1 Answer
1






active

oldest

votes

















up vote
1
down vote













This line does not give sudo permissions to app and app2:



apache ALL=(root) NOPASSWD: /path/to/app /path/to/app2


What the above line does is give sudo permissions to run /path/to/app, only if you also pass a single argument to it of /path/to/app2. To specify multiple commands, they need to be separated by a comma:



apache ALL=(root) NOPASSWD: /path/to/app, /path/to/app2





share|improve this answer




















  • ah, that was just a typo in my post, which I've now changed
    – Michael Riordan
    Sep 26 at 8:40










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f471410%2funable-to-run-command-as-sudo-in-php-centos-7%23new-answer', 'question_page');

);

Post as a guest

















1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
1
down vote













This line does not give sudo permissions to app and app2:



apache ALL=(root) NOPASSWD: /path/to/app /path/to/app2


What the above line does is give sudo permissions to run /path/to/app, only if you also pass a single argument to it of /path/to/app2. To specify multiple commands, they need to be separated by a comma:



apache ALL=(root) NOPASSWD: /path/to/app, /path/to/app2





share|improve this answer




















  • ah, that was just a typo in my post, which I've now changed
    – Michael Riordan
    Sep 26 at 8:40














up vote
1
down vote













This line does not give sudo permissions to app and app2:



apache ALL=(root) NOPASSWD: /path/to/app /path/to/app2


What the above line does is give sudo permissions to run /path/to/app, only if you also pass a single argument to it of /path/to/app2. To specify multiple commands, they need to be separated by a comma:



apache ALL=(root) NOPASSWD: /path/to/app, /path/to/app2





share|improve this answer




















  • ah, that was just a typo in my post, which I've now changed
    – Michael Riordan
    Sep 26 at 8:40












up vote
1
down vote










up vote
1
down vote









This line does not give sudo permissions to app and app2:



apache ALL=(root) NOPASSWD: /path/to/app /path/to/app2


What the above line does is give sudo permissions to run /path/to/app, only if you also pass a single argument to it of /path/to/app2. To specify multiple commands, they need to be separated by a comma:



apache ALL=(root) NOPASSWD: /path/to/app, /path/to/app2





share|improve this answer












This line does not give sudo permissions to app and app2:



apache ALL=(root) NOPASSWD: /path/to/app /path/to/app2


What the above line does is give sudo permissions to run /path/to/app, only if you also pass a single argument to it of /path/to/app2. To specify multiple commands, they need to be separated by a comma:



apache ALL=(root) NOPASSWD: /path/to/app, /path/to/app2






share|improve this answer












share|improve this answer



share|improve this answer










answered Sep 25 at 22:11









jordanm

29.3k27891




29.3k27891











  • ah, that was just a typo in my post, which I've now changed
    – Michael Riordan
    Sep 26 at 8:40
















  • ah, that was just a typo in my post, which I've now changed
    – Michael Riordan
    Sep 26 at 8:40















ah, that was just a typo in my post, which I've now changed
– Michael Riordan
Sep 26 at 8:40




ah, that was just a typo in my post, which I've now changed
– Michael Riordan
Sep 26 at 8:40

















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f471410%2funable-to-run-command-as-sudo-in-php-centos-7%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

How to check contact read email or not when send email to Individual?

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
Read more

Displaying single band from multi-band raster using QGIS

Image
Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
Read more

How many registers does an x86_64 CPU actually have?

Image
Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
Read more