Is this possibly caused by CDH requiring a build-from-source instead of the official binary releases?
On Thu, Jul 7, 2016 at 8:22 PM -0700, "Benjamin Kim" <bbuil...@gmail.com<mailto:bbuil...@gmail.com>> wrote: Moon, My environmental setup consists of an 18 node CentOS 6.7 cluster with 24 cores, 64GB, 12TB storage each: * 3 of those nodes are used as Zookeeper servers, HDFS name nodes, and a YARN resource manager * 15 are for data nodes * jdk1.8_60 and CDH 5.7.1 installed Another node is an app server, 24 cores, 128GB memory, 1TB storage. It has Zeppelin 0.6.0 and Livy 0.2.0 running on it. Plus, Hive Metastore and HiveServer2, Hue, and Oozie are running on it from CDH 5.7.1. This is our QA cluster where we are testing before deploying to production. If you need more information, please let me know. Thanks, Ben On Jul 7, 2016, at 7:54 PM, moon soo Lee <m...@apache.org<mailto:m...@apache.org>> wrote: Randy, Helium is not included in 0.6.0 release. Could you check which version are you using? I created a fix for 500 errors from Helium URL in master branch. https://github.com/apache/zeppelin/pull/1150 Ben, I can not reproduce the error, could you share how to reproduce error, or share your environment? Thanks, moon On Thu, Jul 7, 2016 at 4:02 PM Randy Gelhausen <rgel...@gmail.com<mailto:rgel...@gmail.com>> wrote: I don't- I hoped providing that information may help finding & fixing the problem. On Thu, Jul 7, 2016 at 5:53 PM, Benjamin Kim <bbuil...@gmail.com<mailto:bbuil...@gmail.com>> wrote: Hi Randy, Do you know of any way to fix it or know of a workaround? Thanks, Ben On Jul 7, 2016, at 2:08 PM, Randy Gelhausen <rgel...@gmail.com<mailto:rgel...@gmail.com>> wrote: HTTP 500 errors from a Helium URL
