Troubleshoot Myriad

Log Locations

Table 1. Log Files
File Location
Frame/executor task logs. Used for debugging on Mesos slave nodes. Default: /tmp/mesos/slaves/<slave-ID>/frameworks/ Custom: /etc/mesos-slave/<work-directory>
Mesos master/slave service logs. INFO, WARN, AND ERR logs /var/log/mesos/*
Init log from starting the Mesos services. /opt/mapr/mesos-services/mesos-services-0.1/logs/*-init.log

Resource Manager not Starting

The Resource Manager cannot be started from the command line using the following command:
$ yarn resourcemanager
The following error occurs:
java.lang.UnsatisfiedLinkError: no mesos in java.library.path


Manually pass the MESOS_NATIVE_LIBRARY environment variable when starting the Resource Manager. For example:
env && export MESOS_NATIVE_LIBRARY=/usr/local/lib/ && yarn
Note: This is not an issue when starting Resource Manager from the Marathon UI.

Marathon Fails

The Mesos-3602 fix in Mesos version 0.26 causes an issue when using the maprfs path for the URI. When starting Marathon, an extra forward slash (/) is appended to the URI path. The application fails with a message similar to the following:

hadoop fs -copyToLocal '/maprfs:///dist/hadoop-2.7.0.myriad1.tar.gz'
-copyToLocal: Expected scheme-specific part at
index 7: maprfs:


Replace maprfs:/// with hdfs:/// when specifying the URI on Marathon application.

Note: This issue is fixed by MESOS-4304, which is available with in the Mesos 0.27 release.