Re: Jenkins service going down on Windows Slave

2018-11-26 Thread gotviseryon 
Just found it.  In the Slave configuration section, below "Launch method" 
in "Advanced" there is a section called "JVM options".  We can pass it as a 
parameter here.  Need to test it and see if it works.

On Monday, November 26, 2018 at 4:33:11 PM UTC-5, slide wrote:
>
> There should be a way to pass parameters to the JVM in the .xml file 
> (slave.xml or something similar).
>
> On Mon, Nov 26, 2018 at 1:38 PM > wrote:
>
>> Found a log file on the slave machine.  It's Java heap size error.
>>
>> INFO: HttpClient configured for $URL, authenticating as USER
>> Nov 20, 2018 6:25:09 PM 
>> com.microsoft.tfs.core.ws.runtime.transport.IdleHTTPConnectionCloser run
>> SEVERE: unexpected error
>> java.lang.OutOfMemoryError: Java heap space
>> at java.util.Arrays.copyOf(Unknown Source)
>> at java.util.Arrays.copyOf(Unknown Source)
>> at java.util.ArrayList.grow(Unknown Source)
>> at java.util.ArrayList.ensureExplicitCapacity(Unknown Source)
>> at java.util.ArrayList.ensureCapacityInternal(Unknown Source)
>> at java.util.ArrayList.add(Unknown Source)
>> at 
>> com.microsoft.tfs.core.ws.runtime.transport.IdleHTTPConnectionCloser.run(IdleHTTPConnectionCloser.java:109)
>>
>> Nov 20, 2018 6:25:12 PM 
>> org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader run
>> SEVERE: [JNLP4-connect connection to JENKINS_URL/IP:35351] Reader thread 
>> killed by OutOfMemoryError
>> java.lang.OutOfMemoryError: Java heap space
>>
>> Exception in thread "pool-1-thread-3" java.lang.OutOfMemoryError: Java 
>> heap space
>> Nov 20, 2018 6:29:32 PM hudson.slaves.ChannelPinger$1 onDead
>> INFO: Ping failed. Terminating the channel JNLP4-connect connection to 
>> JENKINS_URL/IP:35351.
>> java.util.concurrent.TimeoutException: Ping started at 1542756332316 
>> hasn't completed by 1542756572331
>> at hudson.remoting.PingThread.ping(PingThread.java:134)
>> at hudson.remoting.PingThread.run(PingThread.java:90)
>>
>> Nov 20, 2018 6:34:32 PM hudson.slaves.ChannelPinger$1 onDead
>> INFO: Ping failed. Terminating the channel JNLP4-connect connection to 
>> JENKINS_URL/IP:35351.
>> java.util.concurrent.TimeoutException: Ping started at 1542756632868 
>> hasn't completed by 1542756872880
>> at hudson.remoting.PingThread.ping(PingThread.java:134)
>> at hudson.remoting.PingThread.run(PingThread.java:90)
>>
>> Nov 20, 2018 6:39:32 PM hudson.slaves.ChannelPinger$1 onDead
>> INFO: Ping failed. Terminating the channel JNLP4-connect connection to 
>> JENKINS_URL/IP:35351.
>> java.util.concurrent.TimeoutException: Ping started at 1542756932704 
>> hasn't completed by 1542757172726
>> at hudson.remoting.PingThread.ping(PingThread.java:134)
>> at hudson.remoting.PingThread.run(PingThread.java:90)
>>
>> Nov 20, 2018 8:38:34 PM hudson.remoting.jnlp.Main createEngine
>> INFO: Setting up agent: HOST_NAME
>> Nov 20, 2018 8:38:34 PM hudson.remoting.jnlp.Main$CuiListener 
>> INFO: Jenkins agent is running in headless mode.
>>
>> Trying to figure out way to increase the heap size.
>>
>> Thanks to all those threw in suggestion.
>>
>> On Monday, November 26, 2018 at 12:44:47 PM UTC-5, gotvi...@gmail.com 
>> wrote:
>>>
>>> The agent port is selected as 'fixed' in the Jenkins master 
>>> configuration.
>>>
>>> On Monday, November 26, 2018 at 12:33:43 PM UTC-5, Pranav Kv wrote:

 Did you checked your port number?My be it is an arbitrary selection. So 
 better to configure the port as fixed number on your master configuration.

 Regards
 Pranav

 On Mon, 26 Nov 2018, 10:52 pm >>>
