
Error Message
Description
Notes/Resolution
'Urika
®
-GX System Administration
Guide'.
Error message:
ERROR: tag(s)
not found in playbook:
non_existent_service.
possible values:
collectl,grafana,hdfs,hdfs
_dn,hdfs_nn,hdfs_sn,hdp_ap
p_timeline,hdp_hist,hive,h
ive2,hive_met,hive_web,hue
,influxdb,jupyterhub,marat
hon,
mesos,nodemanager,oozie,sp
ark_hist,yarn,yarn_rm,
zookeeper
Description: User has specified a
service that does not exist to the
urika-stop
or
urika-start
command.
Resolution: Use the correct name of
the services by selecting one of the
options listed in the error message.
Error message: You are not
authorized to log into this system --
to obtain access please contact
your system administrator
su: Permission denied
This message may be returned by
the
urika-state
command on a
freshly deployed system if the
hdfs
user has not yet been created.
Wait until the
main_run
/
main_update
playbooks have
finished creating the
hdfs
user
Table 39. Spark Error Messages
Error Message
Description
Resolution
INFO
mesos.CoarseMesosSchedulerBac
kend: Blacklisting Mesos slave
20151120-121737-1560611850-505
0-20795-S0 due to too many
failures; is Spark installed on it?
INFO
mesos.CoarseMesosSchedulerBac
kend: Mesos task 30 is now
TASK_FAILED
There may be something preventing
a Mesos slave from starting the
Spark executor. Common causes
include:
●
The SSD is too full
●
The user does not have
permission to write to Spark
temporary files
under
/var/spark/tmp/
Refer to Spark logs.
ERROR
mesos.MesosCoarseGrainedSched
ulerBackend: Mesos error: Master
refused authentication Exiting due
to error from cluster scheduler:
Master refused authentication
This message appears when Spark
is not able to authenticate with
Mesos.
The user may not have Mesos
credentials, in which case the user
would need to be added via the
usm-sync-users script
script.
In other cases, this error may be a
result of the user's credentials being
in a bad state, in which case the
admin would need to run the
usm-
recreate-secret
script to create
a new secret for the user. For more
information, refer to the 'Urika
®
-GX
System Administration Guide'.
Troubleshooting
S3016
260