Support Questions
Find answers, ask questions, and share your expertise

Hue Error on startup

Solved Go to solution

Hue Error on startup

Explorer

I have Hue setup for the first time to use the external DB ( MySQL), however get an error on startup. 

----------

Error 

 

[root@ip-172-31-70-110 scripts]# sudo service hue status

? hue.service - SYSV: Hue web server

   Loaded: loaded (/etc/rc.d/init.d/hue)

   Active: failed (Result: resources) since Thu 2016-08-11 10:06:36 EDT; 43min ago

     Docs: man:systemd-sysv-generator(8)

 

Aug 11 10:06:31 ip-172-31-70-110.ec2.internal systemd[1]: Starting SYSV: Hue web server...

Aug 11 10:06:31 ip-172-31-70-110.ec2.internal su[2406]: (to hue) root on none

Aug 11 10:06:36 ip-172-31-70-110.ec2.internal hue[2398]: Starting hue: [  OK  ]

Aug 11 10:06:36 ip-172-31-70-110.ec2.internal systemd[1]: PID file /usr/lib/hue/pids/supervisor.pid not readable (yet?) after start.

Aug 11 10:06:36 ip-172-31-70-110.ec2.internal systemd[1]: Failed to start SYSV: Hue web server.

Aug 11 10:06:36 ip-172-31-70-110.ec2.internal systemd[1]: Unit hue.service entered failed state.

Aug 11 10:06:36 ip-172-31-70-110.ec2.internal systemd[1]: hue.service failed.

[root@ip-172-31-70-110 scripts]# sudo service hue start

Starting hue (via systemctl):  Job for hue.service failed because a configured resource limit was exceeded. See "systemctl status hue.service" and "journalctl -xe" for details.

                                                           [FAILED]

[root@ip-172-31-70-110 scripts]# systemctl status hue.service

? hue.service - SYSV: Hue web server

   Loaded: loaded (/etc/rc.d/init.d/hue)

   Active: failed (Result: resources) since Thu 2016-08-11 10:50:37 EDT; 7s ago

     Docs: man:systemd-sysv-generator(8)

  Process: 4854 ExecStart=/etc/rc.d/init.d/hue start (code=exited, status=0/SUCCESS)

 

Aug 11 10:50:37 pecos2 systemd[1]: Starting SYSV: Hue web server...

Aug 11 10:50:37 pecos2 hue[4854]: Starting hue: already running

Aug 11 10:50:37 pecos2 systemd[1]: PID file /usr/lib/hue/pids/supervisor.pid not readable (yet?) after start.

Aug 11 10:50:37 pecos2 systemd[1]: Failed to start SYSV: Hue web server.

Aug 11 10:50:37 pecos2 systemd[1]: Unit hue.service entered failed state.

Aug 11 10:50:37 pecos2 systemd[1]: hue.service failed.

[root@ip-172-31-70-110 scripts]# sudo service hue stop

Stopping hue (via systemctl):                              [  OK  ]

[root@ip-172-31-70-110 scripts]# sudo service hue stop

Stopping hue (via systemctl):                              [  OK  ]

[root@ip-172-31-70-110 scripts]# sudo service hue status

? hue.service - SYSV: Hue web server

   Loaded: loaded (/etc/rc.d/init.d/hue)

   Active: failed (Result: resources) since Thu 2016-08-11 10:50:37 EDT; 34s ago

     Docs: man:systemd-sysv-generator(8)

  Process: 4854 ExecStart=/etc/rc.d/init.d/hue start (code=exited, status=0/SUCCESS)

 

Aug 11 10:50:37 pecos2 systemd[1]: Starting SYSV: Hue web server...

Aug 11 10:50:37 pecos2 hue[4854]: Starting hue: already running

Aug 11 10:50:37 pecos2 systemd[1]: PID file /usr/lib/hue/pids/supervisor.pid not readable (yet?) after start.

Aug 11 10:50:37 pecos2 systemd[1]: Failed to start SYSV: Hue web server.

Aug 11 10:50:37 pecos2 systemd[1]: Unit hue.service entered failed state.

Aug 11 10:50:37 pecos2 systemd[1]: hue.service failed.

Aug 11 10:51:05 pecos2 systemd[1]: Stopped SYSV: Hue web server.

