I see. The problem definitively only happens with the "Windows server" launch method. JNLP agent is working well, even when installed as a service itself.
Am Samstag, 15. März 2014 08:27:06 UTC+1 schrieb Richard Bywater: > > I think Daniel is trying to help ascertain whether the problem is just > with the "Windows service" launch method or all the launch methods in a bid > to try and track down where the problem may lie. > > Richard. > > > On Sat, Mar 15, 2014 at 8:21 PM, Markus KARG > <mar...@headcrashing.eu<javascript:> > > wrote: > >> It is rather obvious that the message does not appear for JNLP slaves. >> But what does that help? I don't want to use JNLP. >> >> Am Samstag, 15. März 2014 01:11:10 UTC+1 schrieb Daniel Beck: >> >>> >>> On 14.03.2014, at 23:52, Markus KARG <mar...@headcrashing.eu> wrote: >>> >>> > at hudson.os.windows.ManagedWindowsServiceLauncher.launch( >>> ManagedWindowsServiceLauncher.java:233) >>> >>> Since this appears to go through 'Let Jenkins control this Windows slave >>> as a Windows service', what happens when you launch and control the slave >>> differently? >>> >>> -- >> 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 <javascript:>. >> 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. For more options, visit https://groups.google.com/d/optout.
