The kafka project doesn't have an official web console so you might need to
open an issue on the github page of the project for the web console you are
using as they may not be closing connections and using up all of resources
regardless of what you have set, etc.... if you have the default setting
you may have to increase this value for the operating system if it is not a
bug in the client you are using. You can give
http://www.cyberciti.biz/faq/howto-linux-get-list-of-open-files/ a try to
ascertain which is the problem and/or do a ulimit -n on your machine and
see if the value = 1024 which is the default likely for your OS.

/*******************************************
 Joe Stein
 Founder, Principal Consultant
 Big Data Open Source Security LLC
 http://www.stealth.ly
 Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
********************************************/

On Fri, Jan 2, 2015 at 7:41 PM, Sa Li <sal...@gmail.com> wrote:

> Hi, all
>
> I am running kafka-web-console, I periodically getting such error and cause
> the UI down:
>
>
>
> ! @6kldaf9lj - Internal server error, for (GET)
> [/assets/images/zookeeper_small.gif] ->
> play.api.Application$$anon$1: Execution exception[[FileNotFoundException:
>
> /vagrant/kafka-web-console-master/target/scala-2.10/classes/public/images/zookeeper_small.gif
> (Too many open files)]]
>         at play.api.Application$class.handleError(Application.scala:293)
> ~[play_2.10-2.2.1.jar:2.2.1]
>         at play.api.DefaultApplication.handleError(Application.scala:399)
> [play_2.10-2.2.1.jar:2.2.1]
>         at
>
> play.core.server.netty.PlayDefaultUpstreamHandler$$anonfun$12$$anonfun$apply$1.applyOrElse(PlayDefaultUpstreamHandler.scala:165)
> [play_2.10-2.2.1.jar:2.2.1]
>         at
>
> play.core.server.netty.PlayDefaultUpstreamHandler$$anonfun$12$$anonfun$apply$1.applyOrElse(PlayDefaultUpstreamHandler.scala:162)
> [play_2.10-2.2.1.jar:2.2.1]
>         at
>
> scala.runtime.AbstractPartialFunction.apply(AbstractPartialFunction.scala:33)
> [scala-library-2.10.2.jar:na]
>         at scala.util.Failure$$anonfun$recover$1.apply(Try.scala:185)
> [scala-library-2.10.2.jar:na]
> Caused by: java.io.FileNotFoundException:
>
> /vagrant/kafka-web-console-master/target/scala-2.10/classes/public/images/zookeeper_small.gif
> (Too many open files)
>         at java.io.FileInputStream.open(Native Method) ~[na:1.7.0_65]
>         at java.io.FileInputStream.<init>(FileInputStream.java:146)
> ~[na:1.7.0_65]
>         at java.io.FileInputStream.<init>(FileInputStream.java:101)
> ~[na:1.7.0_65]
>         at
>
> sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
> ~[na:1.7.0_65]
>         at
>
> sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
> ~[na:1.7.0_65]
>         at java.net.URL.openStream(URL.java:1037) ~[na:1.7.0_65]
>
> [debug] application - Getting partition offsets for topic ui_test_topic_6
> [warn] application - Could not connect to partition leader
> exemplary-birds.master:9092. Error message: Failed to open a socket.
> [debug] application - Getting partition offsets for topic ui_test_topic_5
> [warn] application - Could not connect to partition leader
> exemplary-birds.master:9092. Error message: Failed to open a socket.
> [warn] application - Could not connect to partition leader
> harmful-jar.master:9092. Error message: Failed to open a socket.
> [warn] application - Could not connect to partition leader
> voluminous-mass.master:9092. Error message: Failed to open a socket.
> [warn] application - Could not connect to partition leader
> voluminous-mass.master:9092. Error message: Failed to open a socket.
> [warn] application - Could not connect to partition leader
> exemplary-birds.master:9092. Error message: Failed to open a socket.
> [warn] application - Could not connect to partition leader
> exemplary-birds.master:9092. Error message: Failed to open a socket.
> [warn] application - Could not connect to partition leader
> harmful-jar.master:9092. Error message: Failed to open a socket.
> [warn] application - Could not connect to partition leader
> harmful-jar.master:9092. Error message: Failed to open a socket.
> [warn] application - Could not connect to partition leader
> voluminous-mass.master:9092. Error message: Failed to open a socket.
> [warn] application - Could not connect to partition leader
> voluminous-mass.master:9092. Error message: Failed to open a socket.
> [warn] application - Could not connect to partition leader
> exemplary-birds.master:9092. Error message: Failed to open a socket.
> [warn] application - Could not connect to partition leader
> harmful-jar.master:9092. Error message: Failed to open a socket.
> [warn] application - Could not connect to partition leader
> exemplary-birds.master:9092. Error message: Failed to open a socket.
> [debug] application - Getting partition offsets for topic PofApiTest
> [warn] application - Could not connect to partition leader
> harmful-jar.master:9092. Error message: Failed to open a socket.
> [warn] application - Could not connect to partition leader
> voluminous-mass.master:9092. Error message: Failed to open a socket.
> [warn] application - Could not connect to partition leader
> exemplary-birds.master:9092. Error message: Failed to open a socket.
> [debug] application - Getting partition offsets for topic ui_test_topic_4
>
>
> What that means too many files open, is that mean the insufficient local
> memory?
>
> thanks
>
> --
>
> Alec Li
>

Reply via email to