> Any help/suggestion on this?
>
> On Monday, November 26, 2018 at 11:24:45 AM UTC-5, gotvi...@gmail.com 
> wrote:
>>
>> When I looked in Windows Server event logs, I see this error - 
>> sigint to 81192 failed - killing as feedback
>>
>> I see this message multiple times and the number (81192) is defferent 
>> in every error.
>>
>> On Monday, November 26, 2018 at 10:48:58 AM UTC-5, gotvi...@gmail.com 
>> wrote:
>>>
>>> We have couple of more Windows Slaves, but we don't have any issue 
>>> with those.  Just this one slave going down often.
>>>
>>> On Monday, November 26, 2018 at 10:21:14 AM UTC-5, john.mellor wrote:

 We have that problem all the time. IMHO the JNLP connectivity to 
 the master is not robust enough to be used.

 I have tried setting up the agent connection as a service per the 
 Jenkins doc, but it still cannot survive momentary network or 
 performance 
 outages. The only way that I have managed to get this machine 
 consistent, 
 is to reboot the Windows machine and the service will shortly 
 re-establish 
 connectivity. JNLP connections are just-plain defective.



 On Mon, 2018-11-26 at 07:06 -0800, gotvi...@gmail.com wrote:

 Hello, 

 We have a Windows Server 2016 Jenkins Slave.  The Jenkins service 
 i

Re: Jenkins service going down on Windows Slave

2018-11-26 Thread Slide 
There should be a way to pass parameters to the JVM in the .xml file
(slave.xml or something similar).

On Mon, Nov 26, 2018 at 1:38 PM  wrote:

> Found a log file on the slave machine.  It's Java heap size error.
>
> INFO: HttpClient configured for $URL, authenticating as USER
> Nov 20, 2018 6:25:09 PM
> com.microsoft.tfs.core.ws.runtime.transport.IdleHTTPConnectionCloser run
> SEVERE: unexpected error
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Unknown Source)
> at java.util.Arrays.copyOf(Unknown Source)
> at java.util.ArrayList.grow(Unknown Source)
> at java.util.ArrayList.ensureExplicitCapacity(Unknown Source)
> at java.util.ArrayList.ensureCapacityInternal(Unknown Source)
> at java.util.ArrayList.add(Unknown Source)
> at
> com.microsoft.tfs.core.ws.runtime.transport.IdleHTTPConnectionCloser.run(IdleHTTPConnectionCloser.java:109)
>
> Nov 20, 2018 6:25:12 PM
> org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader run
> SEVERE: [JNLP4-connect connection to JENKINS_URL/IP:35351] Reader thread
> killed by OutOfMemoryError
> java.lang.OutOfMemoryError: Java heap space
>
> Exception in thread "pool-1-thread-3" java.lang.OutOfMemoryError: Java
> heap space
> Nov 20, 2018 6:29:32 PM hudson.slaves.ChannelPinger$1 onDead
> INFO: Ping failed. Terminating the channel JNLP4-connect connection to
> JENKINS_URL/IP:35351.
> java.util.concurrent.TimeoutException: Ping started at 1542756332316
> hasn't completed by 1542756572331
> at hudson.remoting.PingThread.ping(PingThread.java:134)
> at hudson.remoting.PingThread.run(PingThread.java:90)
>
> Nov 20, 2018 6:34:32 PM hudson.slaves.ChannelPinger$1 onDead
> INFO: Ping failed. Terminating the channel JNLP4-connect connection to
> JENKINS_URL/IP:35351.
> java.util.concurrent.TimeoutException: Ping started at 1542756632868
> hasn't completed by 1542756872880
> at hudson.remoting.PingThread.ping(PingThread.java:134)
> at hudson.remoting.PingThread.run(PingThread.java:90)
>
> Nov 20, 2018 6:39:32 PM hudson.slaves.ChannelPinger$1 onDead
> INFO: Ping failed. Terminating the channel JNLP4-connect connection to
> JENKINS_URL/IP:35351.
> java.util.concurrent.TimeoutException: Ping started at 1542756932704
> hasn't completed by 1542757172726
> at hudson.remoting.PingThread.ping(PingThread.java:134)
> at hudson.remoting.PingThread.run(PingThread.java:90)
>
> Nov 20, 2018 8:38:34 PM hudson.remoting.jnlp.Main createEngine
> INFO: Setting up agent: HOST_NAME
> Nov 20, 2018 8:38:34 PM hudson.remoting.jnlp.Main$CuiListener 
> INFO: Jenkins agent is running in headless mode.
>
> Trying to figure out way to increase the heap size.
>
> Thanks to all those threw in suggestion.
>
> On Monday, November 26, 2018 at 12:44:47 PM UTC-5, gotvi...@gmail.com
> wrote:
>>
>> The agent port is selected as 'fixed' in the Jenkins master configuration.
>>
>> On Monday, November 26, 2018 at 12:33:43 PM UTC-5, Pranav Kv wrote:
>>>
>>> Did you checked your port number?My be it is an arbitrary selection. So
>>> better to configure the port as fixed number on your master configuration.
>>>
>>> Regards
>>> Pranav
>>>
>>> On Mon, 26 Nov 2018, 10:52 pm >>
 Any help/suggestion on this?

 On Monday, November 26, 2018 at 11:24:45 AM UTC-5, gotvi...@gmail.com
 wrote:
