manual.txt 22 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607
  1. Hue Tarball Installation Guide
  2. ==============================
  3. == Introduction
  4. Hue is a graphical user interface to operate and develop applications for
  5. Hadoop. Hue applications are collected into a desktop-style environment and
  6. delivered as a Web application, requiring no additional installation for
  7. individual users.
  8. This guide describes how to install and configure a Hue tarball. For
  9. information about installing Hue packages, see
  10. https://wiki.cloudera.com/display/DOC/Hue+Installation[Installing Hue].
  11. There is also a companion SDK guide that describes how to develop
  12. new Hue applications:
  13. http://archive.cloudera.com/cdh3/hue/sdk/sdk.html[Hue SDK Documentation]
  14. IMPORTANT: Hue requires the Cloudera Distribution for Hadoop (CDH), version 3 (beta 3).
  15. .Conventions Used in this Guide:
  16. * Commands that must be run with +root+ permission have a +#+ command prompt.
  17. * Commands that do not require +root+ permission have a +$+ command prompt.
  18. == Hue Installation Instructions
  19. The following instructions describe how to install the Hue tarball on a
  20. multi-node cluster. You must install CDH first and update some
  21. Hadoop configuration files before installing Hue.
  22. IMPORTANT: You'll need to install the Hue plugins
  23. on _every_ machine that's running Hadoop daemons.
  24. === Install CDH3
  25. To use Hue, you must install and run CDH3 Beta 3, version 0.20.2+737 or later.
  26. If you are not running this version of CDH or later, upgrade your
  27. cluster before proceeding.
  28. === Install Hue
  29. Hue consists of a web service that runs on a special node in your cluster.
  30. Choose one node where you want to run Hue. This guide refers to that node as
  31. the _Hue Server_. For optimal performance, this should be one of the nodes
  32. within your cluster, though it can be a remote node as long as there are no
  33. overly restrictive firewalls. For small clusters of less than 10 nodes,
  34. you can use your existing master node as the Hue Server.
  35. You can download the Hue tarball here:
  36. http://github.com/cloudera/hue/downloads/
  37. ==== Hue Dependencies
  38. Hue employs some Python modules which use native code and requires
  39. certain development libraries be installed on your system. To install from the
  40. tarball, you must have the following installed:
  41. .Required Dependencies
  42. [grid="rows"]
  43. ``~
  44. Redhat,Debian
  45. ~~~~~~~~~~
  46. gcc,gcc
  47. libxml2-devel,libxml2-dev
  48. libxslt-devel,libxslt-dev
  49. mysql-devel,libmysqlclient-dev
  50. python-devel,python-dev
  51. python-setuptools,python-setuptools
  52. sqlite-devel,libsqlite3-dev
  53. ant,ant
  54. ~~~~~~~~~~
  55. ==== Build
  56. Configure `$HADOOP_HOME` and `$PREFIX` with the path of your Hadoop
  57. installation and the path where you want to install Hue by running:
  58. ----
  59. $ HADOOP_HOME=/path/to/hadoop-0.20 PREFIX=/path/to/install/into make install
  60. ----
  61. You can install Hue anywhere on your system - it does not need root permission
  62. although additional third-party SDK applications may.
  63. It is a good practice to create a new user for Hue and either install Hue in
  64. that user's home directory, or in a directory within `/usr/local`.
  65. ==== Install Hadoop Plugins
  66. In order to communicate with Hadoop, Hue requires a plugin jar that you must
  67. install and configure. This jar is: `desktop/libs/hadoop/java-lib/hue-plugins-*.jar`,
  68. relative to the Hue installation directory.
  69. Run these commands to create a symlink your Hadoop lib directory
  70. (`/usr/lib/hadoop-0.20/lib` if you installed CDH via a Debian or RPM package)
  71. to this jar:
  72. ----
  73. $ cd /usr/lib/hadoop/lib
  74. $ ln -s /usr/local/hue/desktop/libs/hadoop/java-lib/hue*jar .
  75. # Restart Hadoop
  76. ----
  77. NOTE: On a multi-node cluster, you must install the plugin jar on every
  78. node. You do not need to install all of the Hue components on every node.
  79. ==== Specifying the Secret Key
  80. For security, you should also specify the secret key that is used for secure hashing in the session store.
  81. Open the `/etc/hue/hue.ini` configuration file. In the `desktop` section, enter a long series of random characters (30 to 60 characters is recommended).
  82. ----
  83. [desktop]
  84. secret_key=qpbdxoewsqlkhztybvfidtvwekftusgdlofbcfghaswuicmqp
  85. ----
  86. NOTE: If you don't specify a secret key, Hue will run but it will also display error messages telling you to set the secret key.
  87. ==== Restart Hadoop
  88. After making the changes in your Hadoop configuration, restart the Hadoop daemons:
  89. ----
  90. # /etc/init.d/hadoop-0.20-datanode restart
  91. # /etc/init.d/hadoop-0.20-namenode restart
  92. # /etc/init.d/hadoop-0.20-jobtracker restart
  93. # /etc/init.d/hadoop-0.20-secondarynamenode restart
  94. # /etc/init.d/hadoop-0.20-tasktracker restart
  95. ----
  96. ==== Starting Hue
  97. To start Hue, use `build/env/bin/supervisor`. This will start
  98. several subprocesses, corresponding to the different Hue components.
  99. ==== Troubleshooting the Hue Tarball Installation
  100. .Q: I moved my Hue installation from one directory to another and now Hue no longer functions correctly.
  101. A: Due to the use of absolute paths by some Python packages, you must run a series of commands if you move your Hue installation. In the new location, run:
  102. ----
  103. $ rm app.reg
  104. $ rm -r build
  105. $ make apps
  106. ----
  107. .Q: Why does "make install" compile other pieces of software?
  108. A: In order to ensure that Hue is stable on a variety of distributions and architectures, it installs a Python virtual environment which includes its dependencies. This ensures that the software can depend on specific versions of various Python libraries and you don't have to be concerned about missing software components.
  109. === Configuring Hadoop for Hue
  110. Hue requires that you install and configure some plugins in your
  111. Hadoop installation. In order to enable the plugins, you must make some
  112. small additions to your configuration files. Make these configuration changes
  113. on each node in your cluster by editing the following files
  114. in: `/etc/hadoop-0.20/conf/`
  115. ==== `hdfs-site.xml`
  116. Add the following configuration properties to `hdfs-site.xml`:
  117. ----
  118. <property>
  119. <name>dfs.namenode.plugins</name>
  120. <value>org.apache.hadoop.thriftfs.NamenodePlugin</value>
  121. <description>Comma-separated list of namenode plugins to be activated.
  122. </description>
  123. </property>
  124. <property>
  125. <name>dfs.datanode.plugins</name>
  126. <value>org.apache.hadoop.thriftfs.DatanodePlugin</value>
  127. <description>Comma-separated list of datanode plugins to be activated.
  128. </description>
  129. </property>
  130. <property>
  131. <name>dfs.thrift.address</name>
  132. <value>0.0.0.0:10090</value>
  133. </property>
  134. -----
  135. ==== `mapred-site.xml`
  136. Add the following configuration properties to mapred-site.xml:
  137. ----
  138. <property>
  139. <name>jobtracker.thrift.address</name>
  140. <value>0.0.0.0:9290</value>
  141. </property>
  142. <property>
  143. <name>mapred.jobtracker.plugins</name>
  144. <value>org.apache.hadoop.thriftfs.ThriftJobTrackerPlugin</value>
  145. <description>Comma-separated list of jobtracker plugins to be activated.
  146. </description>
  147. </property>
  148. ----
  149. ==== `hadoop-metrics.properties`
  150. To enable full monitoring in the Health application, the metrics
  151. contexts must not be NullContext. You can configure `hadoop-metrics.properties` as shown below:
  152. ----
  153. # Exposes /metrics URL endpoint for metrics information.
  154. dfs.class=org.apache.hadoop.metrics.spi.NoEmitMetricsContext
  155. mapred.class=org.apache.hadoop.metrics.spi.NoEmitMetricsContext
  156. jvm.class=org.apache.hadoop.metrics.spi.NoEmitMetricsContext
  157. rpc.class=org.apache.hadoop.metrics.spi.NoEmitMetricsContext
  158. ----
  159. === Further Hadoop Configuration and Caveats
  160. ==== `HADOOP_CLASSPATH` Caveat
  161. If you are setting `$HADOOP_CLASSPATH` in your `hadoop-env.sh`, be sure
  162. to set it in such a way that user-specified options are preserved. For example,
  163. Correct:
  164. ----
  165. # HADOOP_CLASSPATH=<your_additions>:$HADOOP_CLASSPATH
  166. ----
  167. Incorrect:
  168. ----
  169. # HADOOP_CLASSPATH=<your_additions>
  170. ----
  171. This enables certain components of Hue to add to
  172. Hadoop's classpath using the environment variable.
  173. ==== `hadoop.tmp.dir`
  174. If your users are likely to be submitting jobs both using Hue
  175. and from the same machine via the command line interface, they will be doing so as the `hue`
  176. user if they're using Hue and via their own user account
  177. on the command line. This leads to some contention
  178. on the directory specified by `hadoop.tmp.dir`, which defaults
  179. to `/tmp/hadoop-${user.name}`.
  180. Specifically, `hadoop.tmp.dir` is used to unpack jars in `bin/hadoop jar`.
  181. One work around to this is
  182. to set `hadoop.tmp.dir` to `/tmp/hadoop-${user.name}-${hue.suffix}` in the core-site.xml file:
  183. ----
  184. <property>
  185. <name>hadoop.tmp.dir</name>
  186. <value>/tmp/hadoop-${user.name}${hue.suffix}</value>
  187. </property>
  188. ----
  189. Unfortunately, when the variable is unset, you'll end up
  190. with directories named `/tmp/hadoop-user_name-${hue.suffix}` in
  191. `/tmp`. The job submission daemon, however, will still work.
  192. IMPORTANT: The Beeswax server writes into a local directory on the Hue machine
  193. that is specified by `hadoop.tmp.dir` to unpack its jars. That directory
  194. needs to be writable by the `hue` user, which is the default user who starts
  195. Beeswax Server, or else Beeswax server will not start. You may also make that
  196. directory world-writable.
  197. === Restart Your Hadoop Cluster
  198. Restart all of the daemons in your cluster so that the plugins can be loaded.
  199. You can confirm that the plugins are running correctly by tailing the daemon logs:
  200. ----
  201. $ tail --lines=500 /var/log/hadoop-0.20/hadoop*namenode*.log | grep ThriftPlugin
  202. 2009-09-28 16:30:44,337 INFO org.apache.hadoop.thriftfs.ThriftPluginServer: Starting Thrift server
  203. 2009-09-28 16:30:44,419 INFO org.apache.hadoop.thriftfs.ThriftPluginServer:
  204. Thrift server listening on 0.0.0.0:10090
  205. ----
  206. [TIP]
  207. .Configuring Your Firewall for Hue
  208. ============================================================
  209. Hue currently requires that the machines within your cluster can connect to each other freely over TCP. The machines outside your cluster must be able to open TCP port 8088 on the Hue Server to interact with the system.
  210. ============================================================
  211. == Configuring Hue
  212. Hue ships with a default configuration that will work for
  213. pseudo-distributed clusters. If you are running on a real cluster, you must make a few changes to the `/etc/hue/hue.ini` configuration file. The
  214. following sections describe the key configuration options you must make to configure Hue.
  215. [TIP]
  216. .Listing all Configuration Options
  217. ============================================================
  218. To list all available configuration options, run:
  219. ----
  220. /usr/share/hue/build/env/bin/hue config_help | less
  221. ----
  222. This commands outlines the various sections and options in the configuration,
  223. and provides help and information on the default values.
  224. ============================================================
  225. [TIP]
  226. .Viewing Current Configuration Options
  227. ============================================================
  228. To view the current configuration from within Hue, open:
  229. ----
  230. http://<hue>/dump_config
  231. ----
  232. ============================================================
  233. [TIP]
  234. .Using Multiple Files to Store Your Configuration
  235. ============================================================
  236. Hue loads and merges all of the files with extension `.ini`
  237. located in the `/etc/hue/conf/` directory. Files that are alphabetically later
  238. take precedence.
  239. ============================================================
  240. === Web Server Configuration
  241. Hue uses the CherryPy web server. You can use the following options to
  242. change the IP address and port that the web server listens on. The default
  243. setting is port 8088 on all configured IP addresses.
  244. ----
  245. # Webserver listens on this address and port
  246. http_host=0.0.0.0
  247. http_port=8088
  248. ----
  249. === Authentication
  250. By default, the first user who logs in to Hue can choose any
  251. username and password and becomes an administrator automatically. This
  252. user can create other user and administrator accounts. User information is
  253. stored in the Django database in the Django backend.
  254. The authentication system is pluggable. For more information, see the
  255. http://archive.cloudera.com/cdh3/hue/sdk/sdk.html[Hue SDK Documentation].
  256. === Configuring Hue for SSL
  257. You can configure Hue to serve over HTTPS. To do so, you must install
  258. "pyOpenSSL" within Hue's context and configure your keys.
  259. To install `pyOpenSSL`, from the root of your Hue installation path,
  260. do the following steps:
  261. 1. Run this command:
  262. ----
  263. $ ./build/env/bin/easy_install pyOpenSSL
  264. ----
  265. 2. Configure Hue to use your private key by adding the following
  266. options to the `/etc/hue/hue.ini` configuration file:
  267. ----
  268. ssl_certificate=/path/to/certificate
  269. ssl_private_key=/path/to/key
  270. ----
  271. 3. Ideally, you would have an appropriate key signed by a Certificate Authority.
  272. If you're just testing, you can create a self-signed key using the `openssl`
  273. command that may be installed on your system:
  274. ----
  275. # Create a key
  276. $ openssl genrsa 1024 > host.key
  277. # Create a self-signed certificate
  278. $ openssl req -new -x509 -nodes -sha1 -key host.key > host.cert
  279. ----
  280. [NOTE]
  281. .Self-signed Certificates and File Uploads
  282. ============================================================
  283. To upload files using the Hue File Browser over HTTPS requires
  284. using a proper SSL Certificate. Self-signed certificates don't
  285. work.
  286. ============================================================
  287. === Pointing Hue to Your Master Nodes
  288. If your Hadoop cluster contains multiple nodes, you should configure
  289. Hue to point to the external hostnames of your NameNode and
  290. JobTracker. To do so, change the `namenode_host` and `jobtracker_host`
  291. lines in the `/etc/hue/hue.ini` configuration file. Refer to the inline comments in the configuration file for more information.
  292. == Starting Hue from the Tarball
  293. After your cluster is running with the plugins enabled, you can start Hue on your Hue Server by running:
  294. ----
  295. # build/env/bin/supervisor
  296. ----
  297. Your Hue installation is now running.
  298. == Administering Hue
  299. Now that you've installed and started Hue, you can feel free to skip ahead
  300. to the <<usage,Using Hue>> section. Administrators may want to refer to this section
  301. for more details about managing and operating a Hue installation.
  302. === Hue Processes
  303. ==== Process Hierarchy
  304. A script called `supervisor` manages all Hue processes. The supervisor is a watchdog process -- its only purpose is to spawn and monitor other processes.
  305. A standard Hue installation starts and monitors the following processes:
  306. * `runcpserver` - a web server based on CherryPy that provides the core web functionality of Hue
  307. * `jobsubd` - a daemon which handles submission of jobs to Hadoop
  308. * `beeswax server` - a daemon that manages concurrent Hive queries
  309. If you have installed other applications into your Hue instance, you may see other daemons running under the supervisor as well.
  310. You can see the supervised processes running in the output of `ps -f -u hue`:
  311. ------------------
  312. UID PID PPID C STIME TTY TIME CMD
  313. hue 8685 8679 0 Aug05 ? 00:01:39 /usr/share/hue/build/env/bin/python /usr/share/hue/build/env/bin/desktop runcpserver
  314. hue 8693 8679 0 Aug05 ? 00:00:01 /usr/share/hue/build/env/bin/python /usr/share/hue/build/env/bin/desktop jobsubd
  315. hue 8695 8679 0 Aug05 ? 00:00:06 /usr/java/jdk1.6.0_14/bin/java -Xmx1000m -Dhadoop.log.dir=/usr/lib/hadoop-0.20/logs -Dhadoop.log.file=hadoop.log ...
  316. ------------------
  317. 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.
  318. === Hue Logging
  319. The Hue logs are found in `/var/log/hue`. Inside the log directory you can find:
  320. * An `access.log` file, which contains a log for all requests against the Hue web server.
  321. * A `supervisor.log` file, which contains log information for the supervisor process.
  322. * A `supervisor.out` file, which contains the stdout and stderr for the supervisor process.
  323. * A `.log` file for each supervised process described above, which contains the logs for that process.
  324. * A `.out` file for each supervised process described above, which contains the stdout and stderr for that process.
  325. If users on your cluster have problems running Hue, you can often find error messages in these log files. If you are unable to start Hue from the init script, the
  326. `supervisor.log` log file can often contain clues.
  327. ==== Viewing Recent Log Messages through your Web Browser
  328. In addition to logging `INFO` level messages to the `logs` directory, the Hue web server keeps a small buffer
  329. of log messages at all levels in memory. You can view these logs by visiting `http://myserver:8088/logs`.
  330. The `DEBUG` level messages shown can sometimes be helpful in troubleshooting issues.
  331. === The Hue Database
  332. Hue requires a SQL database to store small amounts of data, including user account information
  333. as well as history of job submissions and Hive queries. By default, Hue is configured to use the
  334. embedded database SQLite for this purpose, and should require no configuration or management by the
  335. administrator. However, MySQL is the recommended database to use; this section
  336. contains instructions for configuring Hue to access MySQL and other databases.
  337. ==== Inspecting the Hue Database
  338. The default SQLite database used by Hue is located in `/usr/share/hue/desktop/desktop.db`.
  339. You can inspect this database from the command line using the `sqlite3` program. For example:
  340. ---------
  341. # sqlite3 /usr/share/hue/desktop/desktop.db
  342. SQLite version 3.6.22
  343. Enter ".help" for instructions
  344. Enter SQL statements terminated with a ";"
  345. sqlite> select username from auth_user;
  346. admin
  347. test
  348. sample
  349. sqlite>
  350. ----------
  351. It is strongly recommended that you avoid making any modifications to the database directly using SQLite, though this trick
  352. can be useful for management or troubleshooting.
  353. ==== Backing up the Hue Database
  354. If you use the default SQLite database, then copy the `desktop.db` file to another node
  355. for backup. It is recommended that you back it up on a regular schedule,
  356. and also that you back it up before any upgrade to a new version of Hue.
  357. ==== Configuring Hue to Access Another Database
  358. Although SQLite is the default database type, some advanced users may prefer to have Hue access an
  359. alternate database type. Note that if you elect to configure Hue to use an external database,
  360. upgrades may require more manual steps in the future.
  361. The following instructions are for MySQL, though you can also configure Hue to work with other common databases such as PostgreSQL and Oracle.
  362. [NOTE]
  363. .Tested Database Backends
  364. ============================================================
  365. Note that Hue has only been tested with SQLite and MySQL database backends.
  366. ============================================================
  367. ===== Configuring Hue to Store Data in MySQL
  368. To configure Hue to store data in MySQL:
  369. 1. Create a new database in MySQL and grant privileges to a Hue user to manage this database.
  370. ----
  371. mysql> create database hue;
  372. Query OK, 1 row affected (0.01 sec)
  373. mysql> grant all on hue.* to 'hue'@'localhost' identified by 'secretpassword';
  374. Query OK, 0 rows affected (0.00 sec)
  375. ----
  376. 2. Shut down Hue if it is running.
  377. 3. To migrate your existing data to MySQL, use the following command to dump the
  378. existing database data to a text file. Note that using the ".json" extension is required.
  379. ----
  380. $ /usr/share/hue/build/env/bin/hue dumpdata > <some-temporary-file>.json
  381. ----
  382. 4. Open the `/etc/hue/hue.ini` file in a text editor. Directly below the `[[database]]` line, add the following options (and modify accordingly for your MySQL setup):
  383. ----
  384. host=localhost
  385. port=3306
  386. engine=mysql
  387. user=hue
  388. password=secretpassword
  389. name=hue
  390. ----
  391. 5. Install the Python drivers for MySQL into Hue's environment:
  392. ----
  393. # su - hue -s /bin/bash
  394. $ /usr/share/hue/build/env/bin/easy_install MySQL-python
  395. ----
  396. `easy_install` will access the Internet to find MySQL-python.
  397. If you don't have network access, you may specify a path
  398. to a tarball (such as `/tmp/MySQL-python-1.2.2.tar.gz`) instead.
  399. 6. As the Hue user, configure Hue to load the existing data and create the
  400. necessary database tables:
  401. ----
  402. $ /usr/share/hue/build/env/bin/hue syncdb --noinput
  403. $ mysql -uhue -psecretpassword -e "DELETE FROM hue.django_content_type;"
  404. $ /usr/share/hue/build/env/bin/hue loaddata <temporary-file-containing-dumped-data>.json
  405. ----
  406. Your system is now configured and you can start the Hue server as normal.
  407. == Hue Applications
  408. This section includes documentation specific to built-in Hue applications.
  409. === Beeswax, the Hive UI
  410. ==== Introduction
  411. Beeswax is an application that is a component within Hue and helps you use Hive to query your data.
  412. ==== Installation
  413. Beeswax is installed as part of Hue.
  414. ==== Hive Configuration
  415. Beeswax, the Hive interface in Hue, includes Hive 0.5. You do
  416. not need an existing Hive installation.
  417. Your Hive data is stored in HDFS, normally under `/user/hive/warehouse`
  418. (or any path you specify as `hive.metastore.warehouse.dir` in your
  419. `hive-site.xml`). Make sure this location exists and is writable by
  420. the users whom you expect to be creating tables. `/tmp` (on the local file
  421. system) must be world-writable, as Hive makes extensive use of it.
  422. ==== Configuration
  423. ===== No Existing Hive Installation
  424. Familiarize yourself with the configuration options in
  425. `hive-site.xml` (see
  426. http://wiki.apache.org/hadoop/Hive/AdminManual/Configuration).
  427. Having a `hive-site.xml` is optional but often useful, particularly on setting
  428. up a http://wiki.apache.org/hadoop/Hive/AdminManual/MetastoreAdmin[metastore].
  429. You may store the `hive-site.xml` in `/etc/hue/conf`, or instruct
  430. Beeswax to locate it using the `hive_conf_dir` configuration variable. See
  431. `/etc/hue/conf/hue-beeswax.ini`.
  432. ===== Existing Hive Installation
  433. In `/etc/hue/conf/hue-beeswax.ini`, modify `hive_conf_dir` to point to the directory containing `hive-site.xml`.
  434. [[usage]]
  435. == Using Hue
  436. After installation, you can use Hue by navigating to `http://myserver:8088/`.
  437. The following login screen appears:
  438. image:images/login.png[]
  439. Launch applications on the bottom-right.
  440. image:images/open-apps.png[,width=50%]
  441. The Help application guides users through the various installed applications.
  442. === Supported Browsers
  443. Hue is primarily tested on Firefox 3.5 and Firefox 3.6, on Windows, Mac, and Linux.
  444. Google Chrome and Safari work as well.
  445. === Feedback
  446. Your feedback is welcome. The best way to send feedback is to join the
  447. https://groups.google.com/a/cloudera.org/group/hue-user[mailing list], and
  448. send e-mail, to mailto:hue-user@cloudera.org[hue-user@cloudera.org].
  449. === Reporting Bugs
  450. If you find that something doesn't work, it'll often be helpful to include logs
  451. from your server. These are available at the +/logs+ URL on Hue's web server
  452. (not part of the graphical Hue UI). Please download the logs as a zip (or cut
  453. and paste the ones that look relevant) and send those with your bug reports.
  454. image:images/logs.png[]