The following sections contain details about managing and operating a Hue installation.
A script called supervisor manages all Hue processes. The supervisor is a watchdog process; its only purpose is to spawn and monitor other processes. A standard Hue installation starts and monitors the following processes:
- runcpserver – a web server that provides the core web functionality of Hue
- beeswax server – a daemon that manages concurrent Hive queries
If you have installed other applications into your Hue instance, you may see other daemons running under the supervisor as well.
You can see the supervised processes running in the output of ps -f -u hue.
Note that the supervisor automatically restarts these processes if they fail for any reason. If the processes fail repeatedly within a short time, the supervisor itself shuts down.
You can view the Hue logs in the /var/log/hue directory, where you can find:
- An access.log file, which contains a log for all requests against the Hue Server.
- A supervisor.log file, which contains log information for the supervisor process.
- A supervisor.out file, which contains the stdout and stderr for the supervisor process.
- A .log file for each supervised process described above, which contains the logs for that process.
- A .out file for each supervised process described above, which contains the stdout and stderr for that process.
If users on your cluster have problems running Hue, you can often find error messages in these log files.
Viewing Recent Log Messages
In addition to logging INFO level messages to the logs directory, the Hue Server keeps a small buffer of log messages at all levels in memory. The DEBUG level messages can sometimes be helpful in troubleshooting issues.
In the Hue UI you can view these messages by selecting the Server Logs tab in the About application. You can also view these logs by visiting http://myserver:port/logs.
|<< Previous: Starting and Stopping the Hue Server||Next: Hue Database >>|