Aug 11 10:51:07 pecos2 systemd[1]: Stopped SYSV: Hue web server.

[root@ip-172-31-70-110 scripts]# sudo service hue startt

Usage: hue {start|stop|status|reload|restart|condrestart

[root@ip-172-31-70-110 scripts]# sudo service hue start

Starting hue (via systemctl):  Job for hue.service failed because a configured resource limit was exceeded. See "systemctl status hue.service" and "journalctl -xe" for details.

                                                           [FAILED]

[root@ip-172-31-70-110 scripts]# systemctl status hue.service

? hue.service - SYSV: Hue web server

   Loaded: loaded (/etc/rc.d/init.d/hue)

   Active: failed (Result: resources) since Thu 2016-08-11 10:51:22 EDT; 8s ago

     Docs: man:systemd-sysv-generator(8)

  Process: 4966 ExecStart=/etc/rc.d/init.d/hue start (code=exited, status=0/SUCCESS)

 

Aug 11 10:51:22 pecos2 systemd[1]: Starting SYSV: Hue web server...

Aug 11 10:51:22 pecos2 hue[4966]: Starting hue: already running

Aug 11 10:51:22 pecos2 systemd[1]: PID file /usr/lib/hue/pids/supervisor.pid not readable (yet?) after start.

Aug 11 10:51:22 pecos2 systemd[1]: Failed to start SYSV: Hue web server.

Aug 11 10:51:22 pecos2 systemd[1]: Unit hue.service entered failed state.

Aug 11 10:51:22 pecos2 systemd[1]: hue.service failed.

[root@ip-172-31-70-110 scripts]# ps -ef | egrep hue

hue       2411     1  0 10:06 ?        00:00:00 python2.7 /usr/lib/hue/build/env/bin/supervisor -p /var/run/hue/supervisor.pid -l /var/log/hue -d

hue       2417  2411  0 10:06 ?        00:00:03 python2.7 /usr/lib/hue/build/env/bin/hue runcherrypyserver

root      4980  3015  0 10:51 pts/0    00:00:00 grep -E --color=auto hue

[root@ip-172-31-70-110 scripts]# kill -9 2411 2417

[root@ip-172-31-70-110 scripts]# ps -ef | egrep hue

root      4984  3015  0 10:52 pts/0    00:00:00 grep -E --color=auto hue

[root@ip-172-31-70-110 scripts]# sudo service hue start

Starting hue (via systemctl):  Job for hue.service failed because a configured resource limit was exceeded. See "systemctl status hue.service" and "journalctl -xe" for details.

                                                           [FAILED]

[root@ip-172-31-70-110 scripts]# systemctl status hue.service

? hue.service - SYSV: Hue web server

   Loaded: loaded (/etc/rc.d/init.d/hue)

   Active: failed (Result: resources) since Thu 2016-08-11 10:52:14 EDT; 8s ago

     Docs: man:systemd-sysv-generator(8)

  Process: 5009 ExecStart=/etc/rc.d/init.d/hue start (code=exited, status=0/SUCCESS)

 

Aug 11 10:52:09 pecos2 systemd[1]: Starting SYSV: Hue web server...

Aug 11 10:52:09 pecos2 su[5018]: (to hue) root on none

Aug 11 10:52:14 pecos2 hue[5009]: Starting hue: [  OK  ]

Aug 11 10:52:14 pecos2 systemd[1]: PID file /usr/lib/hue/pids/supervisor.pid not readable (yet?) after start.

Aug 11 10:52:14 pecos2 systemd[1]: Failed to start SYSV: Hue web server.

Aug 11 10:52:14 pecos2 systemd[1]: Unit hue.service entered failed state.

Aug 11 10:52:14 pecos2 systemd[1]: hue.service failed.

[root@ip-172-31-70-110 scripts]# journalctl -xe

-- Unit user-977.slice has begun starting up.

Aug 11 10:52:09 pecos2 systemd[1]: Started Session c8 of user hue.

-- Subject: Unit session-c8.scope has finished start-up

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit session-c8.scope has finished starting up.

--

-- The start-up result is done.

Aug 11 10:52:09 pecos2 systemd[1]: Starting Session c8 of user hue.

-- Subject: Unit session-c8.scope has begun start-up

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit session-c8.scope has begun starting up.

Aug 11 10:52:09 pecos2 su[5018]: pam_unix(su:session): session opened for user hue by (uid=0)

Aug 11 10:52:09 pecos2 su[5018]: pam_unix(su:session): session closed for user hue

Aug 11 10:52:14 pecos2 hue[5009]: Starting hue: [  OK  ]

Aug 11 10:52:14 pecos2 systemd[1]: PID file /usr/lib/hue/pids/supervisor.pid not readable (yet?) after start.

Aug 11 10:52:14 pecos2 systemd[1]: Failed to start SYSV: Hue web server.

-- Subject: Unit hue.service has failed

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit hue.service has failed.

--

-- The result is failed.

Aug 11 10:52:14 pecos2 systemd[1]: Unit hue.service entered failed state.

Aug 11 10:52:14 pecos2 systemd[1]: hue.service failed.

Aug 11 10:52:14 pecos2 polkitd[539]: Unregistered Authentication Agent for unix-process:5004:275752 (system bus name :1.54, object path /org/freedesktop/Po

 

On /var/log/hue/

[17/Aug/2016 12:06:37 -0700] __init__     WARNING  Couldn't import snappy. Support for snappy compression disabled.

[18/Aug/2016 11:03:17 ] settings     INFO     Welcome to Hue 3.9.0

[18/Aug/2016 08:03:19 -0700] __init__     WARNING  Couldn't import snappy. Support for snappy compression disabled.

[18/Aug/2016 12:31:26 ] settings     INFO     Welcome to Hue 3.9.0

[18/Aug/2016 09:31:26 -0700] __init__     WARNING  Couldn't import snappy. Support for snappy compression disabled.

 

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Hue Error on startup

Explorer

Probably the earlier problem was related to the MySQL not been accessible over the network. The security group setting had the correct setting, but something else was preventing mySQL from talking to the they Hue installation.

 

Followed the procedure from this website: https://techwisdom.wordpress.com/2016/04/28/installing-and-configuring-hue/

 

Thank you.

Sudha K

View solution in original post

7 REPLIES 7

Re: Hue Error on startup

Explorer

The error is :

Aug 11 10:06:36 ip-172-31-70-110.ec2.internal systemd[1]: PID file /usr/lib/hue/pids/supervisor.pid not readable (yet?) after start.

----------------

however, I don't see this directory ../pid/supervisor.pid under /usr/lib/hue.

 

 

Re: Hue Error on startup

Which OS are you using?


FYI CDH5.8 has Hue 3.10 too

Re: Hue Error on startup

Explorer

OS is linux - RHEL 1.7

 

Also the CDH version is 5.7

Hue version 3.9.

 

Re: Hue Error on startup

Explorer

hello,

 

Another question is that Hue is installed on node 2 ( and configured to use external DB mySQL - which sits on the node1).

Should I open up any firewall rules for 3306 on the security group ( on AWS).

 

 

Re: Hue Error on startup

On AWS make sure

"

Then configure the security group like below. We allow everything between
the instances (the first row, don’t forget it on multi machine cluster!)
and open up Cloudera Manager and Hue ports to the outside.

All TCP

TCP

0 – 65535

sg-e2db7777 (hue-demo)

SSH

TCP

22

0.0.0.0/0

Custom TCP Rule

TCP

7180

0.0.0.0/0

Custom TCP Rule

TCP

8888

0.0.0.0/0

Custom ICMP Rule

Echo Reply

N/A

0.0.0.0/0
"

http://gethue.com/hadoop-tutorial-how-to-create-a-real-hadoop-cluster-in-10-minutes/

Re: Hue Error on startup

Explorer

The error was solved when I unistalled and re-installed HUE with all the plug-ins ( ).

This time around I used the internal DB that came with HUE.

+ changed the ownership for Hue folders to be owned by userID ' hue' - and this did the trick.

 

Re: Hue Error on startup

Explorer

Probably the earlier problem was related to the MySQL not been accessible over the network. The security group setting had the correct setting, but something else was preventing mySQL from talking to the they Hue installation.

 

Followed the procedure from this website: https://techwisdom.wordpress.com/2016/04/28/installing-and-configuring-hue/

 

Thank you.

Sudha K

View solution in original post