Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minikube lenses example bundled in the repo doesn't work #27

Open
ValentinFlorea opened this issue Jan 6, 2020 · 0 comments
Open

Minikube lenses example bundled in the repo doesn't work #27

ValentinFlorea opened this issue Jan 6, 2020 · 0 comments

Comments

@ValentinFlorea
Copy link

I'm trying to run Lenses in Minikube. After following the instructions https://github.com/lensesio/lenses-docker/tree/master/_examples I got no error and both pods are running.

The problem is that no http listener is running on the lenses pod (getting a 404 response in browser).

kubectl logs -f pods/lenses` produces:

2020-01-06 13:54:01,060 INFO [k.u.Log4jControllerRegistration$:31] Registered kafka:type=kafka.Log4jController MBean
2020-01-06 13:54:01,089 INFO [k.z.ZooKeeperClient:66] [ZooKeeperClient] Initializing a new session to kafka:2181/.
2020-01-06 13:54:01,118 INFO [k.z.ZooKeeperClient:66] [ZooKeeperClient] Waiting until connected.
2020-01-06 13:54:01,139 INFO [k.z.ZooKeeperClient:66] [ZooKeeperClient] Connected.
2020-01-06 13:54:01,168 INFO [i.l.r.H2ConnectionBuilder$:27] Setting the local storage to [/data/storage]
2020-01-06 13:54:01,168 INFO [i.l.r.H2ConnectionBuilder$:27] Setting the local storage to [/data/storage]
2020-01-06 13:54:01,169 INFO [i.l.r.H2ConnectionBuilder$:43] Opening the storage to lensesdb...
2020-01-06 13:54:02,052 INFO [i.l.r.H2ConnectionBuilder$:27] Setting the local storage to [/data/storage]
2020-01-06 13:54:02,053 INFO [i.l.r.H2ConnectionBuilder$:43] Opening the storage to lensesdb...
2020-01-06 13:54:02,081 INFO [i.l.r.H2ConnectionBuilder$:27] Setting the local storage to [/data/storage]
2020-01-06 13:54:02,082 INFO [i.l.r.H2ConnectionBuilder$:43] Opening the storage to lensesdb...
2020-01-06 13:54:04,616 INFO [c.z.h.HikariDataSource:110] HikariPool-1 - Starting...
2020-01-06 13:54:04,633 INFO [c.z.h.HikariDataSource:123] HikariPool-1 - Start completed.
2020-01-06 13:54:05,043 INFO [i.l.c.k.ConnectClustersTopicValidation$:25] Validating Connect cluster topics...
2020-01-06 13:56:05,448 ERROR [c.l.k.l.Main$:159] Uncaught exception on Thread[main,5,main]
java.util.concurrent.TimeoutException: null
at org.apache.kafka.common.internals.KafkaFutureImpl$SingleWaiter.await(KafkaFutureImpl.java:108)
at org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:274)
at io.lenses.core.kafka.ConnectClustersTopicValidation$.apply(ConnectClustersTopicValidation.scala:33)
at com.landoop.kafka.lenses.Main$.$anonfun$new$2(Main.scala:225)
at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:23)
at io.lenses.domain.logging.MetricsSupport.timed(MetricsSupport.scala:18)
at io.lenses.domain.logging.MetricsSupport.timed$(MetricsSupport.scala:16)
at com.landoop.kafka.lenses.Main$.timed(Main.scala:148)
at com.landoop.kafka.lenses.Main$.delayedEndpoint$com$landoop$kafka$lenses$Main$1(Main.scala:224)
at com.landoop.kafka.lenses.Main$delayedInit$body.apply(Main.scala:148)
at scala.Function0.apply$mcV$sp(Function0.scala:39)
at scala.Function0.apply$mcV$sp$(Function0.scala:39)
at scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:17)
at scala.App.$anonfun$main$1$adapted(App.scala:80)
at scala.collection.immutable.List.foreach(List.scala:392)
at scala.App.main(App.scala:80)
at scala.App.main$(App.scala:78)
at com.landoop.kafka.lenses.Main$.main(Main.scala:148)
at com.landoop.kafka.lenses.Main.main(Main.scala)

So it seems that Lenses cannot connect properly to the kafka pod (even though it seems to succeed connecting to the Zookeeper).

When I'm checking out the kubectl logs -f pods/kafkagroup I see that the pod services seem to start properly but then they restart evey few minutes

2020-01-06 13:53:09,856 INFO success: running-sample-data-telecom-italia entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-01-06 13:53:09,856 INFO success: schema-registry entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-01-06 13:53:09,856 INFO success: smoke-tests entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-01-06 13:53:09,856 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-01-06 13:55:17,425 INFO exited: schema-registry (exit status 1; not expected)
2020-01-06 13:55:17,735 INFO spawned: 'schema-registry' with pid 2521
2020-01-06 13:55:19,161 INFO success: schema-registry entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-01-06 13:56:22,718 INFO exited: running-sample-data-ais (exit status 1; not expected)
2020-01-06 13:56:22,960 INFO exited: running-sample-data-taxis (exit status 1; not expected)
2020-01-06 13:56:28,951 INFO exited: running-sample-data-telecom-italia (exit status 1; not expected)
2020-01-06 13:57:22,719 INFO exited: schema-registry (exit status 1; not expected)
2020-01-06 13:57:22,723 INFO spawned: 'schema-registry' with pid 5805
2020-01-06 13:57:23,761 INFO success: schema-registry entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-01-06 13:58:10,014 INFO exited: logs-to-kafka (exit status 0; expected)
2020-01-06 13:59:27,411 INFO exited: schema-registry (exit status 1; not expected)
2020-01-06 13:59:27,479 INFO spawned: 'schema-registry' with pid 6729
2020-01-06 13:59:28,513 INFO success: schema-registry entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-01-06 13:59:34,563 INFO exited: connect-distributed (exit status 2; not expected)
2020-01-06 13:59:34,569 INFO spawned: 'connect-distributed' with pid 6761
2020-01-06 13:59:35,593 INFO success: connect-distributed entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

Am I doing something wrong?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant