Bug #61873 [Com]: proc_get_status always returns exitcode -1

Edit report at https://bugs.php.net/bug.php?id=61873&edit=1 ID: 61873 Comment by: phpmpan at mpan dot pl Reported by: dcb at insomniacsoft dot com Summary: proc_get_status always returns exitcode -1 Status: Open Type: Bug Package: Program Execution Operating System: Linux PHP Version: 5.4.1 Block user comment: N Private report: N New Comment: Since no one was able to reproduce this to this point, all that can be done is debugging it somehow on your side and eliminate possible reasons. What strace output tells us here is that "/tmp/te" actually exists and you the code is executing it. In other case the second call to execve would not return 0. If it is returning 0, it means that the interpretation of "/tmp/te" has actually started. He's my output for comparison (snaps for 5.4 and trunk): ------------------------------- [pid 7359] execve("/bin/sh", ["sh", "-c", "/tmp/te"], [/* 47 vars */] <unfinished ...> [pid 7359] execve("/tmp/te", ["/tmp/te"], [/* 46 vars */]) = 0 [pid 7359] open("/tmp/te", O_RDONLY) = 3 write(1, "/tmp/te", 7/tmp/te) = 7 ------------------------------- What is puzzling me is why your sh (pid:26199) is not replacing itself with the script. As we can see, another process (pid:26200) is spawned and it is the one that executes your script. My blind guess is that PHP receives status code from 26199, which - for some reason - is not waiting for 26200 or not passing the status code from it properly. Can you check what is this producing? ------------------------------- sh -c /tmp/te echo $? ------------------------------- Maybe the bug is not in PHP... Previous Comments: ------------------------------------------------------------------------ [2012-04-30 23:24:42] dcb at insomniacsoft dot com Still getting -1 for /bin/ls as well I did the strace, here is output, unfortunately I have no idea how to interpret it: [pid 26199] execve("/bin/sh", ["sh", "-c", "/tmp/te"], [/* 19 vars */] <unfinished ...> [pid 26200] execve("/tmp/te", ["/tmp/te"], [/* 19 vars */]) = 0 [pid 26200] open("/tmp/te", O_RDONLY) = 3 write(1, "/tmp/te", 7/tmp/te) = 7 ------------------------------------------------------------------------ [2012-04-29 06:36:21] phpmpan at mpan dot pl Maybe strace shows something interesting? strace -f php -r '$descriptorspec = array( 0 => array("pipe", "r"), 1 => array("pipe", "w"), 2 => array("file", "/tmp/error-output.txt", "a") ); $p = proc_open("/tmp/te", $descriptorspec, $pipes, "/tmp"); sleep(1); fclose($pipes[0]);fclose($pipes[1]); $s = proc_get_status($p); print_r($s);' 2>&1 | grep '/tmp/te' ------------------------------------------------------------------------ [2012-04-29 03:51:46] laruence@php.net what about call "/bin/ls" instead of /tmp/te? ------------------------------------------------------------------------ [2012-04-29 00:18:47] dcb at insomniacsoft dot com I've checked that, the script executes fine and besides I actually discovered the issue while working with the symfony/Process classes. On php 5.3.6 all the tests pass, but on the same machine, with the same config (just different paths) all versions starting from 5.4.0 fail the symfony/Process unit tests related to the exit code. ------------------------------------------------------------------------ [2012-04-28 14:22:18] reeze dot xia at gmail dot com I can't reproduce it either. Any error log in /tmp/error-output.txt? maybe /tmp/te did't have execution permission? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=61873 -- Edit this bug report at https://bugs.php.net/bug.php?id=61873&edit=1