
Error Message
Description
Resolution
●
parser.error("-n should equal (-
N * --ntasks-per-node)")
●
parser.error("-N nodes must be
>= 1")
●
parser.error("-n images must be
>= -N nodes")
●
parser.error("No command
specified to launch"); error("Not
enough CPUs. "
●
error("Not enough CPUs for
exclusive access. "
●
error("Not enough nodes. "
●
parser.error("name [%s] must
only contain 'a-z','0-9','-' and '.'"
●
parser.error("[%s] is not
executable file" % args[0])
ERROR: Zero read: Scaling DOWN
not supported
This error message is returned
when
mrun
is not expecting one of
the remote nodes to abruptly close
its socket. When
mrun
goes to read
the socket, it detects the error,
generates the message, and the
application dies (or is killed).
Marathon UI to scale down
mrun
jobs is not supported.
This message can occur in the
following conditions:
●
The user used the
—kill-on-
scaledown
option of the
mrun
command.
●
The first remote compute node
did not exit successfully
Thus, this error message can only
occur if the application is killed or if
someone used the Marathon REST
API in an attempt to scale the
application down. No action needs
to be taken in either case.
mrun: error: Users may only cancel
their own mrun jobs
This message comes when a non-
root user tries to use
mrun
--
cancel
to cancel any Marathon job
that was not launched by that user
using
mrun
.
User
root
is allowed to use "mrun
--cancel" to kill any Marathon-
started job. All other users should
only kill the Marathon jobs they
launched using the
mrun
command.
INFO: Can not run this application
in secure mode, cancelling app
This message indicates that the
user is attempting to use
mrun
while the system is in the secure
service mode, instead of in the
default mode.
mrun
can only be used in the
default service mode. For more
information, refer to the Urika-GX
System Administration Guide.
Troubleshooting
S3016
266