Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

SocketTimeoutException on NiFi startup #108

Closed
novakov-alexey-zz opened this issue Dec 4, 2020 · 4 comments
Closed

SocketTimeoutException on NiFi startup #108

novakov-alexey-zz opened this issue Dec 4, 2020 · 4 comments
Labels
bug Something isn't working duplicate This issue or pull request already exists

Comments

@novakov-alexey-zz
Copy link
Contributor

Describe the bug
NiFi cluster does not start normally, so that NiFi UI opens with an error:

app-log has such exception thrown infinitely:

 java.net.SocketTimeoutException: timeout                                                                                                                                                                                                        at okio.Okio$4.newTimeoutException(Okio.java:232)
     at okio.AsyncTimeout.exit(AsyncTimeout.java:286)                                                                                                                                                                                            at okio.AsyncTimeout$2.read(AsyncTimeout.java:241)
     at okio.RealBufferedSource.indexOf(RealBufferedSource.java:358)                                                                                                                                                                             at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:230)
     at okhttp3.internal.http1.Http1ExchangeCodec.readHeaderLine(Http1ExchangeCodec.java:242)                                                                                                                                                    at okhttp3.internal.http1.Http1ExchangeCodec.readResponseHeaders(Http1ExchangeCodec.java:213)
     at okhttp3.internal.connection.Exchange.readResponseHeaders(Exchange.java:115)                                                                                                                                                              at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.java:94)
     at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:142)                                                                                                                                                        at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:43)
     at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:142)                                                                                                                                                        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:117)
     at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:94)                                                                                                                                                              at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:142)
     at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:117)                                                                                                                                                        at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
     at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:142)
     at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:88)
     at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:142)
     at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:117)
     at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:229)
     at okhttp3.RealCall.execute(RealCall.java:81)
     at org.apache.nifi.cluster.coordination.http.replication.okhttp.OkHttpReplicationClient.replicate(OkHttpReplicationClient.java:132)
     at org.apache.nifi.cluster.coordination.http.replication.okhttp.OkHttpReplicationClient.replicate(OkHttpReplicationClient.java:126)
     at org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator.replicateRequest(ThreadPoolRequestReplicator.java:647)
     at org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$NodeHttpRequest.run(ThreadPoolRequestReplicator.java:839)
     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
     at java.util.concurrent.FutureTask.run(FutureTask.java:266)
     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
     at java.lang.Thread.run(Thread.java:748)
 Caused by: java.net.SocketException: Socket closed
     at java.net.SocketInputStream.read(SocketInputStream.java:204)
     at java.net.SocketInputStream.read(SocketInputStream.java:141)
     at okio.Okio$2.read(Okio.java:140)
     at okio.AsyncTimeout$2.read(AsyncTimeout.java:237)
     ... 29 common frames omitted

Version of Helm and Kubernetes:
Helm charts v0.6.1
Kubernetes v1.18.8

What happened:
NiFi does not work. NiFi UI shows such error:

An unexpected error has occurred
home
{ "servlet":"jerseySpring", "message":"Service Unavailable", "url":"/nifi-api/flow/process-groups/root", "status":"503" }

What you expected to happen:
Cluster is formed. NiFi UI can be opened.

How to reproduce it (as minimally and precisely as possible):
Deploy with Helm charts 0.6.1 version

helm install nifi cetic/nifi --version 0.6.1

Anything else we need to know:
Helm chart 0.6.0 are working fine.

@novakov-alexey-zz novakov-alexey-zz mentioned this issue Dec 4, 2020
3 tasks
@novakov-alexey-zz
Copy link
Contributor Author

Any feedback on this issue? Does anybody use the latest Helm charts version 0.6.1?

@tunaman
Copy link
Contributor

tunaman commented Dec 22, 2020

Yeah same as issue #115. That one has a good description of what's causing this

@banzo banzo added duplicate This issue or pull request already exists bug Something isn't working labels Feb 11, 2021
@AyadiAmen AyadiAmen mentioned this issue Mar 2, 2021
3 tasks
@patsevanton
Copy link
Contributor

Hello! Same issue.

@AyadiAmen
Copy link
Contributor

#126

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

5 participants