![]() |
|
|
|
|
Issue Type:
|
Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Unassigned |
|
Components:
|
core |
|
Created:
|
10/Jun/14 10:18 AM
|
|
Description:
|
It seems that when we manually restart a jenkins slave agent running on a windows client, a bunch of our other slaves were marked as permanently offline by jenkins (master).
Potentially we had mixed slave versions (2.33 + 2.42) if that's relevant ? (Notably clients running a 2.14 as a service appear un-affected ?)
The system log contained the following errors after we manually restarted the jenkins slave on DEV-CI-SE-16:
|
|
Environment:
|
On Windows, for jenkins the last known point where we know this not to be a problem is 1.544, but recent builds such as 1.566 demonstrate this fault.
|
|
Project:
|
Jenkins
|
|
Priority:
|
Major
|
|
Reporter:
|
ciaranj
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" 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/d/optout.