search

timja / jenkins-gh-issues-poc-06-18

0 stars 0 forks source link

[JENKINS-11364] Low memory debian systems cause IOException: No space left on device #6856

Open timja opened 12 years ago

timja commented 12 years ago

As on newer debian systems /run is now tmpvfs based and allocated to 10% of memory the jenkins startup fails on low-memory systems (512MB ram).

[Winstone 2011/10/16 13:38:21] - Beginning extraction from war file
[Winstone 2011/10/16 13:38:23] - Error initializing web application: prefix []
java.io.IOException: No space left on device
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:282)
at winstone.HostConfiguration.getWebRoot(HostConfiguration.java:273)
at winstone.HostConfiguration.(HostConfiguration.java:73)
at winstone.HostGroup.initHost(HostGroup.java:85)
at winstone.HostGroup.(HostGroup.java:45)
at winstone.Launcher.(Launcher.java:197)
at winstone.Launcher.main(Launcher.java:398)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at Main._main(Main.java:268)
at Main.main(Main.java:96)

The mount command returns this:
none on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)

The df command returns this:
none 50M 50M 0 100% /run

I'm not sure about the best solution but jenkins seems by far the biggest user of /run, all other services together use about 10MB. Maybe jenkins could use a different folder to store it's extracted war?

A temporary fix for this would revert to the previous ubuntu behavior of keeping /run on disk but I have not found how to do this yet.

Originally reported by francisdb, imported from: Low memory debian systems cause IOException: No space left on device
  • status: Reopened
  • priority: Major
  • resolution: Unresolved
  • imported: 2022/01/10
timja commented 8 years ago

dwdyer:

There appears to have been a regression as this issue is re-occurring for me with recent versions. I'm not sure when it started again but it was a problem when I updated a month or so ago and it's still a problem with 1.635. The WAR is being extracted to /run and filling it up, preventing Jenkins from starting.

timja commented 2 years ago

[Duplicates: JENKINS-11366]