>
> When I looked in Windows Server event logs, I see this error -
> sigint to 81192 failed - killing as feedback
>
> I see this message multiple times and the number (81192) is defferent
> in every error.
>
> On Monday, November 26, 2018 at 10:48:58 AM UTC-5, gotvi...@gmail.com
> wrote:
>>
>> We have couple of more Windows Slaves, but we don't have any issue
>> with those.  Just this one slave going down often.
>>
>> On Monday, November 26, 2018 at 10:21:14 AM UTC-5, john.mellor wrote:
>>>
>>> We have that problem all the time. IMHO the JNLP connectivity to the
>>> master is not robust enough to be used.
>>>
>>> I have tried setting up the agent connection as a service per the
>>> Jenkins doc, but it still cannot survive momentary network or 
>>> performance
>>> outages. The only way that I have managed to get this machine 
>>> consistent,
>>> is to reboot the Windows machine and the service will shortly 
>>> re-establish
>>> connectivity. JNLP connections are just-plain defective.
>>>
>>>
>>>
>>> On Mon, 2018-11-26 at 07:06 -0800, gotvi...@gmail.com wrote:
>>>
>>> Hello,
>>>
>>> We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in
>>> this slave goes down at times.  We then go back and start it manually
>>> though the service is set to start automatically.  Need help figuring 
>>> out
>>> what's causing it to go down and why it isn't coming back online on its 
>>> own.
>>>
>>> --
 You received this message because you are subscribed to the Google
 Groups "Jenkins Users" group.
 To unsubscribe from this group and

Re: Jenkins service going down on Windows Slave

2018-11-26 Thread gotviseryon 
Found a log file on the slave machine.  It's Java heap size error.

INFO: HttpClient configured for $URL, authenticating as USER
Nov 20, 2018 6:25:09 PM 
com.microsoft.tfs.core.ws.runtime.transport.IdleHTTPConnectionCloser run
SEVERE: unexpected error
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Unknown Source)
at java.util.Arrays.copyOf(Unknown Source)
at java.util.ArrayList.grow(Unknown Source)
at java.util.ArrayList.ensureExplicitCapacity(Unknown Source)
at java.util.ArrayList.ensureCapacityInternal(Unknown Source)
at java.util.ArrayList.add(Unknown Source)
at 
com.microsoft.tfs.core.ws.runtime.transport.IdleHTTPConnectionCloser.run(IdleHTTPConnectionCloser.java:109)

