Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Not A Defect
-
Component/s: windows-slave-installer-module
-
Labels:None
-
Environment:WindowsXP 32 bit.
-
Similar Issues:
Description
I want to install a slave service on a Windows machine. I start the slave using the launch button on the Web page. This works fine. I then select Rile/Install as Windows Service on the slave pop-up, and click OK. This results in a large stack trace (unfortunately not in a window with copy and paste) starting with:
java.io.FileNotFoundException: c:\JenkinsTest\jenkins-slave.exe (The process cannot access the file because it is being used by another process)
Attachments
Activity
moved to master-slave component
The error means there is already a service running in the directory. If there is an issue, it needs to be retested and reconfirmed after 5 years. Please reopen the ticket if it still happens
Just for future and not search after obvious things. I have reproduced that case.
Steps to reproduce:
- master1 UI > Manage Jenkins > Manage Nodes
- add new node
- connect your agent1 to master1 via jnlp
- install connection as a service
- master2 UI > Manage Jenkins > Manage Nodes
- add new node
- connect your agent1 to master2 via jnlp
- try to install connection as a service
Effect:
Popup with statement as in description:
java.io.FileNotFoundException: c:\JenkinsTest\jenkins-slave.exe (The process cannot access the file because it is being used by another process)
To cross check that service is running execute from cmd:
c:\JenkinsTest\jenkins-slave.exe status
Resolution:
Choose which master should utilize that agent and use another agent for another master
There seems to be something slightly random about the behaviour. I have tried this a few more times on the same machine, and it occasionally works. It also worked on a different machine.