Additional Tips and Troubleshooting Information
●
If JupyterHub processes owned by the user remain running after the user has logged out from Jupyter these
processes can be manually killed using the Linux kill command.
●
The system will return the message, "
Service '
serviceName
' is not supported in the current
security mode
" if it is attempted to start a service that is not supported in the current service mode. Use
the
urika-state
or
urika-service-mode
commands to check which service mode the system is running
in. For more information, refer to
on page 177
●
If for any reason, Marathon does not start after a system crash, as a result of the queue reaching full capacity,
use the
urika-stop
command, followed by the
urika-start
command to resolve the issue.
●
In Urika-GX's multi tenant environment, individual tenant members are restricted from overriding the global
Hadoop configuration directory and from specifying a specific NameNode on the CLI. As such, certain
arguments passed to HDFS commands on the CLI are ignored to ensure security of tenant data. If these
arguments are passed to the CLI, the system will return a warning indicating that it detected an argument that
is not allowed for restricted users and that the argument is being removed
●
Use one of the following mechanisms if it is required to kill Spark jobs:
○
Kill the job using the Spark UI - Click on the text (kill) in the Description column of the Stages tab.
○
Kill the job using the Linux
kill
command.
○
Kill the job using the
Ctrl+C
keyboard keys.
●
The system will return the following error if a user attempts to view help information for an unsupported Lustre
lfs
sub-command:
The
sub-command
command is either unknown or not supported for tenant users. For
more information on tenant user rules try 'lfs help tenant-rules'.
●
When modifying the number of CPUs or memory for a tenant VM, the system will return an error if it is
attempted to allocate more than the acceptable value of CPU or memory to a tenant VM via the
ux-tenant-
alter-vm
command. For more information, refer to the
ux-tenant-alter-vm
man page.
●
In rare cases, switching from the secure to default mode may result in some Romana network policy
information that is not translated into the appropriate IP table rules. This allows a recently created pod to ping
a pod in a different Kubernetes name space. Contact Cray support if this problem is encountered.
8.9
Troubleshoot
mrun
Issues
Some common
mrun
error messages and their cause(s) are listed as following:
Issue related to Mesos/Marathon
Potential cause: - These errors occur when
mrun
is not able to connect/communicate with Mesos and/or
Marathon. To troubleshoot these issues, refer to online Mesos/Marathon documentation.
●
Format:
Mon Jul 11 2016 11:39:43.601145 UTC[][mrun]:ERROR:Unexpected 'frameworks'
data from Mesos
●
Examples:
○
error("Mesos Response: %s" % ret)
Troubleshooting
S3016
268
