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
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:
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
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.
>
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
>
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
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 mo
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
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
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 circu
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 se
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
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 g
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 i
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
15 matches
Mail list logo
