
Error Message
Description
Resolution
service mode, instead of in the
default mode.
INFO: can not get YAM status in
secure mode
This message indicates that the
user is attempting to execute the
urika-yam-status
script while
the system is in the secure service
mode, instead of in the default
mode.
The
urika-yam-status
script
can only be used in the secure
service mode. For more information,
refer to the Urika-GX System
Administration Guide.
Table 41. Marathon/Mesos/
mrun
Error Messages
Error Message
Description
Resolution
ERROR:mrun: Force Terminated
job /mrun/
2016-193-12-13-03.174056
Cancelled due to Timeout
Examples:
●
error("mrun: --immediate timed
out while waiting")
●
error("mrun: Timed out waiting
for mrund : %s" % appID)
●
error("mrun: Force Terminated
job %s Cancelled due to
Timeout" %
These errors indicate timeout and
resource contention issues, such as
the job timed out, the machine is
busy, too many users running too
many jobs, a user waiting for their
job to start, but previous jobs have
not freed up nodes, etc.
Additionally, if a user set a job
timeout's to 1 hour, and the job
lasted longer than 1 hour, the user
would get a
Job Cancelled
timeout error.
Ensure that the there are enough
resources available and that the
timeout interval is set correctly.
HWERR[r0s1c0n3][64]:0x4b14:The
SSID received an unexpected
response:Info1=0x19100000000000
3:Info2=0x7
Mesos is not able to talk to the
Zookeeper cluster and is attempting
to shut itself down.
Restart Mesos using the
urika-
start
command.
WARN
component.AbstractLifeCycle:
FAILED
[email protected]:4
040: java.net.BindException:
Address already in use
User is attempting to execute a job
on a port that is already in use.
This message can be safely
ignored.
ERROR:Unexpected 'frameworks'
data from Mesos
●
Examples:
○
error("Mesos Response:
%s" % ret)
○
error("Unexpected
'frameworks' data from
Mesos")
These errors occur when
mrun
is
not able to connect/communicate
with Mesos and/or Marathon.
Refer to online Mesos/Marathon
documentation.
Troubleshooting
S3016
264