manual.txt 22 KB

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