Error Message
Description
Resolution
○
error("mrun: Getting mrund
state threw exception - %s"
%
○
error("getting marathon
controller state threw
exception - %s" %
○
error("Unexpected 'apps'
data from Marathon")
○
error("mrun: Launching
mrund threw exception -
%s" % (str(e)))
○
error("mrun: unexpected
'app' data from Marathon:
exception - %s" % (str(e)))
○
error("mrun: startMrund
failed")
○
error("mrun: Exception
received while waiting for "
●
error("mrun: select(): Exception
%s" % str(e) )
●
error("mrun: error socket")
●
error("mrund:
●
error %r:%s died\n" %
(err,args[0]))
●
error("mrund: select():
Exception %s\n" % str(e) )
These errors may be encountered
in situations where an admin
physically unplugs an Ethernet
cable while a CGE job was running,
or a node died, etc.
Ensure that the Ethernet cable is
plugged while jobs are running.
●
NCMD: Error leasing cookies
MUNGE:
●
Munge authentication failure
[%s] (%s).\n
These error only occur if the specific
system services have failed.
Refer to log messages
under
/var/log/messages
on the
node the message was
encountered on.
ERROR:Not enough CPUs for
exclusive access. Available: 0
Needed: 1
Examples
●
parser.error("Only --
mem_bind=local supported")
●
parser.error("Only --cpu-
freq=high supported")
●
parser.error("Only --kill-on-bad-
exit=1 supported")
These errors are typically caused by
user errors, typos and when not
enough nodes are available to run a
job.
Ensure that there are enough nodes
available and there are no typos in
the issues command.
Troubleshooting
S3016
265