Nov 20, 2018 6:25:12 PM 
org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader run
SEVERE: [JNLP4-connect connection to JENKINS_URL/IP:35351] Reader thread 
killed by OutOfMemoryError
java.lang.OutOfMemoryError: Java heap space

Exception in thread "pool-1-thread-3" java.lang.OutOfMemoryError: Java heap 
space
Nov 20, 2018 6:29:32 PM hudson.slaves.ChannelPinger$1 onDead
INFO: Ping failed. Terminating the channel JNLP4-connect connection to 
JENKINS_URL/IP:35351.
java.util.concurrent.TimeoutException: Ping started at 1542756332316 hasn't 
completed by 1542756572331
at hudson.remoting.PingThread.ping(PingThread.java:134)
at hudson.remoting.PingThread.run(PingThread.java:90)

Nov 20, 2018 6:34:32 PM hudson.slaves.ChannelPinger$1 onDead
INFO: Ping failed. Terminating the channel JNLP4-connect connection to 
JENKINS_URL/IP:35351.
java.util.concurrent.TimeoutException: Ping started at 1542756632868 hasn't 
completed by 1542756872880
at hudson.remoting.PingThread.ping(PingThread.java:134)
at hudson.remoting.PingThread.run(PingThread.java:90)

Nov 20, 2018 6:39:32 PM hudson.slaves.ChannelPinger$1 onDead
INFO: Ping failed. Terminating the channel JNLP4-connect connection to 
JENKINS_URL/IP:35351.
java.util.concurrent.TimeoutException: Ping started at 1542756932704 hasn't 
completed by 1542757172726
at hudson.remoting.PingThread.ping(PingThread.java:134)
at hudson.remoting.PingThread.run(PingThread.java:90)

Nov 20, 2018 8:38:34 PM hudson.remoting.jnlp.Main createEngine
INFO: Setting up agent: HOST_NAME
Nov 20, 2018 8:38:34 PM hudson.remoting.jnlp.Main$CuiListener 
INFO: Jenkins agent is running in headless mode.

Trying to figure out way to increase the heap size.

Thanks to all those threw in suggestion.

On Monday, November 26, 2018 at 12:44:47 PM UTC-5, gotvi...@gmail.com wrote:
>
> The agent port is selected as 'fixed' in the Jenkins master configuration.
>
> On Monday, November 26, 2018 at 12:33:43 PM UTC-5, Pranav Kv wrote:
>>
>> Did you checked your port number?My be it is an arbitrary selection. So 
>> better to configure the port as fixed number on your master configuration.
>>
>> Regards
>> Pranav
>>
>> On Mon, 26 Nov 2018, 10:52 pm >
>>> Any help/suggestion on this?
>>>
>>> On Monday, November 26, 2018 at 11:24:45 AM UTC-5, gotvi...@gmail.com 
>>> wrote:

 When I looked in Windows Server event logs, I see this error - 
 sigint to 81192 failed - killing as feedback

 I see this message multiple times and the number (81192) is defferent 
 in every error.

 On Monday, November 26, 2018 at 10:48:58 AM UTC-5, gotvi...@gmail.com 
 wrote:
