[Issue 3380] New - Reboot of slavesystem does not take slave offline

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Issue 3380] New - Reboot of slavesystem does not take slave offline

cbos
https://hudson.dev.java.net/issues/show_bug.cgi?id=3380
                 Issue #|3380
                 Summary|Reboot of slavesystem does not take slave offline
               Component|hudson
                 Version|current
                Platform|All
              OS/Version|All
                     URL|
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P1
            Subcomponent|core
             Assigned to|issues@hudson
             Reported by|cbos






------- Additional comments from [hidden email] Mon Mar 30 08:34:27 +0000 2009 -------
If you shutdown/reboot a windows 2003 server with that slave installed as
service the master still thinks the slave is online.
This is related to 2566.

After the reboot the service on the windows2003 is not started. So the slave is
still offline. But the master acts if it is online.
The master is not up to date on the status of the slaves.

When you execute a task on that slave you get:

FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException:
Connection reset
hudson.remoting.RequestAbortedException:
hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset
        at hudson.remoting.Request.call(Request.java:131)
        at hudson.remoting.Channel.call(Channel.java:481)
        at hudson.FilePath.act(FilePath.java:427)
        at hudson.FilePath.mkdirs(FilePath.java:482)
        at hudson.model.AbstractProject.checkout(AbstractProject.java:799)
        at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:314)
        at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:266)
        at hudson.model.Run.run(Run.java:896)
        at hudson.model.Build.run(Build.java:112)
        at hudson.model.ResourceController.execute(ResourceController.java:93)
        at hudson.model.Executor.run(Executor.java:119)
Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException:
Connection reset
        at hudson.remoting.Request.abort(Request.java:223)
        at hudson.remoting.Channel.terminate(Channel.java:528)
        at hudson.remoting.Channel$ReaderThread.run(Channel.java:684)
Caused by: java.net.SocketException: Connection reset
        at java.net.SocketInputStream.read(SocketInputStream.java:168)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
        at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2247)
        at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2540)
        at
java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2550)
        at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297)
        at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
        at hudson.remoting.Channel$ReaderThread.run(Channel.java:665)

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Issue 3380] Reboot of slavesystem does not take slave offline

Kohsuke Kawaguchi
Administrator
https://hudson.dev.java.net/issues/show_bug.cgi?id=3380



User kohsuke changed the following:

                What    |Old value                 |New value
================================================================================
                Priority|P1                        |P3
--------------------------------------------------------------------------------




------- Additional comments from [hidden email] Thu Jul  9 18:41:05 +0000 2009 -------
By the nature of a TCP/IP connection, if one end really cuts the connection
without even sending TCP RESET packet, then the other end will have no clue what
happened.

But to cope with this situation, we should probably have master periodically
ping the slave.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]