Hi Managed to figure this out, turns out the server running Jenkins ran into a file system problem and the root filesystem was remounted read-only. FIxing the file system problem got things running again.
Cheers Adam On Sun, Jul 6, 2014 at 11:00 AM, Adam Mercer <[email protected]> wrote: > Hi > > This morning one of my builds slaves was reporting that both it's > executors were Dead and reported traces such as: > > java.io.IOException: Failed to create a temporary file in > /var/lib/jenkins/jobs/PyLAL_Epydoc > at hudson.util.AtomicFileWriter.<init>(AtomicFileWriter.java:67) > at hudson.util.AtomicFileWriter.<init>(AtomicFileWriter.java:54) > at hudson.util.TextFile.write(TextFile.java:84) > at hudson.model.Job.saveNextBuildNumber(Job.java:266) > at hudson.model.Job.assignBuildNumber(Job.java:323) > at hudson.model.Run.<init>(Run.java:289) > at hudson.model.AbstractBuild.<init>(AbstractBuild.java:177) > at hudson.model.Build.<init>(Build.java:92) > at hudson.model.FreeStyleBuild.<init>(FreeStyleBuild.java:34) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:534) > at hudson.model.AbstractProject.newBuild(AbstractProject.java:1127) > at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1349) > at hudson.model.AbstractProject.createExecutable(AbstractProject.java:156) > at hudson.model.Executor.run(Executor.java:211) > Caused by: java.io.IOException: Read-only file system > at java.io.UnixFileSystem.createFileExclusively(Native Method) > at java.io.File.checkAndCreate(File.java:1833) > at java.io.File.createTempFile0(File.java:1857) > at java.io.File.createTempFile(File.java:1934) > at hudson.util.AtomicFileWriter.<init>(AtomicFileWriter.java:65) > ... 16 more > > Looking in the log I get the following extra information: > > Jul 06, 2014 10:40:12 AM SEVERE > hudson.remoting.SynchronousCommandTransport$ReaderThread run > > I/O error in channel MacOSX > java.io.IOException: Unexpected termination of the channel > at > hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) > Caused by: java.io.EOFException > at > java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2596) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1317) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369) > at hudson.remoting.Command.readFrom(Command.java:92) > at > hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71) > at > hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) > > The first stack track is complaining about being unable to write in > /var/lib/jenkins/jobs/PyLAL_Epydoc, is this on the server or the > slave? The slave is a Mac OS X machine and the jenkins user's home > directory is /Users/jenkins so I'm a little confused as to why is > trying to write in that directory? > > Disconnecting and reconnecting the box results in the same issue, as > does rebooting the slave. > > How can I get more information as to what is going wrong with this box? > > Cheers > > Adam -- 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]. For more options, visit https://groups.google.com/d/optout.