>
> We have couple of more Windows Slaves, but we don't have any issue 
> with those.  Just this one slave going down often.
>
> On Monday, November 26, 2018 at 10:21:14 AM UTC-5, john.mellor wrote:
>>
>> We have that problem all the time. IMHO the JNLP connectivity to the 
>> master is not robust enough to be used.
>>
>> I have tried setting up the agent connection as a service per the 
>> Jenkins doc, but it still cannot survive momentary network or 
>> performance 
>> outages. The only way that I have managed to get this machine 
>> consistent, 
>> is to reboot the Windows machine and the service will shortly 
>> re-establish 
>> connectivity. JNLP connections are just-plain defective.
>>
>>
>>
>> On Mon, 2018-11-26 at 07:06 -0800, gotvi...@gmail.com wrote:
>>
>> Hello, 
>>
>> We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in 
>> this slave goes down at times.  We then go back and start it manually 
>> though the service is set to start automatically.  Need help figuring 
>> out 
>> what's causing it to go down and why it isn't coming back online on its 
>> own.
>>
>> -- 
>>> 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 jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/317ec954-f56e-4990-b183-55f1327aa9ae%40googlegroups.com
>>>  
>>>

Re: Jenkins service going down on Windows Slave

2018-11-26 Thread gotviseryon 
The agent port is selected as 'fixed' in the Jenkins master configuration.

On Monday, November 26, 2018 at 12:33:43 PM UTC-5, Pranav Kv wrote:
>
> Did you checked your port number?My be it is an arbitrary selection. So 
> better to configure the port as fixed number on your master configuration.
>
> Regards
> Pranav
>
> On Mon, 26 Nov 2018, 10:52 pm  wrote:
>
>> Any help/suggestion on this?
>>
>> On Monday, November 26, 2018 at 11:24:45 AM UTC-5, gotvi...@gmail.com 
>> wrote:
>>>
>>> When I looked in Windows Server event logs, I see this error - 
>>> sigint to 81192 failed - killing as feedback
>>>
>>> I see this message multiple times and the number (81192) is defferent in 
>>> every error.
>>>
>>> On Monday, November 26, 2018 at 10:48:58 AM UTC-5, gotvi...@gmail.com 
>>> wrote:

 We have couple of more Windows Slaves, but we don't have any issue with 
 those.  Just this one slave going down often.

 On Monday, November 26, 2018 at 10:21:14 AM UTC-5, john.mellor wrote:
>
> We have that problem all the time. IMHO the JNLP connectivity to the 
> master is not robust enough to be used.
>
> I have tried setting up the agent connection as a service per the 
> Jenkins doc, but it still cannot survive momentary network or performance 
> outages. The only way that I have managed to get this machine consistent, 
> is to reboot the Windows machine and the service will shortly 
> re-establish 
> connectivity. JNLP connections are just-plain defective.
>
>
>
> On Mon, 2018-11-26 at 07:06 -0800, gotvi...@gmail.com wrote:
>
> Hello, 
>
> We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in 
> this slave goes down at times.  We then go back and start it manually 
> though the service is set to start automatically.  Need help figuring out 
> what's causing it to go down and why it isn't coming back online on its 
> own.
>
> -- 
>> 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 jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/317ec954-f56e-4990-b183-55f1327aa9ae%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/7e622ae9-df97-4d9a-a8d1-9d65cd5d8ad5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins service going down on Windows Slave

2018-11-26 Thread Pranav Kv 
Did you checked your port number?My be it is an arbitrary selection. So
better to configure the port as fixed number on your master configuration.

Regards
Pranav

On Mon, 26 Nov 2018, 10:52 pm  Any help/suggestion on this?
>
> On Monday, November 26, 2018 at 11:24:45 AM UTC-5, gotvi...@gmail.com
> wrote:
>>
>> When I looked in Windows Server event logs, I see this error -
>> sigint to 81192 failed - killing as feedback
>>
>> I see this message multiple times and the number (81192) is defferent in
>> every error.
>>
>> On Monday, November 26, 2018 at 10:48:58 AM UTC-5, gotvi...@gmail.com
>> wrote:
>>>
>>> We have couple of more Windows Slaves, but we don't have any issue with
>>> those.  Just this one slave going down often.
>>>
>>> On Monday, November 26, 2018 at 10:21:14 AM UTC-5, john.mellor wrote:

 We have that problem all the time. IMHO the JNLP connectivity to the
 master is not robust enough to be used.

 I have tried setting up the agent connection as a service per the
 Jenkins doc, but it still cannot survive momentary network or performance
 outages. The only way that I have managed to get this machine consistent,
 is to reboot the Windows machine and the service will shortly re-establish
 connectivity. JNLP connections are just-plain defective.



 On Mon, 2018-11-26 at 07:06 -0800, gotvi...@gmail.com wrote:

 Hello,

 We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in
 this slave goes down at times.  We then go back and start it manually
 though the service is set to start automatically.  Need help figuring out
 what's causing it to go down and why it isn't coming back online on its 
 own.

 --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/317ec954-f56e-4990-b183-55f1327aa9ae%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAHwQEkKzS4VBF3LrYAXhKpE2v%2BVM86%3DqnWgxKsyFQQ47ih0f1w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins service going down on Windows Slave

2018-11-26 Thread gotviseryon 
Any help/suggestion on this?

On Monday, November 26, 2018 at 11:24:45 AM UTC-5, gotvi...@gmail.com wrote:
>
> When I looked in Windows Server event logs, I see this error - 
> sigint to 81192 failed - killing as feedback
>
> I see this message multiple times and the number (81192) is defferent in 
> every error.
>
> On Monday, November 26, 2018 at 10:48:58 AM UTC-5, gotvi...@gmail.com 
> wrote:
>>
>> We have couple of more Windows Slaves, but we don't have any issue with 
>> those.  Just this one slave going down often.
>>
>> On Monday, November 26, 2018 at 10:21:14 AM UTC-5, john.mellor wrote:
>>>
>>> We have that problem all the time. IMHO the JNLP connectivity to the 
>>> master is not robust enough to be used.
>>>
>>> I have tried setting up the agent connection as a service per the 
>>> Jenkins doc, but it still cannot survive momentary network or performance 
>>> outages. The only way that I have managed to get this machine consistent, 
>>> is to reboot the Windows machine and the service will shortly re-establish 
>>> connectivity. JNLP connections are just-plain defective.
>>>
>>>
>>>
>>> On Mon, 2018-11-26 at 07:06 -0800, gotvi...@gmail.com wrote:
>>>
>>> Hello, 
>>>
>>> We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in 
>>> this slave goes down at times.  We then go back and start it manually 
>>> though the service is set to start automatically.  Need help figuring out 
>>> what's causing it to go down and why it isn't coming back online on its own.
>>>
>>>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/317ec954-f56e-4990-b183-55f1327aa9ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins service going down on Windows Slave

2018-11-26 Thread gotviseryon 
When I looked in Windows Server event logs, I see this error - 
sigint to 81192 failed - killing as feedback

I see this message multiple times and the number (81192) is defferent in 
every error.

On Monday, November 26, 2018 at 10:48:58 AM UTC-5, gotvi...@gmail.com wrote:
>
> We have couple of more Windows Slaves, but we don't have any issue with 
> those.  Just this one slave going down often.
>
> On Monday, November 26, 2018 at 10:21:14 AM UTC-5, john.mellor wrote:
>>
>> We have that problem all the time. IMHO the JNLP connectivity to the 
>> master is not robust enough to be used.
>>
>> I have tried setting up the agent connection as a service per the Jenkins 
>> doc, but it still cannot survive momentary network or performance outages. 
>> The only way that I have managed to get this machine consistent, is to 
>> reboot the Windows machine and the service will shortly re-establish 
>> connectivity. JNLP connections are just-plain defective.
>>
>>
>>
>> On Mon, 2018-11-26 at 07:06 -0800, gotvi...@gmail.com wrote:
>>
>> Hello, 
>>
>> We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in this 
>> slave goes down at times.  We then go back and start it manually though the 
>> service is set to start automatically.  Need help figuring out what's 
>> causing it to go down and why it isn't coming back online on its own.
>>
>>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8e3018ab-b95d-47f0-9433-24ac44861005%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins service going down on Windows Slave

