Analytics/Archive/Hue/Administration
Information about Hue can be found in the parent wiki page Analytics/Cluster/Hue. The Analytics team uses Hue as handy UI to check the status of the Hadoop jobs, since it offers a nice integration with Oozie and Hive. If this UI is down other tools can be used to gather the same information, so it is not critical for the Analytics team.
Syncing new Hue accounts
When a new Hadoop user is added, an admin needs to give them a Hue account. Once T127850 is resolved, this process should be automatic.
- Log into http://hue.wikimedia.org
- In the upper right, click on your username, and select Manage Users (you will only be able to do this if you are Hue admin. Another admin can make you one.)
- Click 'Add/Sync LDAP User'
- Fill in the form with their UNIX shell username (not their Wikimedia developer account username), deselect both 'Distinguished name' and 'Create home directory', and click 'Add/Sync user'
Restarting Hue
There is an Apache httpd proxy server running in front of Hue, so in case of HTTP failures there are two places to check:
- /var/log/apache2/etc. for the proxy part (even if it rarely gives problems)
- /var/log/hue/etc.. in which the CherryPy server logs the Hue python application errors
Usually a simple systemctl restart hue fixes the problem.
Python processes
Hue usually creates only a process for the CherryPy Python server, but if kerberos is enabled then there will also be another process called kt-renewer responsible to periodically refresh its kerberos credentials via kinit. Logs of both can be found in /var/log/hue.