hi ,
i am trying to run recon from a php page in my Apache Web Server
<?php echo passthru('/usr/local/bin/recon -d 2>&1');
?>
however i am getting the following error
n-1<7876> ssi:boot:open: opening
n-1<7876> ssi:boot:open: opening boot module globus
n-1<7876> ssi:boot:open: opened boot module globus
n-1<7876> ssi:boot:open: opening boot module rsh
n-1<7876> ssi:boot:open: opened boot module rsh
n-1<7876> ssi:boot:open: opening boot module slurm
n-1<7876> ssi:boot:open: opened boot module slurm
n-1<7876> ssi:boot:select: initializing boot module slurm
n-1<7876> ssi:boot:slurm: not running under SLURM
n-1<7876> ssi:boot:select: boot module not available: slurm
n-1<7876> ssi:boot:select: initializing boot module rsh
n-1<7876> ssi:boot:rsh: module initializing
n-1<7876> ssi:boot:rsh:agent: ssh
n-1<7876> ssi:boot:rsh:username:
n-1<7876> ssi:boot:rsh:verbose: 1000
n-1<7876> ssi:boot:rsh:algorithm: linear
n-1<7876> ssi:boot:rsh:no_n: 0
n-1<7876> ssi:boot:rsh:no_profile: 0
n-1<7876> ssi:boot:rsh:fast: 0
n-1<7876> ssi:boot:rsh:ignore_stderr: 0
n-1<7876> ssi:boot:rsh:priority: 10
n-1<7876> ssi:boot:select: boot module available: rsh, priority: 10
n-1<7876> ssi:boot:select: initializing boot module globus
n-1<7876> ssi:boot:globus: globus-job-run not found, globus boot will not run
n-1<7876> ssi:boot:select: boot module not available: globus
n-1<7876> ssi:boot:select: finalizing boot module slurm
n-1<7876> ssi:boot:slurm: finalizing
n-1<7876> ssi:boot:select: closing boot module slurm
n-1<7876> ssi:boot:select: finalizing boot module globus
n-1<7876> ssi:boot:globus: finalizing
n-1<7876> ssi:boot:select: closing boot module globus
n-1<7876> ssi:boot:select: selected boot module rsh
n-1<7876> ssi:boot:base: looking for boot schema in following directories:
n-1<7876> ssi:boot:base:
n-1<7876> ssi:boot:base: $TROLLIUSHOME/etc
n-1<7876> ssi:boot:base: $LAMHOME/etc
n-1<7876> ssi:boot:base: /usr/local/etc
n-1<7876> ssi:boot:base: looking for boot schema file:
n-1<7876> ssi:boot:base: lam-bhost.def
n-1<7876> ssi:boot:base: found boot schema: /usr/local/etc/lam-bhost.def
n-1<7876> ssi:boot:rsh: found the following hosts:
n-1<7876> ssi:boot:rsh: n0 localhost (cpu=1)
n-1<7876> ssi:boot:rsh: resolved hosts:
n-1<7876> ssi:boot:rsh: n0 localhost --> 127.0.0.1 (origin)
n-1<7876> ssi:boot:rsh: starting RTE procs
n-1<7876> ssi:boot:base:linear: starting
n-1<7876> ssi:boot:base:linear: booting n0 (localhost)
n-1<7876> ssi:boot:rsh: starting recon on (localhost)
n-1<7876> ssi:boot:rsh: starting on n0 (localhost): tkill -N -d
n-1<7876> ssi:boot:rsh: launching locally
n-1<7876> ssi:boot:base:linear: Failed to boot n0 (localhost)
n-1<7876> ssi:boot:base:linear: aborted!
-----------------------------------------------------------------------------
recon was not able to complete successfully. There can be any number
of problems that did not allow recon to work properly. You should use
the "-d" option to recon to get more information about each step that
recon attempts.
Any error message above may present a more detailed description of the
actual problem.
Here is general a list of prerequisites that *must* be fulfilled
before recon can work:
- Each machine in the hostfile must be reachable and operational.
- You must have an account on each machine.
- You must be able to rsh(1) to the machine (permissions
are typically set in the user's $HOME/.rhosts file).
*** Sidenote: If you compiled LAM to use a remote shell program
other than rsh (with the --with-rsh option to ./configure;
e.g., ssh), or if you set the LAMRSH environment variable
to an alternate remote shell program, you need to ensure
that you can execute programs on remote nodes with no
password. For example:
unix% ssh -x pinky uptime
3:09am up 211 day(s), 23:49, 2 users, load average: 0.01, 0.08, 0.10
- The LAM executables must be locatable on each machine, using
the shell's search path and possibly the LAMHOME environment
variable.
- The shell's start-up script must not print anything on standard
error. You can take advantage of the fact that rsh(1) will
start the shell non-interactively. The start-up script (such
as .profile or .cshrc) can exit early in this case, before
executing many commands relevant only to interactive sessions
and likely to generate output.
-----------------------------------------------------------------------------
n-1<7876> ssi:boot:rsh: finalizing
n-1<7876> ssi:boot: Closing
any ideas ....
i am able to run other commands like ls easily from the php page .
|
