[JIRA] (JENKINS-61121) Too many open files when using Resource root URL

21 views
Skip to first unread message

ingwar@ingwar.eu.org (JIRA)

unread,
Feb 18, 2020, 5:13:03 AM2/18/20
to jenkinsc...@googlegroups.com
Karol Lassak created an issue
 
Jenkins / Bug JENKINS-61121
Too many open files when using Resource root URL
Issue Type: Bug Bug
Assignee: Unassigned
Components: core
Created: 2020-02-18 10:12
Environment: Jenkins: 2.204.2
OS: Linux
Java: 8
Plugins: Simple Theme Plugin
Labels: resource-root-url simplethemeplugin
Priority: Minor Minor
Reporter: Karol Lassak

Last week I changed our jenkins instance (big one) to using Resource root URL, and since then we had one big crash because of cannot open more files error.

We are using Simple Theme Plugin with Extra CSS file pointing to userContent/styles.css file..
And I see that on OS level this styles.css file is opened more than 900 times.. (increasing with each new session I assume)
That files are never closing..

I was first thinking about bug in Simple Theme Plugin but it just adds code to download that css file.. so I assume bug is in code in Resource root URL implementation (that css is now read via that new redirection)

 

Changing to Inline CSS and fixes the problem, but I assume it may manifest in much more places...

 
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

ingwar@ingwar.eu.org (JIRA)

unread,
Feb 18, 2020, 5:19:02 AM2/18/20
to jenkinsc...@googlegroups.com
Karol Lassak updated an issue
Change By: Karol Lassak
Last week I changed our jenkins instance (big one) to using {{Resource root URL}}, and since then we had one big crash because of {{cannot open more files}} error.


We are using {{Simple Theme Plugin}} with {{Extra CSS}} file pointing to {{userContent/styles.css}} file..
And I see that on OS level this styles.css file is opened more than 900 times.. (increasing with each new session I assume)
That files are never closing..

I was first thinking about bug in {{Simple Theme Plugin}} but it just adds code to download that css file.. so I assume bug is in code in {{Resource root URL}} implementation (that css is now read via that new redirection)

 

Changing to {{Inline CSS}} and fixes the problem, but I assume it may manifest in much more places...

 

 

 

ingwar@ingwar.eu.org (JIRA)

unread,
Feb 18, 2020, 5:19:03 AM2/18/20
to jenkinsc...@googlegroups.com

ingwar@ingwar.eu.org (JIRA)

unread,
Feb 18, 2020, 6:57:02 AM2/18/20
to jenkinsc...@googlegroups.com
Karol Lassak updated an issue
Last week I changed our jenkins instance (big one) to using {{Resource root URL}}, and since then we had one big crash because of {{cannot open more files}} error.

We are using {{Simple Theme Plugin}} with {{Extra CSS}} file pointing to {{userContent/styles.css}} file..
And I see that on OS level this styles.css file is opened more than 900 times.. (increasing with each new session I assume)
That files are never closing..

I was first thinking about bug in {{Simple Theme Plugin}} but it just adds code to download that css file.. so I assume bug is in code in {{Resource root URL}} implementation (that css is now read via that new redirection)

 

Changing to {{Inline CSS}} and fixes the problem, but I assume it may manifest in much more places...

 
Extra data:

Every request ro url redirected to `resource URL root` ends up never closing.

We are using nginx reverse proxy, im trying to investigate it that may be issue..

  

 

 

 

wfollonier@cloudbees.com (JIRA)

unread,
Feb 18, 2020, 8:06:02 AM2/18/20
to jenkinsc...@googlegroups.com

dbeck@cloudbees.com (JIRA)

unread,
Feb 18, 2020, 8:12:04 AM2/18/20
to jenkinsc...@googlegroups.com
Daniel Beck updated an issue
 
Change By: Daniel Beck
Labels: lts-candidate resource-root-url simplethemeplugin

dbeck@cloudbees.com (JIRA)

unread,
Feb 18, 2020, 8:19:03 AM2/18/20
to jenkinsc...@googlegroups.com

Every request ro url redirected to `resource URL root` ends up never closing.

Could you clarify what that means?

When I try to access a file in /userContent, it quickly returns:

$ curl --location -i http://localhost:8080/userContent/readme.txt
HTTP/1.1 302 Found
Date: Tue, 18 Feb 2020 13:17:27 GMT
X-Content-Type-Options: nosniff
Location: http://127.0.0.1:8080/static-files/7VrrCoWq4mzHbJJL3IpSLVJy4MKfIu5SkHrStDHQ9IoxNTgyMDMxODQ3Mjg4Ojk6YW5vbnltb3VzOnVzZXJDb250ZW50/readme.txt
Content-Length: 0
Server: Jetty(9.4.25.v20191220)

HTTP/1.1 200 OK
Date: Tue, 18 Feb 2020 13:17:27 GMT
X-Content-Type-Options: nosniff
Last-Modified: Tue, 18 Feb 2020 10:27:45 GMT
Expires: Tue, 18 Feb 2020 10:27:45 GMT
Accept-Ranges: bytes
Content-Type: text/plain
Content-Length: 82
Server: Jetty(9.4.25.v20191220)

Files in this directory will be served under your http://yourjenkins/userContent/

dbeck@cloudbees.com (JIRA)

unread,
Feb 18, 2020, 8:38:04 AM2/18/20
to jenkinsc...@googlegroups.com
Daniel Beck started work on Bug JENKINS-61121
 
Change By: Daniel Beck
Status: Open In Progress

dbeck@cloudbees.com (JIRA)

unread,
Feb 18, 2020, 8:38:04 AM2/18/20
to jenkinsc...@googlegroups.com

Found it.

dbeck@cloudbees.com (JIRA)

unread,
Feb 18, 2020, 8:38:05 AM2/18/20
to jenkinsc...@googlegroups.com
Daniel Beck assigned an issue to Daniel Beck
 
Change By: Daniel Beck
Assignee: Daniel Beck

dbeck@cloudbees.com (JIRA)

unread,
Feb 18, 2020, 8:50:04 AM2/18/20
to jenkinsc...@googlegroups.com
Change By: Daniel Beck
Status: In Progress Review

dbeck@cloudbees.com (JIRA)

unread,
Feb 21, 2020, 6:49:03 AM2/21/20
to jenkinsc...@googlegroups.com
Change By: Daniel Beck
Status: In Review Fixed but Unreleased
Resolution: Fixed
Released As: 2.222

o.v.nenashev@gmail.com (JIRA)

unread,
Feb 24, 2020, 7:55:04 AM2/24/20
to jenkinsc...@googlegroups.com
Change By: Oleg Nenashev
Status: Fixed but Unreleased Resolved

dbeck@cloudbees.com (JIRA)

unread,
Feb 27, 2020, 5:19:02 PM2/27/20
to jenkinsc...@googlegroups.com
 
Re: Too many open files when using Resource root URL

Keeping this labeled as lts-candidate in case something's wrong with 2.222.
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages