Uploaded image for project: 'Zeppelin'
  1. Zeppelin
  2. ZEPPELIN-3620

zeppelin process died when using kubernetes containers

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 0.7.0
    • Fix Version/s: 0.7.0
    • Component/s: zeppelin-server
    • Labels:
      None
    • Environment:

      Description

      when I deploy a kubernetes service using this docker image: https://hub.docker.com/r/cthiebault/zeppelin-mongodb/

      the container failed, showing up this message:
       

      Zeppelin start [ OK ] Zeppelin process died [FAILED]

       
      I found zeppelin/logs here:

      ZEPPELIN_CLASSPATH: ::/opt/zeppelin/lib/interpreter/*:/opt/zeppelin/lib/*:/opt/zeppelin/*::/opt/zeppelin/conf
      SLF4J: Class path contains multiple SLF4J bindings.
      SLF4J: Found binding in [jar:file:/opt/zeppelin/lib/interpreter/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
      SLF4J: Found binding in [jar:file:/opt/zeppelin/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
      SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
      SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
      Exception in thread "main" java.lang.NumberFormatException: For input string: "tcp://10.43.25.163:8080"
      at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
      at java.lang.Integer.parseInt(Integer.java:492)
      at java.lang.Integer.parseInt(Integer.java:527)
      at org.apache.zeppelin.conf.ZeppelinConfiguration.getInt(ZeppelinConfiguration.java:213)
      at org.apache.zeppelin.conf.ZeppelinConfiguration.getInt(ZeppelinConfiguration.java:208)
      at org.apache.zeppelin.conf.ZeppelinConfiguration.getServerPort(ZeppelinConfiguration.java:283)
      at org.apache.zeppelin.conf.ZeppelinConfiguration.create(ZeppelinConfiguration.java:111)
      at org.apache.zeppelin.server.ZeppelinServer.main(ZeppelinServer.java:156)
      

       
      but if I just use docker CLI to run this image, everything is OK.
       
       
       

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              im_wower george
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: