[Question] WARN WatchConnectionManager:202 - Exec Failure: HTTP 404
See original GitHub issueWhile installing a fresh strimzi kafka operator v0.19.0, i am getting this error:
2020-09-30 06:14:03 INFO ClusterOperator:81 - Creating ClusterOperator for namespace kafka
2020-09-30 06:14:03 INFO ClusterOperator:98 - Starting ClusterOperator for namespace kafka
2020-09-30 06:14:03 WARN WatchConnectionManager:202 - Exec Failure: HTTP 404, Status: 404 - 404 page not found
java.net.ProtocolException: Expected HTTP 101 response but was '404 Not Found'
at okhttp3.internal.ws.RealWebSocket.checkResponse(RealWebSocket.java:229) [com.squareup.okhttp3.okhttp-3.12.6.jar:?]
at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:196) [com.squareup.okhttp3.okhttp-3.12.6.jar:?]
at okhttp3.RealCall$AsyncCall.execute(RealCall.java:203) [com.squareup.okhttp3.okhttp-3.12.6.jar:?]
at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) [com.squareup.okhttp3.okhttp-3.12.6.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:834) [?:?]
2020-09-30 06:14:03 INFO AbstractOperator:304 - Watcher closed in namespace kafka
Exception in thread "OkHttp Dispatcher" java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@22b97f30[Not completed, task = java.util.concurrent.Executors$RunnableAdapter@30a824d5[Wrapped task = io.fabric8.kubernetes.client.dsl.internal.WatchConnectionManager$2@50f6921e]] rejected from java.util.concurrent.ScheduledThreadPoolExecutor@46c51831[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0]
at java.base/java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2055)
at java.base/java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:825)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:340)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:562)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor.submit(ScheduledThreadPoolExecutor.java:715)
at java.base/java.util.concurrent.Executors$DelegatedExecutorService.submit(Executors.java:714)
at io.fabric8.kubernetes.client.dsl.internal.WatchConnectionManager.scheduleReconnect(WatchConnectionManager.java:318)
at io.fabric8.kubernetes.client.dsl.internal.WatchConnectionManager.access$800(WatchConnectionManager.java:50)
at io.fabric8.kubernetes.client.dsl.internal.WatchConnectionManager$1.onFailure(WatchConnectionManager.java:221)
at okhttp3.internal.ws.RealWebSocket.failWebSocket(RealWebSocket.java:571)
at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:198)
at okhttp3.RealCall$AsyncCall.execute(RealCall.java:203)
at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
2020-09-30 06:14:03 WARN WatchConnectionManager:202 - Exec Failure: HTTP 404, Status: 404 - 404 page not found
java.net.ProtocolException: Expected HTTP 101 response but was '404 Not Found'
at okhttp3.internal.ws.RealWebSocket.checkResponse(RealWebSocket.java:229) [com.squareup.okhttp3.okhttp-3.12.6.jar:?]
at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:196) [com.squareup.okhttp3.okhttp-3.12.6.jar:?]
at okhttp3.RealCall$AsyncCall.execute(RealCall.java:203) [com.squareup.okhttp3.okhttp-3.12.6.jar:?]
at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) [com.squareup.okhttp3.okhttp-3.12.6.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:834) [?:?]
2020-09-30 06:14:03 INFO AbstractOperator:304 - Watcher closed in namespace kafka
2020-09-30 06:14:03 WARN WatchConnectionManager:202 - Exec Failure: HTTP 404, Status: 404 - 404 page not found
Any help would be appreciated.
v0.18.0 works fine.
K8s version: v1.17.3
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
[Strimzi] Cluster-Operator 0.9.0 does not start due to ... - RedHat
... WARN WatchConnectionManager:185 - Exec Failure: HTTP 404, Status: 404 - 404 page not found java.net.ProtocolException: Expected HTTP 101 ...
Read more >Kubernetes WatchConnectionManager: Exec Failure: HTTP 403
This is happened in the Kubernetes v1.15.3, Kubernetes v1.14.6, Kubernetes v1.13.10 version, the project spark operator have a workaround ...
Read more >bug - Search OpenShift CI
#1994729 bug 15 months ago
#1955506 bug 15 months ago
#1805019 bug 2 years ago
#1915760 bug 21 months ago
Read more >[JENKINS-62061] Kubernetes plugins show Warning ...
124 ms 2020-04-27 08:20:44.904+0000 [id=2857] WARNING i.f.k.c.d.i.WatchConnectionManager$1#onFailure: Exec Failure java.util.concurrent.
Read more >[jira] [Updated] (SPARK-24227) Not able to submit spark job to ...
2018-05-09 17:28:19 WARN WatchConnectionManager:185 - Exec Failure: HTTP 401, Status: 401 - Unauthorized java.net.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This message normally means that the Custom Resource Definitions are not installed and the operator cannot watch for them. The best way to check them would be to do
kubectl get crds
. It looks like when you installed it, the CRDs did not get installed, so I think you should try to reinstall them.Thanks all, I’ll have a look at the missing CRDs.