php exec function 中的非法命令错误代码 127

Question

I am using this php code:

exec("unrar e file.rar",$ret,$code);

and getting an error code of illegal command ie 127... but when I am using this command through ssh its working... because unrar is installed on the server... so can anyone guess why exec is not doing the right stuff?

Answer 1

尝试使用应用程序的直接路径（/ usr / bin / unrar的任何东西），听起来像php无法找到应用程序。

Answer 2

If you have chrooted apache and php, you will also want to put /bin/sh into the chrooted environment. Otherwise, the exec() or passthru() will not function properly, and will produce error code 127, file not found.

Answer 3

Since this comes up as a top answer in google, I wanted to share my fix:

The simple fix I had was to disable safe_mode in the php.ini file

; Safe Mode
; http://www.php.net/manual/en/ini.sect.safe-mode.php#ini.safe-mode
safe_mode = Off

Answer 4

thanx all for your response!!

I tried this

//somedir is inside the directory where php file is
chdir("somedir");
exec("/home/username/bin/unrar e /home/path/to/dir/file.rar");

and now it returned no exit code ... oher commands are doing file .. i tried mkdir etc .. :s

Answer 5

Just in case somebody else still gets this problem, take a look at the post here:

http://gallery.menalto.com/node/2639#comment-8638

Quote:

I found the problem. The problem was my security-paranoid OpenBSD. When upgrading from 3.1 to 3.2 they added:

• Apache runs chroot'd by default. To disable this, see the new -u option.

The chroot prevented Apache from accessing anything outside of a directory, so I moved everything into the apache directory including netpbm. Everything was accessible and executable, but I guess it was still in some sort of "safe mode" because the exec() always returned 127.

Anyway, running httpd with the -u option went back to the less secure non chroot'd apache startup, which allowed the exec() to work again.

Answer 6

ohkiee guyz thanx ...是的，$ PATH可能会有一些错误...但是给定完整路径它的工作:)

exec("/home/user/bin/unrar e /home/user/xxx/yyy/file.rar");

Answer 7

I did not find the solution for my problem of the same type so sharing what was the cause of it in my Linux setup. For whatever reason I needed an apache module loaded before other modules and so apache was started with LD_PRELOAD. As exec inherits the environment of the parent process LD_PRELOAD was used for starting the exec-ed program (through sh). Now the preloaded module uses some bindings to apache functions and of course they are not to be present in sh. The result of the php exec was an exit status of 127. The solution was to have in my php file a putenv("LD_PRELOAD") that gets executed before any exec calls.