Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2137
Thanks @FRosner reviewing the PR.
> ``` INFO [2017-03-15 10:41:22,547] ({main} Helium.java[loadConf]:114) -
Add helium local registry /usr/local/zeppelin/helium
> INFO [2017-03-15 10:41:22,548] ({main} Helium.java[loadConf]:111) - Add
helium online registry https://s3.amazonaws.com/helium-package/helium.json
> WARN [2017-03-15 10:41:22,552] ({main} Helium.java[loadConf]:122) -
/usr/local/zeppelin/conf/helium.json does not exists
> ERROR [2017-03-15 10:43:30,270] ({main}
HeliumOnlineRegistry.java[getAll]:73) - Connect to s3.amazonaws.com:443
[s3.amazonaws.com/52.216.82.43] failed: Connection timed out (Connection timed
out)
> ```
Zeppelin tries to download available helium package list (which is filtered
list of npm and maven registry). The new error is related with this process.
This is a bit different issue and let me try solve it in different PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