2018-11-26 Thread gotviseryon 
We have couple of more Windows Slaves, but we don't have any issue with 
those.  Just this one slave going down often.

On Monday, November 26, 2018 at 10:21:14 AM UTC-5, john.mellor wrote:
>
> We have that problem all the time. IMHO the JNLP connectivity to the 
> master is not robust enough to be used.
>
> I have tried setting up the agent connection as a service per the Jenkins 
> doc, but it still cannot survive momentary network or performance outages. 
> The only way that I have managed to get this machine consistent, is to 
> reboot the Windows machine and the service will shortly re-establish 
> connectivity. JNLP connections are just-plain defective.
>
>
>
> On Mon, 2018-11-26 at 07:06 -0800, gotvi...@gmail.com  wrote:
>
> Hello, 
>
> We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in this 
> slave goes down at times.  We then go back and start it manually though the 
> service is set to start automatically.  Need help figuring out what's 
> causing it to go down and why it isn't coming back online on its own.
>
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b4d92c64-a769-42c0-90d4-e9df7e1210d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins service going down on Windows Slave

2018-11-26 Thread gotviseryon 
Any idea on where else I can look for details?

On Monday, November 26, 2018 at 10:24:10 AM UTC-5, slide wrote:
>
> Weird, I have had ZERO issues with JNLP agents. It works flawlessly for me.
>
> On Mon, Nov 26, 2018 at 8:21 AM John Mellor  > wrote:
>
>> We have that problem all the time. IMHO the JNLP connectivity to the 
>> master is not robust enough to be used.
>>
>> I have tried setting up the agent connection as a service per the Jenkins 
>> doc, but it still cannot survive momentary network or performance outages. 
>> The only way that I have managed to get this machine consistent, is to 
>> reboot the Windows machine and the service will shortly re-establish 
>> connectivity. JNLP connections are just-plain defective.
>>
>>
>>
>> On Mon, 2018-11-26 at 07:06 -0800, gotvi...@gmail.com  
>> wrote:
>>
>> Hello, 
>>
>> We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in this 
>> slave goes down at times.  We then go back and start it manually though the 
>> service is set to start automatically.  Need help figuring out what's 
>> causing it to go down and why it isn't coming back online on its own.
>>
>> -- 
>> 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 jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/0643151142ab642b3a0117ea0b42ab1e41ccfda3.camel%40esentire.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> Website: http://earl-of-code.com
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/cc698142-b557-4ce9-ac69-8aa85a7ed476%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins service going down on Windows Slave

2018-11-26 Thread John Mellor 
Hi Slide,

We run our worker nodes mostly on sometimes-overloaded VMware hosts. We also 
interrupt the undersized network fairly routinely, for other reasons. Can you 
try hooking in a network degradation service, so that you see network outages, 
for instance.

JNLP connections fail in these circumstances, while ssh connections do not. 
Unfortunately, Windows essentially requires JNLP-only connections.



On Mon, 2018-11-26 at 08:23 -0700, Slide wrote:
Weird, I have had ZERO issues with JNLP agents. It works flawlessly for me.

On Mon, Nov 26, 2018 at 8:21 AM John Mellor 
mailto:john.mel...@esentire.com>> wrote:
We have that problem all the time. IMHO the JNLP connectivity to the master is 
not robust enough to be used.

I have tried setting up the agent connection as a service per the Jenkins doc, 
but it still cannot survive momentary network or performance outages. The only 
way that I have managed to get this machine consistent, is to reboot the 
Windows machine and the service will shortly re-establish connectivity. JNLP 
connections are just-plain defective.



On Mon, 2018-11-26 at 07:06 -0800, 
gotviser...@gmail.com wrote:
Hello,

We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in this slave 
goes down at times.  We then go back and start it manually though the service 
is set to start automatically.  Need help figuring out what's causing it to go 
down and why it isn't coming back online on its own.

