Oh here we go.... from the master log..

May 22, 2013 9:43:29 AM hudson.triggers.SCMTrigger$Runner run
INFO: SCM changes detected in HOS251Filter-main-line. Triggering #419
May 22, 2013 9:44:08 AM hudson.model.Run execute
INFO: HOS251Filter-main-line #419 main build action completed: SUCCESS
May 22, 2013 9:52:31 AM hudson.TcpSlaveAgentListener$ConnectionHandler run
INFO: Accepted connection #4 from /192.168.214.3:34640
May 22, 2013 9:52:31 AM jenkins.slaves.JnlpSlaveAgentProtocol$Handler error
WARNING: TCP slave agent connection handler #4 with /192.168.214.3:34640 is 
aborted: SRV-LJS-03 is already connected to this master. Rejecting this 
connection.
May 22, 2013 9:57:38 AM hudson.slaves.ChannelPinger$1 onDead
INFO: Ping failed. Terminating the channel.
java.util.concurrent.TimeoutException: Ping started on 1369212818723 hasn't 
completed at 1369213058726
at hudson.remoting.PingThread.ping(PingThread.java:120)
at hudson.remoting.PingThread.run(PingThread.java:81)
May 22, 2013 9:57:38 AM 
hudson.remoting.SynchronousCommandTransport$ReaderThread run
SEVERE: I/O error in channel SRV-LJS-03
java.net.SocketException: Socket closed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:146)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
at java.io.BufferedInputStream.read(BufferedInputStream.java:254)
at 
java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2290)
at 
java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2583)
at 
java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2593)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1315)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
at hudson.remoting.Command.readFrom(Command.java:92)
at 
hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59)
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
May 22, 2013 9:57:38 AM jenkins.slaves.JnlpSlaveAgentProtocol$Handler$1 
onClosed
WARNING: Channel reader thread: SRV-LJS-03 for + SRV-LJS-03 terminated
java.net.SocketException: Socket closed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:146)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
at java.io.BufferedInputStream.read(BufferedInputStream.java:254)
at 
java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2290)
at 
java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2583)
at 
java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2593)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1315)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
at hudson.remoting.Command.readFrom(Command.java:92)
at 
hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59)
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)




On Tuesday, 28 May 2013 15:33:53 UTC+1, Stuart Green wrote:
>
> Yes that's right.  I'd need to reboot it again whilst watching to be 
> absolutely sure of what the master is thinking.  Certainly it would be back 
> up within those 4 minutes though.
>
> I might have to go with something like you've made, either your approach 
> or maybe a massive sleep in the init script!  Cheers for the reply.
>
> Stu
>
> On Tuesday, 28 May 2013 15:27:02 UTC+1, Mandeville, Rob wrote:
>>
>>  So the server is complaining that it already has a server by that 
>> name.  When the slave job is down, does the Server still regard it as up?  
>> Maybe Jenkins hasn’t noticed yet (there’s a 4-minute “ping timeout” 
>> involved, so it might not have).
>>
>>  
>>
>> I have a cron job that runs every five minutes, looking for the slave job 
>> with the help of “ps”.  When it can’t find it, it fires off “nohup bash 
>> launchSlave.sh &”.  The launchSlave.sh job sets some environment variables 
>> and launches “java –jar slave.jar –jnlpUrl …”.
>>
>>  
>>
>> --Rob
>>
>>  
>>
>> *From:* [email protected] [mailto:[email protected]] 
>> *On Behalf Of *Stuart Green
>> *Sent:* Tuesday, May 28, 2013 10:03 AM
>> *To:* [email protected]
>> *Subject:* Jenkins Linux Slave fails to connect to Jenkins master - JLNP 
>> Java Web Start
>>
>>  
>>  
>> Hello..
>>  
>>  
>>  
>> This is getting to be a bit of a pain, it seems to happen every time we 
>> reboot the linux slave, but does not happen when we reboot the windows 
>> slave that we have. We are on Jenkins ver. 1.515 so the fix in 1.398(off 
>> the top of my head) is definitely there.
>>  
>>  
>>  
>>  
>>  
>> May 15, 2013 11:13:37 AM hudson.remoting.jnlp.Main$CuiListener status
>> INFO: Connected
>>
>> May 15, 2013 11:13:37 AM hudson.remoting.jnlp.Main$CuiListener status
>> INFO: Connected
>>
>> Session terminated, killing shell... ...killed.
>> Skipping HTTPS certificate checks altogether. Note that this is not 
>> secure at all.
>> May 22, 2013 9:52:30 AM hudson.remoting.jnlp.Main$CuiListener <init>
>> INFO: Jenkins agent is running in headless mode.
>> May 22, 2013 9:52:31 AM hudson.remoting.jnlp.Main$CuiListener status
>> INFO: Locating server among [https://jenkins.internal.ourserver.com/, 
>> http://jenkins.internal.ourserver.com/]
>> May 22, 2013 9:52:31 AM hudson.remoting.jnlp.Main$CuiListener status
>> INFO: Connecting to jenkins.internal.ourserver.com:8081
>> May 22, 2013 9:52:31 AM hudson.remoting.jnlp.Main$CuiListener status
>> INFO: Handshaking
>> May 22, 2013 9:52:31 AM hudson.remoting.jnlp.Main$CuiListener error
>> SEVERE: The server rejected the connection: SRV-LJS-03 is already 
>> connected to this master. Rejecting this connection.
>> java.lang.Exception: The server rejected the connection: SRV-LJS-03 is 
>> already connected to this master. Rejecting this connection.
>> at hudson.remoting.Engine.onConnectionRejected(Engine.java:257)
>> at hudson.remoting.Engine.run(Engine.java:232)
>>  
>>  
>>  
>> Then if I start it manually (when someone shouts) its fine.
>> Skipping HTTPS certificate checks altogether. Note that this is not 
>> secure at all.
>> May 28, 2013 2:17:10 PM hudson.remoting.jnlp.Main$CuiListener <init>
>> INFO: Jenkins agent is running in headless mode.
>> May 28, 2013 2:17:10 PM hudson.remoting.jnlp.Main$CuiListener status
>> INFO: Locating server among [https://jenkins.internal.ourserver.com/, 
>> http://jenkins.internal.ourserver.com/]
>> May 28, 2013 2:17:10 PM hudson.remoting.jnlp.Main$CuiListener status
>> INFO: Connecting to jenkins.internal.ourserver.com:8081
>> May 28, 2013 2:17:10 PM hudson.remoting.jnlp.Main$CuiListener status
>> INFO: Handshaking
>> May 28, 2013 2:17:10 PM hudson.remoting.jnlp.Main$CuiListener status
>> INFO: Connected
>>  
>>  
>>  
>>  
>>  
>> Is there anyone that is using the same method sucessfully able to advise 
>> on how they are doing it?
>>  
>>  
>>  
>> Thanks,
>>  
>> Stu
>>  
>> -- 
>> 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/groups/opt_out.
>>  
>>  
>>  The information in this message is for the intended recipient(s) only 
>> and may be the proprietary and/or confidential property of Litle & Co., 
>> LLC, and thus protected from disclosure. If you are not the intended 
>> recipient(s), or an employee or agent responsible for delivering this 
>> message to the intended recipient, you are hereby notified that any use, 
>> dissemination, distribution or copying of this communication is prohibited. 
>> If you have received this communication in error, please notify Litle & Co. 
>> immediately by replying to this message and then promptly deleting it and 
>> your reply permanently from your computer.
>>  
>

-- 
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/groups/opt_out.


Reply via email to