Also, this could be a bug. So, you need to clarify which "some plugins" you
upgraded. Because if all was fine until now, then there may be some bug
somewhere. Or maybe not if you were already close to the ulimit max without
knowing it for some time. But impossible to tell from here.

2017-04-13 10:23 GMT+02:00 Victor Martinez <[email protected]>:

> Hi there,
>
> You could read the below blog entry:
> - https://support.cloudbees.com/hc/en-us/articles/
> 204246140-Too-many-open-files
>
> Although it's the cloudbees support page, but it's the same core in the
> end.
>
> In my case,
>
> # ulimit -a
> ....
>
> open files                      (-n) 65536
> ....
>
> Cheers
>
>
> On Thursday, 13 April 2017 08:37:42 UTC+1, David Aldrich wrote:
>>
>> Hi
>>
>>
>>
>> Since updating some plugins we are getting lots of “Too many open files”
>> warnings. Here’s an example:
>>
>>
>>
>> Apr 12, 2017 9:38:35 PM WARNING org.eclipse.jetty.util.log.JavaUtilLog
>> warn
>>
>> java.io.IOException: Too many open files
>>
>>         at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
>>
>>         at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChanne
>> lImpl.java:241)
>>
>>         at org.eclipse.jetty.server.ServerConnector.accept(ServerConnec
>> tor.java:377)
>>
>>         at org.eclipse.jetty.server.AbstractConnector$Acceptor.run(
>> AbstractConnector.java:500)
>>
>>         at winstone.BoundedExecutorService$1.run(BoundedExecutorService
>> .java:77)
>>
>>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>> Executor.java:1145)
>>
>>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>> lExecutor.java:615)
>>
>>         at java.lang.Thread.run(Thread.java:745)
>>
>>
>>
>> I know that there is a File Leak Detector plugin but such investigation
>> seems quite involved.
>>
>>
>>
>> On the master, we have:
>>
>>
>>
>> $ ulimit -a
>>
>> <snip>
>>
>> open files                      (-n) 1024
>>
>>
>>
>> Should 1024 be sufficient?  Do I need to worry about limits on the
>> slaves?
>>
>>
>>
>> Any other suggestions please?  I don’t know why these warnings have
>> suddenly appeared.
>>
>>
>>
>> Best regards
>>
>>
>>
>> David
>>
>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/31f1b754-6366-4545-8dd3-68bf6df2c12f%40googlegroups.
> com
> <https://groups.google.com/d/msgid/jenkinsci-users/31f1b754-6366-4545-8dd3-68bf6df2c12f%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS4dZpJiKwPfZNk6Ta6if_ybtOPSVXffEMoQ3RGXypAmig%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to