--
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 
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0643151142ab642b3a0117ea0b42ab1e41ccfda3.camel%40esentire.com.
For more options, visit https://groups.google.com/d/optout.


--
Website: http://earl-of-code.com

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/94638a861184c792de1d164a7b17eef0fa402b41.camel%40esentire.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins service going down on Windows Slave

2018-11-26 Thread Slide 
Weird, I have had ZERO issues with JNLP agents. It works flawlessly for me.

On Mon, Nov 26, 2018 at 8:21 AM John Mellor 
wrote:

> We have that problem all the time. IMHO the JNLP connectivity to the
> master is not robust enough to be used.
>
> I have tried setting up the agent connection as a service per the Jenkins
> doc, but it still cannot survive momentary network or performance outages.
> The only way that I have managed to get this machine consistent, is to
> reboot the Windows machine and the service will shortly re-establish
> connectivity. JNLP connections are just-plain defective.
>
>
>
> On Mon, 2018-11-26 at 07:06 -0800, gotviser...@gmail.com wrote:
>
> Hello,
>
> We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in this
> slave goes down at times.  We then go back and start it manually though the
> service is set to start automatically.  Need help figuring out what's
> causing it to go down and why it isn't coming back online on its own.
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/0643151142ab642b3a0117ea0b42ab1e41ccfda3.camel%40esentire.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Website: http://earl-of-code.com

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVc-xHbnxYWjnpScOZWxOb8Y2qc0TduQ%3DK%2B%3DNskehQZZ2A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins service going down on Windows Slave

2018-11-26 Thread gotviseryon 
This is all I see in the log section of the Slave.  Is there anywhere else 
to see?

JNLP agent connected from IP/IP
Remoting version: 3.17
This is a Windows agent
Agent successfully connected and online




On Monday, November 26, 2018 at 10:16:59 AM UTC-5, slide wrote:
>
> Did you check the logs on the agent or via the Jenkins UI? (FYI, agent is 
> the preferred term instead of "slave").
>
> On Mon, Nov 26, 2018 at 8:06 AM > wrote:
>
>> Hello,
>>
>> We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in this 
>> slave goes down at times.  We then go back and start it manually though the 
>> service is set to start automatically.  Need help figuring out what's 
>> causing it to go down and why it isn't coming back online on its own.
>>
>> -- 
>> 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 jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/fd7cf10d-fd69-4c20-be36-804f6256890a%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> Website: http://earl-of-code.com
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/580f8ba5-1b81-4198-9335-034964390f63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins service going down on Windows Slave

2018-11-26 Thread John Mellor 
We have that problem all the time. IMHO the JNLP connectivity to the master is 
not robust enough to be used.

I have tried setting up the agent connection as a service per the Jenkins doc, 
but it still cannot survive momentary network or performance outages. The only 
way that I have managed to get this machine consistent, is to reboot the 
Windows machine and the service will shortly re-establish connectivity. JNLP 
connections are just-plain defective.



On Mon, 2018-11-26 at 07:06 -0800, gotviser...@gmail.com wrote:
Hello,

We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in this slave 
goes down at times.  We then go back and start it manually though the service 
is set to start automatically.  Need help figuring out what's causing it to go 
down and why it isn't coming back online on its own.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0643151142ab642b3a0117ea0b42ab1e41ccfda3.camel%40esentire.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins service going down on Windows Slave

2018-11-26 Thread Slide 
Did you check the logs on the agent or via the Jenkins UI? (FYI, agent is
the preferred term instead of "slave").

On Mon, Nov 26, 2018 at 8:06 AM  wrote:

> Hello,
>
> We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in this
> slave goes down at times.  We then go back and start it manually though the
> service is set to start automatically.  Need help figuring out what's
> causing it to go down and why it isn't coming back online on its own.
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/fd7cf10d-fd69-4c20-be36-804f6256890a%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Website: http://earl-of-code.com

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVe6keqT58yMu%3Da10FiWUQOwKxDakWbNNg0%3DL-hA_tBfPg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.