Am Using Jenkins, where so many windows machine i have integrated,but at the same all the windows machine got disconnected could not able to launch slave in windows machine,tried all possibilities like
1) slave.jar version upgrade
2)Java_home_path changes
but my doubt is with port, am getting error while launching that slave as follows
enter image description here
So how to connect windows slave , Hope it may be the issue with port connection.TCP port 443 used but getting error. Please suggest good idea.
Related
I am running docker on windows. But I am getting this error:
17:07:22 ---> Running in 8c6a46bbe049
17:07:33 container 8c6a46bbe049260df0ef60b165bd7929a2d8368dcb2baa3cffc7434175a2f811 encountered an error during CreateContainer: failure in a Windows system call: winapi error #2147749890 (0x80041002) extra info: {"SystemType":"Container","Name":"8c6a46bbe049260df0ef60b165bd7929a2d8368dcb2baa3cffc7434175a2f811","Owner":"docker","IsDummy":false,"VolumePath":"\\\\?\\Volume{885e371e-7607-11e9-a9ef-00155de60a79}","IgnoreFlushesDuringBoot":true,"LayerFolderPath":"C:\\ProgramData\\docker\\windowsfilter\\8c6a46bbe049260df0ef60b165bd7929a2d8368dcb2baa3cffc7434175a2f811","Layers":[{"ID":"70d02c58-59c2-5c57-832b-040fbae4082d","Path":"C:\\ProgramData\\docker\\windowsfilter\\3f3b1333b3e56c53c9cdedab9c4ec0e536b923e35c4cfbb64d68d775f7e189ab"},{"ID":"f2b424b8-a849-53e1-9257-7e17fcf4a3fa","Path":"C:\\ProgramData\\docker\\windowsfilter\\874be3b3d29cd1420a8799b482648281a5a04a4604b6f955b305f16c5ffd87db"},{"ID":"865b0b0c-60dc-5052-9af1-6f48b0081b58","Path":"C:\\ProgramData\\docker\\windowsfilter\\ca13b9af8dcc734a0b7dab288ff35a9de9e0b1831122d80315038a368e4be979"},{"ID":"e027a8bd-497f-51a0-bba6-56de6579fd8c","Path":"C:\\ProgramData\\docker\\windowsfilter\\9b2b43be7ff215bea3764306e1d8bbc5a2663c418b5af5643cf720b3604e1909"},{"ID":"754b58d8-c4c4-526a-84df-17b6113fd181","Path":"C:\\ProgramData\\docker\\windowsfilter\\47284b3fd596123a45b89439805ba7f38a7900b1bd67696fafc508f247ca8879"},{"ID":"170bb839-9260-50cf-9f16-2d104a0a41a0","Path":"C:\\ProgramData\\docker\\windowsfilter\\963bfd0727440da144ef3634b9201cf122704bf6171b2306a513c8cc9ca1bd7b"},{"ID":"a3fb6aee-3e04-54c1-8e5b-e665ee073dfe","Path":"C:\\ProgramData\\docker\\windowsfilter\\1daa28b5b08959c93789085549c21165ae66eaebb21092c6019d04939b544085"},{"ID":"a4b61e7f-94cc-5174-95cf-cd5840cd0a92","Path":"C:\\ProgramData\\docker\\windowsfilter\\c81fd28ba0796e1447eee305a9c05f088a0b3ef7920d5fb20b44399fbe584079"},{"ID":"ac5b7f9d-6b96-56fb-93b8-276e30c421ed","Path":"C:\\ProgramData\\docker\\windowsfilter\\58c0426733a33c783f6e3c359c83a63fb31c00fe629bb82764d6a1871b5ac433"},{"ID":"1cd2b979-13de-5fdd-a19b-d33d85fb14eb","Path":"C:\\ProgramData\\docker\\windowsfilter\\5eae35195cd3f58f2d02312aa5df2fec6f87cedf57f41554b625ddac21dddf66"},{"ID":"bee4c6c2-fda9-53d1-97a2-730790e98655","Path":"C:\\ProgramData\\docker\\windowsfilter\\54e2d38e2056906db9e434c33c546a0e536a29a545fe98406be4c1836d90887d"},{"ID":"d30d22d3-5197-555b-928c-d0f2f2099a61","Path":"C:\\ProgramData\\docker\\windowsfilter\\21c171679948030094aa20ecc6c9cf02ea0cc6b438f9a0fde0eb1f76e057d825"}],"HostName":"28224361016f","MappedDirectories":[],"HvPartition":false,"EndpointList":["6864626d-9cdf-4e21-9a34-2ae818f2e8f5"],"Servicing":false,"AllowUnqualifiedDNSQuery":true}
17:07:33 Build step 'Execute shell' marked build as failure
Unfortanely, as soon as I get this error, I am not able to RDP to the remote windows machine anymore ( it's on aws ). So I am not able to investigate further by doing RDP.
[ FYI, my jenkins master is running docker commands on this windows container/slave via SSH ].
Any help/hint will be appreciated here.
I can still run some commands via ssh on the machine if some information needed.
Maybe the two events "not able to RDP" and "the docker error" are somehow connected. But I don't know how.
The docker machine keeps working fine. RDP also works fine in the beginning. But sometime after connecting it as a slave ( and running docker commands via ssh ), RDP stops working.
It turns out the my problem was occuring due to some cleanup utility deleting up the system files required for mstsc ( and also required for docker ).
Everything started working fine after I switched off the cleanup utility.
Thanks for the help though.
I am trying to document my React Components and I am running styleguidist server along side with Laravel development server but the styleguidist server crashes with this error.
You have another server running at port 6060 somewhere, shut it down first
You can change the port using the `serverPort` option in your style guide config:
https://react-styleguidist.js.org/docs/configuration.html
I have configured the styleguidist server to run at port 6060 as to resolve this issue and succeeded to run the server only once. After that I am getting this issue again.
How can i resolve this??
The error is saying you have something else running at that port. Have you tried a different one? If you are running a UNIX system, you can see what is running on that port with:
lsof -i tcp:6060
We have a Jenkins instance running on Ubuntu that has several slaves in different systems. One of them is a Windows 7 host, having jenkins slave instance configured as a service.
We have a problem that when that machine is rebooted, master Jenkins doesn't realize it's gone. It looks to be just fine in the nodes view. Then, when a build is issued that is supposed to use that slave it gets stuck. If that is stopped, the next build fails immediately
Caused by: java.util.concurrent.TimeoutException: Ping started at 1457016721684 hasn't completed by 1457016961684
... 2 more
[EnvInject] - [ERROR] - SEVERE ERROR occurs: channel is already closed
When the slave has started up and it tries to connect back to master, connection is refused, and in the logs there is an error saying connection with that name already exists:
Server didn't accept the handshake: xxx is already connected to this master. Rejecting this connection.
There is issue JENKINS-5055 which claims a fix was committed allowing the same JNLP slave to reconnect without getting rejected, apparently this commit, and according to changelog, it was introduced in version 1.396 (2011/02/02). We are however using version 1.639 and seeing this. Somebody else seems to be seeing it as well. By looking at current codebase, I see where the error is coming from, but don't see the fix done in Jenkins-5055.
Any ideas on resolving this?
Edit: also asked on jenkins user mailing list, but no responses.
We faced the same issue. Used https://wiki.jenkins-ci.org/display/JENKINS/slave-status as workaround
Reinstalling the slave on a Windows Server 2012 R2 machine shows no signs of this behavior, so it seems that either there was a mistake done during installation steps or this is something caused by using a workstation Windows version.
Regardless, here were the steps to get it working, assuming a brand new installation of Windows, with no network connectivity, and master instance using a self-signed certificate:
Install JRE on the machine. If you have 64-bit operating system, install both 32-bit and 64-bit, otherwise go with 32-bit. Download link here
Install .NET 3.5 on the machine. This is needed by the Jenkins service. You can follow the steps outlined by my other answer for this.
Install Jenkins using Windows installer (.zipped) to C:\Jenkins. It can be downloaded from here.
Check your installation is responding by navigating to http://localhost:8080 . In case of trouble, check for logs in the jenkins folder. If there is a port conflict, edit jenkins.xml and change the httpPort to something else.
From the Windows computer, navigate to your master jenkins and configure a new node there.
Start a slave agent using Java Launch Agent in configure -> node screen (you need to be still using your Windows slave computer)
You should see a visible window opening. From there, select File -> Install as a service. (details and screenshots) If you experience an error without proper explanation, confirm .NET 3.5 is properly installed. If you see "WMI.WmiException: AccessDenied", save the jnlp file locally and start it from administrator prompt or otherwise with elevated privileges (details).
From the Administrative tools -> Services, stop and disable the Jenkins service, and stop Jenkins Slave Agent but leave it on Automatic so it will start up when starting up the computer.
This is only relevant if you're using a self-signed or otherwise problematic certificate:
download the previously mentioned Java Launch Agent file (.jnlp file) again and save it to C:\jenkins
open c:\jenkins\jenkins-slave.xml to your editor
change it to refer to your local .jnlp file by changing jnlp url parameter (file:/C:/jenkins/jenkins-slave.jnlp)
add -noCertificateCheck to parameters
replace the -secret parameter with -auth "user:pass", since otherwise automatic url get parameters will be added which will mess finding the .jnlp file
Start the Jenkins Slave Agent service again
For problems with jenkins slave service, check out jenkins-slave.err.log. For Windows Server 2012 R2, you can get the functionality of tail by using Get-Content .\jenkins-slave.err.log -Wait -Tail 10 in Powershell prompt. For older versions of Powershell, leave out -Tail 10.
Texte d'origine Ecoutez le texte source
Hi
Please, can you give me your opinions about this subject :
1.I have instaled Jenkins on VM Linux Centos
2.I have installed Jenkins on VM Windows 7 which contains the project Java Maven.
3.I shared the project from VM Windows 7 to VM Linux Centos and I succed to the project from my VM Linux
My goal is to make Jenkins Master on VM linux and Jenkins slave on VM Windows.
What I should do for creating the communication between all jenkins.
Thanks in Advance.
Best Regards,
Two ways of making a Windows slave (after defining nodes on master), on Windows server:
-browse to Jenkins node listing and launch web agent (Java Web Start) which has to be done manually each time the server starts up
-after starting the agent, register the slave as a service
Plenty of documentation, I found this just now.
Definitely prefer a service you don't have to worry about the web agent dying for some unknown reason and no one noticing, much better to have it auto start.
I have a Jenkins server running happily on a Windows server. I need to connect 2 other windows servers as slaves.
One connects in fine (start using JNLP, then installed as a Windows service).
The other fails to connect using JNLP. Whether I use the Launch button or the javaws command line it fails with 'Unexpected Error - Unable to launch Slave Agent for {node}'. If I start the slave using the headless command line it works, so I suspect it's not networking/firewall related.
I'd like to get the JNLP launch working so I can install it as a Windows service.
Other notes:
the Jenkins URL is set OK
we're using Matrix security, but anonymous has Slave/Connect
Any help gratefully received.